WO2022183453A1 - 一种通信方法、装置及芯片 - Google Patents

一种通信方法、装置及芯片 Download PDF

Info

Publication number
WO2022183453A1
WO2022183453A1 PCT/CN2021/079162 CN2021079162W WO2022183453A1 WO 2022183453 A1 WO2022183453 A1 WO 2022183453A1 CN 2021079162 W CN2021079162 W CN 2021079162W WO 2022183453 A1 WO2022183453 A1 WO 2022183453A1
Authority
WO
WIPO (PCT)
Prior art keywords
eth
link
trunk group
pdu session
members
Prior art date
Application number
PCT/CN2021/079162
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 华为技术有限公司
Priority to PCT/CN2021/079162 priority Critical patent/WO2022183453A1/zh
Priority to CN202180094529.2A priority patent/CN116965002A/zh
Publication of WO2022183453A1 publication Critical patent/WO2022183453A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • H04L45/7453—Address table lookup; Address filtering using hashing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a communication method, device and chip.
  • a single node of the terminal device is connected to the network, and a single link is connected between the terminal device and the data network (DN). If the terminal device fails, or any link between the terminal device and the DN fails, the network is connected. failure, resulting in a failure of business communication.
  • the 3rd generation partnership project defines a multi-link communication method.
  • the terminal The device accesses the DN through the active and standby links.
  • the terminal device accesses the DN through the access network device 1 and the user plane NE 1
  • the terminal device accesses the DN through the access network device 2 and the user plane NE 2 DN.
  • the terminal device needs to support two protocol data unit (protocol data unit, PDU) sessions, and the network side configures the dual connection mode of the PDU session.
  • PDU protocol data unit
  • the sending end sends data packets to the receiving end through the access network device 1 and the user plane network element 1, and the sending end sends the data packets to the receiving end through the access network device 2 and the user plane network element 2.
  • the receiving end sends data packets, and the receiving end deduplicates the two received data packets. In this way, if a link between the terminal device and the DN fails, the terminal device and the DN perform normal service communication through another link.
  • the terminal device needs to establish two PDU sessions, and each PDU session is bound to a "slice + data network name (DNN)" combination, which wastes slice and DNN resources.
  • DNN data network name
  • Embodiments of the present application provide a communication method, device, and chip, so as to save slice and DNN resources, and it is not necessary to improve the network side.
  • a communication method including the following process: a first device obtains link states of multiple members, each member corresponds to a protocol data unit PDU session, and the multiple members belong to an Eth-Trunk group; The first device selects a target member according to link states of the multiple members, and sends a first data packet of a PDU session corresponding to the target member. Wherein, the first device is the sender.
  • the first device may be any one of a user plane network element, an end-side device (such as a switching device/terminal device), or a session management network element.
  • multiple links are deployed between the sender and the receiver, and the links are the links of members in the Eth-Trunk group.
  • the sender selects the target member and the target member according to the link status of the multiple links.
  • the link of the target member is used as the active link for business communication. That is to say, one link can be used for service communication, without occupying too many slices and DNN resources, and it is not necessary to modify the network side, which can reduce the requirements on the network side.
  • the target member is selected through the link state, which can avoid the influence on the service communication when the link fails, and ensure the normal service communication.
  • the link status may be used to indicate that the member's link is the primary link or the backup link, and/or the link status may be used to indicate whether the member's link is faulty.
  • the first device may preferentially select a main link with a high priority and/or a non-faulty link, thereby improving the reliability of service communication.
  • the first device when selecting a target member according to the link states of the multiple members, may use a hash algorithm according to the link states of the multiple members to Select the target member from among the above-mentioned members.
  • the Hash value may correspond to the outgoing interface
  • the first device can calculate the target outgoing interface through the Hash algorithm according to the link states of multiple members, so as to select the target member and the link of the target member according to the outgoing interface.
  • the first device may be a user plane network element, for example, the first device is a first user plane network element.
  • the first user plane network element may also receive a first message, where the first message is used to establish a first PDU session, and the first message includes the data of the Eth-Trunk group.
  • the information of the Eth-Trunk group includes the attributes of the Eth-Trunk group; the first user plane network element establishes a first PDU session according to the first message; if the attributes of the first PDU session are the same as The attributes of the Eth-Trunk group match, and the first user plane network element adds a member corresponding to the first PDU session in the Eth-Trunk group.
  • the user plane network element can maintain the information of the Eth-Trunk group.
  • the information of the Eth-Trunk group further includes the member's link detection type, wherein the member's link detection type includes link aggregation control protocol LACP detection, or bidirectional forwarding detection BFD detection, Or combined detection of LACP and BFD. Therefore, the first device may also detect the link state of the member corresponding to the first PDU session according to the link detection type of the member.
  • the LACP/BFD protocol can be implemented on the first device, so as to detect the link state of the member, and avoid the influence on the service communication when the link fails.
  • the information of the Eth-Trunk group may also include one or more of the following: the identity of the Eth-Trunk group, the link type of the members, the maximum number of links in the Eth-Trunk group, and the minimum chain in the Eth-Trunk group The number of lanes and the link priority in the Eth-Trunk group.
  • the first device may periodically acquire link states of multiple members. In this implementation, the first device obtains the link status of the member periodically, thereby further improving the reliability of service communication.
  • the first device may be a user plane network element, for example, the first device is a first user plane network element.
  • the first user plane network element may release the PDU session corresponding to the first member, or the first user plane network element may release the PDU session corresponding to the first member.
  • the PDU session corresponding to the first member may be retained, and the abnormal state of the PDU session corresponding to the first member may be recorded.
  • the first member is any one of the multiple members. In this way, the user plane network element can maintain the state of the PDU session, thereby further improving the reliability of service communication.
  • the first device may be a user plane network element, for example, the first device is a first user plane network element.
  • the first data packet may include information for indicating that the first data packet is from the second member.
  • the first user plane network element may The link status of the member, among the members in other Eth-Trunk groups except the Eth-Trunk group to which the second member belongs, determines the target member; the first user plane network element adopts the link of the target member
  • the second device sends the first data packet of the PDU session corresponding to the target member.
  • the second device may be a second user plane network element.
  • the first device does not select a link in the same Eth-Trunk group to forward data packets, which can avoid closed-loop flooding of broadcast data.
  • the first device may be a user plane network element, for example, the first device is a first user plane network element.
  • the first user plane network element may also send the link states of the multiple members to the second device. In this way, the link states of multiple members in the Eth-Trunk group can be synchronized between multiple user plane network elements, so that the information of the Eth-Trunk group stored among the multiple user plane network elements is consistent.
  • the first device may be a user plane network element, for example, the first device is a first user plane network element.
  • the first user plane network element may send the link status of the multiple members to the second device through the session management network element Second equipment.
  • the first device may be an end-side device. Before acquiring the link status of multiple members, the end-side device may also receive a second message, where the second message is used to notify that multiple PDU sessions belong to one Eth-Trunk group, and the multiple PDU sessions correspond to one Eth-Trunk group A combination of slice and data network name DNN. In this way, the end-side device can perceive that multiple PDU sessions form an Eth-Trunk group.
  • the first device may be a user plane network element, for example, the first device is a first user plane network element.
  • the first user plane network element may also learn the MAC address of the newly accessed terminal device; the first user plane network element updates the data in the Eth-Trunk group according to the learned MAC address of the newly accessed terminal device.
  • the MAC address, and/or the first user plane network element reports the MAC address of the newly accessed terminal device to the session management network element.
  • the newly accessed terminal device belongs to the Eth-Trunk group, and the newly accessed terminal device corresponds to one PDU session or to multiple PDU sessions. In this way, the reliability of service communication can be further improved.
  • the first device may be a session management network element.
  • the session management network element may also send the link status of the third member to one or more user plane network elements . This ensures that one or more user plane network elements can obtain the link status of members in time, and further ensures that the information of the Eth-Trunk group stored between the user plane network elements is consistent.
  • all members of the Eth-Trunk group are deployed on one user plane network element.
  • the first device may be a session management network element.
  • the session management network element can determine the target member according to the link status of the multiple members and the identity of the Eth-Trunk group , the user plane network element is deployed on the link of the target member. In this way, the PDU sessions of the members of the Eth-Trunk group can be deployed on the one user plane network element.
  • the first device may be a session management network element.
  • the session management network element may also acquire the information of the Eth-Trunk group from the data management network element.
  • the first session management network element may further send a second message, where the second message is used to establish a first PDU session, and the second message includes the information of the Eth-Trunk group.
  • the first device may be a session management network element.
  • the session management network element may also learn the MAC address of the newly accessed terminal device, wherein the newly accessed terminal device belongs to the Eth-Trunk group, and the newly accessed terminal device corresponds to a PDU session or a corresponding Multiple PDU sessions; the session management network element may send the MAC address of the newly accessed terminal device to one or more user plane network elements.
  • a communication method comprising the following steps: a third device receives a third message, where the third message is used to request to update an Eth-Trunk group; The information is updated; wherein, the information of the Eth-Trunk group includes the information of the members in the Eth-Trunk group.
  • the third device may be a data management network element.
  • a communication system including at least one end-side device and at least one user plane network element, the at least one end-side device and the at least one user plane network element are connected; the at least one end-side device is connected to the at least one user plane network element;
  • the device is configured to execute the method described in the first aspect and any aspect thereof;
  • the at least one user plane network element is configured to execute the method described in the first aspect and any aspect thereof.
  • the communication system includes a plurality of end-side devices and a user plane network element, and the communication system further includes a switching device; each port of the switching device is respectively connected to each end-side device , each end-side device corresponds to a PDU session, the PDU sessions corresponding to the multiple end-side devices form an Eth-Trunk group, and the members of the Eth-Trunk group are deployed on the same user plane network element.
  • the communication system includes multiple end-side devices and multiple user plane network elements, and every two user plane network elements are connected, and the communication system further includes a switching device; the switching device Each port is connected to each end-side device, each end-side device corresponds to a PDU session, the PDU sessions corresponding to the multiple end-side devices form an Eth-Trunk group, and the members of the Eth-Trunk group There are at least two members deployed on different user plane network elements respectively.
  • the communication system includes multiple end-side devices and multiple user plane network elements, and every two end-side devices are connected, and every two user plane network elements are connected;
  • the side device corresponds to one PDU session, the PDU sessions corresponding to the multiple end-side devices form an Eth-Trunk group, and at least two members of the Eth-Trunk group are deployed on different user plane network elements respectively.
  • the communication system includes an end-side device and multiple user plane network elements, and every two user plane network elements are connected; the end-side device corresponds to multiple PDU sessions, and the multiple user plane network elements are connected.
  • Each PDU session forms an Eth-Trunk group, and at least two members of the Eth-Trunk group are deployed on different user plane network elements respectively.
  • a communication device in a fourth aspect, has the function of implementing any method provided by the first aspect and any possible designs thereof.
  • the communication device may be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the unit or module may be a processing unit and a transceiver unit.
  • the processing unit is configured to support the communication apparatus to perform the corresponding functions of the first device in the above-described method.
  • the transceiver unit is used for the communication device to send and receive data or information.
  • the communication device may further include a storage unit, which may be coupled with the processing unit, and stores necessary program instructions and data of the communication device.
  • a communication device in a fifth aspect, has the function of implementing any of the methods provided in the second aspect.
  • the communication device may be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the unit or module may be a processing unit and a transceiver unit.
  • the processing unit is configured to support the communication apparatus to perform the corresponding functions of the third device in the method shown above.
  • the transceiver unit is used for the communication device to send and receive data or information.
  • the communication device may further include a storage unit, which may be coupled with the processing unit, and stores necessary program instructions and data of the communication device.
  • a computer-readable storage medium for storing a computer program, the computer program including a method for executing the first aspect, the second aspect, or any of the possible implementations of the first aspect and the second aspect. method instruction.
  • a computer program product comprising: computer program code, when the computer program code is run on a computer, the computer causes the computer to execute the first aspect, the second aspect, or the first aspect .
  • the method in any possible implementation manner of the second aspect.
  • a system-on-chip includes a transceiver for implementing the functions in the methods of the above aspects, for example, for example, receiving or transmitting data and/or information involved in the above methods.
  • the chip system further includes a memory for storing program instructions and/or data.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • Figure 1 is a schematic diagram of a 5G network architecture
  • Figure 2 is a schematic diagram of a 5G LAN network architecture
  • Fig. 3 is a kind of network architecture schematic diagram of multi-link communication
  • Fig. 5, Fig. 7, Fig. 9, Fig. 10, Fig. 14, Fig. 15, Fig. 16 are schematic diagrams of a possible communication flow provided by this application;
  • FIG 6, Figure 8, Figure 11, Figure 12, Figure 13 are schematic diagrams of a possible communication system architecture provided by this application;
  • FIG. 17 and FIG. 18 are schematic diagrams of a communication device provided by the present application.
  • the word "exemplary” is used to mean serving as an example, illustration or illustration. Any embodiment or design described in this application as "exemplary” should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word example is intended to present a concept in a concrete way.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • User equipment also known as terminal equipment, is a kind of equipment with wireless transceiver function, which can communicate with the access network equipment (or also called access equipment) in the radio access network (RAN).
  • RAN radio access network
  • One or more core network (core network, CN) devices (or may also be referred to as core devices) communicate.
  • User equipment may also be referred to as an access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent, user device, or the like.
  • User equipment can be deployed on land, including indoor or outdoor, handheld or vehicle; can also be deployed on water (such as ships, etc.); can also be deployed in the air (such as aircraft, balloons and satellites, etc.).
  • the user equipment may be a cellular phone (cellular phone), a cordless phone, a session initiation protocol (SIP) phone, a smart phone (smart phone), a mobile phone (mobile phone), a wireless local loop (WLL) station, personal digital assistant (PDA), etc.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • the user equipment may also be a handheld device with a wireless communication function, a computing device or other device connected to a wireless modem, an in-vehicle device, a wearable device, a drone device, or a terminal in the Internet of Things, the Internet of Vehicles, the fifth generation Mobile communication (5th-generation, 5G) network and any form of terminal in future network, relay user equipment or terminal in future evolved PLMN, etc.
  • the relay user equipment may be, for example, a 5G home gateway (residential gateway, RG).
  • the user equipment can be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, telemedicine Wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home wireless terminals, etc.
  • VR virtual reality
  • AR augmented reality
  • This embodiment of the present application does not limit the type or type of the terminal device.
  • the user equipment may also include end-side equipment, such as a local switch (local switch, LSW), and/or customer premises equipment (customer premise equipment, CPE), and the like.
  • end-side equipment such as a local switch (local switch, LSW), and/or customer premises equipment (customer premise equipment, CPE), and the like.
  • a user equipment that is registered into the network may be understood as a user.
  • One of the UEs may correspond to a subscriber identity module (SIM) card, that is, when the terminal device is installed with one SIM card, the terminal device corresponds to one user UE, and when the terminal device is installed with multiple SIM cards, the terminal device corresponds to multiple user UEs.
  • SIM subscriber identity module
  • the network device may support at least one wireless communication technology, such as long term evolution (LTE), new radio (NR), wideband code division multiple access (WCDMA), and the like.
  • LTE long term evolution
  • NR new radio
  • WCDMA wideband code division multiple access
  • network equipment may include access network equipment.
  • the network equipment includes, but is not limited to: a next-generation base station or a next-generation node B (generation nodeB, gNB), an evolved node B (evolved node B, eNB), a radio network controller (radio network controller, RNC), node B (node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved node B, or home node B, HNB ), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, small station, micro station, etc.
  • generation nodeB, gNB next-generation node B
  • eNB evolved node B
  • RNC radio network controller
  • node B node B
  • BSC base station controller
  • BTS base transceiver station
  • home base station for example, home evolved node B, or home node B, HNB
  • the network device may also be a wireless controller, a centralized unit (CU), and/or a distributed unit (DU) in a cloud radio access network (CRAN) scenario, or the network device may It is a relay station, an access point, a vehicle-mounted device, a terminal, a wearable device, and a network device in future mobile communications or a network device in a future evolved public land mobile network (PLMN).
  • CU centralized unit
  • DU distributed unit
  • CRAN cloud radio access network
  • PLMN public land mobile network
  • the network device may include a core network (CN) device, and the core network device includes, for example, an AMF and the like.
  • CN core network
  • Link Aggregation refers to a method of bundling a group of physical ports together as a logical interface to increase bandwidth and improve reliability. It can also be called a multi-port load balancing group. Sharing Group). If these bundled links are all Ethernet links, the aggregation group is called an Ethernet link aggregation group (Eth-Trunk group).
  • Device A and Device B are connected through three Ethernet physical links, and the three links are bundled together to form a logical link.
  • the maximum bandwidth of this logical link is equal to the three Ethernet physical links.
  • the total bandwidth of the link increases the link bandwidth, and the three physical Ethernet links back up each other, which can improve link reliability.
  • Each link aggregation group uniquely corresponds to a logical interface, which is called an aggregated interface or an Eth-Trunk interface.
  • the physical interfaces that make up an Eth-Trunk interface are called member interfaces.
  • a link corresponding to a member interface is called a member link.
  • the Eth-Trunk interface is located between the media access control (MAC) sublayer and the logical link control (LLC) sublayer, and belongs to the data link layer (data link layer). ).
  • Link Aggregation Control Protocol is a link aggregation mode responsible for maintaining link status.
  • the device sends information such as system priority, MAC address, interface priority, interface number, and operation key (used to determine whether each interface is connected to the opposite end in the same aggregation group and whether the bandwidth of each interface is consistent) to the peer device through LACP messages.
  • the peer device compares the received information with the information stored by itself, and selects the active link.
  • an interface corresponding to an active link is an active interface
  • an interface corresponding to an inactive link is an inactive interface.
  • An active interface is an interface that forwards data
  • an inactive interface is an interface that does not forward data.
  • System priority can be used to differentiate the priority of different interfaces/links in the same Eth-Trunk group.
  • the link between devices includes a primary link and a backup link, and the priority of the primary link is higher than that of the backup link.
  • the same priority or different priorities can be set between different standby links.
  • Bidirectional forwarding detection is a detection method.
  • the BFD detection mechanism is to establish a BFD session between two devices, and send BFD control packets (periodically) along the link between them. A failure has occurred on the link.
  • LACP detection and the BFD detection can be used alone or in combination.
  • the concepts of "acquiring”, “detecting”, and “negotiating” link states can be used interchangeably.
  • a PDU session is a business session in which a terminal device and a DN exchange PDU data packets.
  • a PDU session is implemented by establishing a PDU connection.
  • a PDU session is also called a PDU UE session, or a UE session, or an Ethernet session.
  • the PDU session is bound to a "slice+DNN” combination, that is, the PDU session corresponds to a pair of slice+DNN information.
  • Slices can be identified by a single network slice selection auxiliary information S-NSSAI.
  • the PDU session is bound to a combination of "slice+DNN+session ID (SessionID)", that is, the PDU session corresponds to a pair of slice+DNN and SessionID information.
  • SessionID is different, and the slice + DNN can be the same or different.
  • Communication systems generally include, but are not limited to, 4th-generation (4th-generation, 4G) networks, LTE systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD), Universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, 5G communication system or NR, and other communication systems in the future such as 6G, etc.
  • 4th-generation (4th-generation, 4G) networks LTE systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD), Universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, 5G communication system or NR, and other communication systems in the future such as 6G, etc.
  • the 3GPP standards group has formulated the Next Generation System for mobile communications, called the 5G network architecture.
  • the 5G network architecture supports the use of wireless technologies (such as LTE, 5G RAN, etc.) defined by the 3GPP standard group, and access methods such as fixed networks to access the core network side.
  • the 5G network architecture shown in FIG. 1 is used as an example to describe the application scenarios used in the present application.
  • Figure 1 shows the 5G network architecture defined in the 3GPP standardization process.
  • the network architecture may include: a terminal device part, a network device part, and a data network (DN) part.
  • DN data network
  • the network equipment part includes an access network (AN) 102, a user plane function (UPF) 103, an access and mobility management function (AMF) 105, a session management function (session management function) management function, SMF) 106, policy control function (policy control function, PCF) 107, unified data management function (unified data management, UDM) 108, unified data repository (unified data repository, UDR) 110, etc.
  • the network part may further include an application function (application function, AF) 109 and/or a network exposure function (network exposure function, NEF) 109.
  • the part other than the access network 102 part may be referred to as the core network part.
  • the data network DN 104 which may also be referred to as a packet data network (PDN), may typically be deployed outside the operator's network, such as a third-party network.
  • the operator network may access multiple data network DNs 104, and multiple services may be deployed on the data network DNs 104, so as to provide the terminal device 101 with services such as data and/or voice.
  • the application function AF is used to convey the requirements of the application side to the network side, such as quality of service (quality of service, QoS) requirements or user status event subscriptions.
  • the AF can be a third-party functional entity (that is, an application functional entity of a third-party application), or can be an application service deployed by an operator, such as an Internet Protocol (IP) multimedia subsystem (IP multimedia subsystem, IMS) voice call service.
  • IP Internet Protocol
  • IMS Internet Multimedia subsystem
  • the AF can perform authorization processing through the NEF when interacting with the core network. For example, the AF sends a request message to the NEF, and the NEF determines whether the AF is allowed to send the request message. The request message is forwarded to the corresponding PCF 107 or UDM 108.
  • the AN 102 also called a radio (Radio) AN, is a sub-network of the operator's network, and is an implementation system between a service node (or network function) and the terminal device 101 in the operator's network.
  • the terminal device 101 To access the operator's network, the terminal device 101 first passes through the AN 102, and then connects with the service node in the operator's network through the AN 102.
  • the AN 102 in the embodiment of the present application may refer to the access network itself, or may refer to the access network equipment, which is not distinguished here.
  • the names of devices with access network device functions may be different, and the access methods may also be different (such as wired access methods, wireless base station access methods, etc.).
  • the user plane function UPF 103 is the gateway for the operator network to communicate with the DN 104.
  • UPF103 can complete functions such as user plane data forwarding, session-level/flow-level accounting statistics, and bandwidth limitation.
  • the access and mobility management function AMF 105 is responsible for performing functions such as mobility management and access authentication/authorization for the terminal device 101. In addition, AMF 105 may also be responsible for transferring user policies between terminal device 101 and PCF 107.
  • the session management function SMF 106 is responsible for managing the protocol data unit (PDU) session of the terminal device 101, executing the PCF 107 to issue control policies, selecting the UPF, and assigning the IP address of the terminal device 101 when the PDU type is IP type.
  • PDU protocol data unit
  • the policy control function PCF107 is responsible for policy control functions such as session-level/flow-level charging, QoS bandwidth guarantee and mobility management, and terminal device policy decision-making.
  • the unified data management UDM 108 is responsible for managing contract data, user access authorization and other functions.
  • the unified data warehouse UDR110 is responsible for the access functions of contract data, policy data, application data and other types of data.
  • the network architecture shown in FIG. 1 may further include other network functions, which are not limited in this embodiment of the present application.
  • N1, N2, N3, N4, N5, N6, N7, N8, N9, N10, N11, N15, N35, and N36 are interface serial numbers.
  • the interface names between various network functions in FIG. 1 are just an example, and in specific implementation, the interface names of the system architecture may also be other names, which are not limited in this application.
  • the user plane function UPF 103 is abbreviated as UPF in the embodiments of the present application, that is, the UPF described later in the embodiments of the present application can be replaced by the user plane function. It can be understood that other network functions not shown are also applicable to this alternative method.
  • 3GPP defines the 5G local area network (LAN) service, which builds a virtual mobile private network for users through the 5G LAN service on the mobile network.
  • 5G LAN can be used in a wider range of mobile network coverage, that is, regardless of whether users are in the same region, as long as they join the same 5G LAN, LAN-based data exchange and communication can be realized.
  • the terminal device realizes data exchange between the terminal device and the DN by establishing a PDU connection.
  • 5G LAN adds the concept of group to the current PDU connection.
  • Multiple 5G LAN groups (groups for short) can be supported simultaneously in the mobile network.
  • Terminal devices belonging to the same 5G LAN group can exchange data with the DN corresponding to the group, or complete data exchange with other terminal devices in the same group through UPF. That is, terminal devices in the same group can communicate with each other, and terminal devices in different groups are isolated from each other.
  • the 5G LAN group is mainly used as the Eth-Trunk group for description.
  • FIG. 2 shows a 5G LAN network architecture, including terminal-side equipment, network-side equipment, and DN-side equipment.
  • the terminal-side equipment includes personal computer (PC) 1, L2 switch (switch, SW), CPE1/UE1, PC2, CPE2/UE2, PC3 and CPE3/UE3, network side devices include gNB1, UPF1, gNB2, gNB3 and UPF2, DN side devices include DN SW and PC4.
  • the 5G LAN network in Figure 2 supports local exchange of end-side devices (such as data exchange between PC1 and PC2), exchange of end-side devices with DN-side devices (that is, cross-network exchange, such as data exchange between PC1 and PC4), and end-side devices Devices are exchanged across UPFs (eg PC2 exchanges data with PC3).
  • end-side devices such as data exchange between PC1 and PC2
  • DN-side devices that is, cross-network exchange, such as data exchange between PC1 and PC4
  • end-side devices Devices are exchanged across UPFs (eg PC2 exchanges data with PC3).
  • terminal devices may refer to PC1, PC2, PC3, and PC4.
  • the CPE/UE mainly plays a bridging role in the data plane.
  • the switch can be connected behind the CPE/UE (for example, at the location of PC1), for example, CPE1/UE1 is connected to the L2 SW.
  • the session type that the CPE/UE can carry in the session establishment message is an Ethernet (Ethernet) type.
  • UPF learns the source MAC address of the data packet sent by the end-side device or the DN-side device, and configures the destination MAC address for forwarding data packets based on the learned MAC address. For example, the configured destination MAC address is different from the learned MAC address.
  • a single node of terminal equipment accesses the network, and a single link is connected between the terminal equipment and the DN. If the terminal equipment fails, or any link between the terminal equipment and the DN fails, the network The connection failure will also cause the business communication to fail.
  • a multi-link communication mode is defined in 3GPP.
  • the terminal equipment accesses the DN through the active and standby links. For example, as shown in FIG. 3 , the terminal device accesses the DN through (R)AN1 and UPF1, and the terminal device accesses the DN through (R)AN2 and UPF2.
  • the terminal device needs to support two PDU sessions, and the network side configures the dual connection mode of the PDU session.
  • the sender such as terminal equipment or DN
  • the receiver such as DN or terminal equipment
  • the receiver such as DN or terminal equipment
  • the two received packets 1 are deduplicated. If a link between the terminal device and the DN fails, the terminal device and the DN can perform normal service communication through another link.
  • the terminal device needs to establish two PDU sessions, and each PDU session is bound with a combination of "slice (S-NSSAI) + data network name (DNN)", which wastes slices and DNN resources.
  • S-NSSAI slice
  • DNN data network name
  • the multi-link communication method needs to be synchronously modified on the DN side, and the multiple transmission and selective reception puts forward higher requirements on the network side.
  • an embodiment of the present application provides a communication method.
  • the first device obtains the link status of multiple members, each member corresponds to a protocol data unit PDU session, and the multiple members belong to one Eth-Trunk group;
  • the link state of the member is selected, the target member is selected, and the first data packet of the PDU session corresponding to the target member is sent.
  • the first device acts as a sender, and there are multiple links deployed between the first device and the receiver, and the links are links of members in the Eth-Trunk group.
  • the sender selects target members and The link of the target member, using the link of the target member as the active link for business communication.
  • one link can be used for business communication without occupying too many slice and DNN resources, and it is not necessary to modify the network side to reduce the requirements of the network side.
  • the target member is selected through the link state, which can avoid the influence on the service communication when the link fails, and ensure the normal service communication.
  • the communication method provided by the embodiment of the present application may be applied to the communication system shown in FIG. 1 or FIG. 2 .
  • the definition of Eth-Trunk can be added, and the parameters of Eth-Trunk can be opened to the outside world (optionally, it can be opened to the outside world through NEF).
  • the Eth-Trunk parameter may be stored in the UDR, or the third party may store the Eth-Trunk parameter in the DN-authentication authorization accounting (AAA).
  • AAA DN-authentication authorization accounting
  • Members with the same attributes (CPE/UE) correspond to the same Eth-Trunk parameters.
  • Members with the same attributes can be regarded as belonging to the same Eth-Trunk group.
  • the information of the Eth-Trunk group includes the Eth-Trunk parameters.
  • multiple end-side devices can access layer 2 5GLAN and form an Eth-Trunk group. All CPE/UE members in an Eth-Trunk group can forward data packets according to active/standby or load sharing to ensure the reliability of service communication.
  • the AF provides the Eth-Trunk data parameter and the Eth-Trunk member parameter to the NEF.
  • the Eth-Trunk parameters include Eth-Trunk data parameters and/or Eth-Trunk member parameters.
  • the attributes of the Eth-Trunk group include Eth-Trunk data parameters and/or Eth-Trunk member parameters.
  • the Eth-Trunk data parameters include one or more of the following: a group external identifier (External Group ID), an Eth-Trunk identifier (TrunkId), a link type (LinkType), a virtual local area network (virtual local area network) that allows access , VLAN) identification (AllowVlanList), link detection type (LinkCheckType), maximum number of links (MaxLinkNum) and minimum number of links (MinLinkNum).
  • the group external identifier may refer to a 5G virtual network (virtual network, VN) group external identifier.
  • the link type includes an access (Access) type or a Trunk type.
  • the link detection type includes LACP, BFD or LACP+BFD and the like.
  • the group external identifier, the Eth-Trunk identifier, and the link type are mandatory parameters.
  • the link type is a Trunk type
  • the access-allowed VLAN identifier is a mandatory parameter; otherwise, the access-allowed VLAN identifier is an optional parameter.
  • the link detection type, the maximum number of links, and the minimum number of links are optional parameters.
  • the Eth-Trunk member parameters include one or more of the following: member ID, group external ID, Eth-Trunk ID, and member priority (Priority).
  • the member identifier is a 5G VN member identifier, which can be identified by a generic public subscription identifier (GPSI).
  • Eth-Trunk data parameters and Eth-Trunk member parameters can be saved in the form of a table.
  • the key value (key value) of the table can be External Group ID+TrunkId.
  • the network-side device in the communication system supports the Eth-Trunk feature.
  • the end-side equipment CPE/UE
  • the end-side device includes CPE and/or CE.
  • S401 The AF calls the interface provided by the NEF, and sends a create (Create)/update (Update)/delete (Delete) request message to manage the Eth_Trunk.
  • the interfaces provided by NEF include Nnef_ParameterProvision_Create/Update/Delete and other interfaces.
  • the interface provided by the NEF is an authorized interface.
  • S402 The NEF sends a Create/Update/Delete request message through the interface provided by the UDM, requesting the UDM to create/update/store/delete the corresponding subscription data.
  • the interfaces provided by UDM include Nudm_ParameterProvision_Create/Update/Delete and other interfaces.
  • S402 is performed. If the NEF determines that the request message sent by the AF is an unauthorized request, the NEF may directly return a response message to the AF (see S406 ), and send the failure reason.
  • the UDM initiates a data query request through the interface provided by the UDR to complete the verification and authorization of the AF creation/update/deletion request.
  • the interfaces provided by UDR include interfaces such as Uudr_DM_Query.
  • the UDM sends the create/update/delete request message to the UDR through the interface provided by the UDR, so as to realize the creation/update/deletion of the Eth-Trunk information.
  • the UDM can call the Nudr_DM_Create interface provided by the UDR.
  • the UDM may call the Nudr_DM_Update interface provided by the UDR.
  • the request message for updating Eth-Trunk may be used to update information of Eth-Trunk members and/or update information of Eth-Trunk data.
  • S405 The UDM returns a create/update/delete response message. If there is an error in UDM execution, the UDM returns the cause of the error.
  • UDM responds to Nudm_ParameterProvision_Create/Update/Delete request messages.
  • NEF returns a create/update/delete response message. If there is an error in NEF execution, NEF returns the cause of the error.
  • NEF responds to Nnef_ParameterProvision_Create/Update/Delete request messages.
  • FIG. 5 takes FIG. 5 as an example to describe the communication method provided by the embodiment of the present application, including the following steps:
  • S501 The first device acquires link states of multiple members. Each member corresponds to one protocol data unit PDU session, and the multiple members belong to one Eth-Trunk group.
  • the first device may be one of a user plane network element (UPF), an end-side device (such as LSW or CPE or UE) or a session management network element (SMF).
  • UPF user plane network element
  • end-side device such as LSW or CPE or UE
  • SMF session management network element
  • the first device may be the sender.
  • the terminal-side device is the sender
  • the user plane network element is the receiver
  • the terminal-side device sends uplink data packets to the user plane network element.
  • the user plane network element is the sender
  • the terminal-side device is the receiver
  • the user-plane network element sends downlink data packets to the terminal-side device.
  • each member of the Eth-Trunk group corresponds to one PDU session and corresponds to one link. That is, the members in the Eth_Trunk group send data packets corresponding to the PDU session through the corresponding link.
  • the link status is used to indicate the priority of the member's link, and/or the link status is used to indicate that the member's link is a primary link or a backup link, and/or the link Status is used to indicate whether a member's link is down.
  • the priority of the primary link is higher than that of the backup link, and the priorities of different backup links are the same or different.
  • the first device may use LACP to detect link states of multiple members.
  • the first device may use BFD to detect link states of multiple members.
  • the first device uses the LACP and BFD to jointly detect the link states of multiple members.
  • the link status of the members in the Eth_Trunk group does not require link detection, so as long as the PDU session corresponding to the member is successfully established, it can be confirmed that the links of the members in the Eth_Trunk group are available.
  • the first device may maintain Eth-Trunk group information (eg, Eth-Trunk data information and/or Eth_Trunk member information).
  • Eth-Trunk group information eg, Eth-Trunk data information and/or Eth_Trunk member information.
  • the first device is a user plane network element UPF.
  • the first device may receive a first message, where the first message is used to establish a first PDU session.
  • the first message includes information of an Eth-Trunk group, and the information of the Eth-Trunk group includes attributes of the Eth-Trunk group.
  • the attributes of the Eth_Trunk group may include information of Eth-Trunk data parameters and/or information of Eth-Trunk member parameters, or the attributes of the Eth_Trunk group may be External Group ID+TrunkId.
  • the first device establishes a first PDU session according to the first message.
  • the first device may add a member corresponding to the first PDU session in the Eth-Trunk group (for example, a member identifier may be added). ). If the attribute of the first PDU session does not match the attribute of any currently saved Eth-Trunk group, the first device may create the attribute of the first PDU session as the attribute of the new Eth-Trunk group, and A member corresponding to the first PDU session is added to the newly created Eth-Trunk group (for example, the attributes and new members of the new Eth-Trunk group can be saved by creating a table). The first device may maintain information such as the members of the Eth-Trunk group, the MAC address of the terminal device, and the like with the Eth-Trunk group as the granularity.
  • the information of the Eth-Trunk group may also include one or more of the following: the identifier of the Eth-Trunk group, the link type of the member, the link detection type of the member, and the largest chain in the Eth-Trunk group.
  • the first device may detect the link state of the member corresponding to the first PDU session according to the link detection type of the member.
  • the first device is an end-side device, such as LSW/CPE/UE.
  • the first device may receive a second message, where the second message is used to notify the first device that multiple PDU sessions belong to an Eth-Trunk group, and the multiple PDU sessions correspond to a slice and a A combination of DNNs.
  • the network architecture includes only one end-side device, each PDU session corresponds to a combination of slice, DNN and session ID (SessionID).
  • SessionID session ID
  • each PDU session corresponds to the same slice + DNN, and corresponds to a different SessionID.
  • the first device is a session management network element SMF, and the first device may detect a link state transmission change of one or more members of the plurality of members. Assuming that the link status of the third member changes, the first device sends the link status of the third member to one or more user plane network elements, where the third member belongs to one of the multiple members member.
  • SMF session management network element
  • the first device may periodically acquire link states of multiple members.
  • the first device detects that a link of one or more members of the plurality of members is faulty. Assuming that the link of the first member fails, the first device may release the PDU session corresponding to the first member, or the first device retains the PDU session corresponding to the first member, and records the first member The state of the corresponding PDU session is abnormal; wherein the first member belongs to one of the multiple members.
  • the first device selects a target member according to link states of the multiple members, and sends a first data packet of a PDU session corresponding to the target member.
  • the first device selects a target member from the multiple members by using a hash (Hash) algorithm according to the link states of the multiple members. Or the first device selects a link that is not faulty and has a high priority among the links of the multiple members as the link of the target member. For example, the first device may select a link with a higher priority among the non-faulty links as the link of the target member, and if the priorities of the non-faulty links are the same, the first device may select one link as the target member 's link.
  • a hash Hash
  • the sender detects the link status of the member and selects the target member to send the data packet.
  • the receiver also detects the link status of the member, adopts the same selection strategy as the sender, and selects the target member to receive the data packet. That is, during the communication process, the sender and the receiver perform detection synchronously, and then select target members for business communication.
  • the members of the Eth-Trunk group may be distributed on the same UPF, or may be distributed on different UPFs. If the members of an Eth-Trunk group are distributed on different UPFs, the information of the Eth-Trunk group can be synchronized between different UPFs to keep the Eth-Trunk parameters and the link status of the members consistent between different UPFs.
  • the first device sends the link states of the multiple members to a second device, where the first device is the first UPF, and the second device is the second UPF.
  • the first device sends the link states of the multiple members to the second device through the session management network element SMF.
  • the first data packet includes information for indicating that the first data packet is from a second member.
  • the first device may, according to the link status of the multiple members, be in other Eth-Trunk groups except the Eth-Trunk group to which the second member belongs.
  • the target member is determined, and the first device uses the link of the target member to send (via the second device, if any) the first data packet of the PDU session corresponding to the target member.
  • the first device forwards data packets, it does not select a link in the same Eth-Trunk group for forwarding, which can avoid closed-loop flooding of broadcast packets (same as UPF/cross-UPF).
  • the first device can learn the MAC address of the newly accessed terminal device, and the first device updates the Eth-Trunk group according to the learned MAC address of the newly accessed terminal device and/or the first device reports the MAC address of the newly accessed terminal device to the session management network element.
  • the newly accessed terminal device may belong to the Eth-Trunk group, and the newly accessed terminal device may correspond to one PDU session or to multiple PDU sessions.
  • the first device may determine the target member according to the link status of the multiple members and the identifier of the Eth-Trunk group, and the target member The user plane network element is deployed on the link.
  • the first device can ensure that the selected target members are members of the Eth-Trunk group through the identification of the Eth-Trunk group, thereby ensuring that all members in the same Eth-Trunk group are distributed on the same UPF.
  • the first device may acquire the information of the Eth-Trunk group from a data management network element (such as UDM/UDR).
  • a data management network element such as UDM/UDR
  • the session management network element may send a second message to the LSW/CPE, where the second message is used to establish a first PDU session, and the second message includes the information of the Eth-Trunk group.
  • the session management network element can learn the MAC address of the newly accessed terminal device, and send the MAC address of the newly accessed terminal device to one or more user plane network elements.
  • the newly accessed terminal equipment belongs to the Eth-Trunk group, and the newly accessed terminal equipment corresponds to one PDU session or to multiple PDU sessions.
  • the first device acts as a sender, and multiple links are deployed between the first device and the receiver, and the links are links of members in the Eth-Trunk group.
  • the link status of the road is selected, the target member and the link of the target member are selected, and the link of the target member is used as the active link for business communication. That is to say, one link can be used for business communication, without occupying too many slices and DNN resources, and it is not necessary to modify the network side to reduce the requirements of the network side.
  • the target member is selected through the link state, which can avoid the influence on the service communication when the link fails, and ensure the normal service communication.
  • the communication system may include at least one end-side device and one UPF.
  • FIG. 6 is a schematic diagram of the architecture of a possible communication system
  • the communication system includes PC1, PC2, PC3, a layer 2 switch (L2 SW) connected to PC1, CPE1/UE1 and CPE2/UE2 connected to L2 SW, gNB1 connected to CPE1/UE1, gNB2 connected to CPE2/UE2, UPF connected to gNB1 and gNB2, DN side switch (DN SW) and gNB3 connected to UPF, PC2 connected to DN SW, CPE3 connected to gNB3 /UE3, and PC3 connected to CPE3/UE3.
  • L2 SW layer 2 switch
  • DN SW DN side switch
  • CPE1/UE1 and CPE2/UE2 are members belonging to the same Eth-Trunk group. It can be understood that, an Eth-Trunk group may contain more members, and only two members are used as an example for description here, but it does not constitute a limitation.
  • the L2 SW supports the Eth-Trunk feature. The L2 SW uses two ports to connect to two CPEs/UEs respectively, and the CPEs/UEs transparently transmit all Layer 2 data packets in a bridging manner. Sessions of all CPE/UE members forming an Eth-Trunk group are on the same UPF.
  • the port of the L2 SW can negotiate the link status of the members with the session of the UPF.
  • the LACP/BFD protocol stack is implemented on the UPF.
  • both BFD and LACP can detect whether member links are available.
  • the detection efficiency of BFD is higher than that of LACP.
  • BFD and LACP can be deployed together, and joint detection produces a superimposed effect.
  • LACP can determine whether a member's link is in the active or standby state, and BFD can quickly detect whether the link is connected or faulty.
  • UPF and DN SW can guarantee multi-link transmission through multi-link mode.
  • Fig. 7 provides a communication process, including the following steps:
  • S701 CPE1/UE1 sends a session establishment request message to the AMF, requesting to establish a PDU session.
  • S702 AMF selects SMF.
  • S703 The AMF forwards the session establishment request message to the selected SMF.
  • the SMF obtains user subscription data from the UDM/UDR.
  • the user subscription data may also include the information of the Eth-Trunk group to which the user belongs, such as the identity (TrunkId) of the Eth-Trunk to which the user belongs, and the Eth-Trunk group to which the user belongs. properties, etc. If the information of the Eth-Trunk group is not stored in the UDM/UDR, the user subscription data also includes the identifier (TrunkId) of the Eth-Trunk to which the user belongs.
  • Optional S706 If the UDM/UDR only returns the TrunkId, the SMF obtains the information of the Eth-Trunk group from the DN-AAA.
  • S707 SMF selects UPF.
  • SMF selects the same UPF for the user as other users in the same Eth-Trunk group.
  • S708 The SMF notifies the UPF through the N4 interface to establish a PDU session.
  • the message sent by the SMF to the UPF may also carry the information of the Eth-Trunk group.
  • the UPF establishes a PDU session.
  • the PDU session is an N4UE session.
  • S710 The SMF/AMF/CPE1/UE1 completes the establishment process of the subsequent PDU session.
  • the L2 SW negotiates the link status of the PDU session of CPE1/UE1 with the UPF using the port connected to CPE1/UE1 (eg, port 1).
  • Steps S712 and S713 are optional steps, and of course they may not be executed.
  • S714 The SMF releases the current PDU session and carries the cause value.
  • the reason value is used to inform the CPE/UE of the reason why the user plane link of the session fails.
  • the reason value is that the data plane of the PDU session is unavailable, or the data plane is unreachable.
  • CPE2/UE2 (not shown in FIG. 7 ) repeats the process similar to S701-S714 until the UPF saves the link status of all members in the Eth-Trunk group, which will not be repeated here.
  • the UPF learns the MAC address of the source side PC1 through the PDU session of the CPE1/UE1, and the UPF stores the learned new MAC address (the MAC address of the PC1) in the information of the Eth-Trunk group.
  • the information of the Eth-Trunk group can store the learned MAC addresses of all members.
  • the UPF learns the MAC address of the source side PC2, and stores the learned new MAC address (the MAC address of PC2) in the information of the Eth-Trunk group.
  • the UPF selects the link of CPE1/UE1 to forward the data packet.
  • FIG. 8 is a schematic diagram of the architecture of a possible communication system. Compared with FIG. 6 , FIG. 8 includes two UPFs, UPF1 and UPF2, and other similarities are not repeated.
  • Fig. 9 provides a communication process, including the following steps:
  • S907 SMF selects UPF1.
  • the selection of UPF1 is taken as an example for description.
  • the SMF may select UPF2, which is not limited here.
  • S908 The SMF notifies the UPF1 through the N4 interface to establish a PDU session.
  • the message sent by the SMF to the UPF1 may also carry the information of the Eth-Trunk group.
  • the SMF may also require the UPF1 to report the member's link status and updated MAC address.
  • UPF1 If the user in UPF1 is the first member of the Eth-Trunk group, you can create a new Eth-Trunk group table in UPF1 to save the information of the Eth-Trunk group; if the user is not the first member of the Eth-Trunk group , that is, there are other members in the Eth-Trunk group, and UPF1 adds the user as a new member in the Eth-Trunk group.
  • the L2 SW negotiates the link status of the PDU session of CPE1/UE1 with UPF1 using the port connected to CPE1/UE1 (eg port 1).
  • UPF1 reports the link status of the member (eg, CPE1/UE1) to the SMF through the N4 interface.
  • the CPE2/UE2 repeats the similar process of S901-S914, which is not repeated here.
  • the UPF2 can also report the link status of the member (CPE2/UE2) to the SMF.
  • UPF1 learns the MAC address of source side PC1 through the PDU session of CPE1/UE1, and UPF1 saves the learned new MAC address (MAC address of PC1) in the information of the Eth-Trunk group. UPF1 can report the new MAC address to SMF through the N4 interface.
  • S917 SMF notifies UPF2 of a new MAC address (eg, the new MAC address reported by UPF1) through the N4 interface, and stores the learned new MAC address in the information of the Eth-Trunk group of UPF2.
  • a new MAC address eg, the new MAC address reported by UPF1
  • UPF1 first forwards the packet to UPF2, UPF2 forwards the packet to CPE2/UE2, and CPE2/UE2 forwards the packet to the L2 SW.
  • UPF1 learns the MAC address of PC2 on the source side, and stores the learned new MAC address (the MAC address of PC2) in the information of the Eth-Trunk group. UPF1 notifies UPF2 of the new MAC address.
  • UPF1 When communicating between UPF1 and UPF2, UPF1 forwards data packets to UPE2 through the N19 interface. UPF1 can add source-side information of the data packet to the extension header of the GPRS tunnel protocol (GPRS tunnel protocol, GTP)-U to indicate which PDU session the data packet passes through to reach UPF1.
  • GTP GPRS tunnel protocol
  • L2 SW and UPF1 use LACP/BFD to periodically send detection packets to detect link status.
  • the UPF1 refreshes the currently saved link state of the member.
  • UPF1 notifies UPF2 that the member's link state has changed, and UPF2 refreshes the saved member's link state.
  • the link status can be detected between L2 SW and UPF2. For similarities, see the detection process of UPF1.
  • UPF1 can age the MAC address of PC1, UPF1 reports the MAC address aging event through the N4 interface, SMF notifies UPF2 of the MAC address aging event through the N4 interface, and UPF2 refreshes the saved MAC address.
  • the function of the UPF is implemented by the SMF, and the LACP/BFD protocol stack is deployed on the SMF to maintain the information of the Eth-Trunk group and the link status of the members. Notify all UPFs when the link status of members in the Eth-Trunk group changes.
  • Figure 10 provides a communication process that includes the following steps:
  • S1008 The SMF notifies the UPF1 through the N4 interface to establish a PDU session.
  • the message sent by the SMF to the UPF1 may also carry the information of the Eth-Trunk group.
  • the SMF may also require the UPF1 to report the member's link status and updated MAC address.
  • the SMF may also require the UPF1 to report received detection packets (eg, LACP/BFD messages).
  • UPF1 when UPF1 recognizes LACP messages, UPF1 recognizes that the destination MAC address in the message is 01:80:C2:00:00:02, the Ethernet Type is Slow Protocol (0x8809), or the Slow Protocol SubType is One or more of 0x01.
  • UPF1 identifies BFD, UPF1 identifies whether the multicast IP address and UDP port number in the message are consistent with those configured locally.
  • the L2 SW negotiates the link status of the member with the SMF.
  • the L2 SW negotiates the member's link status with the SMF through UPF1.
  • the UPF1 receives the uplink LACP/BFD message and forwards the LACP/BFD message to the SMF.
  • the UPF1 receives the downlink LACP/BFD message, and forwards the LACP/BFD message to the corresponding CPE/UE (eg, CPE1/UE1).
  • S1012 The SMF sends the link state of the member to the UPF1, and the UPF1 refreshes the currently saved link state of the member.
  • the SMF sends the link status of the member to all UPFs related to the Eth-Trunk group to which the member belongs. All UPFs related to the Eth-Trunk group to which the member belongs refreshes the saved link status of the member.
  • the SMF sends the link status of the member to UPF2.
  • S1017 L2 SW and SMF use LACP/BFD to periodically send detection packets to detect link status.
  • SMF If it is detected that the link status of the member changes, SMF notifies all UPFs related to the Eth-Trunk group to which the member belongs, and sends the link status of the member. All UPFs related to the Eth-Trunk group to which the member belongs refresh the link status of the saved member.
  • FIG. 11 is a schematic diagram of the architecture of a possible communication system.
  • the CEP/UE is directly connected to the PC, not connected to the L2 SW, and the CPE/UE can interact with each other, and multiple CPE/UE form an Eth-Trunk group.
  • CEP/UE can directly forward uplink unicast data packets, and forward downlink unicast data packets according to the learned MAC address.
  • the CPE/UE may forward the uplink broadcast data packet to the network side and the opposite end CPE/UE (the opposite end CPE/UE of CPE1/UE1 is CPE2/UE2).
  • the peer CPE/UE After receiving the uplink broadcast data packet, the peer CPE/UE can forward it to the downlink (eg, the PC corresponding to the peer CPE/UE), but not to the uplink.
  • the CPE/UE can forward downlink broadcast data packets to the PC and the peer CPE/UE.
  • the peer CPE/UE After receiving the downlink broadcast data packet, the peer CPE/UE can forward it to the downlink but not to the uplink.
  • the communication process in FIG. 9 or FIG. 11 and details are not described here.
  • CPEs/UEs in Figure 11 may be located on one terminal device.
  • a plurality of subscriber identity module (subscriber identity module, SIM) cards are inserted into a terminal device, and each SIM corresponds to a UE.
  • a PDU session is established on the "slice (S-NSSAI) + DNN" of each UE, and an Eth-Trunk group is implemented inside the terminal device.
  • the end-side device negotiates the link status of each UE with the network side (such as UPF/SMF) through the UE.
  • the end-side device receives the uplink data packet of PC1, it can select the uplink UE for forwarding according to the Hash algorithm.
  • a certain UE in the end-side device receives the downlink data packet, it forwards the downlink data packet to PC1.
  • a single CPE/UE, a single S-NSSAI+DNN, and multiple SessionIDs form an Eth-Trunk group.
  • FIG. 13 is a schematic diagram of the architecture of a possible communication system.
  • the terminal-side device includes a CPE/UE, that is, a SIM card is used to connect to the network.
  • the CPE/UE uses a pair of S-NSSAI+DNN and multiple SessionIDs to establish multiple PDU sessions, and these PDU sessions form an Eth-Trunk group.
  • the granularity of the PDU session established by the end-side device is S-NSSAI+DNN+SessionID.
  • An Eth-Trunk link is formed between each PDU session on the CPE/UE side and the corresponding PDU session on the UPF side.
  • the CPE/UE When the CPE/UE receives the uplink data packet of PC1, it can select the uplink PDU session for forwarding according to the Hash algorithm. When a PDU session of the CPE/UE receives a downlink data packet, it forwards the downlink data packet to PC1.
  • Figure 14 provides a communication process, assuming that two PDU sessions of the CPU/UE are established on the same UPF, including the following steps:
  • S1401 The subscriber in the UDM supports Eth-Trunk access.
  • the UDR or DN-AAA stores the information of the Eth-Trunk group.
  • a subscription user supports Eth-Trunk access means that the user subscribes to the Eth-Trunk feature.
  • S1402 The CPE/UE initiates a session establishment request, requesting to establish a PDU session.
  • the session establishment request message carries slice information (S-NSSAI)+DNN and SessionID1.
  • the user subscription data may also include the information of the Eth-Trunk group to which the user belongs. If the Eth-Trunk group information is not stored in the UDM/UDR, the user subscription data includes information used to indicate that the user subscribes to the Eth-Trunk feature.
  • Optional S1407 If the UDM/UDR only returns information indicating that the user has subscribed to the Eth-Trunk feature, the SMF obtains the information of the Eth-Trunk group from the DN-AAA.
  • S1408 The CPE/UE and the core network complete the establishment process of the subsequent PDU session.
  • S1409 The CPE/UE negotiates the link state of the SessionID1 member in the Eth-Trunk group with the core network (eg UPF/SMF).
  • the core network eg UPF/SMF.
  • S1410 The CPE/UE and/or the UPF forward the received data packet.
  • the CPE/UE selects the PDU session to forward the uplink data packet to UPF1/UPF2 according to the Hash algorithm.
  • UPF1/UPF2 receives the upstream data packet and forwards the upstream data packet to the DN side.
  • UPF1/UPF2 selects the PDU session to forward the downlink data packet to the CPE/UE according to the Hash algorithm.
  • the CPE/UE forwards the downlink data packet to PC1.
  • the UE is responsible for accessing the network and may not be aware of whether each PDU session constitutes an Eth-Trunk group.
  • the CPE is aware of the Eth-Trunk group.
  • the network side can request multiple PDU sessions on the UE side to form an Eth-Trunk group through URSP.
  • the UE can perceive that the PDU sessions form an Eth-Trunk group, and negotiate with the network side the link status of the members of the Eth-Trunk group formed by each PDU session.
  • the CPE forwards the uplink data packet
  • the UE can select the PDU session to forward the uplink data packet according to the Eth-Trunk routing rule.
  • the PDU session of the UE receives the downlink data packet, the UE forwards the downlink data packet to the CPE.
  • Step 1 when the UE registers and joins the network, the network side informs the UE through the URSP that multiple PDU sessions of the user form an Eth-Trunk group.
  • Step 2 the network side actively informs the UE through the configuration update process that multiple PDU sessions of the user form an Eth-Trunk group.
  • Step 3 the UE establishes multiple PDU sessions, and the multiple PDU sessions form a group.
  • step 3 reference may be made to the communication process shown in FIG. 14 above.
  • Step 1 may be implemented in the UE registration process. See Figure 15, including the following steps:
  • S1501 The UE sends a registration request to the access network device.
  • the AMF returns a registration acceptance response to the UE, where the registration acceptance response includes a parameter used to indicate that multiple PDU sessions form an Eth-Trunk group.
  • Step 2 may be implemented in the UE configuration update process. See Figure 16, including the following steps:
  • the AMF decides to update the configuration information of the UE or perform reconfiguration.
  • the AMF sends a configuration update command to the UE, where the configuration update command includes a parameter used to instruct multiple PDU sessions to form an Eth-Trunk group.
  • AMF can be generated through PCF dynamic policy, or obtained information of "multiple PDU sessions form an Eth-Trunk group" through UDM subscription data.
  • the AMF can be updated through the UE registration process or the UE configuration update process.
  • an optional parameter Eth-TrunkFlag can be formulated according to an operator's policy, where the Eth-TrunkFlag is used to indicate that multiple PDU sessions form an Eth-Trunk group.
  • the Eth-TrunkFlag parameter can be stored in the UE context.
  • the Eth-TrunkFlag can allow the network side to modify the PCF policy through the URSP.
  • the Eth-TrunkFlag parameter may be added to the Route Selection Descriptor in Table 6.6.2.1-3 of 3GPP 23.503.
  • the UE When the UE wants to initiate a service or application, the UE matches whether there is a specific rule of the Eth-TrunkFlag parameter in the Route Selection Descriptor. If there is, the UE configures the existing PDU session with the same information as the service/application to be initiated, and the UE can choose to carry the service/application to be initiated in the existing PDU session, or carry out a Revise. If the information in the existing PDU session configured by the UE is inconsistent with the information of the service/application to be initiated, the UE may initiate a PDU session establishment request for the service/application to be initiated.
  • the embodiment of the present application also provides a communication device.
  • the communication device 1700 includes a processing unit 1701 and a transceiver unit 1702, and the apparatus 1700 can be used to implement the methods described in the above method embodiments.
  • the transceiver unit 1702 when the apparatus 1700 is applied to the first device, the transceiver unit 1702 is configured to acquire the link status of multiple members, each member corresponds to a protocol data unit PDU session, and the multiple members belong to one Eth-Trunk group; the processing unit 1701 is configured to select a target member according to the link states of the multiple members; the transceiver unit 1702 is further configured to send the first data of the PDU session corresponding to the target member Bag.
  • the link status is used to indicate that the member's link is the primary link or the backup link, and/or the link status is used to indicate whether the member's link is faulty.
  • the processing unit 1701 is specifically configured to select a target member from the multiple members by using a hash algorithm according to the link status of the multiple members.
  • the transceiver unit 1702 is further configured to receive a first message, where the first message is used to establish a first PDU session, the first message includes information of an Eth-Trunk group, the Eth-Trunk The information of the Trunk group includes the attributes of the Eth-Trunk group;
  • the processing unit 1701 is further configured to establish a first PDU session according to the first message; if the attribute of the first PDU session matches the attribute of the Eth-Trunk group, add the attribute in the Eth-Trunk group. the member corresponding to the first PDU session.
  • the information of the Eth-Trunk group further includes the link detection type of the member, wherein the link detection type of the member includes link aggregation control protocol LACP detection, or bidirectional forwarding detection BFD detection, or LACP detection Joint detection with BFD;
  • the processing unit 1701 is further configured to detect the link state of the member corresponding to the first PDU session according to the link detection type of the member.
  • the information of the Eth-Trunk group further includes one or more of the following: the identifier of the Eth-Trunk group, the link type of the member, the maximum number of links in the Eth-Trunk group, the Eth-Trunk group Minimum number of links in the group, link priority in the Eth-Trunk group.
  • the transceiver unit 1702 may be specifically configured to periodically acquire link states of multiple members.
  • the processing unit 1701 is further configured to release the PDU session corresponding to the first member or retain the PDU session corresponding to the first member if the link of the first member fails, and record the The state of the PDU session corresponding to the first member is abnormal; wherein the first member is any one of the multiple members.
  • the first data packet includes information used to indicate that the first data packet is from a second member;
  • the processing unit 1701 is specifically configured to, according to the link states of the multiple members, In the members in other Eth-Trunk groups except the Eth-Trunk group to which the second member belongs, determine the target member;
  • the transceiver unit 1702 is specifically configured to use the link of the target member, through the second member The device sends the first data packet of the PDU session corresponding to the target member.
  • the second device when the communication device is a first user plane network element, the second device is the second user plane network element.
  • the transceiver unit 1702 is further configured to send the link status of the multiple members to the second device.
  • the transceiver unit 1702 is specifically configured to send the link status of the multiple members to the second device through a session management network element.
  • the transceiver unit 1702 is further configured to receive a second message, where the second message is used to notify that multiple PDU sessions belong to one Eth-Trunk group, and the multiple PDU sessions correspond to one slice and data A combination of network name DNNs.
  • the processing unit 1701 is further configured to learn the MAC address of the newly accessed terminal device; update the MAC address in the Eth-Trunk group according to the learned MAC address of the newly accessed terminal device, and/or reporting the MAC address of the newly accessed terminal device to the session management network element through the transceiver unit; wherein the newly accessed terminal device belongs to the Eth-Trunk group, and the newly accessed terminal device belongs to the Eth-Trunk group.
  • the terminal device corresponds to one PDU session or to multiple PDU sessions.
  • the transceiver unit 1702 is further configured to send the link status of the third member to one or more user plane network elements if the link status of the third member changes.
  • all members of the Eth-Trunk group can be deployed on one user plane network element; the processing unit 1701 is specifically configured to, according to the link states of the multiple members, and the Eth-Trunk The identity of the trunk group determines the target member, and the user plane network element is deployed on the link of the target member.
  • the transceiver unit 1702 is further configured to acquire the information of the Eth-Trunk group from the data management network element.
  • the transceiver unit 1702 is further configured to send a second message, where the second message is used to establish a first PDU session, and the second message includes the information of the Eth-Trunk group.
  • the transceiver unit 1702 is further configured to learn the MAC address of a newly accessed terminal device, wherein the newly accessed terminal device belongs to the Eth-Trunk group, and the newly accessed terminal device belongs to the Eth-Trunk group.
  • the device corresponds to one PDU session or multiple PDU sessions; and sends the MAC address of the newly accessed terminal device to one or more user plane network elements.
  • the transceiver unit 1702 is configured to receive a third message, where the third message is used to request to update the Eth-Trunk group; the processing unit 1701 is configured to use For updating the information of the currently saved Eth-Trunk group; wherein, the information of the Eth-Trunk group includes the information of the members in the Eth-Trunk group.
  • each functional unit in each embodiment of the present application It can be integrated in one processing unit, or it can exist physically alone, or two or more units can be integrated in one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
  • the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .
  • an embodiment of the present application further provides a schematic structural diagram of a communication apparatus 1800 .
  • the apparatus 1800 may be used to implement the methods described in the foregoing method embodiments, and reference may be made to the descriptions in the foregoing method embodiments.
  • the apparatus 1800 includes one or more processors 1801 .
  • the processor 1801 may be a general-purpose processor or a special-purpose processor, or the like.
  • it may be a baseband processor, or a central processing unit.
  • the baseband processor may be used to process communication protocols and communication data
  • the central processing unit may be used to control communication devices (eg, base stations, terminals, or chips, etc.), execute software programs, and process data of software programs.
  • the communication device may include a transceiving unit for implementing signal input (reception) and output (transmission).
  • the transceiver unit may be a transceiver, a radio frequency chip, or the like.
  • the apparatus 1800 includes one or more of the processors 1801, and the one or more processors 1801 can implement the methods in the above-described embodiments.
  • the processor 1801 may also implement other functions in addition to implementing the methods in the above-described embodiments.
  • the processor 1801 may execute an instruction, so that the apparatus 1800 executes the method described in the foregoing method embodiments.
  • the instructions may be stored in whole or in part within the processor, such as instruction 1803, or may be stored in whole or in part in a memory 1802 coupled to the processor, such as instruction 1804, or may be jointly caused by instructions 1803 and 1804.
  • the apparatus 1800 executes the methods described in the above method embodiments.
  • the communication apparatus 1800 may also include a circuit, and the circuit may implement the functions in the foregoing method embodiments.
  • the apparatus 1800 may include one or more memories 1802 having stored thereon instructions 1804 that may be executed on the processor to cause the apparatus 1800 to perform the above-described method methods described in the examples.
  • data may also be stored in the memory.
  • Instructions and/or data may also be stored in the optional processor.
  • the one or more memories 1802 may store the correspondences described in the foregoing embodiments, or related parameters or tables involved in the foregoing embodiments, and the like.
  • the processor and the memory can be provided separately or integrated together.
  • the apparatus 1800 may further include a transceiver 1805 and an antenna 1806 .
  • the processor 1801 may be called a processing unit, and controls the device (terminal or base station).
  • the transceiver 1805 may be referred to as a transceiver, a transceiver circuit, or a transceiver unit, etc., and is used to implement the transceiver function of the device through the antenna 1806 .
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • Embodiments of the present application further provide a computer-readable medium on which a computer program is stored, and when the computer program is executed by a computer, implements the communication method described in any of the foregoing method embodiments.
  • An embodiment of the present application further provides a computer program product, which implements the communication method described in any of the above method embodiments when the computer program product is executed by a computer.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, optical fiber, Digital Subscriber Line, DSL) or wireless (eg infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state disks, SSD)) etc.
  • An embodiment of the present application further provides a processing apparatus, including a processor and an interface; the processor is configured to execute the communication method described in any of the above method embodiments.
  • the above-mentioned processing device may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software
  • the processor can be a general-purpose processor, which is realized by reading the software codes stored in the memory, and the memory can be integrated in the processor, and can be located outside the processor and exist independently.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of units is only a logical function division.
  • there may be other division methods for example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium can be any available medium that a computer can access.
  • computer readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or be capable of carrying or storing instructions or data structures in the form of desired program code and any other medium that can be accessed by a computer. also.
  • any connection can be appropriately made into a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable , fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the fusing of the pertinent medium.
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and blu-ray disc, where disks generally reproduce data magnetically, and discs Lasers are used to optically copy data. Combinations of the above should also be included within the scope of computer-readable media.

Landscapes

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

Abstract

本申请实施例提供一种通信方法、装置及芯片，用以节省切片和DNN资源，降低对网络侧的要求。所述方法包括：第一设备获取多个成员的链路状态，每个成员对应一个协议数据单元PDU会话，所述多个成员属于一个Eth-Trunk组；所述第一设备根据所述多个成员的链路状态，选择目标成员，并发送所述目标成员对应的PDU会话的第一数据包。

Description

一种通信方法、装置及芯片 技术领域
本申请涉及无线通信技术领域，尤其涉及一种通信方法、装置及芯片。
背景技术
终端设备单节点接入网络，且终端设备与数据网络(data network，DN)之间单链路连接，如果终端设备发生故障，或者终端设备与DN之间任意一段链路发生故障，则网络连接失败，导致业务通信失败。
为了避免终端设备与DN之间任意一段链路发生故障影响上层业务，第三代合作伙伴项目(3rd generation partnership project，3GPP)中定义了多链路通信方式，在多链路通信方式中，终端设备通过主备两条链路接入DN，例如终端设备通过接入网设备1和用户面网元1接入DN，且所述终端设备通过接入网设备2和用户面网元2接入DN。此时所述终端设备需要支持两个协议数据单元(protocol data unit，PDU)会话，网络侧配置PDU会话的双连接方式。所述终端设备与DN进行业务通信时，发送端通过接入网设备1和用户面网元1向接收端发送数据包，且所述发送端通过接入网设备2和用户面网元2向所述接收端发送数据包，所述接收端对接收到的两个数据包进行去重。这样，若所述终端设备与DN之间某一条链路发生故障，所述终端设备与所述DN通过另一条链路进行正常的业务通信。
但是在多链路通信方式中，终端设备需要建立两个PDU会话，并且每个PDU会话绑定一个“切片+数据网络名称(data network name，DNN)”组合，浪费切片和DNN资源。该多链路通信方式需要DN侧进行同步修改，多发选收对网络侧提出了更高的要求。
发明内容
本申请实施例提供一种通信方法、装置及芯片，从而节省切片和DNN资源，且不必须对网络侧进行改进。
第一方面，提供一种通信方法，包括如下过程：第一设备获取多个成员的链路状态，每个成员对应一个协议数据单元PDU会话，所述多个成员属于一个Eth-Trunk组；所述第一设备根据所述多个成员的链路状态，选择目标成员，并发送所述目标成员对应的PDU会话的第一数据包。其中，所述第一设备为发送方。所述第一设备可以为用户面网元、端侧设备(如交换设备/终端设备)或会话管理网元中的任意一个。
在该方法中，发送方和接收方之间部署有多条链路，链路为Eth-Trunk组中成员的链路，发送方根据多条链路的链路状态，选择目标成员及目标成员的链路，将目标成员的链路作为活动链路进行业务通信。也就是说可以采用一条链路进行业务通信，无需过多占用切片和DNN资源，也不必须对网络侧进行修改，可以降低对网络侧的要求。并且通过链路状态选择目标成员，可以避免链路发生故障时对业务通信的影响，保障正常的业务通信。
在一种可能的实现中，所述链路状态可以用于指示成员的链路为主链路或备链路，和/或所述链路状态用于指示成员的链路是否故障。在该实现中，第一设备可以优先选择优先级高的主链路和/或无故障的链路，从而提高业务通信的可靠性。
在一种可能的实现中，在根据所述多个成员的链路状态，选择目标成员时，所述第一设备可以根据所述多个成员的链路状态，采用哈希Hash算法，在所述多个成员中选择目标成员。
在该实现中，Hash值可以与出接口对应，第一设备根据多个成员的链路状态，通过Hash算法可以计算出目标出接口，从而根据出接口选择目标成员及目标成员的链路。
在一种可能的实现中，所述第一设备可以为用户面网元，例如所述第一设备为第一用户面网元。在获取多个成员的链路状态之前，所述第一用户面网元还可以接收第一消息，所述第一消息用于建立第一PDU会话，所述第一消息包括Eth-Trunk组的信息，所述Eth-Trunk组的信息包括所述Eth-Trunk组的属性；所述第一用户面网元根据所述第一消息建立第一PDU会话；若所述第一PDU会话的属性与所述Eth-Trunk组的属性匹配，所述第一用户面网元在所述Eth-Trunk组中添加所述第一PDU会话对应的成员。在该实现中，用户面网元可以对Eth-Trunk组的信息进行维护。
在一种可能的实现中，所述Eth-Trunk组的信息还包括成员的链路检测类型，其中所述成员的链路检测类型包括链路聚合控制协议LACP检测、或者双向转发检测BFD检测、或者LACP与BFD联合检测。从而，所述第一设备还可以按照所述成员的链路检测类型，检测所述第一PDU会话对应的成员的链路状态。在该实现中，第一设备上可以实现LACP/BFD协议，从而对成员的链路状态进行检测，避免链路发生故障时对业务通信的影响。
所述Eth-Trunk组的信息还可以包括以下一种或多种：Eth-Trunk组的标识、成员的链路类型、Eth-Trunk组中的最大链路数量、Eth-Trunk组中的最小链路数量、Eth-Trunk组中的链路优先级。
在一种可能的实现中，所述第一设备可以周期性的获取多个成员的链路状态。在该实现中，第一设备通过周期性获取成员的链路状态，进一步提高业务通信的可靠性。
在一种可能的实现中，所述第一设备可以为用户面网元，例如所述第一设备为第一用户面网元。在获取多个成员的链路状态之后，若第一成员的链路发生故障，所述第一用户面网元可以释放所述第一成员对应的PDU会话，或者所述第一用户面网元可以保留所述第一成员对应的PDU会话，并记录所述第一成员对应的PDU会话的状态异常。其中所述第一成员为所述多个成员中的任意一个成员。这样，用户面网元可以对PDU会话的状态进行维护，进一步提高业务通信的可靠性。
在一种可能的实现中，所述第一设备可以为用户面网元，例如所述第一设备为第一用户面网元。所述第一数据包中可以包括用于指示所述第一数据包来自第二成员的信息。相应的，在根据所述多个成员的链路状态，选择目标成员，并发送所述目标成员对应的PDU会话的第一数据包时，所述第一用户面网元可以根据所述多个成员的链路状态，在除所述第二成员所属的Eth-Trunk组外的其他Eth-Trunk组中的成员中，确定目标成员；所述第一用户面网元采用所述目标成员的链路，通过第二设备发送所述目标成员对应的PDU会话的第一数据包。可选的，所述第二设备可为第二用户面网元。
在该实现中，第一设备不在同一Eth-Trunk组内选择链路转发数据包，可以避免广播数据的闭环泛洪。
在一种可能的实现中，所述第一设备可以为用户面网元，例如所述第一设备为第一用户面网元。所述第一用户面网元还可以将所述多个成员的链路状态发送给所述第二设备。 这样，多个用户面网元之间可以同步Eth-Trunk组内多个成员的链路状态，使得多个用户面网元之间保存的Eth-Trunk组的信息一致。
在一种可能的实现中，所述第一设备可以为用户面网元，例如所述第一设备为第一用户面网元。在将所述多个成员的链路状态发送给所述第二设备时，所述第一用户面网元可以通过会话管理网元，将所述多个成员的链路状态发送给所述第二设备。
在一种可能的实现中，所述第一设备可以为端侧设备。在获取多个成员的链路状态之前，所述端侧设备还可以接收第二消息，所述第二消息用于通知多个PDU会话属于一个Eth-Trunk组，所述多个PDU会话对应一个切片和数据网络名称DNN的组合。这样，端侧设备可以感知多个PDU会话构成Eth-Trunk组。
在一种可能的实现中，所述第一设备可以为用户面网元，例如所述第一设备为第一用户面网元。所述第一用户面网元还可以学习新接入的终端设备的MAC地址；所述第一用户面网元根据学习的所述新接入的终端设备的MAC地址更新Eth-Trunk组中的MAC地址，和/或所述第一用户面网元将所述新接入的终端设备的MAC地址上报给会话管理网元。其中所述新接入的终端设备属于所述Eth-Trunk组，所述新接入的终端设备对应一个PDU会话或对应多个PDU会话。这样，可以进一步提高业务通信的可靠性。
在一种可能的实现中，所述第一设备可以为会话管理网元。在获取多个成员的链路状态之后，若第三成员的链路状态发生改变，所述会话管理网元还可以将所述第三成员的链路状态发送给一个或多个用户面网元。从而保证一个或多个用户面网元及时获取到成员的链路状态，且进一步保证用户面网元之间保存的Eth-Trunk组的信息一致。
在一种可能的实现中，所述Eth-Trunk组的所有成员部署在一个用户面网元上。所述第一设备可以为会话管理网元。这样，在根据所述多个成员的链路状态，选择目标成员时，所述会话管理网元可以根据所述多个成员的链路状态，以及所述Eth-Trunk组的标识，确定目标成员，所述目标成员的链路上部署有所述用户面网元。这样可以将Eth-Trunk组中的成员的PDU会话部署在该一个用户面网元上。
在一种可能的实现中，所述第一设备可以为会话管理网元。所述会话管理网元还可以从数据管理网元中获取Eth-Trunk组的信息。相应的，所述第一会话管理网元还可以发送第二消息，所述第二消息用于建立第一PDU会话，所述第二消息包括所述Eth-Trunk组的信息。
在一种可能的实现中，所述第一设备可以为会话管理网元。所述会话管理网元还可以学习新接入的终端设备的MAC地址，其中所述新接入的终端设备属于所述Eth-Trunk组，所述新接入的终端设备对应一个PDU会话或对应多个PDU会话；所述会话管理网元将所述新接入的终端设备的MAC地址，可以发送给一个或多个用户面网元。
第二方面，提供一种通信方法，包括以下步骤：第三设备接收第三消息，所述第三消息用于请求更新Eth-Trunk组；所述第三设备对当前保存的Eth-Trunk组的信息进行更新；其中，所述Eth-Trunk组的信息包括Eth-Trunk组中的成员的信息。
所述第三设备可以为数据管理网元。
第三方面，提供一种通信系统，包括至少一个端侧设备和至少一个用户面网元，所述至少一个端侧设备和所述至少一个用户面网元之间连接；所述至少一个端侧设备用于执行第一方面及其任一方面所述的方法；所述至少一个用户面网元用于执行第一方面及其任一方面所述的方法。
在一种可能的实现中，所述通信系统包括多个端侧设备和一个用户面网元，所述通信系统还包括交换设备；所述交换设备的每个端口分别与每个端侧设备连接，每个端侧设备对应一个PDU会话，所述多个端侧设备对应的PDU会话组成一个Eth-Trunk组，所述Eth-Trunk组中的成员部署在同一个用户面网元上。
在一种可能的实现中，所述通信系统包括多个端侧设备和多个用户面网元，每两个用户面网元之间连接，所述通信系统还包括交换设备；所述交换设备的每个端口分别与每个端侧设备连接，每个端侧设备对应一个PDU会话，所述多个端侧设备对应的PDU会话组成一个Eth-Trunk组，所述Eth-Trunk组中的成员存在至少两个成员分别部署在不同用户面网元上。
在一种可能的实现中，所述通信系统包括多个端侧设备和多个用户面网元，每两个端侧设备之间连接，每两个用户面网元之间连接；每个端侧设备对应一个PDU会话，所述多个端侧设备对应的PDU会话组成一个Eth-Trunk组，所述Eth-Trunk组中的成员存在至少两个成员分别部署在不同用户面网元上。
在一种可能的实现中，所述通信系统包括一个端侧设备和多个用户面网元，每两个用户面网元之间连接；所述端侧设备对应多个PDU会话，所述多个PDU会话组成一个Eth-Trunk组，所述Eth-Trunk组中的成员存在至少两个成员分别部署在不同用户面网元上。
第四方面，提供一种通信装置，该通信装置具有实现上述第一方面及其任一可能设计提供的任一方法的功能。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。
示例性的，所述单元或模块可以为处理单元和收发单元。该处理单元被配置为支持该通信装置执行以上所示方法中第一设备的相应功能。收发单元，用于所述通信装置收发数据或信息。
在一种可能的实现方式中，该通信装置还可以包括存储单元，该存储单元可以与处理单元耦合，其保存该通信装置必要的程序指令和数据。
第五方面，提供一种通信装置，该通信装置具有实现上述第二方面提供的任一方法的功能。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。
示例性的，所述单元或模块可以为处理单元和收发单元。该处理单元被配置为支持该通信装置执行以上所示方法中第三设备的相应功能。收发单元，用于所述通信装置收发数据或信息。
在一种可能的实现方式中，该通信装置还可以包括存储单元，该存储单元可以与处理单元耦合，其保存该通信装置必要的程序指令和数据。
第六方面，提供一种计算机可读存储介质，用于存储计算机程序，该计算机程序包括用于执行第一方面、第二方面，或第一方面、第二方面中任一种可能实现方式中的方法的指令。
第七方面，提供一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面、第二方面，或第一方面、第二方面中任一种可能实现方式中的方法。
第八方面，提供一种芯片系统，该芯片系统包括收发器，用于实现上述各方面的方法中的功能，例如，例如接收或发送上述方法中所涉及的数据和/或信息。
在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
上述第二方面至第八方面任一方面可以达到的技术效果，请参照上述第一方面可以带来的技术效果描述，这里不再重复赘述。
附图说明
图1为一种5G网络架构示意图；
图2为一种5G LAN网络架构示意图；
图3为一种多链路通信的网络架构示意图；
图4为本申请提供的一种Eth-Trunk参数配置过程示意图；
图5、图7、图9、图10、图14、图15、图16为本申请提供的一种可能的通信流程示意图；
图6、图8、图11、图12、图13为本申请提供的一种的可能的通信系统架构示意图；
图17、图18为本申请提供的一种通信装置示意图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
以下对本申请实施例的部分用语进行解释说明，以便于本领域技术人员理解。
1)用户设备，也称终端设备，是一种具有无线收发功能的设备，可以经无线接入网(radio access network，RAN)中的接入网设备(或者也可以称为接入设备)与一个或多个核心网(core network，CN)设备(或者也可以称为核心设备)进行通信。
用户设备也可称为接入终端、终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、用户代理或用户装置等。用户设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。用户设备可以是蜂窝电话(cellular phone)、无绳电话、会话启动协议(session initiation protocol，SIP)电话、智能电话(smart phone)、手机(mobile phone)、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)等。或者，用户设备还可以是具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备、无人机设备或物联网、车联网中的终 端、第五代移动通信(5th-generation，5G)网络以及未来网络中的任意形态的终端、中继用户设备或者未来演进的PLMN中的终端等。其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。例如用户设备可以是虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。本申请实施例对终端设备的类型或种类等并不限定。
所述用户设备还可以包括端侧设备，如本地交换机(local switch，LSW)，和/或客户端设备(customer premise equipment，CPE)等。
在本申请实施例中注册入网的用户设备(user equipment，UE)可以理解为用户。其中一个UE可以对应一个用户识别模块(subscriber identity module，SIM)卡，即当终端设备安装有一个SIM卡时，终端设备对应一个用户UE，当终端设备安装有多个SIM卡时，终端设备对应多个用户UE。
2)网络设备，指可以为终端提供无线接入功能的设备。其中，网络设备可以支持至少一种无线通信技术，例如长期演进(long term evolution，LTE)、新无线(new radio，NR)、宽带码分多址(wideband code division multiple access，WCDMA)等。
例如网络设备可以包括接入网设备。示例的，网络设备包括但不限于：5G网络中的下一代基站或下一代节点B(generation nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved node B、或home node B，HNB)、基带单元(baseband unit，BBU)、收发点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心、小站、微型站等。网络设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、集中单元(centralized unit，CU)、和/或分布单元(distributed unit，DU)，或者网络设备可以为中继站、接入点、车载设备、终端、可穿戴设备以及未来移动通信中的网络设备或者未来演进的公共移动陆地网络(public land mobile network，PLMN)中的网络设备等。
又如，网络设备可以包括核心网(CN)设备，核心网设备例如包括AMF等。
3)链路聚合组(Link Aggregation)是指将一组(group)物理端口捆绑在一起作为一个逻辑接口来增加带宽和提高可靠性的一种方法，又可称为多端口负载均衡组(Load Sharing Group)。如果这些被捆绑链路都是以太网链路，该聚合组则被称为以太网链路聚合组(Eth-Trunk组)。
例如设备(Device)A与Device B之间通过三条以太网物理链路相连，将这三条链路捆绑在一起，成为一条逻辑链路，这条逻辑链路的最大带宽等于该三条以太网物理链路的带宽总和，增加了链路带宽，并且，这三条以太网物理链路相互备份，可以提高链路的可靠性。
每个链路聚合组唯一对应一个逻辑接口，这个逻辑接口称为聚合接口或Eth-Trunk接口。组成Eth-Trunk接口的各个物理接口称为成员接口。成员接口对应的链路称为成员链路。在以太网协议栈中，Eth-Trunk接口位于媒体访问控制(media access control，MAC) 子层与逻辑链路控制(logical link control，LLC)子层之间，属于数据链路层(data link layer)。
4)链路聚合控制协议(link aggregation control protocol，LACP)，是一种链路聚合模式，负责维护链路状态。设备通过LACP消息向对端设备发送系统优先级、MAC地址、接口优先级、接口号和操作Key(用来判断各接口相连对端是否在同一聚合组以及各接口带宽是否一致等)等信息。对端设备将接收到信息与自身保存的信息比较，选择活动链路。一般的，活动链路对应的接口为活动接口，非活动链路对应的接口为非活动接口。活动接口为转发数据的接口，非活动接口为不转发数据的接口。
系统优先级可以用于区分同一Eth-Trunk组中的不同接口/链路的优先级。可选的，设备之间的链路包括主链路和备链路，主链路的优先级高于备链路的优先级。不同的备链路之间可以设置相同的优先级，或者设置不同的优先级。
5)双向转发检测(bidirectional forwarding detection，BFD)，是一种检测方式。BFD的检测机制是在两个设备之间建立BFD会话，并沿它们之间的链路(周期性)发送BFD控制报文，如果一方在规定的时间内没有收到BFD控制报文，则认为链路上发生了故障。
可以理解的是，LACP检测和BFD检测可以单独使用，也可以联合使用。“获取”、“检测”、“协商”链路状态的概念之间可以替换使用。
6)PDU会话，是终端设备和DN之间交互PDU数据包的业务会话。PDU会话通过建立PDU连接实现。在本申请实施例中，PDU会话也称PDU UE会话，或者UE会话，或者以太会话。
可选的，PDU会话绑定一个“切片+DNN”组合，即PDU会话对应一对切片+DNN的信息。切片可以采用单一网络切片选择辅助信息S-NSSAI标识。或者，PDU会话绑定一个“切片+DNN+会话标识(SessionID)”组合，即PDU会话对应一对切片+DNN和SessionID的信息。对于不同的PDU会话，SessionID不同，切片+DNN可以相同或不同。
本申请中的“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请中所涉及的多个，是指两个或两个以上。
另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
本申请实施例的技术方案可以应用于各种通信系统(也称无线通信系统)。通信系统通常包括但不限于第四代移动通信(4th-generation，4G)网络、LTE系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、5G通信系统或NR以及未来的其他通信系统如6G等。
3GPP标准组制定了下一代移动通信网络架构(Next Generation System)，称为5G网络架构。5G网络架构支持采用3GPP标准组定义的无线技术(如LTE、5G RAN等)，固定网络等接入方式接入核心网侧。
为了便于理解本申请实施例，以图1所示的5G网络架构为例对本申请使用的应用场景进行说明。图1为3GPP标准化过程中定义的5G网络架构。所述网络架构中可以包括： 终端设备部分、网络设备部分和数据网络(data network，DN)部分。
网络设备部分包括接入网(access network，AN)102、用户面功能(user plane function，UPF)103、接入与移动性管理功能(access and mobility management function，AMF)105、会话管理功能(session management function，SMF)106、策略控制功能(policy control function，PCF)107、统一数据管理功能(unified data management，UDM)108、统一数据仓库(unified data repository，UDR)110等。可选的，网络部分还可以包括应用功能(application function，AF)109和/或网络开放功能(network exposure function，NEF)109。上述网络设备中，除接入网102部分之外的部分可以称为核心网部分。
数据网络DN 104，也可以称为分组数据网络(packet data network，PDN)，通常可以部署在运营商网络之外，例如第三方网络。示例性的，运营商网络可以接入多个数据网络DN 104，数据网络DN 104上可部署多种业务，从而为终端设备101提供数据和/或语音等服务。
应用功能AF用于传递应用侧对网络侧的需求，例如服务质量(quality of service，QoS)需求或用户状态事件订阅等。AF可以是第三方功能实体(即第三方应用的应用功能实体)，可以是运营商部署的应用服务，如互联网协议(internet protocol，IP)多媒体子系统(IP multimedia subsystem，IMS)语音呼叫业务。若AF为第三方功能实体，AF与核心网进行交互时，可以经由NEF进行授权处理，例如，AF向NEF发送请求消息，NEF判断该AF是否被允许发送该请求消息，若允许，NEF将该请求消息转发给对应的PCF107或UDM108。
AN 102，也称无线(Radio)AN，是运营商网络的子网络，是运营商网络中业务节点(或网络功能)与终端设备101之间的实施系统。终端设备101要接入运营商网络，首先是经过AN 102，进而通过AN 102与运营商网络中的业务节点连接。本申请实施例中的AN 102，可以指代接入网本身，也可以指接入网设备，此处不作区分。采用不同无线接入技术的系统中，具备接入网设备功能的设备的名称可能会有所不同，接入方式也可能会有所不同(如有线接入方式、无线基站接入方式等)。
用户面功能UPF103是运营商网络与DN 104通信的网关。UPF103可以完成用户面数据转发、基于会话级/流级的计费统计、带宽限制等功能。
接入与移动性管理功能AMF 105负责对终端设备101进行移动性管理、接入鉴权/授权等功能。此外，AMF 105还可以负责在终端设备101与PCF107间传递用户策略。
会话管理功能SMF 106负责管理终端设备101的协议数据单元(protocol data unit，PDU)会话、执行PCF107下发控制策略、选择UPF、在PDU类型为IP类型时分配终端设备101的IP地址。
策略控制功能PCF107负责针对会话级/流级的计费、QoS带宽保障及移动性管理、终端设备策略决策等策略控制功能。
统一数据管理UDM 108负责管理签约数据、用户接入授权等功能。
统一数据仓库UDR110负责签约数据、策略数据、应用数据等类型数据的存取功能。
图1所示的网络架构还可以包括其他网络功能，本申请实施例对其他网络功能不做限定。
图1中N1、N2、N3、N4、N5、N6、N7、N8、N9、N10、N11、N15、N35，以及N36为接口序列号。示例性的，上述接口序列号的含义可参见3GPP标准协议中定义的含义，本申请对于上述接口序列号的含义不做限制。需要说明的是，图1中的各个网络功能 之间的接口名称仅仅是一个示例，在具体实现中，该系统架构的接口名称还可能为其他名称，本申请对此不作限定。
为方便说明，本申请实施例中将用户面功能UPF103简称为UPF，即本申请实施例中后文所描述的UPF均可替换为用户面功能。可理解，其他未示出的网络功能同样适用该替换方法。
3GPP定义了5G局域网(local area network，LAN)服务，在移动网络通过5G LAN服务为用户构建虚拟移动专网。5G LAN可以在更广泛的移动网络覆盖范围内使用，即无论用户是否在同一地域，只要加入同一5G LAN，即可实现基于LAN的数据交换和通信。
终端设备通过建立PDU连接实现终端设备与DN之间的数据交换。5G LAN在目前PDU连接的基础上，增加了组(group)的概念。移动网络内可同时支持多个5G LAN group(简称group)。归属于同一个5G LAN group(简称group)的终端设备可以与group对应的DN进行数据交换，也可以通过UPF与同一group内的其他终端设备完成数据交换。即同一group内的终端设备之间可以相互通信，不同group之间的终端设备相互隔离。在本申请实施例中主要以5G LAN group为Eth-Trunk组进行说明。
终端设备与DN或终端设备与终端设备进行数据交换时，支持IPv4、IPv6、以太会话等会话类型。在以太会话中UPF根据目标MAC地址转发数据包。如图2为一种5G LAN网络架构，包括端侧设备、网络侧设备、DN侧设备，端侧设备包括个人计算机(personal computer，PC)1、L2交换机(switch，SW)、CPE1/UE1、PC2、CPE2/UE2、PC3和CPE3/UE3，网络侧设备包括gNB1、UPF1、gNB2、gNB3和UPF2，DN侧设备包括DN SW和PC4。图2的5G LAN网络下支持端侧设备本地交换(如PC1与PC2进行数据交换)，端侧设备与DN侧设备交换(也即跨网交换，如PC1与PC4进行数据交换)，以及端侧设备跨UPF交换(如PC2与PC3进行数据交换)。在图2中，终端设备可以指PC1、PC2、PC3和PC4。
CPE/UE在数据面主要起到桥接作用，CPE/UE后面(如在PC1的位置)可以再连接交换机(LSW)，如CPE1/UE1连接L2 SW。CPE/UE可以在会话建立消息中携带的会话类型为以太网(Ethernet)类型。
UPF学习端侧设备或DN侧设备发送数据包的源MAC地址，并根据学习到的MAC地址在后续转发的数据包时配置目的MAC地址进行转发。例如配置目的MAC地址与学习到的MAC地址不同。
在图1所示的5G网络架构中，终端设备单节点接入网络，并且终端设备到DN之间单链路连接，如果终端设备故障，或终端设备到DN间任意一段链路故障，则网络连接失败，也会导致业务通信失败。为了避免终端设备到DN之间任意一段链路发生故障影响上层业务，3GPP中定义了多链路通信方式。在多链路通信方式中，终端设备通过主备两条链路接入DN。例如图3所示，终端设备通过(R)AN1和UPF1接入DN，且终端设备通过(R)AN2和UPF2接入DN。此时终端设备需要支持两个PDU会话，网络侧配置PDU会话的双连接方式。在进行业务通信时，发送端(如终端设备或DN)通过(R)AN1和UPF1发送数据包1，且通过(R)AN2和UPF2发送数据包2，接收端(如DN或终端设备)对接收到的两个数据包1进行去重。若终端设备与DN之间的某一条链路发生故障，终端设备与DN可以通过另一条链路进行正常的业务通信。
但是在多链路通信方式中，终端设备需要建立两个PDU会话，并且每个PDU会话绑定一个“切片(S-NSSAI)+数据网络名称(data network name，DNN)”组合，浪费切片和DNN资源。且该多链路通信方式需要DN侧进行同步修改，多发选收对网络侧提出了更高的要求。
基于此，本申请实施例提供一种通信方法。在该方法中，第一设备获取多个成员的链路状态，每个成员对应一个协议数据单元PDU会话，所述多个成员属于一个Eth-Trunk组；所述第一设备根据所述多个成员的链路状态，选择目标成员，并发送所述目标成员对应的PDU会话的第一数据包。所述第一设备作为发送方，与接收方之间部署有多条链路，链路为Eth-Trunk组中成员的链路，发送方根据多条链路的链路状态，选择目标成员及目标成员的链路，将目标成员的链路作为活动链路进行业务通信。也就是说可以采用一条链路进行业务通信，无需过多占用切片和DNN资源，也不必须对网络侧进行修改，降低网络侧的要求。并且通过链路状态选择目标成员，可以避免链路发生故障时对业务通信的影响，保障正常的业务通信。
本申请实施例提供的通信方法可以应用于图1或图2所示的通信系统中。在通信系统中可以增加Eth-Trunk的定义，并将Eth-Trunk参数对外开放(可选的，通过NEF对外开放)。可选的，UDR中可以保存Eth-Trunk参数，或者第三方在DN-认证授权计费(authentication authorization accounting，AAA)中保存Eth-Trunk参数。具有相同属性的成员(CPE/UE)对应相同的Eth-Trunk参数，具有相同属性的成员可以看作属于同一Eth-Trunk组，Eth-Trunk组的信息包括Eth-Trunk参数。在通信系统中，多个端侧设备(CPE/UE)可以接入层二5GLAN，并组成一个Eth-Trunk组。一个Eth-Trunk组内的所有CPE/UE成员可以按照主备或负荷分担等方式转发数据包，保证业务通信的可靠性。
在一个可能的实施例中，AF向NEF提供Eth-Trunk数据参数和Eth-Trunk成员参数。可选的，Eth-Trunk参数包括Eth-Trunk数据参数和/或Eth-Trunk成员参数。或者可选的，Eth-Trunk组的属性包括Eth-Trunk数据参数和/或Eth-Trunk成员参数。
所述Eth-Trunk数据参数包括以下一种或多种：组外部标识(External Group ID)、Eth-Trunk标识(TrunkId)、链路类型(LinkType)、允许接入的虚拟局域网(virtual local area network，VLAN)标识(AllowVlanList)、链路检测类型(LinkCheckType)、最大链路数量(MaxLinkNum)和最小链路数量(MinLinkNum)。组外部标识可以指5G虚拟网络(virtual network，VN)组外部标识。例如所述链路类型包括接入(Access)类型或Trunk类型。所述链路检测类型包括LACP、BFD或LACP+BFD等。可选的，所述组外部标识，所述Eth-Trunk标识，所述链路类型为必选参数。可选的，所述链路类型为Trunk类型时，所述允许接入的VLAN标识为必选参数，否则，所述允许接入的VLAN标识为可选参数。所述链路检测类型，所述最大链路数量，所述最小链路数量为可选参数。
所述Eth-Trunk成员参数包括以下一种或多种：成员标识、组外部标识、Eth-Trunk标识和成员优先级(Priority)。所述成员标识为5G VN成员标识，可以采用通用公共用户标识(generic public subscription identifier，GPSI)进行标识。
Eth-Trunk数据参数和Eth-Trunk成员参数可以以表格的形式进行保存。表格的键值(key值)可以为External Group ID+TrunkId。
以图4为例说明，将上述Eth-Trunk参数配置到UDR中。DN侧将上述Eth-Trunk参 数配置到DN侧的AAA中，这里不做详细说明。
可选的，通信系统中的网络侧设备支持Eth-Trunk特性。端侧设备(CPE/UE)可能支持或不支持Eth-Trunk特性。在后续实施例中，除额外说明，端侧设备包括CPE和/或CE。
S401：AF调用NEF提供的接口，发送创建(Create)/更新(Update)/删除(Delete)请求消息，实现对Eth_Trunk进行管理。
其中NEF提供的接口包括Nnef_ParameterProvision_Create/Update/Delete等接口。所述NEF提供的接口为已授权的接口。
S402：NEF通过UDM提供的接口，发送Create/Update/Delete请求消息，请求UDM创建/更新/存储/删除对应的签约数据。
UDM提供的接口包括Nudm_ParameterProvision_Create/Update/Delete等接口。
可选的，NEF确定AF发送的请求消息为已授权请求时，执行S402。若NEF确定AF发送的请求消息为未授权请求，NEF可以直接向AF返回响应消息(可参见S406)，并发送失败原因。
S403：UDM通过UDR提供的接口发起数据查询请求，以完成对AF创建/更新/删除请求的检验与授权。
UDR提供的接口包括Uudr_DM_Query等接口。
S404：UDM通过UDR提供的接口将创建/更新/删除请求消息发送给UDR，实现对Eth-Trunk的信息的创建/更新/删除。
例如，针对创建Eth-Trunk的请求消息，UDM可以调用UDR提供的Nudr_DM_Create接口。
又如，针对更新Eth-Trunk的请求消息，UDM可以调用UDR提供的Nudr_DM_Update接口。所述更新Eth-Trunk的请求消息可以用于更新Eth-Trunk成员的信息，和/或更新Eth-Trunk数据的信息。
若S404执行成功，则针对向UDM订阅了签约信息变更通知的网元，将对应的签约数据发生变更的信息通知给网元。
S405：UDM返回创建/更新/删除的响应消息。若UDM执行出错，UDM返回错误原因。
例如，UDM响应Nudm_ParameterProvision_Create/Update/Delete的请求消息。
S406：NEF返回创建/更新/删除的响应消息。若NEF执行出错，NEF返回错误原因。
例如，NEF响应Nnef_ParameterProvision_Create/Update/Delete的请求消息。
下面以图5为例，对本申请实施例提供的通信方法进行说明，包括以下步骤：
S501：第一设备获取多个成员的链路状态。每个成员对应一个协议数据单元PDU会话，所述多个成员属于一个Eth-Trunk组。
所述第一设备可以为用户面网元(UPF)、端侧设备(如LSW或CPE或UE)或会话管理网元(SMF)中的一个。
所述第一设备可以为发送方。例如，端侧设备为发送方，用户面网元为接收方，所述端侧设备向用户面网元发送上行数据包。又如用户面网元为发送方，端侧设备为接收方，所述用户面网元向所述端侧设备发送下行数据包。
在本申请实施例中，Eth-Trunk组中的每个成员对应的一个PDU会话，且对应一条链 路。也就是说，Eth_Trunk组中的成员通过对应的链路发送对应PDU会话的数据包。
其中，所述链路状态用于指示成员的链路的优先级，和/或，所述链路状态用于指示成员的链路为主链路或备链路，和/或所述链路状态用于指示成员的链路是否故障。可选的，主链路的优先级高于备链路的优先级，不同备链路之间的优先级相同或不同。
在该S501中，所述第一设备可以采用LACP检测多个成员的链路状态。或者所述第一设备可以采用BFD检测多个成员的链路状态。或者所述第一设备采用所述LACP与BFD联合检测多个成员的链路状态。或者Eth_Trunk组中的成员的链路状态不需要链路检测，那么只要成员对应的PDU会话建立成功，则可以确认Eth_Trunk组中的成员的链路可用。
可选的，所述第一设备可以维护Eth-Trunk组的信息(如Eth-Trunk数据的信息和/或Eth_Trunk成员的信息)。
在一个实施例中，所述第一设备为用户面网元UPF。在该S501之前，所述第一设备可以接收第一消息，所述第一消息用于建立第一PDU会话。所述第一消息包括Eth-Trunk组的信息，所述Eth-Trunk组的信息包括所述Eth-Trunk组的属性。所述Eth_Trunk组的属性可以包括Eth-Trunk数据参数的信息和/或Eth-Trunk成员参数的信息，或者所述Eth_Trunk组的属性可以为External Group ID+TrunkId。所述第一设备根据所述第一消息建立第一PDU会话。若所述第一PDU会话的属性与所述Eth-Trunk组的属性匹配，所述第一设备可以在所述Eth-Trunk组中添加所述第一PDU会话对应的成员(例如可以添加成员标识)。若所述第一PDU会话的属性与当前保存的任一Eth-Trunk组的属性不匹配，所述第一设备可以新建所述第一PDU会话的属性为新的Eth-Trunk组的属性，并在该新建的Eth-Trunk组中添加所述第一PDU会话对应的成员(例如可以通过建立表格保存新的Eth-Trunk组的属性和新的成员)。所述第一设备可以以Eth-Trunk组为粒度对Eth-Trunk组的成员、终端设备的MAC地址等信息进行维护。
可选的，所述Eth-Trunk组的信息还可以包括以下一种或多种：Eth-Trunk组的标识、成员的链路类型、成员的链路检测类型、Eth-Trunk组中的最大链路数量、Eth-Trunk组中的最小链路数量、Eth-Trunk组中的链路优先级，其中所述成员的链路检测类型包括链路聚合控制协议LACP检测、或者双向转发检测BFD检测、或者LACP与BFD联合检测。
所述第一设备可以按照所述成员的链路检测类型，检测所述第一PDU会话对应的成员的链路状态。
在一个实施例中，所述第一设备为端侧设备，如LSW/CPE/UE。在该S501之前，所述第一设备可以接收第二消息，所述第二消息用于通知所述第一设备多个PDU会话属于一个Eth-Trunk组，所述多个PDU会话对应一个切片和DNN的组合。可选的，若网络架构中仅包括一个端侧设备，每个PDU会话对应一个切片、DNN和会话标识(SessionID)的组合。可选的，每个PDU会话对应相同的切片+DNN，对应不同的SessionID。
在一个实施例中，所述第一设备为会话管理网元SMF，所述第一设备可能检测到所述多个成员中的一个或多个成员的链路状态发送改变。假设第三成员的链路状态发生改变，所述第一设备将所述第三成员的链路状态发送给一个或多个用户面网元，其中第三成员属于所述多个成员中的一个成员。
可选的，在该S501中，所述第一设备可以周期性的获取多个成员的链路状态。
一种可能的场景中，所述第一设备检测到所述多个成员中的一个或多个成员的链路发生故障。假设第一成员的链路发生故障，所述第一设备可以释放所述第一成员对应的PDU 会话，或者所述第一设备保留所述第一成员对应的PDU会话，记录所述第一成员对应的PDU会话的状态异常；其中所述第一成员属于所述多个成员中的一个成员。
S502：所述第一设备根据所述多个成员的链路状态，选择目标成员，并发送所述目标成员对应的PDU会话的第一数据包。
在S502中，所述第一设备根据所述多个成员的链路状态，采用哈希(Hash)算法，在所述多个成员中选择目标成员。或者所述第一设备在所述多个成员的链路中选取未故障且优先级高的链路，作为目标成员的链路。例如所述第一设备可以在未故障的链路中选取优先级高的链路作为目标成员的链路，若未故障的链路的优先级相同，所述第一设备可以选取一个作为目标成员的链路。
可以理解的是，在通信过程中，发送方检测成员的链路状态，选择目标成员发送数据包。对应的，接收方也检测成员的链路状态，采用与发送方相同的选择策略，选择目标成员接收数据包。即，在通信过程中发送方和接收方同步进行检测，然后选取目标成员进行业务通信。
在本申请实施例中，Eth-Trunk组中的成员可以分布在同一UPF上，或者可以分布在不同UPF上。若Eth-Trunk组的成员分布在不同的UPF上，不同的UPF之间可以同步Eth-Trunk组的信息，保持不同的UPF之间的Eth-Trunk参数和成员的链路状态一致。例如所述第一设备将所述多个成员的链路状态发送给第二设备，所述第一设备为第一UPF，第二设备为第二UPF。可选的，所述第一设备通过会话管理网元SMF，将所述多个成员的链路状态发送给所述第二设备。
可选的，所述第一数据包中包括用于指示所述第一数据包来自第二成员的信息。所述第一设备在转发第一数据包时，所述第一设备可以根据所述多个成员的链路状态，在除所述第二成员所属的Eth-Trunk组外的其他Eth-Trunk组中的成员中，确定目标成员，所述第一设备采用所述目标成员的链路，(通过所述第二设备，如果有)发送所述目标成员对应的PDU会话的第一数据包。第一设备在进行数据包转发时，不在同一个Eth-Trunk组内选择链路进行转发，可以避免(同UPF/跨UPF)广播包闭环泛洪。
如果有新接入的终端设备，所述第一设备可以学习新接入的终端设备的MAC地址，所述第一设备根据学习的所述新接入的终端设备的MAC地址更新Eth-Trunk组中的MAC地址，和/或所述第一设备将所述新接入的终端设备的MAC地址上报给会话管理网元。其中所述新接入的终端设备可以属于所述Eth-Trunk组，所述新接入的终端设备可以对应一个PDU会话或对应多个PDU会话。
若Eth-Trunk组中的所有成员分布在同一UPF上，所述第一设备可以根据所述多个成员的链路状态，以及所述Eth-Trunk组的标识，确定目标成员，所述目标成员的链路上部署有所述用户面网元。所述第一设备通过Eth-Trunk组的标识，可以保证选取的目标成员为该Eth-Trunk组中的成员，进而保证同一Eth-Trunk组中的所有成员分布在同一UPF上。
可选的，所述第一设备可以从数据管理网元(如UDM/UDR)中获取Eth-Trunk组的信息。
会话管理网元可以向LSW/CPE发送第二消息，所述第二消息用于建立第一PDU会话，所述第二消息包括所述Eth-Trunk组的信息。
如果有新接入的终端设备，会话管理网元可以学习新接入的终端设备的MAC地址，将所述新接入的终端设备的MAC地址，发送给一个或多个用户面网元。其中所述新接入 的终端设备属于所述Eth-Trunk组，所述新接入的终端设备对应一个PDU会话或对应多个PDU会话。
通过本申请实施例提供的通信方法，所述第一设备作为发送方，与接收方之间部署有多条链路，链路为Eth-Trunk组中成员的链路，发送方根据多条链路的链路状态，选择目标成员及目标成员的链路，将目标成员的链路作为活动链路进行业务通信。也就是说可以采用一条链路进行业务通信，无需过多占用切片和DNN资源，也不必须对网络侧进行修改，降低网络侧的要求。并且通过链路状态选择目标成员，可以避免链路发生故障时对业务通信的影响，保障正常的业务通信。
下面以几个具体的实施例对上述实施例进行说明。
1)Eth-Trunk组中的所有成员分布在同一个UPF上。此时通信系统中可以包括至少一个端侧设备和一个UPF。
例如，图6为一种可能的通信系统的架构示意图，通信系统中包括PC1，PC2，PC3，与PC1连接的层二交换机(L2 SW)，与L2 SW连接的CPE1/UE1和CPE2/UE2，与CPE1/UE1连接的gNB1，与CPE2/UE2连接的gNB2，与gNB1、gNB2连接的UPF，与UPF连接的DN侧交换机(DN SW)和gNB3，与DN SW连接的PC2，与gNB3连接的CPE3/UE3，以及与CPE3/UE3连接的PC3。
在图6中，CPE1/UE1和CPE2/UE2为属于同一Eth-Trunk组中的成员。可以理解的是，一个Eth-Trunk组中可以包含更多成员，在此仅以两个成员为例进行说明，而不构成限制。L2 SW支持Eth-Trunk特性，L2 SW使用两个端口分别连接到两个CPE/UE，CPE/UE以桥接方式透传所有层二的数据包。组成Eth-Trunk组的所有CPE/UE成员的会话在同一个UPF上。
如果Eth-Trunk组支持LACP/BFD协商，则L2 SW的端口可以与UPF的会话协商成员的链路状态。此时在UPF上实现LACP/BFD协议栈。其中，BFD和LACP都可以检测成员的链路是否可用，BFD的检测效率比LACP的检测效果高。可选的，BFD和LACP可以一块部署，联合检测产生叠加效果，如LACP可以确定成员的链路是主备状态，BFD可以快速检测链路是否连通/是否故障。
UPF和DN SW可以通过多链路方式保证多链路传输。
在图6的基础上，图7提供了一种通信过程，包括以下步骤：
S701：CPE1/UE1向AMF发送会话建立请求消息，请求建立PDU会话。
S702：AMF选择SMF。
S703：AMF向选择的SMF转发会话建立请求消息。
S704：SMF从UDM/UDR中获取用户签约数据。
S705：UDM/UDR返回用户签约数据。
如果UDM/UDR中保存有Eth-Trunk组的信息，用户签约数据中还可以包括用户所属的Eth-Trunk组的信息，如包含用户所属的Eth-Trunk的标识(TrunkId)、Eth-Trunk组的属性等。如果UDM/UDR中未保存Eth-Trunk组的信息，用户签约数据中还包括用户所属的Eth-Trunk的标识(TrunkId)。
可选的S706：若UDM/UDR仅返回TrunkId，SMF到DN-AAA中获取Eth-Trunk组的信息。
S707：SMF选择UPF。
若存在与该用户属于同一Eth-Trunk组的其他用户，SMF为该用户选择与同一Eth-Trunk组的其他用户相同UPF。
S708：SMF通过N4接口通知UPF建立PDU会话。
SMF向UPF发送的消息中除携带PDU会话所需的参数，还可以携带Eth-Trunk组的信息。
S709：UPF建立PDU会话。所述PDU会话为N4UE会话。
如果UPF中该用户为Eth-Trunk组中的第一个成员，UPF中可以新建Eth-Trunk组的表格，保存Eth-Trunk组的信息；如果该用户非Eth-Trunk组中的第一个成员，即Eth-Trunk组中存在其他成员，UPF在Eth-Trunk组中添加该用户为新成员。
S710：SMF/AMF/CPE1/UE1完成后续PDU会话的建立流程。
S711：如果Eth-Trunk组支持LACP/BFD协商，L2 SW与UPF协商成员的链路状态。
例如，L2 SW使用与CPE1/UE1连接的端口(如端口1)与UPF协商CPE1/UE1的PDU会话的链路状态。
S712：若存在链路状态发生变化的成员，UPF对当前保存的成员的链路状态进行刷新。
S713：若PDU会话的链路状态发生故障，UPF通知SMF释放当前PDU会话。
步骤S712和S713为可选步骤，当然也可以不执行。
S714：SMF释放当前的PDU会话，并携带原因值。
所述原因值用于告知CPE/UE会话用户面链路不通的原因。例如所述原因值为PDU会话数据面不可用，或数据面不可达。
CPE2/UE2(图7未示出)重复S701-S714相似的流程，直至UPF保存Eth-Trunk组中所有成员的链路状态，在此不做赘述。
S715：PC1向DN侧的PC2发送数据包时，L2 SW根据Hash算法，选择CPE1/UE1的链路转发数据包至UPF，UPF通过DN SW将数据包转发给PC2。
可选的，UPF通过CPE1/UE1的PDU会话学习到了源侧PC1的MAC地址，UPF在Eth-Trunk组的信息中保存学习到的新的MAC地址(PC1的MAC地址)。这样，Eth-Trunk组的信息中可以保存学习到的所有成员的MAC地址。
S716：DN侧的PC2向PC1发送数据包时，UPF根据Hash算法，选择CPE2/UE2的链路转发数据包至L2 SW，L2 SW将数据包转发给PC1。
可选的，UPF学习到源侧PC2的MAC地址，在Eth-Trunk组的信息中保存学习到的新的MAC地址(PC2的MAC地址)。
一种可能的，UPF选择CPE1/UE1的链路转发数据包。
S717：如果Eth-Trunk组支持LACP/BFD协商，L2 SW与UPF采用LACP/BFD定时发送检测包检测链路状态。
若超过设定时长未接收到应答包，则确定当前检测的链路发生故障。若存在某个成员的链路发生故障，UPF对当前保存的成员的链路状态进行刷新。
2)Eth-Trunk组中的成员可以分布在不同的UPF上。此时通信系统中可以包括至少一个端侧设备和多个UPF。例如，图8为一种可能的通信系统的架构示意图，相比于图6，图8中包括UPF1和UPF2两个UPF，其他相似之处不做赘述。
在图8的基础上，图9提供了一种通信过程，包括以下步骤：
S901-S906的过程参见S701-S706。
S907：SMF选择UPF1。
可以理解的是，在该S907中以选择UPF1为例进行说明，一些场景中SMF可能选择UPF2，在此不做限制。
S908：SMF通过N4接口通知UPF1建立PDU会话。
SMF向UPF1发送的消息中除携带PDU会话所需的参数，还可以携带Eth-Trunk组的信息。SMF还可以要求UPF1上报成员的链路状态以及更新的MAC地址。
S909：UPF1建立PDU会话。
如果UPF1中该用户为Eth-Trunk组中的第一个成员，UPF1中可以新建Eth-Trunk组的表格，保存Eth-Trunk组的信息；如果该用户非Eth-Trunk组中的第一个成员，即Eth-Trunk组中存在其他成员，UPF1在Eth-Trunk组中添加该用户为新成员。
S910的过程参见S710。
S911：如果Eth-Trunk组支持LACP/BFD协商，L2 SW与UPF1协商成员的链路状态。
例如，L2 SW使用与CPE1/UE1连接的端口(如端口1)与UPF1协商CPE1/UE1的PDU会话的链路状态。
S912：若存在链路状态发生变化的成员，UPF1对当前保存的成员的链路状态进行刷新。
S913：UPF1通过N4接口向SMF上报成员(如CPE1/UE1)的链路状态。
S914：若PDU会话的链路状态发生故障，UPF1通知SMF释放当前PDU会话。
S915的过程参见S714。
CPE2/UE2重复S901-S914相似的流程，在此不做赘述。UPF2也可以向SMF上报成员(CPE2/UE2)的链路状态。
S916：PC1向DN侧的PC2发送数据包时，L2 SW根据Hash算法，选择CPE1/UE1的链路转发数据包至UPF1，UPF1通过DN SW将数据包转发给PC2。
可选的，UPF1通过CPE1/UE1的PDU会话学习到源侧PC1的MAC地址，UPF1在Eth-Trunk组的信息中保存学习到的新的MAC地址(PC1的MAC地址)。UPF1可以通过N4接口向SMF上报新的MAC地址。
S917：SMF通过N4接口通知UPF2新的MAC地址(如UPF1上报的新的MAC地址)，在UPF2的Eth-Trunk组的信息中保存学习到的新的MAC地址。
S918：DN侧的PC2向PC1发送数据包时，UPF1根据Hash算法，选择CPE2/UE2的链路转发数据包至L2 SW，L2 SW将数据包转发给PC1。
例如，UPF1先将数据包转发至UPF2，UPF2将数据包转发到CPE2/UE2，CPE2/UE2将数据包转发至L2 SW。
可选的，UPF1学习到源侧PC2的MAC地址，在Eth-Trunk组的信息中保存学习到的新的MAC地址(PC2的MAC地址)。UPF1将新的MAC地址通知到UPF2。
UPF1和UPF2之间通信时，UPF1通过N19接口转发数据包至UPE2。UPF1可以在GPRS隧道传输协议(GPRS tunnel protocol，GTP)-U的扩展头中增加数据包的源侧信息，用于说明数据包经过哪个PDU会话达到UPF1。
S919：L2 SW与UPF1采用LACP/BFD定时发送检测包检测链路状态。
若检测到成员的链路状态发生变化，UPF1对当前保存的成员的链路状态进行刷新。UPF1将成员的链路状态发生变化的信息通知给UPF2，UPF2对保存的成员的链路状态进行刷新。
L2 SW与UPF2之间可以检测链路状态，相似之处参见UPF1的检测过程。
S920：UPF1可以老化PC1的MAC地址，UPF1通过N4接口上报MAC地址老化事件，SMF通过N4接口通知UPF2 MAC地址老化事件，UPF2刷新保存的MAC地址。
3)在SMF上实现LACP/BFD协议栈。上述实施例中UPF的功能由SMF实现，SMF上部署LACP/BFD协议栈，维护Eth-Trunk组的信息和成员的链路状态。在Eth-Trunk组中成员的链路状态发生变更时，通知所有UPF。
图10提供了一种通信过程，包括以下步骤：
S1001-S1007的过程参见S901-S907。
S1008：SMF通过N4接口通知UPF1建立PDU会话。
SMF向UPF1发送的消息中除携带PDU会话所需的参数，还可以携带Eth-Trunk组的信息。SMF还可以要求UPF1上报成员的链路状态以及更新的MAC地址。SMF还可以要求UPF1上报收到的检测包(如LACP/BFD消息)。
例如，UPF1识别LACP消息时，UPF1识别消息中的目的MAC地址为01:80:C2:00:00:02、Ethernet Type为Slow Protocol(0x8809)，或慢速协议子类型(Slow Protocol SubType)为0x01中的一个或多个。UPF1识别BFD时，UPF1识别消息中的组播IP地址和UDP端口号，是否与本地配置的一致。
S1009-S1010的过程参见S909-S910。
S1011：L2 SW与SMF协商成员的链路状态。
L2 SW通过UPF1与SMF协商成员的链路状态。例如UPF1接收到上行的LACP/BFD消息，将LACP/BFD消息转发给SMF。又如，UPF1接收到下行的LACP/BFD消息，将LACP/BFD消息转发给对应的CPE/UE(如CPE1/UE1)。
S1012：SMF将成员的链路状态发送给UPF1，UPF1对当前保存的成员的链路状态进行刷新。
例如SMF向与成员所属Eth-Trunk组相关的所有UPF，发送成员的链路状态。与成员所属Eth-Trunk组相关的所有UPF对保存的成员的链路状态进行刷新。可选的，SMF将成员的链路状态发送给UPF2。
S1013-S1016的过程参见S915-S918。
S1017：L2 SW与SMF采用LACP/BFD定时发送检测包检测链路状态。
若检测到成员的链路状态发生变化，SMF通知与该成员所属Eth-Trunk组相关的所有UPF，发送该成员的链路状态。与该成员所属Eth-Trunk组相关的所有UPF对保存的成员的链路状态进行刷新。
S1018的过程参见S920。
4)多个CPE/UE组成Eth-Trunk组。
例如，图11为一种可能的通信系统的架构示意图。相比于图8，图11中CEP/UE与PC直接连接，未与L2 SW连接，且CPE/UE之间可以交互，多个CPE/UE组成一个Eth-Trunk 组。CEP/UE可以直接转发上行单播数据包，根据学习到的MAC地址转发下行单播数据包。CPE/UE可以向网络侧和对端CPE/UE(CPE1/UE1的对端CPE/UE为CPE2/UE2)转发上行广播数据包。对端CPE/UE接收到上行的广播数据包后，可以向下行(如对端CPE/UE对应的PC)转发，不向上行转发。CPE/UE可以向PC和对端CPE/UE转发下行广播数据包。对端CPE/UE接收到下行的广播数据包后，可以向下行转发，不向上行转发。图11中的其他设备可以参见图9或图11的通信过程，在此不做赘述。
图11中的多个CPE/UE可以位于一个终端设备上。例如图12所示，在一个终端设备上插入多张用户识别模块(subscriber identity module，SIM)卡，每张SIM对应一个UE。每个UE的“切片(S-NSSAI)+DNN”上建立一个PDU会话，在终端设备内部实现Eth-Trunk组。端侧设备通过UE与网络侧(如UPF/SMF)协商每个UE的链路状态。端侧设备接收到PC1的上行数据包时，可以根据Hash算法选择上行UE进行转发。端侧设备中的某个UE接收到下行数据包时，将下行数据包转发给PC1。
5)单CPE/UE、单S-NSSAI+DNN、多SessionID组成Eth-Trunk组。
例如，图13为一种可能的通信系统的架构示意图。在图13中，端侧设备包括一个CPE/UE，即使用一张SIM卡连接网络。CPE/UE用一对S-NSSAI+DNN，多个SessionID的方式建立多个PDU会话，这些PDU会话组成一个Eth-Trunk组。端侧设备建立PDU会话的粒度为S-NSSAI+DNN+SessionID。CPE/UE侧的每个PDU会话与UPF侧的对应PDU会话之间形成一个Eth-Trunk链路。CPE/UE接收到PC1的上行数据包时，可以根据Hash算法选择上行PDU会话进行转发。CPE/UE的某个PDU会话接收到下行数据包时，将下行数据包转发给PC1。
在图13的基础上，网络侧通过静态签约允许UE侧多个PDU会话组成Eth-Trunk组。图14提供了一种通信过程，假设CPU/UE的两个PDU会话在同一个UPF上建立，包括以下步骤：
S1401：UDM中签约用户支持Eth-Trunk接入。UDR或DN-AAA保存有Eth-Trunk组的信息。
签约用户支持Eth-Trunk接入指该用户签约了Eth-Trunk特性。
S1402：CPE/UE发起会话建立请求，请求建立PDU会话。会话建立请求消息中携带切片信息(S-NSSAI)+DNN以及SessionID1。
S1403-S1405的过程参见S702-S704。
S1406：UDM返回用户签约数据，UDR返回Eth-Trunk组的信息。
如果UDM/UDR中保存有Eth-Trunk组的信息，用户签约数据中还可以包括用户所属的Eth-Trunk组的信息。如果UDM/UDR中未保存Eth-Trunk组的信息，用户签约数据中包括用于指示该用户签约了Eth-Trunk特性的信息。
可选的S1407：若UDM/UDR仅返回用于指示该用户签约了Eth-Trunk特性的信息，SMF到DN-AAA中获取Eth-Trunk组的信息。
S1408：CPE/UE与核心网完成后续PDU会话的建立流程。
S1409：CPE/UE与核心网(如UPF/SMF)协商Eth-Trunk组中SessionID1成员的链路状态。
对于其他PDU会话，可以参见上述S1402-S1409。
S1410：CPE/UE和/或UPF对接收到的数据包进行转发。
例如CPE/UE接收到的上行数据包后，根据Hash算法，选择PDU会话转发上行数据包给UPF1/UPF2。UPF1/UPF2接收到上行数据包，将上行数据包转发给DN侧。UPF1/UPF2接收到下行数据包后，根据Hash算法，选择PDU会话转发下行数据包给CPE/UE。CPE/UE接收到下行数据包后，将下行数据包转发给PC1。
需要说明的是，UE负责接入网络，可以不感知各PDU会话是否构成Eth-Trunk组。CPE感知Eth-Trunk组。
在图13的基础上，网络侧可以通过URSP要求UE侧多个PDU会话组成Eth-Trunk组。UE可以感知PDU会话构成Eth-Trunk组，并与网络侧协商各PDU会话组成的Eth-Trunk组的成员的链路状态。CPE转发上行数据包时，UE可以根据Eth-Trunk选路规则，选择PDU会话转发上行数据包。UE的PDU会话接收到下行数据包时，UE将下行数据包转发给CPE。
具体的：步骤1，UE在注册入网时，网络侧通过URSP通知UE该用户的多个PDU会话组成一个Eth-Trunk组。步骤2，网络侧主动通过配置更新流程通知UE该用户的多个PDU会话组成一个Eth-Trunk组。步骤3，UE建立多个PDU会话，并且该多个PDU会话组成一个组。其中步骤3可以参见上述图14所示的通信过程。
步骤1可以在UE注册过程中实现。参见图15所示，包括以下步骤：
S1501：UE向接入网设备发送注册请求。
S1502：网络侧处理所述注册请求。
S1503：AMF向UE返回注册接受响应，所述注册接受响应中包括用于指示多个PDU会话组成Eth-Trunk组的参数。
S1504：UE与网络侧完成后续注册流程。
步骤2可以在UE配置更新过程中实现。参见图16所示，包括以下步骤：
S1601：AMF决定更新UE的配置信息或进行重配置。
S1602：AMF向UE发送配置更新命令，所述配置更新命令中包括用于指示多个PDU会话组成Eth-Trunk组的参数。
S1603：完成配置信息更新的后续流程。
S1604：当UE进行空闲态后，UE发起注册流程。
AMF可以通过PCF动态策略生成，或者通过UDM签约数据获取“多个PDU会话组成Eth-Trunk组”的信息。
当“多个PDU会话组成Eth-Trunk组”的信息发生变更时，例如当PDU会话从Eth-Trunk组恢复到单个Eth-Trunk，AMF可以通过UE注册过程或UE配置更新过程进行更新。
可选的，根据运营商策略可以制定可选参数Eth-TrunkFlag，所述Eth-TrunkFlag用于指示多个PDU会话组成Eth-Trunk组。所述Eth-TrunkFlag参数可以保存在UE上下文中。所述Eth-TrunkFlag可以允许网络侧通过URSP在PCF策略中修改。例如可以在3GPP 23.503表格(Table)6.6.2.1-3的路由选择描述表(Route Selection Descriptor)中新增所述Eth-TrunkFlag参数。
当UE想要发起业务或应用时，UE在Route Selection Descriptor中匹配是否存在具体的所述Eth-TrunkFlag参数的规则。若存在，UE配置已有的PDU会话中与待发起的业务/应用的信息一致，UE可以选择在已有的PDU会话中承载所述待发起的业务/应用，或者对 已有的PDU会话进行修改。若UE配置已有的PDU会话中与待发起的业务/应用的信息不一致，UE可以为该待发起的业务/应用发起PDU会话建立请求。
以上结合图5至图16详细说明了本申请实施例的通信方法，基于与上述通信方法的同一技术构思，本申请实施例还提供了一种通信装置，如图17所示，所述通信装置1700中包含处理单元1701和收发单元1702，装置1700可用于实现上述方法实施例中描述的方法。
在一个实施例中，装置1700应用于第一设备时，所述收发单元1702，用于获取多个成员的链路状态，每个成员对应一个协议数据单元PDU会话，所述多个成员属于一个Eth-Trunk组；所述处理单元1701，用于根据所述多个成员的链路状态，选择目标成员；所述收发单元1702，还用于发送所述目标成员对应的PDU会话的第一数据包。
在一个实现方式中，所述链路状态用于指示成员的链路为主链路或备链路，和/或所述链路状态用于指示成员的链路是否故障。
在一个实现方式中，所述处理单元1701，具体用于根据所述多个成员的链路状态，采用哈希Hash算法，在所述多个成员中选择目标成员。
在一个实现方式中，所述收发单元1702，还用于接收第一消息，所述第一消息用于建立第一PDU会话，所述第一消息包括Eth-Trunk组的信息，所述Eth-Trunk组的信息包括所述Eth-Trunk组的属性；
所述处理单元1701，还用于根据所述第一消息建立第一PDU会话；若所述第一PDU会话的属性与所述Eth-Trunk组的属性匹配，在所述Eth-Trunk组中添加所述第一PDU会话对应的成员。
在一个实现方式中，所述Eth-Trunk组的信息还包括成员的链路检测类型，其中所述成员的链路检测类型包括链路聚合控制协议LACP检测、或者双向转发检测BFD检测、或者LACP与BFD联合检测；
所述处理单元1701，还用于按照所述成员的链路检测类型，检测所述第一PDU会话对应的成员的链路状态。
在一个实现方式中，所述Eth-Trunk组的信息还包括以下一种或多种：Eth-Trunk组的标识、成员的链路类型、Eth-Trunk组中的最大链路数量、Eth-Trunk组中的最小链路数量、Eth-Trunk组中的链路优先级。
在一个实现方式中，所述收发单元1702，具体可以用于周期性的获取多个成员的链路状态。
在一个实现方式中，所述处理单元1701，还用于若第一成员的链路发生故障，释放所述第一成员对应的PDU会话，或者保留所述第一成员对应的PDU会话，并记录所述第一成员对应的PDU会话的状态异常；其中所述第一成员为所述多个成员中的任意一个成员。
在一个实现方式中，所述第一数据包中包括用于指示所述第一数据包来自第二成员的信息；所述处理单元1701，具体用于根据所述多个成员的链路状态，在除所述第二成员所属的Eth-Trunk组外的其他Eth-Trunk组中的成员中，确定目标成员；所述收发单元1702，具体用于采用所述目标成员的链路，通过第二设备发送所述目标成员对应的PDU会话的第一数据包。
在一个实现方式中，所述通信装置为第一用户面网元时，所述第二设备为所述第二用 户面网元。
在一个实现方式中，所述收发单元1702，还用于将所述多个成员的链路状态发送给所述第二设备。
在一个实现方式中，所述收发单元1702，具体用于通过会话管理网元，将所述多个成员的链路状态发送给所述第二设备。
在一个实现方式中，所述收发单元1702，还用于接收第二消息，所述第二消息用于通知多个PDU会话属于一个Eth-Trunk组，所述多个PDU会话对应一个切片和数据网络名称DNN的组合。
在一个实现方式中，所述处理单元1701，还用于学习新接入的终端设备的MAC地址；根据学习的所述新接入的终端设备的MAC地址更新Eth-Trunk组中的MAC地址，和/或通过所述收发单元将所述新接入的终端设备的MAC地址上报给会话管理网元；其中所述新接入的终端设备属于所述Eth-Trunk组，所述新接入的终端设备对应一个PDU会话或对应多个PDU会话。
在一个实现方式中，所述收发单元1702，还用于若第三成员的链路状态发生改变，将所述第三成员的链路状态发送给一个或多个用户面网元。
在一个实现方式中，所述Eth-Trunk组的所有成员可以部署在一个用户面网元上；所述处理单元1701，具体用于根据所述多个成员的链路状态，以及所述Eth-Trunk组的标识，确定目标成员，所述目标成员的链路上部署有所述用户面网元。
在一个实现方式中，所述收发单元1702，还用于从数据管理网元中获取Eth-Trunk组的信息。
在一个实现方式中，所述收发单元1702，还用于发送第二消息，所述第二消息用于建立第一PDU会话，所述第二消息包括所述Eth-Trunk组的信息。
在一个实现方式中，所述收发单元1702，还用于学习新接入的终端设备的MAC地址，其中所述新接入的终端设备属于所述Eth-Trunk组，所述新接入的终端设备对应一个PDU会话或对应多个PDU会话；将所述新接入的终端设备的MAC地址，发送给一个或多个用户面网元。
在另一个实施例中，装置1700应用于第三设备时，所述收发单元1702，用于接收第三消息，所述第三消息用于请求更新Eth-Trunk组；所述处理单元1701，用于对当前保存的Eth-Trunk组的信息进行更新；其中，所述Eth-Trunk组的信息包括Eth-Trunk组中的成员的信息。
需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储 器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
基于与上述通信方法相同的构思，如图18所示，本申请实施例还提供了一种通信装置1800的结构示意图。装置1800可用于实现上述方法实施例中描述的方法，可以参见上述方法实施例中的说明。
所述装置1800包括一个或多个处理器1801。所述处理器1801可以是通用处理器或者专用处理器等。例如可以是基带处理器、或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、终端、或芯片等)进行控制，执行软件程序，处理软件程序的数据。所述通信装置可以包括收发单元，用以实现信号的输入(接收)和输出(发送)。例如，所述收发单元可以为收发器，射频芯片等。
所述装置1800包括一个或多个所述处理器1801，所述一个或多个处理器1801可实现上述所示的实施例中的方法。可选的，处理器1801除了实现上述所示的实施例的方法，还可以实现其他功能。
可选的，一种设计中，处理器1801可以执行指令，使得所述装置1800执行上述方法实施例中描述的方法。所述指令可以全部或部分存储在所述处理器内，如指令1803，也可以全部或部分存储在与所述处理器耦合的存储器1802中，如指令1804，也可以通过指令1803和1804共同使得装置1800执行上述方法实施例中描述的方法。
在又一种可能的设计中，通信装置1800也可以包括电路，所述电路可以实现前述方法实施例中的功能。
在又一种可能的设计中所述装置1800中可以包括一个或多个存储器1802，其上存有指令1804，所述指令可在所述处理器上被运行，使得所述装置1800执行上述方法实施例中描述的方法。可选的，所述存储器中还可以存储有数据。可选的处理器中也可以存储指令和/或数据。例如，所述一个或多个存储器1802可以存储上述实施例中所描述的对应关系，或者上述实施例中所涉及的相关的参数或表格等。所述处理器和存储器可以单独设置，也可以集成在一起。
在又一种可能的设计中，所述装置1800还可以包括收发器1805以及天线1806。所述处理器1801可以称为处理单元，对装置(终端或者基站)进行控制。所述收发器1805可以称为收发机、收发电路、或者收发单元等，用于通过天线1806实现装置的收发功能。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介 质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(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)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读介质，其上存储有计算机程序，该计算机程序被计算机执行时实现上述任一方法实施例所述的通信方法。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例所述的通信方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(Digital Video Disc，DVD))、或者半导体介质(例如，固态硬盘(Solid State Disk，SSD))等。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器，用于执行上述任一方法实施例所述的通信方法。
应理解，上述处理装置可以是一个芯片，所述处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，改存储器可以集成在处理器中，可以位于所述处理器之外，独立存在。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本申请所使用的，盘(Disk)和碟(disc)包括压缩光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
总之，以上所述仅为本申请技术方案的较佳实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (24)

  1. 一种通信方法，其特征在于，包括：
    第一设备获取多个成员的链路状态，每个成员对应一个协议数据单元PDU会话，所述多个成员属于一个Eth-Trunk组；
    所述第一设备根据所述多个成员的链路状态，选择目标成员，并发送所述目标成员对应的PDU会话的第一数据包。
  2. 如权利要求1所述的方法，其特征在于，所述链路状态用于指示成员的链路为主链路或备链路，和/或所述链路状态用于指示成员的链路是否故障。
  3. 如权利要求1或2所述的方法，其特征在于，所述第一设备根据所述多个成员的链路状态，选择目标成员，包括：
    所述第一设备根据所述多个成员的链路状态，采用哈希Hash算法，在所述多个成员中选择目标成员。
  4. 如权利要求1-3任一项所述的方法，其特征在于，所述第一设备获取多个成员的链路状态之前，还包括：
    所述第一设备接收第一消息，所述第一消息用于建立第一PDU会话，所述第一消息包括Eth-Trunk组的信息，所述Eth-Trunk组的信息包括所述Eth-Trunk组的属性；
    所述第一设备根据所述第一消息建立第一PDU会话；
    若所述第一PDU会话的属性与所述Eth-Trunk组的属性匹配，所述第一设备在所述Eth-Trunk组中添加所述第一PDU会话对应的成员。
  5. 如权利要求4所述的方法，其特征在于，所述Eth-Trunk组的信息还包括成员的链路检测类型，所述成员的链路检测类型包括链路聚合控制协议LACP检测、或者双向转发检测BFD检测、或者LACP与BFD联合检测；
    所述方法还包括：
    所述第一设备按照所述成员的链路检测类型，检测所述第一PDU会话对应的成员的链路状态。
  6. 如权利要求4或5所述的方法，其特征在于，所述Eth-Trunk组的信息还包括以下一种或多种：Eth-Trunk组的标识、成员的链路类型、Eth-Trunk组中的最大链路数量、Eth-Trunk组中的最小链路数量、Eth-Trunk组中的链路优先级。
  7. 如权利要求1-6任一项所述的方法，其特征在于，所述第一设备获取多个成员的链路状态，还包括：
    所述第一设备周期性的获取多个成员的链路状态。
  8. 如权利要求1-7任一项所述的方法，其特征在于，所述第一设备获取多个成员的链路状态之后，还包括：
    若第一成员的链路发生故障，所述第一设备释放所述第一成员对应的PDU会话，或者所述第一设备保留所述第一成员对应的PDU会话，并记录所述第一成员对应的PDU会话的状态异常；
    其中所述第一成员为所述多个成员中的任意一个成员。
  9. 如权利要求1-8任一项所述的方法，其特征在于，所述第一数据包中包括用于指示所述第一数据包来自第二成员的信息；
    所述第一设备根据所述多个成员的链路状态，选择目标成员，并发送所述目标成员对应的PDU会话的第一数据包，包括：
    所述第一设备根据所述多个成员的链路状态，在除所述第二成员所属的Eth-Trunk组外的其他Eth-Trunk组中的成员中，确定目标成员；
    所述第一设备采用所述目标成员的链路，通过第二设备发送所述目标成员对应的PDU会话的第一数据包。
  10. 如权利要求9所述的方法，其特征在于，所述第一设备为第一用户面网元，所述第二设备为所述第二用户面网元。
  11. 如权利要求9或10所述的方法，其特征在于，还包括：
    所述第一设备将所述多个成员的链路状态发送给所述第二设备。
  12. 如权利要求11所述的方法，其特征在于，所述第一设备将所述多个成员的链路状态发送给所述第二设备，包括：
    所述第一设备通过会话管理网元，将所述多个成员的链路状态发送给所述第二设备。
  13. 如权利要求1-3任一项所述的方法，其特征在于，所述第一设备获取多个成员的链路状态之前，还包括：
    所述第一设备接收第二消息，所述第二消息用于通知多个PDU会话属于一个Eth-Trunk组，所述多个PDU会话对应一个切片和数据网络名称DNN的组合。
  14. 如权利要求1-13任一项所述的方法，其特征在于，还包括：
    第一设备学习新接入的终端设备的MAC地址；
    所述第一设备根据学习的所述新接入的终端设备的MAC地址更新Eth-Trunk组中的MAC地址，和/或所述第一设备将所述新接入的终端设备的MAC地址上报给会话管理网元；
    其中所述新接入的终端设备属于所述Eth-Trunk组，所述新接入的终端设备对应一个PDU会话或对应多个PDU会话。
  15. 如权利要求1-3任一项所述的方法，其特征在于，所述第一设备获取多个成员的链路状态之后，还包括：
    若第三成员的链路状态发生改变，所述第一设备将所述第三成员的链路状态发送给一个或多个用户面网元。
  16. 如权利要求1-3任一项所述的方法，其特征在于，所述Eth-Trunk组的所有成员部署在一个用户面网元上；
    所述第一设备根据所述多个成员的链路状态，选择目标成员，包括：
    所述第一设备根据所述多个成员的链路状态，以及所述Eth-Trunk组的标识，确定目标成员，所述目标成员的链路上部署有所述用户面网元。
  17. 如权利要求1-3任一项所述的方法，其特征在于，还包括：
    所述第一设备从数据管理网元中获取Eth-Trunk组的信息。
  18. 如权利要求17所述的方法，其特征在于，还包括：
    所述第一设备发送第二消息，所述第二消息用于建立第一PDU会话，所述第二消息包括所述Eth-Trunk组的信息。
  19. 如权利要求1-3任一项所述的方法，其特征在于，还包括：
    所述第一设备学习新接入的终端设备的MAC地址，其中所述新接入的终端设备属于 所述Eth-Trunk组，所述新接入的终端设备对应一个PDU会话或对应多个PDU会话；
    所述第一设备将所述新接入的终端设备的MAC地址，发送给一个或多个用户面网元。
  20. 一种通信方法，其特征在于，包括：
    第三设备接收第三消息，所述第三消息用于请求更新Eth-Trunk组；
    所述第三设备对当前保存的Eth-Trunk组的信息进行更新；其中，所述Eth-Trunk组的信息包括Eth-Trunk组中的成员的信息。
  21. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器与所述存储器耦合；
    存储器存储有计算机程序；
    处理器，用于执行所述存储器中存储的计算机程序，以使得所述装置执行如权利要求1-19中任一项所述的方法，或执行如权利要求20所述的方法。
  22. 一种计算机可读存储介质，其特征在于，包括程序或指令，当所述程序或指令在计算机上运行时，如权利要求1-19中任一项所述的方法被执行，或如权利要求20所述的方法被执行。
  23. 一种计算机程序产品，其特征在于，包括程序或指令，当所述程序或指令在计算机上运行时，如权利要求1-19中任一项所述的方法被执行，或如权利要求20所述的方法被执行。
  24. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以执行如权利要求1-19中任一项所述的方法，或执行如权利要求20所述的方法。
PCT/CN2021/079162 2021-03-04 2021-03-04 一种通信方法、装置及芯片 WO2022183453A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/079162 WO2022183453A1 (zh) 2021-03-04 2021-03-04 一种通信方法、装置及芯片
CN202180094529.2A CN116965002A (zh) 2021-03-04 2021-03-04 一种通信方法、装置及芯片

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/079162 WO2022183453A1 (zh) 2021-03-04 2021-03-04 一种通信方法、装置及芯片

Publications (1)

Publication Number Publication Date
WO2022183453A1 true WO2022183453A1 (zh) 2022-09-09

Family

ID=83154836

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/079162 WO2022183453A1 (zh) 2021-03-04 2021-03-04 一种通信方法、装置及芯片

Country Status (2)

Country Link
CN (1) CN116965002A (zh)
WO (1) WO2022183453A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120320737A1 (en) * 2011-06-14 2012-12-20 Avaya Inc. Method and apparatus for lossless link recovery between two devices interconnected via multi link trunk/link aggregation group (mlt/lag)
CN105681138A (zh) * 2014-11-21 2016-06-15 中国移动通信集团广东有限公司 网络链路组网的方法及系统
CN112217658A (zh) * 2019-07-11 2021-01-12 华为技术有限公司 一种堆叠分裂处理方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120320737A1 (en) * 2011-06-14 2012-12-20 Avaya Inc. Method and apparatus for lossless link recovery between two devices interconnected via multi link trunk/link aggregation group (mlt/lag)
CN105681138A (zh) * 2014-11-21 2016-06-15 中国移动通信集团广东有限公司 网络链路组网的方法及系统
CN112217658A (zh) * 2019-07-11 2021-01-12 华为技术有限公司 一种堆叠分裂处理方法及装置

Also Published As

Publication number Publication date
CN116965002A (zh) 2023-10-27

Similar Documents

Publication Publication Date Title
EP3516922B1 (en) Method and apparatus for establishing dual-connectivity to transmit data in new radio communication architecture
EP3589026B1 (en) Method and device for managing state of session according to position of terminal in wireless communication system
US9788353B2 (en) Mobile network communications method, communications apparatus, and communications system
US10812292B2 (en) Packet processing method and device
CN110351030A (zh) 报文传输方法、装置和系统
EP4138443A1 (en) Communication method and apparatus
WO2022017285A1 (zh) 报文转发方法、装置及系统
WO2010088835A1 (zh) 实现本地交换的方法及系统
WO2022143697A1 (zh) 避免环路的方法及装置
WO2022143395A1 (zh) 一种冗余路径创建方法、装置及系统
CN115699816A (zh) 用于在双连接下进行侧行链路中继通信的方法
WO2023124875A1 (zh) 一种通信方法及装置
WO2022183453A1 (zh) 一种通信方法、装置及芯片
WO2023205941A1 (zh) 信息的发送、接收、配置方法以及装置和通信系统
WO2023020046A1 (zh) 一种通信方法及通信装置
WO2023060401A1 (zh) 无线路由方法及装置
WO2023015454A1 (zh) 路径建立方法、选择方法、装置、终端设备及存储介质
WO2023150974A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2023130260A1 (zh) Rrc消息的配置方法、装置和系统
WO2023137579A1 (zh) 紧急业务的提供方法、装置、设备及存储介质
WO2023197105A1 (zh) 配置信息的方法、装置和通信系统
WO2023150976A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2022021142A1 (zh) QoS参数的设置方法、装置、通信设备及存储介质
TWI827186B (zh) 路由方法和通信裝置
WO2023184542A1 (zh) 配置信息的方法、装置和通信系统

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202180094529.2

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21928538

Country of ref document: EP

Kind code of ref document: A1