WO2020103828A1 - 群组通信方法、设备及系统 - Google Patents

群组通信方法、设备及系统

Info

Publication number
WO2020103828A1
WO2020103828A1 PCT/CN2019/119475 CN2019119475W WO2020103828A1 WO 2020103828 A1 WO2020103828 A1 WO 2020103828A1 CN 2019119475 W CN2019119475 W CN 2019119475W WO 2020103828 A1 WO2020103828 A1 WO 2020103828A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
user plane
group
identifier
plane network
Prior art date
Application number
PCT/CN2019/119475
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 EP19887489.3A priority Critical patent/EP3876494B1/en
Publication of WO2020103828A1 publication Critical patent/WO2020103828A1/zh
Priority to US17/324,928 priority patent/US11653180B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/246—Connectivity information discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0009—Control or signalling for completing the hand-off for a plurality of users or terminals, e.g. group communication or moving wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • This application relates to the field of communication technology, and in particular, to group communication methods, devices, and systems.
  • the 5th generation (5G) local area network (5GLAN) service is a service provided by the current 5G network, which is mainly used in home communication, corporate office, factory manufacturing, vehicle networking, power grid transformation and public security organs.
  • the 5GLAN service can provide private communication of Internet protocol (IP) type or non-IP type (such as Ethernet type) for two or more terminals in a group.
  • IP Internet protocol
  • non-IP type such as Ethernet type
  • the equipment in the factory can form a group, and the equipment in the group can send Ethernet packets to each other; or, the office equipment (such as mobile phones, computers, or laptops) of employees in a department of the enterprise can be formed A group, send IP packets to each other, and so on. If the two terminals are not in the same group, they cannot communicate with each other.
  • the 3rd Generation Partnership Project (3GPP) Technical Rules (TR) 23.734 proposed to support 5GLAN one-to-one and one-to-many communication.
  • the 3GPP network is required to support group-based unicast, multicast, and broadcast; support for copy and distribution of multicast and broadcast messages; and support for any terminal as a group Broadcast source.
  • the 3GPP technical standard (TS) 29.244 defines the way in which the user plane forwards messages. Its architecture is shown in Figure 1. Its working mechanism is that after a user plane function (UPF) network element receives a message from an entrance (such as the N3 port), it is marked according to the 5G user plane protocol of the user message (such as tunnel endpoint identifier (tunnel endpoint identifier), TEID)) Determine the session to which the message belongs. Then the UPF network element uses the packet detection rules (packet detection (rule), PDR) (may be one or more) in the N4 session context (N4 session context) of the session to match the characteristic information of the packet to find a match PDR.
  • packet detection rules packet detection (rulet detection (rule), PDR) (may be one or more) in the N4 session context (N4 session context) of the session to match the characteristic information of the packet to find a match PDR.
  • the PDR specifies forwarding action rules (FAR), quality of services (QoS) execution rules (QoS enforcement rules (QER) and statistical information reporting rules (usage reporting port rules (URR)) corresponding to packets.
  • FAR forwarding action rules
  • QoS quality of services
  • QER quality of services
  • URR usage reporting port rules
  • the UPF network element may perform drop, forward, buffer, report control, or duplicate on the message according to the FAR.
  • UPF network elements can perform QoS operations on packets according to QER.
  • UPF network elements can perform statistical information reporting on packets based on URR.
  • the message is sent from the exit (such as the N6 port).
  • the key actions include specifying the exit identifier and the exit action.
  • the export action may include, for example, adding an outer header, a marking at the transport layer, a marking at the transport layer, a forwarding policy, or a header enhancement.
  • the embodiments of the present application provide a group communication method, device, and system, which can greatly reduce the configuration workload caused by the change in the number of terminal members when there are many terminal members in the group.
  • a group communication method includes: when a first terminal initiates access to a local area network group, a group management function network element acquires a first user plane to be accessed by the first terminal The identifier of the network element, the context information of the local area network group, and the first session port identifier, where the context information includes a user in the terminal member list of the local area network group who is currently connected to the local area network group A list of identifiers of the face network elements, the first session port identifier is the identifier of the first session port on the first user plane network element for the first terminal to access; the group management function network element is created for the LAN group A rule group applied on the first session port; and, the group management function network element creates or updates the LAN group forwarding action applied to the first user plane network element for the LAN group based on the context information Rule FAR; wherein, the rule group includes an entry packet detection rule PDR, an exit PDR, and an exit FAR; the exit PDR includes an identification
  • the method further includes: including the identifier of the second user plane network element in the identifier list, and the identifier of the first user plane network element is not in the identifier list, the group The management function network element obtains a first tunnel port identifier and a second tunnel port identifier, where the first tunnel port identifier is the identifier of the first tunnel port of the first tunnel on the first user plane network element, and the second tunnel port identifier Is the identifier of the second tunnel port of the first tunnel on the second user plane network element, the first tunnel is a tunnel between the first user plane network element and the second user plane network element; the group The management function network element creates the rule group applied to the first tunnel port for the local area network group, and the group management function network element creates the rule group applied to the second tunnel port for the local area network group And, the group management function network element updates the local area network group FAR applied on the second user plane network element; correspondingly, the first message is also used to configure the rule group on the first tunnel port
  • the method further includes: when the first terminal is updated from accessing the first user plane network element to accessing a third user plane network element in the local area network group, the group The group management function network element obtains a third session port identifier, which is the identifier of the third session port on the third user plane network element for the first terminal to access; the group management function network element Creating a rule group applied to the third session port for the local area network group; and, the group management function network element creates or updates the local area network group applied to the third user plane network element according to the context information FAR; the group management function network element sends a third message to the session management network element, the third message is used to configure the rule group on the third session port, and configure or configure on the third user plane network element Update the LAN group FAR, and delete the rule group on the first session port, and delete or update the LAN group FAR applied on the first user plane network element, wherein the updated application is on the first
  • the local area network group FAR on a user plane network element is obtained by
  • terminal members who have entered the network in the LAN group move within the LAN group, they only need to adjust (create, update, or delete) the LAN group FAR on the associated UPF network element and adjust (create, create, Update or delete)
  • the entry PDR, exit PDR, and exit FAR corresponding to the terminal member on the associated user plane network element are sufficient.
  • the entry PDR, exit PDR, and exit FAR corresponding to other terminal members who have entered the network in the LAN group are not changes happened. Therefore, when there are many terminal members in the LAN group, the configuration workload caused by the change in the number of terminal members will be greatly increased, and the configuration workload due to the change in the number of terminal members is greatly reduced.
  • the method further includes: including an identifier of the fourth user plane network element in the identifier list, and dividing the first user plane network element from the terminal member list that does not have the LAN group
  • the group management function network element updates the local area network group FAR applied to the fourth user plane network element; correspondingly, the third message is also used to delete the A second tunnel between the first user plane network element and the fourth user plane network element, and deleting the rule group on the third tunnel port of the first user plane network element, and deleting the fourth user plane network
  • the rule group on the fourth tunnel port of the element and update the LAN group FAR applied to the fourth user plane network element, where the third tunnel port is the second tunnel on the first user plane network A tunnel port on the element, and the fourth tunnel port is a tunnel port of the second tunnel on the fourth user plane network element.
  • the method further includes: including the identifier of the fourth user plane network element in the identifier list, and the identifier of the third user plane network element is not in the identifier list, the group The management function network element obtains a fifth tunnel port identifier and a sixth tunnel port identifier, where the fifth tunnel port identifier is the identifier of the fifth tunnel port of the third tunnel on the third user plane network element, and the sixth tunnel port identifier Is the identifier of the sixth tunnel port of the third tunnel on the fourth user plane network element, the third tunnel is the tunnel between the third user plane network element and the fourth user plane network element; the group The management function NE creates the rule group applied to the fifth tunnel port for the LAN group, and the group management function NE creates the rule group applied to the sixth tunnel port for the LAN group And, the group management function network element updates the local area network group FAR applied on the fourth user plane network element; correspondingly, the third message is also used to configure the rule group on the fifth tunnel port; And con
  • the method further includes: in a case where the first terminal will leave the local area network group, the group management function network element sends a fifth message to the session management network element, the fifth message Used to delete the rule group applied on the first session port and delete or update the local area network group FAR applied on the first user plane network element, wherein the updated application is on the first user plane network
  • the local area network group FAR on the element is obtained by the group management function network element updating the local area network group FAR applied to the first user plane network element according to the context information.
  • the method further includes: including an identifier of a fifth user plane network element in the identifier list, and dividing the first user plane network element from the terminal member list that does not have the LAN group
  • the group management function network element updates the local area network group FAR applied to the fifth user plane network element; correspondingly, the fifth message is also used to delete the A fourth tunnel between the first user plane network element and the fifth user plane network element, and deleting the rule group on the seventh tunnel port of the first user plane network element, and deleting the fifth user plane network
  • the rule group on the eighth tunnel port of the element and updating the local area network group FAR applied to the fifth user plane network element, where the seventh tunnel port is the fourth tunnel on the first user plane network
  • the tunnel port on the element, the eighth tunnel port is the tunnel port of the fourth tunnel on the fifth user plane network element.
  • a group communication method includes: in a case where a first terminal initiates access to a local area network group, a first user plane network element receives a first message from a session management network element.
  • a message includes a first session port identifier, a rule group applied on the first session port corresponding to the first session port identifier, and a LAN group forwarding action of the created or updated application on the first user plane network element Rule FAR, where the first session port identifier is the identifier of the first session port on the first user plane network element used for access by the first terminal;
  • the rule group includes an ingress packet detection rule PDR, an egress PDR and Exit FAR;
  • the exit PDR includes the identification of the exit FAR, and the entrance PDR includes the identification of the local area network group FAR; wherein, the entrance PDR is used to identify broadcast messages belonging to the local area network group, and the local area network group FAR It is used to copy the broadcast message and forward it to the designated exit;
  • the exit PDR includes:
  • the first message further includes a first tunnel port identifier and the rule group applied to the first tunnel port corresponding to the first tunnel port identifier, where the first tunnel port identifier is the first An identification of a first tunnel port of the tunnel on the first user plane network element.
  • the first tunnel is a tunnel between the first user plane network element and the second user plane network element; the method further includes: The first user plane network element creates the first tunnel port according to the first tunnel port identifier, and configures the rule group on the first tunnel port.
  • the method further includes: in a case where the first terminal is no longer served by the first user plane network element, the first user plane network element receives the first from the session management network element Two messages, the second message includes the first session port identifier, and the second message includes the ID of the local area network group FAR applied on the first user plane network element or the updated application on the first user plane The local area network group FAR on the network element; the first user plane network element deletes the first session port and the rule group applied to the first session port according to the first session port identifier; and, the first user The surface network element deletes the local area network group FAR applied to the first user plane network element according to the identification of the local area network group FAR applied to the first user plane network element; or, the first user plane network element Update the LAN group FAR on the first user plane network element according to the updated LAN group FAR on the first user plane network element.
  • the second message further includes a first tunnel port identifier, where the first tunnel port identifier is the identifier of the first tunnel port of the first tunnel on the first user plane network element, the The first tunnel is a tunnel between the first user plane network element and the second user plane network element; the method further includes: the first user plane network element deleting the first tunnel port according to the first tunnel port identifier And the rule group applied to the first tunnel port.
  • a group communication method includes: in a case where a first terminal initiates access to a local area network group, a session management network element receives a first message from a group management function network element.
  • a message includes an identifier of the first user plane network element, a first session port identifier corresponding to the identifier of the first user plane network element, a rule group applied to the first session port corresponding to the first session port identifier, And the created or updated application group local area group forwarding action rule FAR on the first user plane network element, where the first session port is used on the first user plane network element for the first terminal to access Session port;
  • the rule group includes the entry packet detection rule PDR, exit PDR and exit FAR;
  • the exit PDR includes the identification of the exit FAR,
  • the entrance PDR includes the identification of the local area network group FAR; wherein, the entrance PDR is used
  • the LAN group FAR is used to copy the broadcast message and forward it to the
  • the first message further includes a first tunnel port identifier corresponding to the identifier of the first user plane network element and the rule applied to the first tunnel port corresponding to the first tunnel port identifier Group, and the identifier of the second user plane network element, the second tunnel port identifier corresponding to the identifier of the second user plane network element, the rule group applied to the second tunnel port corresponding to the second tunnel port identifier, and The updated LAN group FAR applied on the second user plane network element; wherein, the first tunnel port is the tunnel port of the first tunnel on the first user plane network element, and the second tunnel port is the first A tunnel is a tunnel port on the second user plane network element, the first tunnel is a tunnel between the first user plane network element and the second user plane network element; correspondingly, the first message also includes the A first tunnel port identifier and the rule group on the first tunnel port; the method further includes: the session management network element sending a third message to the second user plane network element according to the identifier of the second user plane network
  • the method further includes: when the first terminal is updated from accessing the first user plane network element to accessing a third user plane network element in the local area network group, the session The management network element receives a fourth message from the group management function network element, the fourth message includes the identifier of the first user plane network element, and the first session port identifier corresponding to the identifier of the first user plane network element , And the fourth message includes the identification of the local area network group FAR applied on the first user plane network element or the updated local area network group FAR applied on the first user plane network element, and, the first The four messages include the identifier of the third user plane network element, the third session port identifier corresponding to the identifier of the third user plane network element, and the rule group applied to the third session port corresponding to the third session port identifier And a LAN group FAR of the created or updated application on the third user plane network element, wherein the third session port is a session port on the third user plane network element for the first terminal to access
  • the session management network element receive
  • the method further includes: the fourth message further includes a third tunnel port identifier corresponding to the identifier of the first user plane network element, an identifier of the fourth user plane network element, and the fourth The fourth tunnel port identifier corresponding to the identifier of the user plane network element, and the updated local area network group FAR applied to the fourth user plane network element, wherein the third tunnel port identifier is the second tunnel in the first A tunnel port identifier on a user plane network element, the fourth tunnel port identifier is the tunnel port identifier of the second tunnel on the fourth user plane network element; correspondingly, the fifth message also includes the third tunnel port Identification; the method further includes: the session management network element sending a seventh message to the fourth user plane network element according to the identification of the fourth user plane network element, the seventh message including the fourth tunnel port identifier and the update The later application is to the local area network group FAR on the fourth user plane network element.
  • the fourth message further includes a fifth tunnel port identifier corresponding to the identifier of the third user plane network element and the rule group applied to the fifth tunnel port corresponding to the fifth tunnel port identifier ; And, the fourth message further includes an identifier of the fourth user plane network element, a sixth tunnel port identifier corresponding to the identifier of the fourth user plane network element, and a sixth tunnel port corresponding to the sixth tunnel port identifier
  • the fifth tunnel port is the tunnel port of the third tunnel on the third user plane network element, and the sixth The tunnel port is a tunnel port of the third tunnel on the fourth user plane network element, and the third tunnel is a tunnel between the third user plane network element and the fourth user plane network element; correspondingly, the first
  • the six messages also include the fifth tunnel port identifier and the rule group of the fifth tunnel port; the method further includes: the session management network element according to the identifier of the fourth user plane network element, to the fourth user
  • the session management network element receives a ninth message from the group management function network element, the ninth message includes the first The identifier of the user plane network element, the first session port identifier corresponding to the identifier of the first user plane network element, and the ninth message include the identifier of the local area network group FAR applied to the first user plane network element Or the updated local application group FAR on the first user plane network element; the session management network element sends a tenth message to the first user plane network element according to the identifier of the first user plane network element, The tenth message includes the first session port identifier, and the fifth message includes the identification of the local area network group FAR applied on the first user plane network element or the updated application on the first user plane network element The local area network FAR.
  • the ninth message further includes a seventh tunnel port identifier corresponding to the identifier of the first user plane network element, an identifier of the fifth user plane network element, and an identifier of the fifth user plane network element An eighth tunnel port identifier corresponding to the identifier, and the updated local area network FAR applied on the fifth user plane network element, where the seventh tunnel port identifier is the fourth tunnel on the first user plane network element A tunnel port identifier on the Internet, the eighth tunnel port identifier is the tunnel port identifier of the fourth tunnel on the fourth user plane network element, the fourth tunnel is the first user plane network element and the fifth user plane network Tunnel between elements; correspondingly, the tenth message also includes the seventh tunnel port identifier; the sending module is further configured to send the tenth to the fifth user plane network element according to the identifier of the fifth user plane network element A message, the eleventh message includes the eighth tunnel port identifier, and the updated local area network group FAR applied on the fifth user plane network element.
  • a group communication method includes: in a case where a first terminal joins a multicast group, a group management function network element obtains an identifier of a first user plane network element accessed by the first terminal And the first session identifier, the first session port identifier is the identifier of the first session port on the first user plane network element for the first terminal to access; the group management function network element creates an application for the multicast group in the first The egress PDR and egress FAR of a session port, and the group management function network element creates or updates the multicast group FAR applied to the first user plane network element for the multicast group, and the multicast group FAR is used for the multicast
  • the group's multicast messages are copied and forwarded to the designated outlet; the outlet PDR is used to identify the type of multicast message, and the outlet FAR is used to add an outer message header and mark the transport layer to the multicast message and send it through the corresponding port Go out; the group management function network element send
  • the multicast members of the multicast group join, they only need to adjust (update or create) the multicast group FAR on the associated user plane network element, and adjust (create) the associated UPF network element with The ingress PDR, egress PDR and egress FAR corresponding to the multicast member, or adjusting (creating) the egress PDR and egress FAR corresponding to the multicast member on the associated UPF network element, other multicast members in the multicast group
  • the corresponding entrance PDR, exit PDR and exit FAR will not change. Therefore, when there are many multicast members in the multicast group, the configuration workload caused by the change in the number of multicast members can be greatly increased, and the configuration workload caused by the change in the number of multicast members can be greatly reduced.
  • a group communication method includes: a first user plane network element receives a first message from a session management network element, the first message includes a first session port identifier, and is applied in a first session The exit PDR and exit FAR on the first session port corresponding to the port identifier, and the created or updated multicast group forwarding action rule FAR applied on the first user plane network element, where the first session port identifier is the first The identifier of the first session port on the user plane network element used by the first terminal to access; the multicast group FAR is used to copy the multicast message of the multicast group and forward it to the specified exit; the exit PDR is used to identify the group The type of broadcast message.
  • the export FAR is used to add an outer message header and mark the transport layer to the multicast message and send it through the corresponding port; the first user plane network element is identified on the first session port according to the first session port identifier Configure the egress PDR and egress FAR; and, the first user plane network element creates the multicast group FAR on the first user plane network element according to the created multicast group FAR on the first user plane network element; or, the first A user plane network element updates the multicast group FAR on the first user plane network element according to the updated multicast group FAR applied on the first user plane network element.
  • a group communication method includes: in a case where a first terminal joins a multicast group, a session management network element receives a first message from a group management function network element.
  • the message includes the identifier of the first user plane network element accessed by the first terminal, the first session port identifier corresponding to the identifier of the first user plane network element, and the exit applied to the first session port corresponding to the first session port identifier PDR and egress FAR, and the created or updated multicast group forwarding action rule FAR applied on the first user plane network element; the session management network element sends the first user plane network element according to the identifier of the first user plane network element Send the first session port identifier, the egress PDR and egress FAR on the first session port, and the multicast group FAR created or updated on the first user plane network element.
  • a group management function network element having a function of implementing the method described in the first aspect or the fourth aspect.
  • This function can be realized by hardware, and can also be realized by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a group management function network element including: a processor and a memory; the memory is used to store computer-executed instructions, and when the group management function network element is running, the processor executes The computer executes instructions to cause the group management function network element to perform the group communication method as described in any one of the first aspect or the fourth aspect above.
  • a network element for group management function including: a processor; the processor is configured to couple with a memory and read an instruction in the memory, and then execute the first aspect or the first as described above according to the instruction
  • the group communication method according to any one of the four aspects.
  • a computer-readable storage medium having instructions stored therein, which when run on a computer, enables the computer to perform any of the above-mentioned first or fourth aspects.
  • a computer program product containing instructions, which when run on a computer, enables the computer to execute the group communication method described in any one of the first aspect or the fourth aspect.
  • an apparatus for example, the apparatus may be a chip system
  • the apparatus includes a processor for supporting a group management function network element to implement the functions mentioned in the first aspect or the fourth aspect , For example, creating a rule group applied to the first session port for a local area network group.
  • the device further includes a memory for storing program instructions and data necessary for the network element of the group management function.
  • the device When the device is a chip system, it may be constituted by a chip, or may include a chip and other discrete devices.
  • a first user plane network element is provided, and the first user plane network element has a function of implementing the method described in the second aspect or the fifth aspect.
  • This function can be realized by hardware, and can also be realized by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a first user plane network element including: a processor and a memory; the memory is used to store computer execution instructions, and when the first user plane network element is running, the processor executes the memory storage The computer executes instructions to cause the first user plane network element to perform the group communication method as described in any one of the second or fifth aspects above.
  • a first user plane network element including: a processor; the processor is configured to couple with a memory and read an instruction in the memory, and execute the second aspect or the above according to the instruction
  • the group communication method according to any one of the fifth aspects.
  • a computer-readable storage medium in which instructions are stored in a computer-readable storage medium, which when executed on a computer, enables the computer to perform any one of the second aspect or the fifth aspect The group communication method.
  • a computer program product containing instructions which, when run on a computer, enable the computer to execute the group communication method described in any one of the above second or fifth aspects.
  • an apparatus for example, the apparatus may be a chip system
  • the apparatus includes a processor for supporting the first user plane network element to implement the functions described in the second aspect or the fifth aspect For example, create the first session port according to the first session port identifier, and configure the rule group on the first session port.
  • the device further includes a memory for storing necessary program instructions and data of the first user plane network element.
  • the device When the device is a chip system, it may be constituted by a chip, or may include a chip and other discrete devices.
  • a session management network element having the function of implementing the method described in the third aspect or the sixth aspect.
  • This function can be realized by hardware, and can also be realized by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a session management network element including: a processor and a memory; the memory is used to store computer execution instructions, and when the session management network element is running, the processor executes the computer execution stored in the memory An instruction to cause the session management network element to perform the group communication method described in any one of the third aspect or the sixth aspect above.
  • a session management network element including: a processor; the processor is configured to couple with a memory and read an instruction in the memory, and then perform the third aspect or the first as described above according to the instruction
  • the group communication method according to any one of the six aspects.
  • a computer-readable storage medium stores instructions which, when run on a computer, enable the computer to perform any of the third or sixth aspects Item group communication method.
  • a computer program product containing instructions which when run on a computer, enables the computer to execute the group communication method described in any one of the third or sixth aspects.
  • an apparatus for example, the apparatus may be a chip system
  • the apparatus includes a processor for supporting a session management network element to implement the functions mentioned in the third aspect or the sixth aspect,
  • the first user plane network element is determined according to the identifier of the first user plane network element.
  • the device further includes a memory, which is used to store necessary program instructions and data of the session management network element.
  • the device is a chip system, it may be constituted by a chip, or may include a chip and other discrete devices.
  • a group communication system in a twenty-fifth aspect, includes a group management function network element, a session management function network element, and a first user plane network element.
  • the group management function network element is used to perform the steps performed by the group management function network element in the above-mentioned first aspect or fourth aspect, or the solution provided in the embodiments of the present application.
  • the first user plane network element is used to perform the steps performed by the first user plane network element in the above-mentioned second aspect or fifth aspect, or the solution provided in the embodiments of the present application.
  • the session management network element is used to perform the steps performed by the session management network element in the above-mentioned third aspect or sixth aspect, or the solution provided in the embodiments of the present application.
  • Figure 1 is a schematic diagram of the flow of user plane forwarding messages defined by the existing 3GPP TS29.244;
  • 2a is a schematic diagram of communication in a broadcast scenario provided by an embodiment of the present application.
  • 2b is a schematic diagram of communication in a multicast scenario provided by an embodiment of the present application.
  • FIG. 3a is a schematic diagram 1 of distribution of session ports or tunnel ports provided by an embodiment of the present application.
  • 3b is a second schematic diagram of distribution of session ports or tunnel ports provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of an entrance and an exit provided by an embodiment of this application.
  • FIG. 5 is a schematic diagram 1 of an idea architecture of a group communication method provided by an embodiment of this application.
  • FIG. 6 is a schematic diagram of a group FAR provided by an embodiment of this application.
  • 7a is a schematic diagram of a rule group provided by an embodiment of this application.
  • 7b is a schematic structural diagram of a multicast forwarding tree provided by an embodiment of this application.
  • 7c is a schematic diagram 1 of a configuration of a UPF network element in a multicast scenario provided by an embodiment of this application;
  • FIG. 8 is a schematic structural diagram of a group communication system according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a 5G network architecture provided by an embodiment of this application.
  • 10 is a schematic diagram of the existing user plane architecture of 5GLAN services
  • FIG. 11 is a schematic structural diagram of a communication device according to an embodiment of this application.
  • FIG. 12 is a schematic flowchart 1 of a group communication method provided by an embodiment of the present application.
  • FIG. 13 is a schematic diagram 1 of a configuration of a UPF network element in a broadcast scenario provided by an embodiment of this application;
  • FIG. 14 is a schematic diagram 2 of a configuration of a UPF network element in a broadcast scenario provided by an embodiment of this application;
  • 15 is a schematic diagram 3 of a configuration of a UPF network element in a broadcast scenario provided by an embodiment of this application;
  • 16 is a second schematic flowchart of a group communication method according to an embodiment of the present application.
  • 17 is a schematic diagram 4 of configuration of a UPF network element in a broadcast scenario provided by an embodiment of the present application.
  • FIG. 18 is a schematic diagram 5 of configuration of a UPF network element in a broadcast scenario provided by an embodiment of this application;
  • 19 is a schematic diagram 6 of configuration of a UPF network element in a broadcast scenario provided by an embodiment of this application;
  • 20 is a schematic diagram 7 of configuration of a UPF network element in a broadcast scenario provided by an embodiment of this application;
  • 21 is a schematic diagram 8 of configuration of a UPF network element in a broadcast scenario provided by an embodiment of this application;
  • FIG. 22 is a schematic diagram 9 of configuration of a UPF network element in a broadcast scenario provided by an embodiment of this application;
  • FIG. 23 is a third schematic flowchart of a group communication method according to an embodiment of the present application.
  • FIG. 24 is a schematic diagram 10 of a configuration of a UPF network element in a broadcast scenario provided by an embodiment of this application;
  • 25 is a schematic diagram 11 of configuration of a UPF network element in a broadcast scenario provided by an embodiment of the present application.
  • 26 is a schematic diagram 12 of a configuration of a UPF network element in a broadcast scenario provided by an embodiment of this application;
  • FIG. 27 is a schematic diagram 13 of configuration of a UPF network element in a broadcast scenario provided by an embodiment of this application;
  • 29 is a fourth schematic flowchart of a group communication method according to an embodiment of the present application.
  • FIG. 30 is a second schematic diagram of configuration of a UPF network element in a multicast scenario provided by an embodiment of this application;
  • FIG. 31 is a schematic diagram 3 of configuration of a UPF network element in a multicast scenario provided by an embodiment of this application;
  • FIG. 32 is a schematic diagram 4 of configuration of a UPF network element in a multicast scenario provided by an embodiment of the present application;
  • 33 is a schematic diagram 5 of configuration of a UPF network element in a multicast scenario provided by an embodiment of this application;
  • 34 is a schematic flowchart 5 of a group communication method according to an embodiment of the present application.
  • 35 is a schematic diagram 6 of configuration of a UPF network element in a multicast scenario provided by an embodiment of this application;
  • 36 is a schematic diagram 7 of configuration of a UPF network element in a multicast scenario provided by an embodiment of this application;
  • FIG. 37 is a schematic diagram 8 of configuration of a UPF network element in a multicast scenario provided by an embodiment of this application;
  • FIG. 38 is a second schematic diagram of an idea architecture of a group communication method provided by an embodiment of this application.
  • 39 is a schematic structural diagram of a group management function network element provided by an embodiment of this application.
  • FIG. 40 is a schematic structural diagram of a first user plane network element provided by an embodiment of this application.
  • FIG. 41 is a schematic structural diagram of a session management network element provided by an embodiment of this application.
  • Broadcast is a pair of all communication methods.
  • one LAN for example, 5GLAN
  • Terminals contracted to the LAN can form a LAN group, where the terminal contracted to the LAN can be called a terminal member of the LAN group, that is, the terminal joins the LAN group during the contract (may be joining
  • the related implementation can refer to the existing solution, which will not be repeated here.
  • the terminal members of the LAN group enter the network (that is, establish a user plane connection.
  • the typical network access method is that the terminal initiates a packet data unit (PDU) session establishment request.
  • PDU packet data unit
  • the following embodiments all use the network access method to initiate PDU session establishment for the terminal
  • the request is used as an example to explain
  • the terminal member can be regarded as having entered the network, and the terminal members after the network access can communicate the same.
  • the terminal member can be regarded as having entered the network, and the terminal members after the network access can communicate the same.
  • any terminal in the LAN group that has been connected to the network can be used as a broadcast source to send broadcast messages; at the same time, it can be used as a broadcast member to receive broadcast messages.
  • terminal members in the LAN group that have entered the network include terminal 1, terminal 2, terminal 3, terminal 4, terminal 5, and terminal 6.
  • terminal 1 as a broadcast source as an example, the corresponding communication diagram can be shown in Figure 2a, that is, the broadcast message sent by terminal 1 can be transmitted to terminal 2, terminal 3, terminal 4, terminal 5, and terminal 5 in the LAN group.
  • Terminal 6 the broadcast message sent by terminal 1 can be transmitted to terminal 2, terminal 3, terminal 4, terminal 5, and terminal 5 in the LAN group.
  • the broadcast address in the embodiment of the present application may be the destination IP address is all 1, such as 255.255.255.255; or, the broadcast address in the embodiment of the present application may also be the destination media access control (MAC) address All are 1, such as 255.255.255.255, for details, please refer to the definition of the existing broadcast address, which will not be repeated here.
  • MAC media access control
  • one multicast source and multiple multicast members can form a multicast group (also referred to as a multicast group for short).
  • a multicast group also referred to as a multicast group for short.
  • the source for sending IP packets is called the multicast source
  • the multicast users receiving multicast data are called multicast members. That is, multicast is directional, and the direction is from the multicast source to the multicast members.
  • the perspective of the multicast source and the multicast members cannot be changed, otherwise they belong to different multicast groups. For example, assume that the terminal members in the LAN group include terminal 1, terminal 2, terminal 3, terminal 4, terminal 5, and terminal 6.
  • terminal 1 Taking terminal 1 as a multicast source, terminal 3, terminal 5 and terminal 6 as multicast members to form a multicast group as an example, the corresponding communication diagram can be shown in Figure 2b, that is, the multicast message sent by terminal 1 can be Transmit to terminal 2, terminal 5 and terminal 6 in the multicast group respectively.
  • the multicast source is determined by the application layer of the open system interconnection (OSI) model.
  • OSI open system interconnection
  • the terminal wants to receive multicast data, it can explicitly send the Internet Group Management Protocol ( internet group management protocol (IGMP) join message to the network, the network records that the terminal joins a multicast group, and then forwards the multicast data sent by the multicast source to it, that is, the multicast member is
  • IGMP internet group management protocol
  • the specific joining process may refer to the subsequent method embodiments, which will not be repeated here.
  • the multicast address in the embodiment of the present application may be a multicast IP version 4 (IP version 4 (IPv4) address assigned by the Internet Digital Assignment Authority (IANA), ranging from 224.0.0.0 to 239.255 .255.255 interval; or, the multicast address in this embodiment of the present application may also be a multicast MAC address with the last bit of 48 bits high in 48 bits constant at 1, or the multicast address in this embodiment of the present application may also be other
  • IP version 4 IP version 4
  • IANA Internet Digital Assignment Authority
  • the group in the embodiment of the present application may include the above-mentioned LAN group and multicast group, which will be described here in a unified manner, and will not be repeated below.
  • the session port on the user plane network element is a logical port.
  • the user plane network element is established according to the session port identifier allocated by the session management network element or the user plane network element.
  • the core network tunnel port can also be understood as the anchor point of the terminal's PDU session on the core network side. Its function is to anchor the terminal to the user plane network element (that is, to connect a terminal), so as to receive the message sent by the terminal through the session port and send the message to the terminal through the session port.
  • the session port identifier here may be TEID, for example.
  • the user plane network element 1 may manage the network element or the user plane according to the session
  • the session port identifier 1 assigned by network element 1 establishes session port 1.
  • the terminal 2 may establish a PDU session, assuming that the user plane network element accessed by the terminal 2 is the user plane network element 1, the user plane network element 1 may be based on the session port identifier assigned by the session management network element or the user plane network element 1. 2 Establish session port 2.
  • the terminal 3 when the terminal 3 establishes a PDU session, assuming that the user plane network element accessed by the terminal 3 is the user plane network element 1, the user plane network element 1 may be based on the session port identifier assigned by the session management network element or the user plane network element 1.
  • 3 Establish session port 3.
  • the terminal n when the terminal n establishes a PDU session, assuming that the user plane network element accessed by the terminal n is the user plane network element 1, the user plane network element 1 may be based on the session port identifier allocated by the session management network element or the user plane network element 1.
  • n Establish session port n, etc.
  • the tunnel port on the user plane network element is a logical port, which may specifically be that when a terminal in a LAN group establishes a PDU session, the user plane network element accessed by the terminal and the LAN group After the first tunnel is established between the user plane network elements accessed by other terminals in the group, the user plane network elements accessed by the terminal and the user plane network elements accessed by other terminals in the group are respectively managed according to the session
  • the assigned first tunnel port identifier and second tunnel port identifier create a tunnel of the LAN group granularity, where the first tunnel identifier is the tunnel port of the first tunnel on the user plane network element side that the terminal accesses, and the second tunnel The identifier is a tunnel port on the user plane network element side where the first tunnel is accessed by other terminals in the group.
  • the function of the tunnel port is to receive the LAN group message from the connected user plane network element through the tunnel port, and send the LAN group message to the connected user plane network element through the tunnel port.
  • the first tunnel port identifier here may be TEID1
  • the second tunnel port identifier may be TEID2, for example.
  • the sequence of terminals in the LAN group to access the network is terminal 3, terminal 4, terminal 1, terminal 2, and terminal 5, respectively.
  • the terminal 3 establishes a PDU session, assuming that the user plane network element accessed by the terminal 3 is the user plane network element 2, the user plane network element 2 may be based on the session port identifier 3 assigned by the session management network element or the user plane network element 2.
  • the terminal 4 establishes a PDU session, assuming that the user plane network element accessed by the terminal 4 is the user plane network element 2, the user plane network element 2 may be established according to the session port identifier 4 assigned by the session management network element or the user plane network element 2. Session port 4.
  • the terminal 1 When the terminal 1 establishes a PDU session, assuming that the user plane network element accessed by the terminal 1 is the user plane network element 1, the user plane network element 1 may be established according to the session port identifier 1 assigned by the session management network element or the user plane network element 1. Session port 1.
  • the session management network element needs to initiate the establishment of the tunnel 1 between the user plane network element 1 and the user plane network element 2, and then the user
  • the network element 1 can establish the tunnel port 1 according to the tunnel port identifier 1 assigned to the user plane NE 1 of the tunnel 1 assigned by the session management network element, and the user plane network element 2 can use the tunnel 1 assigned to the user plane by the session management network element Tunnel port identifier 2 on the side of element 2 establishes tunnel port 2.
  • terminal 2 When terminal 2 establishes a PDU session, it is assumed that the user plane network element that terminal 2 accesses is user plane network element 1, although terminal 3 and terminal 4 in the LAN group already exist to access user plane network element 2, but because the terminal 1When establishing a PDU session, tunnel port 1 has been established on user plane network element 1 and tunnel port 2 has been established on user plane network element 2.
  • tunnel port 1 and tunnel port 2 broadcast messages or LANs of the LAN group can be received or sent Multicast messages of a multicast group under the group, so at this time, the user plane network element 1 only needs to establish the session port 2 according to the session port identifier 2 assigned by the session management network element or the user plane network element 1.
  • the terminal 5 When the terminal 5 establishes a PDU session, assuming that the user plane network element accessed by the terminal 5 is the user plane network element 3, the user plane network element 3 may be established according to the session port identifier 5 assigned by the session management network element or the user plane network element 3. Session port 5.
  • the session management NE needs to initiate A tunnel 2 is established between the user plane network element 3 and the user plane network element 2, and then the user plane network element 3 can establish the tunnel port 4 according to the tunnel port identifier 4 assigned by the session management network element on the side of the user plane network element 3,
  • the user plane network element 2 may establish the tunnel port 3 according to the tunnel port identifier 3 of the tunnel 2 allocated by the session management network element on the user plane network element 2 side.
  • a tunnel 2 is established between the user plane network element 2 and the user plane network element 3 as an example for description.
  • a tunnel 3 may also be established between the user plane network element 1 and the user plane network element 3.
  • the packet sent by the terminal 1 can be forwarded to the user plane network element 3 through the user plane network element 2 and thus can be sent to the terminal 5, which will be described here in a unified manner, and will not be repeated below.
  • the member ports on the user plane network element refer to the set of ports of a group on the user plane network element, including at least one of the aforementioned session ports or tunnel ports.
  • the functions and roles of member ports are the same.
  • For a LAN group all ports on a user plane network element that can receive or send broadcast messages of the LAN group belong to member ports;
  • For a multicast group a user All ports on the surface NE that send the multicast packets of the multicast group belong to member ports.
  • the terminal or user plane network element connected to the member port can be called a member.
  • the member ports on the user plane network element only include the session port of the group, excluding the group's Tunnel port.
  • a group includes terminal 1, terminal 2, terminal 3, ..., terminal n, a total of n terminals, and these n terminals are all connected to the user plane network element 1, then in the broadcast scenario
  • user plane network element 1 includes session port 1, session port 2, session port 3, ..., session port n, a total of n member ports
  • the members on the user plane network element 1 include terminal 1, terminal 2, terminal 3, ..., terminal n, a total of n members.
  • terminal 1 is a multicast source
  • user plane network element 1 includes session port 2, session Port 3, ...
  • session port n has a total of (n-1) member ports
  • the members on user plane network element 1 include terminal 2, terminal 3, ..., and terminal n with a total of (n-1) members.
  • the member ports on user plane network element 1 include session port 1, session port 2, and tunnel port 1, a total of 3 member ports.
  • the members on user plane network element 1 include terminal 1, terminal 2 and user plane network element 2 in total 3 members.
  • the member ports on user plane NE 2 include a total of 4 member ports: tunnel port 2, tunnel port 3, session port 3, and session port 4.
  • the members on user plane NE 2 include user plane NE 1 and user plane NE 3. There are 4 members in Terminal 3 and Terminal 4.
  • the member ports on user plane network element 3 include a total of 2 member ports, tunnel port 4 and session port 5, and the members on user plane network element 3 include a total of 2 members on user plane network element 2 and terminal 5.
  • a multicast group includes terminal 1, terminal 2, and terminal 5.
  • terminal 1 is used as a multicast source
  • terminal 2 and terminal 5 are used as multicast members.
  • the member ports on element 1 include a total of 2 member ports: session port 2 and tunnel port 1.
  • the members on the user plane network element 1 include a terminal 2 and a user plane network element 2 with a total of 2 members.
  • the member ports on user plane NE 2 include a total of 3 member ports: tunnel port 3, session port 3, and session port 4.
  • the members on user plane NE 2 include a total of 3 user plane NE 3, terminal 3, and terminal 4 member.
  • the member ports on the user plane network element 3 include a total of one member port of the session port 5, and the members on the user plane network element 3 include a total of one member of the terminal 5.
  • the number of member ports of a LAN group is equal to the sum of all session ports and tunnel ports corresponding to the LAN group on the user plane network element ;
  • the number of member ports of a multicast group is equal to the number of all ports on the user plane network element of the multicast group that send the multicast packets of the multicast group.
  • the entry refers to the port on the user plane network element that receives the message
  • the exit refers to the port on the user plane network element that sends the message.
  • the ingress and egress both belong to two directions of a logical port, where the logical port may be the above-mentioned session port or tunnel port.
  • the exit here is also a member port, which is described here in a unified manner and will not be described in detail below.
  • the entrance may be session port 1, the exit may be session port 2 and tunnel port 1; or, the entrance may be session port 2.
  • the exit can be session port 1 and tunnel port 1; or, the entrance can be tunnel port 1, and the exit can be session port 1 and session port 2.
  • a port can be used as both an entrance and an exit.
  • the entrance may be session port 1, and the exit Can be session port 2 and tunnel port 1; or, taking the user plane network element 2 in FIG. 3b as an example, the entrance can be tunnel port 2 and the exit can be tunnel port 3; or, the user in FIG. 3b above Taking network element 3 as an example, the entrance may be tunnel port 4, and the exit may be session port 5.
  • FIG. 4 is only for convenience of explanation, and the inlet and the outlet are shown separately.
  • the entrance and the exit may correspond to the same physical interface or different physical interfaces, which is not specifically limited in the embodiment of the present application.
  • the following embodiments are similar, and are described here in a unified manner, and are not described in detail below.
  • the upstream port and the downstream port in the embodiment of the present application are introduced to facilitate the description in the group communication scenario.
  • the upstream port can correspond to the above-mentioned inlet and be directly or indirectly connected to the multicast source
  • the downstream port can correspond to the above-mentioned outlet and be directly or indirectly connected to the multicast member.
  • At least one of the following or a similar expression refers to any combination of these items, including any combination of a single item or a plurality of items.
  • at least one item (a) in a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be a single or multiple .
  • the words “first” and “second” are used to distinguish the same or similar items that have substantially the same functions and functions. Those skilled in the art may understand that the words “first” and “second” do not limit the number and execution order, and the words “first” and “second” do not necessarily mean different.
  • the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly explain the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.
  • FIG. 5 it is a schematic diagram of the main idea of the group communication method, device, and system provided by the embodiments of the present application.
  • the inress function on the user plane network element is simplified, and a group forwarding function and an egress function are added on the user plane network element.
  • the entry function on the user plane network element includes a broadcast message or a multicast message that identifies that the message belongs to a certain group through the entry PDR applied to the session port or the tunnel port.
  • the ingress PDR applied to session port 3 or tunnel port 3 in FIG. 5 includes ingress PDR1, ingress PDR2, ..., ingress PDRn.
  • the entry PDR1 can identify the broadcast messages belonging to the group 1
  • the entry PDR2 can identify the broadcast messages belonging to the group 2
  • the entry PDRn can identify the multicast messages belonging to the group 2, and so on.
  • the function of identifying the broadcast message or the multicast message belonging to a certain group through the ingress PDR will be described in detail in subsequent embodiments, and will not be repeated here.
  • the group forwarding function on the user plane network element is realized by group FAR (group FAR).
  • group FAR group FAR
  • the entrance PDR includes the identifier of the group FAR of the corresponding group, that is, the entrance PDR points to the group FAR of the corresponding group.
  • the entry PDR2 in FIG. 5 points to the group FAR2.
  • the group FAR in the embodiment of the present application includes the following fields:
  • an identification field of a group FAR may be, for example, a group identifier
  • the group identifier may be, for example, a virtual local area network (Virtual Local Area Network, VLAN) identifier or a multicast group identifier.
  • VLAN Virtual Local Area Network
  • the group type field which may be broadcast or multicast, for example.
  • the forwarding action bucket (forwarding action buckets) field, where the forwarding action bucket can be understood as a collection of forwarding actions (forwarding actions, FA).
  • the identifier of the group FAR is 1, and the group FAR of type broadcast may include FA1, FA2, ..., FAm, and m is a positive integer.
  • the number of FAs in the group FAR of a group is the same as the number of exits of the group on the user plane network element where the group FAR is located.
  • m FAs in the group FAR correspond to m outlets, which are outlet 1, outlet 2, ..., outlet m.
  • the main function of each FA is to specify the corresponding outlet, that is, the outlet from which the message is sent.
  • the multiple FAs in the group FAR in FIG. 6 are just an example for decomposing the rules of the FAR for ease of understanding.
  • the rules of the group FAR may not need to be disassembled After the split, they respectively correspond to the FA in FIG. 6 and are described here in a unified manner, and will not be described in detail below.
  • the processing logic of the group FAR is that, according to the number of exits of the group on the user plane network element where the group FAR is located, the message is copied into the same number of multiple copies and forwarded to the group FAR The specified exit is all member ports.
  • the processing logic of the group FAR is that according to the number of FAs, the message is copied into multiple copies equal to the number of FAs, and each FA processes a copy of the message.
  • the processing result includes forwarding the message to the outlet designated by the FA.
  • group-related broadcast and multicast communication can be completed through group FAR.
  • the egress function on the user plane network element is implemented through the egress PDR and egress FAR applied in the session port or tunnel port.
  • the export PDR includes the identification of the export FAR, that is, the export PDR points to the export FAR.
  • the exit PDR11 points to the exit FAR11
  • the exit PDR12 points to the exit FAR12, etc., and no further examples are given here.
  • the export PDR is used to identify the type of the message, such as the differentiated services code point (DSCP) field based on the IP message, or the 802.1p bit of the Ethernet frame to identify the priority of the message, the specific implementation The method will be described in detail in the subsequent method embodiments, and will not be repeated here.
  • the type of the message may be divided by the service priority corresponding to the message, for example, the service priority is divided into eight levels, which are the first service priority, the second service priority, ..., Eighth business priority.
  • the exit PDR1 may be used to identify the first service priority message
  • the exit PDR2 may be used to identify the second service priority message
  • the exit PDR3 may be used to identify the third service priority message.
  • the egress FAR is used to add an outer header (creation) to the packet and mark the transport layer (transport level) before forwarding the packet from the port where the egress PDR is located.
  • the port where the egress PDR is located is a session port
  • GPRS General Packet Radio Service
  • GTP tunneling protocol
  • QoS quality of service
  • QoS quality of service
  • the port where the egress PDR is located is a tunnel port (tunnel endpoint)
  • Other user plane network elements, etc. are not specifically limited in this embodiment of the present application.
  • FIG. 5 uses packets matching session port 1 or tunnel port 1 to egress PDR12 and session ports 2 or tunnel port 2 to egress PDR22 as an example.
  • the exit FAR12 indicated by the exit PDR12 and the exit FAR22 indicated by the exit PDR22 are sent to other terminals or user plane network elements.
  • the embodiment shown in FIG. 5 is only an example for taking a message sent by a terminal or a user plane network element as an example.
  • the terminal or user plane network element connected to the exit FAR in FIG. 5 may also be the same as the terminal or user plane network element connected to the entrance PDR in FIG.
  • the ingress function, group forwarding function and egress function please refer to the above description for details, and no more examples will be given here.
  • the terminal members in the group change for example, the terminal members of the LAN group enter the network, the multicast members of the multicast group join, the terminal members of the LAN group leave the network, and the multicast members of the multicast group leave .
  • the terminal members of the LAN group that have already entered the network move, or the multicast members of the multicast group move) only need to adjust (create, update or delete) the group FAR of the group on the associated user plane network element, and Adjust (create, update, or delete) the exit PDR and exit FAR associated with the terminal member on the associated user plane network element, or the entrance PDR, exit PDR, and exit FAR associated with the terminal member.
  • the rule group in the embodiment of the present application is applicable to the scenario where the group communication is broadcast (that is, the group is a LAN group).
  • each member port of the LAN group on the user plane network element is configured with an ingress PDR , Export PDR and export FAR rules.
  • session port 1 is configured with rule group 1 including ingress PDR1, egress PDR1 and egress FAR1
  • tunnel port 2 is configured with rules including ingress PDR2, egress PDR2 and egress FAR2 Group 2.
  • the entrance PDR belongs to the entrance section
  • the exit PDR and exit FAR belong to the exit section.
  • each member port of the LAN group on the user plane network element can receive and send messages.
  • the entrance PDR, the exit PDR, and the exit FAR reference may be made to the above-mentioned embodiment part, which will not be repeated here.
  • the specific configuration method of the LAN group information (including the rule group and the above-mentioned LAN group FAR) on the user plane network element and the forwarding method of the LAN group broadcast message will be described in detail in the subsequent method embodiment section, and will not be repeated here. .
  • the entrance PDR included in each member port points to the group of the user plane network element.
  • Group FAR As shown in (a) of FIG. 7a, the ingress PDR1 on the session port 1 and the ingress PDR2 on the tunnel port 2 point to the same LAN group FAR1.
  • the entrance PDR1 is used to identify broadcast messages from a terminal belonging to a certain LAN group
  • the entrance PDR2 is used to identify broadcast messages from a user plane network element belonging to the LAN group.
  • the description is unified and will not be repeated below.
  • FIG. 7a is only an example of a rule group applied to the session port of the user plane network element, and a rule group applied to the tunnel port of the user plane network element.
  • each terminal since there may be different terminal accesses on one user plane network element, and each terminal may correspond to one or more sessions, it is possible that one user plane network element may include multiple session ports or multiple tunnel ports.
  • each session port since one terminal can access different groups, each session port may include multiple rule groups 1 described above, and multiple rule groups 2 may be configured on each tunnel port.
  • multiple ingress PDRs are configured on session port 3 or tunnel port 3 in FIG. 5, and the multiple ingress PDRs belong to multiple rule groups 1, which are described here in a unified manner and will not be described in detail below.
  • the entry here may include multiple entry PDRs, and only after a match can be determined which entry PDR (that is, the aforementioned entry PDR identification message belongs to a group of broadcast messages or multicast messages).
  • multiple exit PDRs may be included in the exit, and it is necessary to determine which entry PDR corresponds to the match (that is, the above exit PDR is used to identify the type of the message), which is described here in a unified manner, and will not be repeated below.
  • the multicast forwarding tree in the embodiment of the present application is applicable to a scenario where group communication is multicast (that is, the group is a multicast group).
  • FIG. 7b it is a schematic structural diagram of a multicast forwarding tree provided by an embodiment of the present application.
  • the multicast forwarding tree includes a multicast source, a multicast member (one or more), and a user plane network element (one or more) between the multicast source and the multicast member.
  • the multicast source in FIG. 7b may be, for example, terminal 1; the multicast members may be, for example, terminal 2, terminal 3, and terminal 4; the user plane network element between terminal 1 and terminal 2 may be user plane network element 1, for example.
  • the user plane network element between the terminal 1 and the terminal 3 is, for example, the user plane network element 1 and the user plane network element 2 from the upstream direction to the downstream direction
  • the user plane network element between the terminal 1 and the terminal 4 is, for example, the upstream direction
  • the downstream direction is user plane network element 1 and user plane network element 2 in sequence.
  • the upstream direction here refers to the direction of the multicast source
  • the downstream direction refers to the direction of the multicast members.
  • user plane network element 1 can be regarded as the upstream user plane network element of user plane network element 2
  • the user plane network Element 2 can be regarded as a downstream user plane network element of user plane network element 1, which will be described here in a unified manner and will not be described in detail below.
  • terminal 1 may serve as an upstream member of user plane network element 1
  • user plane network element 1 may serve as an upstream member of user plane network element 2 and terminal 2, user plane.
  • the network element 2 may serve as an upstream member of the terminal 3 and the terminal 4.
  • terminal 3 and terminal 4 can serve as downstream members of user plane network element 2
  • user plane network element 2 and terminal 2 can serve as downstream members of user plane network element 1
  • user plane network element 1 can serve as downstream members of terminal 1.
  • the multicast group FAR needs to be configured on each user plane network element, and the ingress PDR is configured on each upstream port, and the respective downstream port is configured Export PDR and FAR, the results are shown in Figure 7c.
  • multicast group FAR1 and multicast group FAR2 are configured on user plane NE 1 and user plane NE 2, respectively; and, ingress PDR1 is configured on upstream port 1 of user plane NE 1, and on the user plane NE 1 Configure egress PDR1 and egress FAR1 on downstream port 1, configure egress PDR2 and egress FAR2 on downstream port 2 of user plane network element 1; and configure ingress PDR2 on upstream port 2 of user plane network element 2, and configure it on user plane network
  • the downstream port 3 of the element 2 is configured with the outlet PDR3 and the outlet FAR3, and the downstream port 4 of the user plane network element 2 is configured with the outlet PDR4 and the outlet FAR4.
  • the group communication system 80 includes a group management function network element, and one or more session management devices connected to the group management function network element Network elements (such as the first session management network element and the second session management network element in Figure 8), and one or more user plane network elements connected to each session management network element (as shown in Figure 8 with the first session The first user plane network element connected to the management network element, the second user plane network element and the third user plane network element, and the fourth user plane network element connected to the second session management network element).
  • Network elements such as the first session management network element and the second session management network element in Figure 8
  • user plane network elements connected to each session management network element (as shown in Figure 8 with the first session The first user plane network element connected to the management network element, the second user plane network element and the third user plane network element, and the fourth user plane network element connected to the second session management network element).
  • the group management function network element is used when the terminal members in the group change (such as the terminal member of the LAN group enters the network, the multicast member of the multicast group joins, the terminal member of the LAN group leaves the network, multicast The multicast members of the group leave, the terminal members of the LAN group that have entered the network move, or the multicast members of the multicast group move), adjust (create, update, or delete) the associated user plane through the associated session management NE
  • the group FAR of the group on the network element and adjust (create, update or delete) the associated user plane network element's exit PDR and exit FAR associated with the terminal member, or the entry PDR associated with the terminal member, Export PDR and export FAR.
  • multicast or broadcast communication can be implemented through the ingress PDR, egress PDR, egress FAR, and group FAR on the user plane network element.
  • the group communication system shown in FIG. 8 may be applied to the current 5G network or other networks in the future, which is not specifically limited in this embodiment of the present application.
  • the network element or entity corresponding to the group management function network element in FIG. 8 may be a 5G network architecture Group management function (group management function, GMF) network element in FIG. 8; the network element or entity corresponding to the session management network element (such as the first session management network element or the second session management network element) in FIG. 8 may be 5G Session management function (SMF) network element in the network architecture; user plane network element in Figure 8 (such as the first user plane network element, the second user plane network element, the third user plane network element or the fourth The network element or entity corresponding to the user plane network element) may be a UPF network element in a 5G network architecture.
  • group management function group management function
  • GMF group management function
  • SMF 5G Session management function
  • the aforementioned local area network may be 5GLAN.
  • 5GLAN may also be referred to as LAN, LAN-type service, LAN-virtual network (VN), 5GLAN-type service, 5GLAN- VN, 5GLAN group (5GLAN group), or LAN Group, etc.
  • VN LAN-virtual network
  • 5GLAN-type service 5GLAN- VN
  • 5GLAN group 5GLAN group
  • LAN Group etc.
  • the above-mentioned GMF network element may be a newly added network element in the 5G network architecture, and its function is 5GLAN group management, such as dynamically creating, modifying, or deleting a group based on the request of the terminal.
  • the above-mentioned functions of the GMF network element may also include managing user plane paths, setting user plane forwarding rules, and implementing isolation between groups.
  • the functions of managing user plane paths and achieving isolation between groups can also be completed by adding a path management function (path management function, PMF) network element, which is not specifically limited in the embodiments of the present application.
  • the embodiments of the present application are described by taking the function of the GMF network element may further include managing a user plane path, and implementing the function of isolating between groups.
  • the current 5G network can also include access equipment, access and mobility management (core) access and mobility management function (AMF) network elements, and user plane function (user plane function (UPF) network Element, authentication server function (AUSF) network element, network slice selection function (NSSF) network element, network open function (network exposure function, NEF) network element, network function storage function (network function Repository (NRF) network element, policy control function (PCF) network element, unified data management (Unified Data Management (UDM) network element and application function (application) function (AF) network element, etc., implemented in this application The example does not specifically limit this.
  • core access and mobility management
  • AMF access and mobility management function
  • UPF user plane function
  • AUSF authentication server function
  • NSSF network slice selection function
  • NEF network exposure function
  • NEF network exposure function
  • NEF network exposure function
  • NEF network exposure function
  • NEF network exposure function
  • NEF network exposure function
  • NEF network exposure function
  • NEF network exposure function
  • NEF network function storage
  • the terminal accesses the 5G network through the access device, the terminal communicates with the AMF network element through the next generation (N) 1 interface (abbreviated as N1), and the access device through the N2 interface (abbreviated as N2) ) Communicate with AMF network element; access equipment communicates with UPF network element through N3 interface (N3 for short); SMF network element communicates with UPF network element through N4 interface (N4 for short); UPF network element connects with N6 interface (N6 for short) Into the data network.
  • N1 next generation
  • N2 interface abbreviated as N2
  • N2 interface abbreviated as N2 interface
  • control plane network elements such as AUSF network element, AMF network element, SMF network element, NSSF network element, NEF network element, NRF network element, PCF network element, UDM network element, or AF network element shown in FIG. 9 can also be used Service interface to interact.
  • the service interface provided by the AUSF network element can be Nausf; the service interface provided by the AMF network element can be Namf; the service interface provided by the SMF network element can be Nsmf; the service interface provided by the NSSG network element It can be Nnssf; the service interface provided by the NEF network element can be Nnef; the service interface provided by the NRF network element can be Nnrf; the service interface provided by the PCF network element can be Npcf; the service provided by the UDM network element The interface can be Nudm; the service interface provided by the AF network element can be Naf.
  • Relevant descriptions can refer to the 5G system architecture (23G) architecture diagram in the 23501 standard, which will not be repeated here.
  • the service interface provided by the LAN controller to the outside may be Nlan.
  • each network element is only an exemplary one.
  • each network element may be deployed in multiples.
  • multiple SMF network elements or multiple UPF network elements may be deployed in a 5G network.
  • Different SMF network elements may communicate through the N16 interface (referred to as N16 for short) or through the forwarding of AMF network elements.
  • the AMF network element The interface between the element and the SMF network element is the N11 interface (abbreviated as N11), and the interface between the AMF network element is N14 (abbreviated as N14); different UPF network elements can pass the N9 interface (abbreviated as N9) or the Nx interface ( Referred to as Nx) communication.
  • the above-mentioned first session management network element may correspond to the SMF1 network element
  • the above-mentioned second session management network element may correspond to the SMF2 network element
  • the SMF1 network element and the SMF2 network element may communicate through N16 or be forwarded through the AMF network element Communicate.
  • the foregoing first user plane network element may correspond to the UPF1 network element
  • the foregoing second user plane network element may correspond to the UPF2 network element
  • the UPF1 network element and the UPF2 network element may communicate through N9 or Nx.
  • FIG 10 shows a schematic diagram of the existing user plane architecture of the 5GLAN service.
  • the terminal establishes a session to the UPF network element providing the 5GLAN service, thereby accessing the UPF network element providing the 5GLAN service.
  • UPF network elements that provide 5GLAN services can communicate with existing LANs in the data network through N6, for example, to communicate with personal computers (PCs) in the LAN; or, UPF network elements that provide 5GLAN services can also pass through
  • the connection between the internal UPF network element and the UPF network element associates sessions of different terminals to realize private communication, which is not specifically limited in the embodiments of the present application.
  • the terminals involved in the embodiments of the present application may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem; or Including subscriber units, cellular phones, smart phones, wireless data cards, personal digital assistant (PDA) computers, tablet computers, wireless modems, handheld devices (handheld), laptop (laptop computer), cordless phone (cordless phone) or wireless local loop (wireless local loop (WLL) station, machine type communication (machine type communication (MTC) terminal, user equipment (user equipment) , UE), mobile station (mobile station, MS), terminal device (terminal device) or relay user equipment, etc.
  • the relay user equipment may be, for example, a 5G residential gateway (RG).
  • RG 5G residential gateway
  • the access devices refer to devices that access the core network, and may be, for example, base stations and broadband network service gateways. (broadband network, gateway, BNG), aggregation switches, non-3rd generation partnership project (3GPP) access equipment, etc.
  • the base station may include various forms of base stations, such as macro base stations, micro base stations (also called small stations), relay stations, and access points.
  • the network element, the second user plane network element, the third user plane network element, or the fourth user plane network element can be implemented by one device, or can be implemented by multiple devices together, or can be a functional module within a device, This embodiment of the present application does not specifically limit this.
  • the above function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualized function instantiated on a platform (for example, a cloud platform).
  • FIG. 11 is a schematic diagram of a hardware structure of a communication device provided by an embodiment of the present application.
  • the communication device 1100 includes a processor 1101, a communication line 1102, a memory 1103, and at least one communication interface (FIG. 11 is only exemplary by including the communication interface 1104 as an example).
  • the processor 1101 may be a general-purpose central processing unit (central processing unit, CPU), microprocessor, application-specific integrated circuit (ASIC), or one or more used to control the execution of the program program of the application integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 1102 may include a path to transfer information between the above components.
  • Communication interface 1104 using any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area network
  • the memory 1103 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (random access memory, RAM), or other types of information and instructions that can be stored
  • the dynamic storage device can also be electrically erasable programmable read-only memory (electrically erasable programmable-read-only memory (EEPROM), read-only compact disc (compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Access to any other media, but not limited to this.
  • the memory may exist independently, and is connected to the processor through the communication line 1102. The memory can also be integrated with the processor.
  • the memory 1103 is used to store computer execution instructions for executing the solution of the present application, and the processor 1101 controls execution.
  • the processor 1101 is configured to execute computer execution instructions stored in the memory 1103, thereby implementing a local area network communication method provided by the following embodiments of the present application.
  • the computer execution instructions in the embodiments of the present application may also be called application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 11.
  • the communication device 1100 may include multiple processors, such as the processor 1101 and the processor 1107 in FIG. 11. Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and / or processing cores for processing data (eg, computer program instructions).
  • the communication device 1100 may further include an output device 1105 and an input device 1106.
  • the output device 1105 communicates with the processor 1101 and can display information in various ways.
  • the output device 1105 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • the input device 1106 communicates with the processor 1101 and can receive user input in various ways.
  • the input device 1106 may be a mouse, keyboard, touch screen device, or sensor device.
  • the aforementioned communication device 1100 may be a general-purpose device or a dedicated device.
  • the communication device 1100 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a similar structure as shown in FIG. 11 device.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of the communication device 1100.
  • the group communication system shown in FIG. 8 is applied to the 5G network shown in FIG. 9, the group management function network element is the GMF network element, the session management network element is the SMF network element, and the user plane network element is the UPF network (For example, the first user plane network element is UPF1 network element, and the second user plane network element is UPF2 network element).
  • the group communication method includes the following steps:
  • the first terminal sends a PDU session establishment request (PDU session establishment request) message to the AMF network element through the access device.
  • the AMF network element receives the PDU session establishment request message from the first terminal.
  • the PDU session establishment request message is used to request the establishment of a first session (may also be referred to as a first PDU session, hereinafter referred to as a first session).
  • the PDU session establishment request message includes the identifier of the first terminal and the 5GLAN ID.
  • the 5GLAN ID is the identifier of the 5GLAN group and is used to instruct the first terminal to access the 5GLAN group.
  • the identifier of the first terminal may be, for example, a user permanent identifier (SUPI) of the first terminal, or a general public user identifier (GPSI), etc.
  • SUPI user permanent identifier
  • GPSI general public user identifier
  • the identifier of the following terminal 2 may be the SUPI or GPSI of the terminal 2, which is described here in a unified manner, and will not be described in detail below.
  • the PDU session establishment request may also carry the session identifier of the first session.
  • This embodiment of the present application exemplarily takes the PDU session establishment request not carrying the session identifier of the first session as an example for description.
  • the AMF network element After selecting the SMF network element for the first terminal, the AMF network element sends a PDU session creation session management (SM) context request (PDU session creation SM context) message to the SMF network element.
  • PDU session creation SM context PDU session creation SM context
  • the SMF network element receives the PDU session creation SM context message from the AMF network element.
  • SM PDU session creation session management
  • the PDU session creation SM context request message includes the above-mentioned first terminal identifier and 5GLAN ID.
  • the SMF network element learns that the first terminal needs to access the 5GLAN group according to the 5GLAN ID, and then sends a 5GLAN service request (5GLAN service request) message to the GMF network element.
  • the GMF network element receives the 5GLAN service request message from the SMF network element.
  • the 5GLAN service request message includes the identifier of the first terminal and the 5GLAN ID, which is used by the first terminal to request access to the 5GLAN group corresponding to the 5GLAN ID.
  • the GMF network element learns that the first terminal requests to access the 5GLAN group corresponding to the 5GLAN ID, and then obtains the context information of the 5GLAN group corresponding to the 5GLAN ID.
  • the GMF network element may determine whether the first terminal has the right to access the 5GLAN group corresponding to the 5GLAN ID according to the subscription information saved locally or saved by other network elements (such as UDM) in the core network. When it is determined that the first terminal does not have the right to access the 5GLAN group corresponding to the 5GLAN ID, the GMF network element may directly reject the 5GLAN service request message.
  • the GMF network element acquiring the context information of the 5GLAN group corresponding to the 5GLAN ID may be, for example: establishing the context information of the 5GLAN group corresponding to the 5GLAN ID, or reading the 5GLAN stored on the GMF network element Context information of the 5GLAN group corresponding to the ID.
  • the GMF network element needs to establish a 5GLAN based on the 5GLAN subscription information obtained from the UDM network element or corresponding to the 5GLAN ID stored on the GMF network element
  • the context information of the 5GLAN group corresponding to the ID or, for example, when the first terminal requests access to the 5GLAN group and the ID corresponds to the 5GLAN group, the GMF network element can read if there are other terminals accessing the 5GLAN group Context information of the 5GLAN group corresponding to the 5GLAN ID stored on the GMF network element.
  • the context information of the 5GLAN group may include the identifier of the terminal that has currently accessed the 5GLAN group in the terminal member list (list) of the 5GLAN group, and has already accessed the 5GLAN group.
  • the terminal member list of the 5GLAN group includes one or more terminals subscribed to the 5GLAN group.
  • the terminal member list of the 5GLAN group may include the identifications of multiple terminals corresponding to 5GLAN ID1 as shown in Table 1.
  • Table 1 is only an exemplary form storage form, and there may be other form storage forms or non-table storage forms.
  • the terminal identifier and the 5GLAN group identifier are stored in a one-to-one correspondence.
  • the embodiment of the present application does not specifically limit the storage form of the correspondence. This description is applicable to all the embodiments of the present application, and is described here in a unified manner, and will not be described in detail below.
  • 5GLAN ID Terminal identification 5GLAN ID1 Terminal 1 logo
  • 5GLAN ID1 Terminal 2 logo
  • 5GLAN ID1 Terminal 3 logo
  • 5GLAN ID1 Terminal n logo
  • the terminal that has been connected to the 5GLAN group in the terminal member list of the 5GLAN group may be regarded as a terminal that has been connected to the network in the 5GLAN group, and the terminal member list in the 5GLAN group
  • the terminal connected to the 5GLAN group may be regarded as a terminal not connected to the network (or called off-network) in the 5GLAN group.
  • network access in the embodiment of the present application may also be understood as going online, and offline may also be understood as offline, which is not specifically limited in the embodiment of the present application.
  • the context information of the 5GLAN group may be as shown in Table 3; If the terminal 5 and the terminal 2 in the above Table 1 or Table 2 have been connected to the network, the context information of the 5GLAN group may be as shown in Table 4.
  • Table 3 or Table 4 includes the identifier of the terminal that has access to the 5GLAN group, the identifier of the UPF network element that the terminal that has access to the 5GLAN group accesses, and the user plane that each terminal accesses ID of the session port on the NE.
  • the terminal member list of the 5GLAN group If there is no terminal connected to the network in this time, the context information of the 5GLAN group is not yet available on the GMF network element, which will be described here in a unified manner and will not be repeated below.
  • the context information of the 5GLAN group may further include a member list on a UPF network element accessed by a terminal that has already entered the network and a member port identifier corresponding to each member.
  • the UPF network element The member on may be an access terminal, or may be another UPF network element selected by a terminal that has already entered the network, which is not specifically limited in this embodiment of the present application.
  • the ID of the 5GLAN group is 5GLAN ID1
  • the ID of the 5GLAN group the ID of the UPF network element accessed by the terminal that has been connected to the network
  • the list of members on the UPF network element and the members corresponding to each member The corresponding relationship of port identifiers can be shown in Table 5.
  • the context information of the 5GLAN group in the embodiment of the present application may also include other information, such as QoS requirements, etc., which is not specifically limited in the embodiment of the present application.
  • the UPF network element accessed by the terminal can also understand the anchor UPF network element when the terminal creates the PDU session, and the terminal uses the anchor UPF network element to communicate with other network elements (or UEs)
  • the communication in the embodiments of the present application may specifically be a UPF network element that provides 5GLAN services for the terminal. This description is applicable to all the embodiments of the present application, and is described here in a unified manner, and is not described in detail below.
  • the GMF network element obtains the identifier of the UPF network element capable of providing the 5GLAN service for the first terminal.
  • the UPF1 network element is assumed.
  • the GMF network element may request the identifier of the UPF network element that can provide the 5GLAN service to the first terminal from the SMF network element.
  • the GMF network element sends a request message 1 to the SMF network element.
  • the request message 1 includes the identifier of the first terminal and the context information of the 5GLAN group.
  • the request message 1 is used to request the session port identifier of the first session and can be
  • the first terminal provides the identification of the UPF network element of the 5GLAN service.
  • the request message 1 may also include the identifier of the UPF network element selected by the GMF network element to recommend the SMF network element.
  • the SMF network element can allocate the session port identifier 11 for the first session according to the identifier of the first terminal, and according to the context information of the 5GLAN group (optional, it can be combined with GMF
  • the network element suggests the identifier of the UPF network element selected by the SMF network element) to select the UPF network element for the first terminal.
  • the UPF network element accessed by the first terminal is the UPF1 network element, and then the SMF network element can send a response message 1 to the GMF network element, where the response message 1 includes the identifier of the first terminal, the identifier of the UPF1 network element, and the session port Logo 11.
  • the GMF network element can obtain the identifier of the UPF1 network element selected by the SMF network element for the first terminal, and the session port identifier 11 allocated by the SMF network element for the first session of the first terminal.
  • the session port identifier 11 here may be TEID1, for example.
  • the SMF network element may also allocate a session identifier (such as PDU session ID) for the first session.
  • a session identifier such as PDU session ID
  • the SMF network element may select the UPF network element according to the prior art and select the selected UPF
  • the network element is determined to be a UPF network element capable of providing 5GLAN services for the first terminal.
  • the SMF network element may select the UPF network element that provides the 5GLAN service for the first terminal according to the method in the existing standard TS23.501 V15.2.0 6.3.3.
  • the SMF network element may be able to provide the 5GLAN service Of the UPF network elements that have not yet been accessed by other terminal members of the 5GLAN group are determined to be UPF network elements that can provide 5GLAN services for the first terminal; or, an SMF network element can select a certain group that has the 5GLAN group A UPF network element that is accessed by other terminal members of the group but has fewer terminal members is determined as a UPF network element capable of providing 5G LAN services for the first terminal.
  • SMF can also select the UPF network element that provides the 5GLAN service for the first terminal by combining the identification information of the UPF network elements selected by other terminals in the terminal member list of the 5GLAN group on the basis of the prior art.
  • the application examples do not specifically limit this.
  • the GMF network element may select the UPF network element that provides the 5GLAN service for the first terminal.
  • the GMF network element can temporarily allocate a session port identifier for the first session.
  • the subsequent SMF network element completes the establishment of the user plane session and the installation of group forwarding rules, the GMF network element is notified, and then the GMF network element updates the 5GLAN group
  • the session port identifier of the first session in the context information of the group is not specifically limited in this embodiment of the present application.
  • the above embodiments are merely exemplary ways to provide several GMF network elements to obtain the identity of the UPF network element that can provide the 5GLAN service for the first terminal.
  • the GMF network element may also be obtained by other methods to provide the first terminal.
  • the identifier of the UPF network element of the 5GLAN service is not specifically limited in this embodiment of the present application.
  • the subsequent embodiments of the present application are all exemplified by taking the scenario where the SMF network element is the first terminal to select the UPF network element that provides the 5GLAN service as an example, which will be described here in a unified manner and will not be described in detail below.
  • the GMF network element After the GMF network element obtains the session port identifier 11 and the UPF1 network element identifier, it may update the context information of the 5GLAN group stored on the GMF network element before the first terminal does not join the network, or establish a 5GLAN group on the GMF network element Context information.
  • the context information of the 5GLAN group may be shown as six; or, assuming that the first terminal is terminal 1, before the first terminal enters the network, the context information of the 5GLAN group stored on the GMF network element is shown in Table 3, then the After a terminal accesses the network, the updated context information of the 5GLAN group may be as shown in Table 7; or, assuming that the first terminal is terminal 1, before the first terminal accesses the network, the context information of the 5GLAN group stored on the GMF network element is as follows: As shown in Table 4, after the first terminal accesses the network, the updated context information of the 5GLAN group may be as shown in Table 8.
  • rule groups such as rule group 11 or rule group 12
  • 5GLAN group FAR such as group FAR1 or group FAR2, etc.
  • 11 and 12 in rule group 11 and rule group 12 are only used to distinguish the rule groups applied on different member ports
  • group FAR1 and group FAR2 are only used to distinguish the 5GLAN group FAR applied on different UPF network elements
  • first and second, etc. which are not specifically limited in the embodiments of the present application. This description is applicable to all subsequent embodiments, and is described here in a unified manner, and will not be described in detail below.
  • the group communication method provided in this embodiment of the present application further includes the following step S1206a- S1210a:
  • the GMF network element creates a rule group 11 applied to the session port 11 on the UPF1 network element for the 5GLAN group, and the GMF network element creates a 5GLAN group FAR applied on the UPF1 network element for the 5GLAN group. As group FAR1.
  • the rule group 11 includes an entrance PDR11, an exit PDR11 and an exit FAR11.
  • group FAR1 here may include FA11, which is used to copy the received broadcast message belonging to the 5GLAN group and send it to session port 11.
  • the GMF network element sends a 5GLAN service response message 1 to the SMF network element.
  • the SMF network element receives the 5GLAN service response message 1 from the GMF network element.
  • the 5GLAN service response message 1 includes the identifier of the UPF1 network element, the session port identifier 11, the rule group 11 and the group FAR1 corresponding to the identifier of the UPF1 network element.
  • the identifier of the UPF network element may be, for example, the IP address of the UPF network element, which is not specifically limited in the embodiment of the present application.
  • This description can also be similarly applied to the UPF network elements in all the embodiments of the present application, which will be described here in a unified manner, and will not be repeated below.
  • the SMF network element sends the N4 session establishment request (N4 session establishment request) message 1 to the corresponding UPF1 network element according to the identifier of the UPF1 network element in the 5GLAN service response message 1.
  • the UPF1 network element receives the N4 session establishment request message 1 from the SMF network element.
  • the N4 session establishment request message 1 includes configuration information 1, and the configuration information 1 includes a session port identifier 11, a rule group 11, and group FAR1.
  • the UPF1 network element establishes the first session, and configures the rule group 11 on the session port 11 of the UPF1 network element according to the session port identifier 11 and the rule group 11 in the configuration information 1, and the group FAR1 in the configuration information 1 Configure group FAR1 on the UPF1 network element.
  • the establishment of the first session by the UPF1 network element includes the creation of the session port 11 according to the session port identifier 11. Relevant descriptions can refer to the introduction part of the foregoing embodiment, which will not be repeated here.
  • the configuration diagram of the 5GLAN group on the UPF1 network element may be as shown in FIG. 13.
  • the UPF1 network element sends an N4 session establishment response (N4 session establishment response) message 1 to the SMF network element.
  • the SMF network element receives the N4 session establishment request response message 1 from the UPF1 network element.
  • the N4 session establishment request response message 1 is used to notify the establishment of the N4 session establishment and rule installation.
  • scenario two if the GMF network element determines that other terminal members in the 5GLAN group have joined the 5GLAN group, and the SMF network element is the UPF network element that the first terminal chooses to access and the other terminal members that have access to the 5GLAN group
  • the selected UPF network elements are the same (for example, the context information of the 5GLAN group is shown in Table 3 above), then the group communication method provided in this embodiment of the present application further includes the following steps S1206b-S1210b:
  • S1206b-S1210b is similar to steps S1206a-S1210a.
  • the difference is, for example, in steps S1206a-S1210a, a 5GLAN group FAR applied on the UPF1 network element is created, while in steps S1206b-S1210b, the 5GLAN group applied on the UPF1 network element is updated.
  • FAR for other related descriptions, please refer to the above steps S1206a-S1210a, which will not be repeated here.
  • the context information of the 5GLAN group stored on the GMF network element is shown in Table 3 above.
  • the terminal 5 in Table 3 is connected to the network in a similar manner to the terminal 1 in steps S1206a-S1210a above.
  • a rule group 51 is configured on the session port 51 of the UPF1 network element and group FAR1 and group FAR1 are configured on the UPF1 network element. It includes FA51, and rule group 51 includes ingress PDR51, egress PDR51 and egress FAR51, that is, the configuration diagram of the 5GLAN group on the UPF1 network element is shown as (a) in FIG. 14.
  • FA51 is used to copy the received broadcast message belonging to the 5GLAN group corresponding to the 5GLAN ID and send it to the session port 51.
  • the configuration diagram of the 5GLAN group on the UPF1 network element at this time may be as shown in (b) in FIG. 14 As shown.
  • scenario three if the GMF network element determines that other terminal members in the 5GLAN group have joined the 5GLAN group, and the SMF network element selects a UPF network for the first terminal to which other terminal members of the 5GLAN group do not exist to access If the context information of the 5GLAN group is as shown in Table 4 above, this situation indicates that the 5GLAN group can span multiple UPF network elements, and further the group communication method provided in the embodiments of the present application further includes the following steps S1209c-S1218c :
  • the GMF network element sends a request message 2 to the SMF network element.
  • the SMF network element receives the request message 2 from the GMF network element.
  • the request message 2 is used to request the establishment of a first tunnel between the UPF1 network element and UPF2.
  • the first tunnel is used to transmit communication data between group members in the 5GLAN group.
  • the SMF network element sends a response message 2 to the GMF network element.
  • the GMF network element receives the response message 2 from the SMF network element.
  • the response message 2 includes a tunnel port identifier 41 and a tunnel port identifier 42.
  • the tunnel port 41 here is the port of the first tunnel between the UPF1 element and the UPF2 element on the side of the UPF1 element; the tunnel port 42 here is the first tunnel between the UPF1 element and the UPF2 element on the UPF2 element Port on the side.
  • the tunnel port identifier 41 may be, for example, TEID41
  • the tunnel port identifier 42 may be, for example, TEID42.
  • the tunnel identifier may be assigned by the SMF network element, or may be assigned by the corresponding UPF network element (for example, the UPF1 network element assigns the first tunnel port identifier 41 on the UPF2 network element side; the UPF2 network The port number of the first tunnel allocated to the first tunnel on the UPF2 network element side 42), which is not limited in this embodiment of the present application.
  • the GMF network element creates a rule group 11 applied to the session port 11 on the UPF1 network element for the 5GLAN group; and, the GMF network element creates a 5GLAN group FAR applied on the UPF1 network element for the 5GLAN group.
  • group FAR1 the GMF network element creates a rule group 41 applied to the tunnel port 41 of the UPF1 network element for the 5GLAN group; and, the GMF network element creates a tunnel applied to the UPF2 network element for the 5GLAN group
  • group FAR1 here may include FA11 and FA41.
  • the FA11 is used to copy the received broadcast message belonging to the 5GLAN group corresponding to the 5GLAN ID and send it to the session port 11.
  • the FA41 is used to receive The broadcast messages that belong to the 5GLAN group corresponding to the 5GLAN ID are copied and sent to the tunnel port 41.
  • group FAR2 here may include FA42, which is used to copy the received broadcast message belonging to the 5GLAN group corresponding to the 5GLAN ID and send it to tunnel port 42.
  • the GMF network element sends a 5GLAN service response message 2 to the SMF network element.
  • the SMF network element receives the 5GLAN service response message 2 from the GMF network element.
  • the 5GLAN service response message 2 includes the identifier of the UPF1 network element, the group FAR1 corresponding to the identifier of the UPF1 network element, the session port identifier 11 and the rule group 11, the tunnel port identifier 41 and the rule group 41, the identifier of the UPF2 network element , The updated group FAR2, tunnel port identifier 42 and rule group 42 corresponding to the identifier of the UPF2 network element.
  • the SMF network element sends the N4 session establishment request message 2 to the corresponding UPF1 network element according to the identifier of the UPF1 network element in the 5GLAN service response message 2.
  • the UPF1 network element receives the N4 session establishment request message 2 from the SMF network element.
  • the N4 session establishment request message 2 includes configuration information 2, which includes group FAR1, session port identifier 11 and rule group 11, tunnel port identifier 41 and rule group 41.
  • the UPF1 network element establishes the first session and the first tunnel, and configures the rule group 11 on the session port 11 of the UPF1 network element according to the session port identifier 11 and the rule group 11 in the configuration information 2, and according to the configuration information 2
  • the establishment of the first session by the UPF1 network element may include, for example, creating a session port 11 according to the session port identifier 11; the establishment of the first tunnel by the UPF1 network element may include, for example, creating a tunnel port 41 according to the tunnel port identifier 41.
  • Relevant descriptions can refer to the introduction part of the foregoing embodiment, which will not be repeated here.
  • the UPF1 network element sends an N4 session establishment response message 2 to the SMF network element.
  • the SMF network element receives the N4 session establishment request response message 2 from the UPF1 network element.
  • the N4 session establishment request response message 2 is used to notify the completion of N4 session establishment and rule installation.
  • the SMF network element sends the N4 session modification request (N4 session modification request) message to the corresponding UPF2 network element according to the identifier of the UPF2 network element in the 5GLAN service response message 2.
  • the UPF1 network element receives the N4 session modification request message from the SMF network element.
  • the N4 session modification request message includes configuration information 3, and the configuration information 3 includes the updated group FAR2, tunnel port identifier 42, and rule group 42.
  • the UPF2 network element establishes the first tunnel to the UPF1 network element, and configures the rule group 42 on the tunnel port 42 of the UPF2 network element according to the tunnel port identifier 42 and the rule group 42 in the configuration information 3, and according to the configuration information 3
  • the updated group FAR2 in updates the group FAR2 on the UPF2 network element.
  • the establishment of the first tunnel by the UPF2 network element may include, for example, creating a tunnel port 42 according to the tunnel port identifier 42. Relevant descriptions can refer to the introduction part of the foregoing embodiment, which will not be repeated here.
  • the UPF2 network element sends an N4 session modification response message to the SMF network element.
  • the SMF network element receives the N4 session modification response message from the UPF2 network element.
  • the N4 session modification response message is used to notify the completion of N4 session modification and rule installation.
  • step S1213c is performed first, and then step S1210c; or step S1210c is performed first, and then step S1213c; or step S1213c and step S1210c may be performed simultaneously, which is not specifically limited in the embodiments of the present application.
  • the context information of the 5GLAN group stored on the GMF network element is shown in Table 4 above.
  • the way in which terminal 5 and terminal 2 in Table 4 are connected to the network is similar to the way in which terminal 2 and terminal 5 in steps S1206b-S1210b described above are connected to the network.
  • Rule group 22 is configured on session port 22 of the UPF2 network element.
  • the rule group 52 is configured on the session port 52 of the element, and the group FAR2 is configured on the UPF2 network element.
  • the group FAR2 includes FA4 and FA5
  • the rule group 22 includes the entrance PDR22, the exit PDR22, and the exit FAR22
  • the rule group 52 includes The configuration diagram of the ingress PDR52, egress PDR52, and egress FAR52, that is, the 5GLAN group on the UPF2 network element, is shown in (a) in FIG. 15.
  • FA52 is used to copy the received broadcast messages belonging to the 5GLAN group corresponding to the 5GLAN ID to the session port 52
  • FA22 is used to copy the received broadcast messages belonging to the 5GLAN group corresponding to the 5GLAN ID Then sent to the session port 22.
  • the UPF1 network element allocates the session port port identifier 111 for the first session, there are two solutions that are consistent with the session port identifier 11 allocated by the SMF network element for the first session.
  • the UPF1 network element maintains the correspondence between the session port port identifier 111 allocated by the local end for the first session and the session port identifier 11 allocated by the SMF network element for the first session.
  • the other is that the UPF1 network element updates the correspondence between the session port identifier 11 and the rule group 11 configured on the UPF network element to the correspondence relationship between the session port port identifier 111 and the rule group 11, and the UPF1 network element sets the local end as the first
  • the session port identifier 111 of the session allocation is sent to the SMF network element (for example, through the N4 session establishment response message 1 in the above step S1210a or the N4 session establishment response message 2 in the above step S1212c), so that the SMF network element deletes itself as the first
  • the session port identifier 11 allocated for a session uses the session port port identifier 111 allocated by the UPF1 network element for the first session.
  • the SMF network element initiates an update request to the GMF network element, and the update request includes the session port port identifier 111, so that the GMF network element can update the session port identifier 11 corresponding to the first session to the session port port identifier 111.
  • the terminals in the 5GLAN group access the network, they only need to adjust (create or update) the 5GLAN group FAR on the associated UPF network element and adjust (create or update) the associated UPF network
  • the entry PDR, exit PDR, and exit FAR corresponding to the terminal member in the meta are sufficient, and the entry PDR, exit PDR, and exit FAR corresponding to other terminal members in the 5GLAN group do not change. Therefore, when there are many terminal members connected to the network in the 5GLAN group, the problem of greatly increased configuration workload caused by the change in the number of terminal members can be avoided, and the configuration workload caused by the change in the number of terminal members can be greatly reduced.
  • the actions of the GMF network element, SMF network element, UPF1 network element or UPF2 network element in the above steps S1201 to S1216 can be called by the processor 1101 in the communication device 1100 shown in FIG. 11 to the application program code stored in the memory 1103 To implement, this embodiment does not limit this.
  • the group communication system shown in FIG. 8 is applied to the 5G network shown in FIG. 9, the group management function network element is a GMF network element, the session management network element is an SMF network element, and the user plane network element is a UPF network (For example, the first user plane network element is UPF1 network element, the second user plane network element is UPF2 network element, and the third user plane network element is UPF3 network element).
  • the group communication method includes the following steps:
  • the first terminal has access to the UPF1 network element, and the configuration of the 5GLAN group has been created on the UPF1 network element, including group FAR1 and related rule groups; 5GLAN may have been created on other UPF network elements in the 5GLAN group
  • the configuration of the group, including the relevant group FAR and the relevant rule group, the establishment method is shown in the embodiment shown in FIG. 12, which will not be repeated here.
  • the UPF1 network element and the UPF2 network element are connected.
  • S1601 The first terminal switches from the first access device to the second access device.
  • the second access device sends a path switch request (path switch request) to the AMF network element.
  • the AMF network element receives the path switching request from the second access device.
  • the above path switching request may also be replaced with a handover announcement (handover), which is not specifically limited in this embodiment of the present application.
  • handover a handover announcement
  • the AMF network element sends a PDU session update request (PDU session update request) to the SMF network element.
  • the SMF network element receives the PDU session update request from the AMF network element.
  • PDU session update request may also be replaced with a PDU session SM context update request (PDU session SM context update request), which is not specifically limited in the embodiment of the present application.
  • PDU session SM context update request PDU session SM context update request
  • the SMF network element determines to update the UPF network element according to the PDU session update request. For example, the UPF network element serving the first terminal is replaced from the UPF1 network element to the UPF3 network element. At the same time, if the SMF network element determines that the first terminal initiates 5GLAN group communication, the SMF network element sends a 5GLAN service update request (5GLAN service update request) to the GMF network element. Correspondingly, the GMF network element receives the 5GLAN service update request from the SMF network element.
  • 5GLAN service update request 5GLAN service update request
  • the 5GLAN service update request includes the identifier of the first terminal, the identifier of the UPF3 network element (that is, the target UPF network element), and the session port identifier 11 of the first session.
  • the 5GLAN service update request may further include the identifier of the UPF1 network element (that is, the source UPF network element).
  • the GMF network element learns that the UPF network element serving the first terminal is changed from the UPF1 network element to the UPF3 network element, and creates an application for the 5GLAN group on the session port 31 of the UPF3 network element Rule group 31, and based on the context information of the 5GLAN group, create or update the 5GLAN group FAR applied to the UPF3 network element for the 5GLAN group, and record it as group FAR3.
  • the created or updated group FAR3 includes rules for copying the received broadcast messages belonging to the 5GLAN group and sending them to the session port 31 of the UPF3 network element.
  • the GMF network element when the GMF network element determines that there are other terminals in the terminal member list of the 5GLAN group to access the UPF1 network element according to the context information of the 5GLAN group stored on the GMF network element, the GMF network element also updates the group FAR1 applied to the UPF1 network element for the 5GLAN group. Among them, the rule in the updated group FAR1 for copying the received broadcast message belonging to the 5GLAN group and sending it to the session port 11 of the UPF1 network element is deleted.
  • the GMF network element sends a 5GLAN service update response (5GLAN service update response) to the SMF network element.
  • the SMF network element receives the 5GLAN service update response from the GMF network element.
  • the 5GLAN service update response includes the identifier of the UPF3 network element, the group FAR3 corresponding to the identifier of the UPF3 network element, the session port identifier 31 and the rule group 31, which are used to configure the rule group 31 on the session port 31 of the UPF3 network element , And configure or update group FAR3 on UPF3 network elements.
  • the 5GLAN service update response includes the identifier of the UPF1 network element and the session port identifier 11 corresponding to the identifier of the UPF1 network element, which is used to delete the session port 11 and the rule group 11 on the session port 11 of the UPF1 network element.
  • the 5GLAN service update response may include the identifier of the rule group 11, which is not specifically limited by the embodiment of the present application.
  • the 5GLAN service update response also includes The ID of the group FAR1 corresponding to the ID of the UPF1 network element is used to delete the group FAR1 on the UPF1 network element.
  • the 5GLAN service update response also includes The updated group FAR1 corresponding to the identifier of the UPF1 network element is used to update the group FAR1 on the UPF1 network element.
  • the SMF network element sends the N4 session establishment request message 1 to the corresponding UPF3 network element according to the identifier of the UPF3 network element in the 5GLAN service update response.
  • the UPF3 network element receives the N4 session establishment request message 1 from the SMF network element.
  • the N4 session establishment request message 1 includes configuration information, and the configuration information includes group FAR3, session port identifier 31, and rule group 31 corresponding to the identifier of the UPF3 network element.
  • the UPF3 network element establishes the first session, and configures the rule group 31 on the session port 31 of the UPF3 network element according to the session port identifier 31 and the rule group 31 in the configuration information in step S1607, and according to the configuration in step S1607
  • the group FAR3 in the message configures or updates group FAR3 on the UPF3 network element.
  • the establishment of the first session by the UPF3 network element includes the creation of the session port 31 according to the session port identifier 31.
  • Relevant descriptions can refer to the introduction part of the foregoing embodiment, which will not be repeated here.
  • the SMF network element sends the N4 session release request (N4 session release request) 1 to the corresponding UPF1 network element according to the identifier of the UPF1 network element in the 5GLAN service update response.
  • the UPF1 network element receives the N4 session release request 1 from the SMF network element.
  • the N4 session release request 1 includes an indication 1
  • the indication information 1 includes the session port identifier 11 corresponding to the identifier of the UPF1 network element and the updated group FAR1 .
  • the N4 session release request 1 when there is no other terminal access on the UPF1 network element, the N4 session release request 1 includes indication information 2, the indication information 2 includes the session port identifier 11 corresponding to the identifier of the UPF1 network element and the group FAR1 identifier .
  • the N4 session release request 1 may include the identifier of the rule group 11, which is not specifically limited by the embodiment of the present application.
  • the UPF1 network element releases the first session, and deletes the session port 11 on the UPF1 network element and the rule group 11 on the session port 11 according to the session port identifier 11 in the indication information 1 or the indication information 2.
  • the UPF1 network element updates the group FAR1 on the UPF1 network element according to the updated group FAR1 in the instruction information 1, or the UPF1 network element deletes the group FAR1 on the UPF1 network element according to the group FAR1 identifier in the instruction information 2.
  • releasing the first session by the UPF1 network element includes deleting the session port 11 according to the session port identifier 11.
  • the configuration diagram of the 5GLAN group on the UPF1 network element may be as shown in (a) of FIG. 17.
  • the rule group 11 is configured on the session port 11 of the UPF1 network element
  • the group FAR1 is configured on the UPF1 network element.
  • rule group 11 includes ingress PDR11, egress PDR11 and egress FAR111
  • group FAR1 includes FA11
  • FA11 is used to copy and receive the broadcast messages belonging to the 5GLAN group corresponding to the 5GLAN ID and send it to session port 11.
  • the schematic diagram of the configuration of the 5GLAN group on the UPF1 network element and the UPF3 network element may be as shown in (b) of FIG. 17.
  • a schematic diagram of the configuration of the 5GLAN group on the UPF1 network element may be as shown in (a) in FIG. 18.
  • the schematic diagram of the configuration of the 5GLAN group on the UPF1 network element and the UPF3 network element may be as shown in (b) in FIG. 18.
  • the GMF network element deletes the corresponding tunnel port of the 5GLAN group and the rule group on the tunnel port, deletes the group FAR applied to the UPF1 NE, and updates the group FAR applied to other UPF NEs.
  • the implementation is similar to the above steps S1609-S1610, and will not be repeated here.
  • the identifier of the UPF network element selected by the terminal currently connected to the network in the terminal member list of the 5GLAN group includes the identifier of the UPF1 network element ,
  • the logo of the UPF2 network element and the logo of the UPF3 network element the schematic diagram of the configuration of the 5GLAN group on the UPF1 network element, UPF2 network element and UPF3 network element is shown as (a) in FIG. 19.
  • a schematic diagram of the configuration of the 5GLAN group on each UPF network element is shown in (b) of FIG. 19.
  • rule group 41 on the tunnel port 41 and the rule group 43 on the tunnel port 43 corresponding to the tunnel between the UPF1 network element and the UPF3 network element are deleted; and the group FAR3 on the UPF3 network element is also updated Among them, FA43 in group FAR3 is deleted. FA43 is used to copy the received broadcast message belonging to the 5GLAN group and send it to the tunnel port 43 of the UPF3 network element. In addition, there is no configuration for the 5GLAN group on the UPF1 network element, so it is not shown in (b) in FIG. 19.
  • the identifier of the UPF network element selected by the terminal currently connected to the network in the terminal member list of the 5GLAN group includes the UPF1 network element
  • the logo of the UPF3 network element the schematic diagram of the configuration of the 5GLAN group on the UPF1 network element and the UPF3 network element is shown as (a) in FIG. 20.
  • a schematic diagram of the configuration of the 5GLAN group on each UPF network element is shown in (b) in FIG. 20.
  • rule group 41 on the tunnel port 41 and the rule group 43 on the tunnel port 43 corresponding to the tunnel between the UPF1 network element and the UPF3 network element are deleted; and the group FAR3 on the UPF3 network element is also updated Among them, FA43 in group FAR3 is deleted. FA43 is used to copy the received broadcast message belonging to the 5GLAN group and send it to the tunnel port 43 of the UPF3 network element. In addition, there is no configuration for the 5GLAN group on the UPF1 network element, so it is not shown in (b) in FIG. 20.
  • the identifier of the UPF network element selected by the terminal currently connected to the network in the terminal member list of the 5GLAN group does not include the UPF3 network element, if the service for the first terminal is provided
  • the UPF network element is updated from the UPF1 network element to the UPF3 network element.
  • the GMF network element also needs to request the SMF network element to establish a tunnel between the UPF3 network element and other UPF network elements, and then after receiving the tunnel port identifier from the SMF network element , Configure the rule groups applied to the tunnel ports on the UPF3 network element and other UPF network elements through the SMF network element, create the group FAR3 applied on the UPF3 network element, and update the group FAR applied on the other UPF network element.
  • the other UPF network elements here may be, for example, UPF1 network elements, or UPF network elements other than UPF1 whose identifiers of the UPF network elements selected by the terminal currently connected to the network in the terminal member list of the 5GLAN group.
  • the implementation is similar to the above steps S1607 and S1608, and will not be repeated here.
  • the identifier of the UPF network element selected by the terminal currently connected to the network in the terminal member list of the 5GLAN group includes only the UPF1 network element.
  • logo the schematic diagram of the configuration of the 5GLAN group on the UPF1 network element is shown in (a) of FIG. 21.
  • a schematic diagram of the configuration of the 5GLAN group on each UPF network element is shown in (b) of FIG. 21.
  • the rule group 41 on the tunnel port 41 corresponding to the tunnel between the UPF1 NE2 and the UPF3 NE is configured on the UPF1 NE; the UPF1 NE and the UPF3 NE are configured on the UPF3 NE
  • the rule group 43 on the tunnel port 43 corresponding to the tunnel; and the group FAR3 is configured on the UPF3 network element; and the group FAR1 on the UPF1 network element is also updated.
  • FA41 is added to the group FAR1, and FA41 is used to receive The broadcast messages belonging to the 5GLAN group are copied and sent to the tunnel port 41 of the UPF1 network element.
  • the identifier of the UPF network element selected by the terminal currently connected to the network in the terminal member list of the 5GLAN group includes the UPF1 network element
  • the configuration diagram of the 5GLAN group on the UPF1 network element and the UPF2 network element is shown in (a) in FIG. 22.
  • a schematic diagram of the configuration of the 5GLAN group on each UPF network element is shown in (b) in FIG. 22.
  • the UPF2 network element is configured with the rule group 62 on the tunnel port 62 corresponding to the tunnel between the UPF2 network element and the UPF3 network element; the UPF3 network element is configured between the UPF2 network element and the UPF3 network element The rule group 63 on the tunnel port 63 corresponding to the tunnel; and the group FAR3 is configured on the UPF3 network element; and the group FAR2 on the UPF2 network element is also updated.
  • FA62 is added to group FAR2, and FA62 is used to receive The broadcast messages belonging to the 5GLAN group are copied and sent to the tunnel port 62 of the UPF2 network element.
  • the terminal members who have already entered the network in the 5GLAN group move within the 5GLAN group, they only need to adjust (create, update, or delete) the 5GLAN group FAR on the associated UPF network element, and adjust (Create, update, or delete)
  • the entry PDR, exit PDR, and exit FAR corresponding to the terminal member on the associated UPF network element, and the entry PDR, exit PDR, and exit corresponding to other terminal members who have already entered the network in the 5GLAN group FAR does not change. Therefore, when there are many terminal members connected to the network in the 5GLAN group, the problem that the configuration workload caused by the change in the number of terminal members will increase greatly is avoided, and the configuration workload due to the change in the number of terminal members is greatly reduced.
  • the actions of the GMF network element, SMF network element, UPF1 network element or UPF3 network element in the above steps S1601 to S1611 can be called by the processor 1101 in the communication device 1100 shown in FIG. 11 to the application program code stored in the memory 1103 To implement, this embodiment does not limit this.
  • the group communication system shown in FIG. 8 is applied to the 5G network shown in FIG. 9, the group management function network element is a GMF network element, the session management network element is an SMF network element, and the user plane network element is a UPF network (For example, the first user plane network element is UPF1 network element, the second user plane network element is UPF2 network element, and the third user plane network element is UPF3 network element).
  • the group communication method includes the following steps:
  • the first terminal has access to the UPF1 network element, and the configuration of the 5GLAN group has been created on the UPF1 network element, including group FAR1 and related rule groups; 5GLAN may have been created on other UPF network elements in the 5GLAN group
  • the configuration of the group, including the relevant group FAR and the relevant rule group, the establishment method is shown in the embodiment shown in FIG. 12, which will not be repeated here.
  • the UPF1 network element and the UPF2 network element are connected.
  • S2301 The first terminal sends a session release request to the AMF network element.
  • the AMF network element receives the session release request from the first terminal.
  • the AMF network element sends an SM context update request to the SMF network element.
  • the SMF network element receives the SM context update request from the AMF network element.
  • the above SM context update request may also be replaced with a PDU session update request, which is not specifically limited in this embodiment of the present application.
  • the SMF network element determines that the first terminal has initiated 5GLAN group communication, the SMF network element sends a 5GLAN service release request (5GLAN service release request) to the GMF network element.
  • the GMF network element receives the 5GLAN service release request from the SMF network element.
  • the 5GLAN service release request is used to instruct to release the first session of the first terminal.
  • the 5GLAN service release request message itself has a function of instructing to release the session.
  • the 5GLAN service release request may include the identifier of the first terminal.
  • the 5GLAN service release request includes indication information and an identifier of the first terminal, where the indication information is used to indicate the release of the session.
  • the 5GLAN service release request may further include the identifier of the UPF1 network element that the first terminal accesses when accessing the network, which is not specifically limited in this embodiment of the present application.
  • the GMF network element learns that the first terminal will release the first session, and can then perform related operations.
  • the group communication method provided by the embodiment of the present application will be further explained in the following two scenarios.
  • the group communication method further includes the following steps S2304a-S2307a:
  • the GMF network element determines that there are other terminals connected to the UPF1 network element in the terminal member list of the 5GLAN group according to the context information of the 5GLAN group stored on the GMF network element, the GMF network element also returns Update the group FAR1 applied to the UPF1 network element for the 5GLAN group. Among them, the rule in the updated group FAR1 for copying the received broadcast message belonging to the 5GLAN group and sending it to the session port 11 of the UPF1 network element is deleted.
  • the GMF network element sends a 5GLAN service release response (5GLAN service release response) 1 to the SMF network element.
  • the SMF network element receives the 5GLAN service release response 1 from the GMF network element.
  • the 5GLAN service release response 1 includes the identifier of the UPF1 network element, the session port identifier 11 corresponding to the identifier of the UPF1 network element, and is used to delete the session port 11 of the UPF1 network element and the rule group 11 on the session port 11.
  • the 5GLAN service release response 1 may include the identifier of the rule group 11, which is not specifically limited in this embodiment of the present application.
  • the 5GLAN service release response 1 also It includes the ID of group FAR1 corresponding to the ID of the UPF1 network element, which is used to delete the group FAR1 on the UPF1 network element.
  • the 5GLAN service release response 1 also It includes the updated group FAR1 corresponding to the identifier of the UPF1 network element, which is used to update the group FAR1 on the UPF1 network element.
  • the SMF network element sends the N4 session release request 1 to the corresponding UPF1 network element according to the identifier of the UPF1 network element in the 5GLAN service release response 1.
  • the UPF1 network element receives the N4 session release request 1 from the SMF network element.
  • the N4 session release request 1 includes the indication 1, the indication information 1 includes the session port identifier 11 corresponding to the identifier of the UPF1 network element and the updated group FAR1 .
  • the N4 session release request 1 includes indication information 2, the indication information 2 includes the session port identifier 11 and the group FAR1 identifier corresponding to the identifier of the UPF1 network element .
  • the N4 session release request 1 may include the identifier of the rule group 11, which is not specifically limited in this embodiment of the present application.
  • the UPF1 network element releases the first session, and deletes the session port 11 of the UPF1 network element and the rule group 11 on the session port 11 according to the session port identifier 11 and the rule group 11 identifier in the indication information 1 or the indication information 2.
  • the UPF1 network element updates the group FAR1 on the UPF1 network element according to the updated group FAR1 in the instruction information 1, or the UPF1 network element deletes the group FAR1 on the UPF1 network element according to the group FAR1 identifier in the instruction information 2.
  • releasing the first session by the UPF1 network element includes deleting the session port 11 according to the session port identifier 11.
  • the configuration diagram of the 5GLAN group on the UPF1 network element may be as shown in (a) in FIG. 24.
  • the configuration diagram of the 5GLAN group on the UPF1 network element may be as shown in (b) in FIG. 24, that is, there is no configuration information of the 5GLAN group on the UPF1 network element.
  • the first terminal is terminal 1.
  • the configuration diagram of the 5GLAN group on the UPF1 network element may be as shown in (a) in FIG. 25.
  • the configuration diagram of the 5GLAN group on the UPF1 network element may be as shown in (b) in FIG. 25.
  • the group communication method provided in this embodiment of the present application further includes the following steps S2304b-S2309b:
  • the GMF network element determines that there are other terminals connected to the UPF1 network element in the terminal member list of the 5GLAN group according to the context information of the 5GLAN group stored on the GMF network element, the GMF network element also returns Update the group FAR1 applied to the UPF1 network element for the 5GLAN group. Among them, the rule in the updated group FAR1 for copying the received broadcast message belonging to the 5GLAN group and sending it to the session port 11 of the UPF1 network element is deleted.
  • the GMF network element determines that there is no other terminal accessing the UPF1 network element in the terminal member list of the 5GLAN group according to the context information of the 5GLAN group stored on the GMF network element, the GMF network element also returns Update the group FAR2 applied to the UPF2 network element for the 5GLAN group. Among them, the rule in the updated group FAR2 for copying the received broadcast message belonging to the 5GLAN group to the tunnel port 42 is deleted.
  • the tunnel port 42 is a tunnel port of the first tunnel between the UPF1 network element and the UPF2 network element on the side of the UPF2 network element.
  • the GMF network element sends a 5GLAN service release response 2 to the SMF network element.
  • the SMF network element receives the 5GLAN service release response 2 from the GMF network element.
  • the 5GLAN service release response 2 includes the identifier of the UPF1 network element, the session port identifier 11 corresponding to the identifier of the UPF1 network element, and is used to delete the session port 11 of the UPF1 network element and the rule group 11 on the session port 11.
  • the GLAN service release response 2 may include the identifier of the rule group 11, which is not specifically limited in this embodiment of the present application.
  • the 5GLAN service release response also includes The updated group FAR1 corresponding to the identifier of the UPF1 network element is used to update the group FAR1 on the UPF1 network element.
  • the 5GLAN service release response 2 when the GMF network element determines that no other terminal is connected to the UPF1 network element in the terminal member list of the 5GLAN group based on the context information of the 5GLAN group stored on the GMF network element, the 5GLAN service release response 2 also It includes the ID of group FAR1 corresponding to the ID of the UPF1 network element, which is used to delete the group FAR1 on the UPF1 network element. And, the 5GLAN service release response 2 further includes an identifier of the tunnel port 41 corresponding to the identifier of the UPF1 network element, which is used to delete the tunnel port 41 of the UPF1 network element and the rule group 41 on the tunnel port 41.
  • the 5GLAN service release response 2 further includes an identifier of the tunnel port 42 corresponding to the identifier of the UPF2 network element, which is used to delete the tunnel port 42 of the UPF2 network element and the rule group 42 on the tunnel port 42.
  • the 5GLAN service release response 2 may include the identifier of the rule group 41 and the identifier of the rule group 42, which is not specifically limited in this embodiment of the present application.
  • the SMF network element sends the N4 session release request 2 to the corresponding UPF1 network element according to the identifier of the UPF1 network element in the 5GLAN service release response 2.
  • the UPF1 network element receives the N4 session release request 2 from the SMF network element.
  • the N4 session release request 2 when there are other terminal accesses on the UPF1 network element, the N4 session release request 2 includes indication information 3, and the indication information 3 includes the session port identifier 11 corresponding to the identifier of the UPF1 network element and the updated group FAR1.
  • the N4 session release request 2 may include the identifier of the rule group 11, which is not specifically limited in this embodiment of the present application.
  • the N4 session release request 2 when there is no other terminal access on the UPF1 network element, the N4 session release request 2 includes an indication 4, the indication information 4 includes the session port identifier 11 and the tunnel port 41 identifier corresponding to the identifier of the UPF1 network element And group FAR1 logo.
  • the N4 session release request 2 may include the identifier of the rule group 11 and the identifier of the rule group 41, which is not specifically limited in this embodiment of the present application.
  • the UPF1 network element releases the first session, and deletes the session port 11 of the UPF1 network element and the rule group 11 of the session port 11 according to the session port identifier 11. And, the UPF1 network element deletes the group FAR1 applied to the UPF1 network element according to the group FAR1 identifier, or the UPF1 network element updates the group FAR1 applied to the UPF1 network element according to the updated group FAR1.
  • the UPF1 network element may also delete the tunnel port 41 and the rule group 41 on the tunnel port 41 according to the identifier of the tunnel port 41.
  • the SMF network element sends the N4 session modification request 3 to the corresponding UPF2 network element according to the identifier of the UPF2 network element in the 5GLAN service release response 2 .
  • the UPF2 network element receives the N4 session modification request 3 from the SMF network element.
  • the N4 session modification request 3 includes indication information 5, which includes the updated group FAR2 corresponding to the identifier of the UPF2 network element, for updating the group FAR2 applied on the UPF2 network element.
  • the indication information 5 also includes an identifier of the tunnel port 42 corresponding to the identifier of the UPF2 network element, and is used to delete the tunnel port 42 of the UPF2 network element and the rule group 42 on the tunnel port 42.
  • the UPF2 network element updates the group FAR2 applied to the UPF2 network element according to the updated group FAR2; and, the UPF2 network element deletes the tunnel port 42 and the tunnel port of the UPF2 network element according to the identifier of the tunnel port 42 The rule group 42 on 42.
  • the configuration diagram of the 5GLAN group on the UPF1 network element may be as shown in (a) in FIG. 26.
  • the configuration diagram of the 5GLAN group on the UPF1 network element may be as shown in (b) in FIG. 26. It can be seen that the rule group 41 on the tunnel port 41 and the rule group 43 on the tunnel port 43 corresponding to the tunnel between the UPF1 network element and the UPF3 network element are deleted; and the group FAR3 on the UPF3 network element is also updated Among them, FA43 in group FAR3 is deleted.
  • FA43 is used to copy the received broadcast message belonging to the 5GLAN group and send it to the tunnel port 43 of the UPF3 network element.
  • the 5GLAN group there is no configuration for the 5GLAN group on the UPF1 network element, so it is not shown in (b) in FIG. 26.
  • the configuration diagram of the 5GLAN group on the UPF1 network element may be as shown in (a) in FIG. 27.
  • the configuration diagram of the 5GLAN group on the UPF1 network element may be as shown in (b) in FIG. 27.
  • the terminal members in the 5GLAN group leave the network, they only need to adjust (update or delete) the 5GLAN group FAR on the associated UPF network element and adjust (update or delete) the associated
  • the entrance PDR, exit PDR, and exit FAR corresponding to the terminal member on the UPF network element are sufficient, and the entrance PDR, exit PDR, and exit FAR corresponding to other members in the 5GLAN group do not change. Therefore, when there are many terminal members connected to the network in the 5GLAN group, the problem of greatly increased configuration workload caused by the change in the number of terminal members can be avoided, and the configuration workload caused by the change in the number of terminal members can be greatly reduced.
  • the actions of the GMF network element, SMF network element, UPF1 network element or UPF2 network element in the above steps S2301 to S2310 can be called by the processor 1101 in the communication device 1100 shown in FIG. 11 to the application program code stored in the memory 1103 To implement, this embodiment does not limit this.
  • FIGS. 12 to 27 respectively exemplarily show the corresponding groups when the terminal members in the 5GLAN group change (for example, the terminal member joins the network, the terminal member leaves the network, and the terminal member who has entered the network moves) in the broadcast scenario.
  • the group communication method is mainly explained by the configuration of the control plane. The following is a description of how user plane network elements forward group broadcast messages.
  • terminal 1, terminal 2, and terminal 3 in 5GLAN group 1 whose current 5GLAN group ID is 1 have already joined the network.
  • terminal 1 and terminal 2 access the UPF1 network element
  • terminal 3 accesses the UPF2 network element.
  • the configuration diagram of the 5GLAN group on the UPF1 and UPF2 network elements is shown in Figure 28.
  • the terminal 1 sends the message 1 to the UPF1 network element through the 5G user plane protocol (that is, forwarding through the access device). It is assumed here that the destination address of message 1 is all 1s (representing broadcast messages), and the source address is the address of terminal 1.
  • the UPF1 network element can determine the session port corresponding to the message 1 according to the 5G user plane protocol flag (such as TEID) of the message 1, here it is assumed that the session corresponding to the message 1 The port is session port 11. Then, the UPF1 network element may use the entry PDR (may be one or more) in the rule group 11 applied on the session port 11 to match the characteristic information of the packet 1 to find the matching entry PDR.
  • the 5G user plane protocol flag such as TEID
  • the method for identifying the incoming PDR message may be, for example, identifying that the message belongs to a certain 5GLAN group according to the 5G user plane protocol tag, and identifying the message as a broadcast message according to the identification rules of the broadcast message.
  • the 5G user plane protocol flag here may be, for example, TEID, or TEID + QFI, which is not specifically limited in this embodiment of the present application.
  • the identification rule of the broadcast packet may be, for example, that the destination IP address is all 1s; or, if the packet 1 is an Ethernet frame, the broadcast packet
  • the identification rule may be, for example, that the destination MAC address is all 1, which is not specifically limited in this embodiment of the present application.
  • the UPF1 network element finds the corresponding 5GLAN group FAR according to the identifier of the 5GLAN group included in the entrance PDR1, and processes the message 1 from the terminal 1 through the 5GLAN group FAR. Specifically, the UPF1 network element copies the message into the same number of multiple copies according to the total number of member ports corresponding to the 5GLAN group 1 on the UPF1 network element, and then forwards the message to the outlet specified by the 5GLAN group FAR. For example, in FIG. 28, the UPF1 network element can find the corresponding 5GLAN group FAR as group FAR1 according to the identifier 1 of the 5GLAN group included in the entrance PDR1, and then process the message 1 from the terminal 1 through the group FAR1. Among them, FIG.
  • group FAR1 includes three FAs, namely FA11, FA21, and FA41, where FA11 is used to forward message 1 to the exit of session port 11, and FA21 is used to forward message 1 to the session port At the exit of 21, FA41 is used to forward packet 1 to the exit of tunnel port 41. Among them, since the exit of session port 11 is the entrance of packet 1, the packet forwarded to the exit of session port 11 will be throw away.
  • the UPF1 network element further processes the packet 1 according to the egress PDR and egress FAR on the session port 21 (may be multiple sets of egress PDR and egress FAR); and, the UPF1 network element according to the egress PDR and egress on the tunnel port 41
  • the export FAR (may be multiple sets of export PDR and processing FAR) further processes the message 1.
  • the way in which the UPF1 network element processes packet 1 according to the egress PDR and egress FAR on session port 21 is similar to the way that the UPF1 network element further processes packet 1 according to the egress PDR and egress FAR on tunnel port 41,
  • the exemplary manner in which the UPF1 network element processes the message 1 according to the egress PDR and egress FAR on the session port 21 will be described.
  • the UPF1 network element can use the egress PDR on the session port 21 to match the type information of the packet 1 to find the egress PDR that matches it.
  • the differentiated services code point (DSCP) field based on the IP message or the 802.1p bit of the Ethernet frame identifies the priority of message 1. It is assumed here that the priority of the packet 1 is the first priority, and the egress PDR11 on the session port 21 is used to identify the packet of the first priority. At this time, the egress PDR found by the UPF1 network element matching it is the egress PDR11 .
  • the UPF1 network element finds the corresponding outlet FAR11 according to the identifier of the outlet FAR11 included in the outlet PDR11, adds the outer message header to the message 1 through the outlet FAR11, and marks the transport layer, then removes the message 1 from the session port 11 Forward it, and then terminal 2 can receive message 1.
  • the outlet FAR11 adds the outer message header to the packet and marks the transport layer, reference may be made to the embodiment part shown in FIG. 5, which will not be repeated here.
  • the processing method after the UPF2 network element receives the message 1 is similar to the processing method of the UPF1 network element when it receives the message 1, the difference is that after the UPF2 network element receives the message 1 from the UPF1 network element, it can
  • the tunnel header of the packet 1 and the tunnel port identifier set in the tunnel header determine the tunnel port corresponding to the packet 1.
  • the tunnel port corresponding to the packet 1 is the tunnel port 42.
  • control plane configuration process and the user plane network element forwarding group broadcast message process in the foregoing broadcast scenario in the embodiment of the present application can be decoupled. That is to say, based on the control plane configuration process in the above-mentioned broadcast scenario according to the embodiment of the present application, there may be another user plane network element forwarding group broadcast message process; or, based on the above-mentioned broadcast scenario, the user plane The process of the network element forwarding the group broadcast message may also exist other control plane configuration processes, which are not specifically limited in the embodiments of the present application.
  • control plane configuration process in the above-mentioned broadcast scenario in the embodiment of the present application is described by using different UPF network elements managed by the same SMF network element as an example.
  • different UPF network elements may also be composed of different SMF network elements.
  • the GMF network element needs to send the above 5GLAN service response message or 5GLAN service update response or 5GLAN release response to different SMF network elements, respectively, and then pass the corresponding
  • the SMF network element sends the message sent by the SMF network element to the UPF network element in the above-mentioned control plane configuration process to the UPF network element it manages.
  • This embodiment of the present application does not elaborate on this scenario.
  • this description is also applicable to the following multicast scenarios, which will be described here in a unified manner, and will not be repeated here.
  • the following uses a multicast scenario as an example to give a group communication method provided by an embodiment of the present application.
  • the group communication system shown in FIG. 8 is applied to the 5G network shown in FIG. 9, the group management function network element is a GMF network element, and the session management network element is an SMF network element (such as the first session management network element Is SMF1 network element, the second session management network element is SMF2 network element), the user plane network element is UPF network element (such as the first user plane network element is UPF1 network element, the second user plane network element is UPF2 network element), Take the scenario where a multicast member joins a multicast group as an example, in the scenario where a multicast member joins, the following two situations may exist (taking the multicast member to be joined as the first terminal as an example):
  • Step 1 Modify the multicast group FAR1 on the UPF1 network element and add a rule that points to the downstream port of the multicast member.
  • Step 2 Configure the egress PDR and egress FAR of the downstream port of the multicast member applied to the UPF1 network element.
  • Step 1 Configure the multicast group FAR1 applied to the UPF1 network element and configure the egress PDR and egress FAR of the multicast member's downstream port applied to the UPF1 network element.
  • the multicast group FAR1 includes Rules for downstream ports.
  • Step 2 Configure the ingress PDR applied to the upstream port of the multicast member on the UPF1 network element.
  • Step 3 Update the multicast group FAR on the UPF network element upstream of the UPF1 network element, add a rule that points to the downstream port associated with the multicast member; and configure the multicast member to apply to the upstream UPF network element of the UPF1 network element The outlet PDR and outlet FAR of the associated downstream port.
  • Step 4 If there is no other multicast member or source of the multicast group on the upstream UPF network element of the UPF1 network element, repeat the steps similar to those in step 2 and step 3 above (the difference is that the targeted UPF network element is different) , Until there is another multicast member or multicast source of the multicast group on an upstream UPF network element or until the UPF network element that the multicast source accesses (can be regarded as the target UPF network element).
  • step 3 the steps similar to step 3 above (the difference is that the targeted UPF network element is different) for the target UPF network element ends; or, if The target UPF network element is a UPF network element accessed by a multicast source. For this UPF network element, it is also necessary to perform steps similar to step 2 and step 3 above (the difference is that the targeted UPF network element is different).
  • the following exemplarily shows a group communication method provided by an embodiment of the present application in a scenario where a multicast member joins.
  • the group communication method includes the following steps:
  • the first terminal has connected to the UPF1 network element, and the configuration of the 5GLAN group has been created on the UPF1 network element.
  • the establishment method is shown in the embodiment shown in FIG. 12, which will not be repeated here.
  • the configuration of the 5GLAN group may have been created on the UPF2 network element, and the establishment method is as shown in the embodiment shown in FIG. 12, which will not be repeated here.
  • the UPF1 network element and the UPF2 network element are connected.
  • the first terminal sends an Internet Group Management Protocol (IGMP) join (IGMP) message to the UPF1 network element through the access device.
  • IGMP Internet Group Management Protocol
  • the UPF1 network element receives the IGMP join message from the first terminal.
  • the IGMP join message includes the address of the multicast group (which may also be referred to as the multicast address for short).
  • the IGMP join message may also include the address of the multicast source.
  • the first terminal only sends IGMP join messages to the UPF1 network element as a multicast member, while members of the multicast source or non-multicast group do not send IGMP join to the UPF1 network element
  • the message is described here in a unified manner, and will not be repeated below.
  • the method for the first terminal to obtain the address of the multicast source and the address of the multicast group can refer to the existing implementation method, which will not be repeated here.
  • the UPF1 network element recognizes the IGMP join message, and then sends the IGMP join message to the connected SMF network element.
  • the SMF network element receives the IGMP join message from the UPF1 network element.
  • the IGMP join message may be carried in the N4 interface message sent by the UPF1 network element to the SMF network element and sent to the SMF network element, which is not specifically limited in the embodiment of the present application.
  • the SMF network element recognizes the IGMP join message, and then sends a 5GLAN service request message to the GMF network element.
  • the GMF network element receives the 5GLAN service request message from the SMF network element.
  • the 5GLAN service request message carries the IGMP join message, the identifier of the first terminal, the identifier of the UPF1 network element, and the session port identifier 11.
  • the identifier of the first terminal may be, for example, the address of the first terminal.
  • the address of the first terminal may be, for example, the IP address of the first terminal or the IP address of the first terminal, which is not specifically limited in this embodiment of the present application. This description can also be similarly applied to other terminals in other embodiments in the multicast scenario of this application.
  • the following identifier of the terminal 3 may be the address of the terminal 3, and the address may be, for example, an IP address or a MAC address, which is described here in a unified manner and will not be described in detail below.
  • the GMF network element parses the IGMP join message to obtain the multicast source address and the multicast group address. Furthermore, the GMF network element can obtain the context information of the multicast group according to the address of the multicast group (optionally combined with the address of the multicast source).
  • the GMF network element acquiring and acquiring the context information of the multicast group may be, for example: establishing the context information of the multicast group, or reading the context information of the multicast group stored on the GMF network element.
  • the GMF network element needs to establish the context information of the multicast group; or, the first terminal is not the first to access the multicast group
  • the GMF network element can read the context information of the multicast group stored on the GMF network element.
  • the context information of the multicast group may include information of the multicast forwarding tree, such as the identification of the multicast source, the identification of the multicast members, and the multicast source and each multicast
  • the identification of the UPF network element may be one or more between members.
  • the multicast forwarding tree and the configuration diagram of the multicast group on the UPF network element of the multicast forwarding tree are shown in FIG. 30.
  • the information of the multicast forwarding tree included in the context information of the multicast group may be as shown in Table 9, including the identifier of the multicast source, the identifier of the downstream member of the multicast source, and the downstream member of the downstream member of the multicast source. logo, and so on.
  • the identifier of the multicast source here may specifically be the address of the above-mentioned multicast source, and the identifier of the downstream member may also specifically be the IP address of the downstream member, which will be described here in a unified manner and will not be repeated below.
  • the context information of the multicast group may further include an upstream port identifier and a downstream port identifier of the multicast group on the UPF network element between the multicast source and each multicast member.
  • the context information of the multicast group may further include an upstream member ID, an upstream port ID, and a downstream member ID corresponding to the identifier of the UPF network element between the multicast source and each multicast member And downstream port identification, as shown in Table 10.
  • the GMF network element combines the identifier of the UPF1 network element and the session port identifier 11 carried in the 5GLAN service request message to create an egress PDR and an egress FAR applied on the downstream port of the UPF1 network element. And update the multicast group FAR1 applied to the UPF1 network element.
  • the identifier of the downstream port is the session port identifier 11.
  • the updated multicast group FAR1 adds a rule for copying the received multicast message belonging to the multicast group and sending it to the downstream port.
  • a schematic diagram of the configuration of the multicast group may be as shown in (a) in FIG. 31.
  • the terminal 3 in (a) in FIG. 31 does not join the multicast group, so it is only a simple illustration of the session port 11 on the UPF1 network element that the terminal 3 accesses after the terminal 3 establishes a PDU session, the specific PDU For the process of session establishment, reference may be made to the embodiment shown in FIG. 12, which is not repeated here.
  • the configuration diagram of the multicast group may be as shown in FIG. 31 Shown in (b). That is, egress PDR3 and egress FAR3 are configured on the downstream port 3 corresponding to the session port identifier 11 on the UPF1 network element, and at the same time, the updated multicast group FAR1 adds the received multicast packets belonging to the multicast group The rule sent to this downstream port 3 after copying.
  • the GMF network element if the UPF network element accessed by the multicast source and the UPF1 network element are not the same UPF network element, the GMF network element also needs to perform the following operations:
  • the GMF network element determines whether there is an upstream port corresponding to the multicast group on the UPF1 network element. If not, it creates an ingress PDR applied on the upstream port of the UPF1 network element.
  • the identifier of the upstream port is the identifier of the tunnel port on the UPF network element side of the tunnel between the UPF1 network element and the upstream UPF network element of the UPF1 network element.
  • the GMF network element sequentially traverses the upstream UPF network element of the UPF1 network element to the target UPF network element according to the context information of the multicast group, where the target UPF network element is a UPF network element with an upstream port corresponding to the multicast group Or the UPF network element accessed by the multicast source.
  • the target UPF network element is a UPF network element with an upstream port corresponding to the multicast group
  • the GMF network element is created and applied to each UPF
  • the GMF network element creates the egress PDR and egress FAR applied to the downstream port of the target UPF network element, and updates the multicast group FAR applied to the target UPF network element.
  • the created or updated multicast group FAR includes rules for copying the received multicast message belonging to the multicast group and sending it to the downstream port of the UPF network element.
  • the GMF network element is created and applied to each The entrance PDR of the upstream port of each UPF network element, and the creation of the exit PDR and exit FAR applied to the downstream port of each UPF network element, and the creation of the multicast group FAR applied to each UPF network element.
  • the created multicast group FAR includes a rule for copying the received multicast message belonging to the multicast group and sending it to the downstream port of the UPF network element.
  • the corresponding port identifier is the tunnel port identifier. If the above upstream port is a session port, that is, the target UPF network element is the upstream port on the target UPF network element in the scenario where the multicast source accesses the UPF network element, the corresponding port identifier is when the multicast source establishes a PDU session.
  • the session port identifier corresponding to the session port created on the target UPF network element will be described here in a unified manner, and will not be repeated below.
  • the schematic diagram of the configuration of the multicast group may be as shown in (a) in FIG. 32.
  • the terminal 4 in (a) in FIG. 32 does not join the multicast group, so it is only a simple illustration of the session port 11 and the tunnel port 41 on the UPF1 network element that the terminal 4 accesses after the terminal 4 establishes a PDU session , And the tunnel port 42 on the UPF2 network element connected to the UPF1 network element.
  • the terminal 4 in (a) in FIG. 32 does not join the multicast group, so it is only a simple illustration of the session port 11 and the tunnel port 41 on the UPF1 network element that the terminal 4 accesses after the terminal 4 establishes a PDU session , And the tunnel port 42 on the UPF2 network element connected to the UPF1 network element.
  • FIG. 12 For the specific PDU session establishment process, reference may be made to the embodiment shown in FIG. 12, which will not be repeated here.
  • the configuration diagram of the multicast group may be as shown in FIG. 32
  • the egress PDR4 and the egress FAR4 are configured on the session port 11 corresponding to the session port identifier 11 on the UPF1 NE (that is, the downstream port 4 in (b) in FIG. 32), and the tunnel port 41 on the UPF1 NE Ingress PDR2 is configured on the above, and the updated multicast group FAR1 adds a rule for copying the received multicast message belonging to the multicast group and sending it to the downstream port 4.
  • egress PDR1 and egress FAR1 are configured on the tunnel port 42 of the UPF2 network element (that is, downstream port 1 in (b) in FIG. 32), and the updated multicast group FAR2 is added to the The rule that the multicast packets of the multicast group are copied and sent to the downstream port 1.
  • a schematic diagram of the configuration of the multicast group may be as shown in (a) in FIG. 33.
  • terminal 4 in (a) in FIG. 33 does not join the multicast group, so it is only a simple illustration of session port 11 and tunnel port 41 on the UPF1 network element that terminal 4 accesses after terminal 4 establishes a PDU session , And the tunnel port 42 and the session port 12 on the UPF2 network element connected to the UPF1 network element.
  • FIG. 12 For the specific PDU session establishment process, reference may be made to the embodiment shown in FIG. 12, which will not be repeated here.
  • the configuration diagram of the multicast group may be as shown in FIG. 33
  • the egress PDR4 and the egress FAR4 are configured on the session port 11 corresponding to the session port identifier 11 on the UPF1 NE (that is, the downstream port 4 in (b) in FIG. 33), and the tunnel port 41 on the UPF1 NE (That is, upstream port 2 in (b) in FIG.
  • ingress PDR2 is configured, and the updated multicast group FAR1 is added to copy the received multicast packets belonging to the multicast group and send it to the Rules on downstream port 4.
  • egress PDR1 and egress FAR1 are configured on the tunnel port 42 of the UPF2 NE (that is, downstream port 1 in (b) in FIG. 33), and the session port 12 of the UPF2 NE (that is, (b in FIG. 33) )
  • the upstream port 1) is configured with ingress PDR1, and the updated multicast group FAR2 adds a rule for copying the received multicast packets belonging to the multicast group and sending it to the downstream port 1.
  • the group communication method provided in the embodiment of the present application uses the multicast member as the terminal member in the 5GLAN group in the broadcast scenario described above as an example.
  • the multicast members in the embodiment of the present application may not be limited to the terminal members in the 5GLAN group in the above broadcast scenario that have been connected to the network.
  • the GMF network element sends a 5GLAN service response message to the SMF network element.
  • the SMF network element receives the 5GLAN service response message from the GMF network element.
  • the 5GLAN service response message carries the identifier of the UPF1 network element, the identifier of the downstream port corresponding to the identifier of the UPF1 network element, the egress PDR and egress FAR applied on the downstream port of the UPF1 network element, and the updated application Multicast group FAR1 on UPF1 network element.
  • the 5GLAN service response message may also carry the identifier of the upstream port corresponding to the identifier of the UPF1 network element, the entry PDR applied on the upstream port of the UPF1 network element, each UPF network element between the UPF1 network element and the target UPF network element.
  • the The 5GLAN service response message can also carry the identifier of the upstream port corresponding to the identifier of the UPF1 network element, the ingress PDR applied on the upstream port of the UPF1 network element, the UPF1 network element and the target UPF network element between each UPF network element The identification and the identification of the target UPF network element; and the identification of the downstream port corresponding to the identification of the corresponding UPF network element, the egress PDR and egress FAR applied to the downstream port, the identification of the upstream port, the application Ingress PDR, the created or updated multicast group FAR applied on the UPF network element.
  • the SMF network element sends an N4 session modification request message to the UPF1 network element according to the identifier of the UPF1 network element.
  • the UPF1 network element receives the N4 session modification request message from the SMF network element.
  • the N4 session modification request message includes the identifier of the downstream port corresponding to the identifier of the UPF1 network element, the egress PDR and egress FAR applied on the downstream port of the UPF1 network element, and the updated application on the UPF1 network element Of the multicast group FAR1.
  • the UPF1 network element configures the egress PDR and egress FAR on the downstream port of the UPF1 network element according to the downstream port identifier and the egress PDR and egress FAR applied on the downstream port of the UPF1 network element; and the UPF1 network element updates according to After the multicast group FAR1, update the multicast group FAR1 applied to the UPF1 network element.
  • the UPF1 network element sends an N4 session modification response to the SMF network element.
  • the SMF network element receives the N4 session modification response from the UPF1 network element.
  • the N4 session modification response message is used to notify the completion of N4 session modification and rule installation.
  • the foregoing N4 session modification request message further includes an upstream port corresponding to the identifier of the UPF1 network element And the entry PDR applied on the upstream port of the UPF1 network element.
  • the UPF1 network element can also configure the ingress PDR on the upstream port of the UPF1 network element according to the identifier of the upstream port and the ingress PDR applied on the upstream port of the UPF1 network element.
  • the SMF network element also needs to send the corresponding downstream port identifier to the corresponding UPF network element according to the identifier of each UPF network element between the UPF1 network element and the target UPF network element, and apply the egress PDR and The exit FAR, the identifier of the upstream port, the entry PDR applied on the upstream port, and the updated multicast group FAR applied on the UPF network element.
  • each UPF network element can configure the egress PDR and egress FAR on the downstream port of the UPF network element according to the identifier of the downstream port and the egress PDR and egress FAR applied on the downstream port; and, each UPF network element
  • the ingress PDR can be configured on the upstream port of the UPF network element according to the identifier of the upstream port and the ingress PDR applied on the upstream port, and each UPF network element can update the application on the upstream port according to the updated multicast group FAR Multicast group FAR on the UPF network element.
  • the SMF network element needs to send the target UPF network element the identifier of the downstream port corresponding to the target UPF network element, the egress PDR and egress FAR applied on the downstream port, and the updated application on the target UPF network element FAR on the multicast group.
  • the target UPF network element can configure the egress PDR and egress FAR on the downstream port of the target UPF network element according to the identifier of the downstream port and the egress PDR and egress FAR applied on the downstream port; and the target UPF network element can The updated multicast group FAR updates the multicast group FAR applied to the target UPF network element.
  • the SMF network needs to send the downstream port corresponding to the identifier of the corresponding UPF network element to the corresponding UPF network element according to the identifier of each UPF network element between the UPF1 network element and the target UPF network element and the identifier of the target UPF network element Identification, the exit PDR and exit FAR applied on the downstream port, the identification of the upstream port, the entry PDR applied on the upstream port, and the created or updated multicast group FAR applied on the UPF network element.
  • each UPF network element can configure the egress PDR and egress FAR on the downstream port of the UPF network element according to the identifier of the downstream port and the egress PDR and egress FAR applied on the downstream port; and, each UPF network element
  • the ingress PDR can be configured on the upstream port of the UPF network element according to the identifier of the upstream port and the ingress PDR applied on the upstream port, and each UPF network element can update the application on the upstream port according to the updated multicast group FAR Multicast group FAR on the UPF network element.
  • the multicast members of the multicast group join, it is only necessary to adjust (update or create) the multicast group FAR on the associated UPF network element and adjust (create) the associated UPF network element On the ingress PDR, egress PDR and egress FAR corresponding to the multicast member, or adjust (create) the egress PDR and egress FAR corresponding to the multicast member on the associated UPF network element, other groups in the multicast group
  • the entrance PDR, exit PDR, and exit FAR corresponding to the broadcast members are not changed. Therefore, when there are many multicast members in the multicast group, the configuration workload caused by the change in the number of multicast members can be greatly increased, and the configuration workload caused by the change in the number of multicast members can be greatly reduced.
  • the actions of the GMF network element, SMF network element or UPF1 network element in the above steps S2901 to S2909 can be executed by the processor 1101 in the communication device 1100 shown in FIG. 11 calling the application program code stored in the memory 1103.
  • the embodiment does not limit this.
  • the group communication system shown in FIG. 8 is applied to the 5G network shown in FIG. 9, the group management function network element is a GMF network element, and the session management network element is an SMF network element (such as the first session management The network element is SMF1 network element, the second session management network element is SMF2 network element), the user plane network element is UPF network element (such as the first user plane network element is UPF1 network element, the second user plane network element is UPF2 network element ),
  • SMF1 network element such as the first session management The network element
  • the second session management network element is SMF2 network element
  • the user plane network element is UPF network element (such as the first user plane network element is UPF1 network element, the second user plane network element is UPF2 network element)
  • the multicast member leaves the multicast group is used as an example. In the scenario where the multicast member leaves, the following two situations may exist (taking the multicast member who is leaving as the first terminal as an example):
  • Step 1 Modify the multicast group FAR3 on the UPF3 network element and delete the rule pointing to the downstream port of the multicast member.
  • Step 2 Delete the egress PDR and egress FAR of the downstream port of the multicast member on the UPF3 network element.
  • the UPF network element (assumed to be UPF3 network element) originally accessed by the first terminal does not have other multicast members or multicast sources of the multicast group, then:
  • Step 1 Delete the multicast group FAR3 on the UPF3 network element, and delete the egress PDR and egress FAR of the multicast member's downstream port on the UPF3 network element.
  • Step 2 Delete the entry PDR of the upstream port of the multicast member on the UPF3 network element.
  • Step 3 Modify the multicast group FAR on the upstream UPF network element of the UPF3 network element, delete the rule pointing to the downstream port associated with the multicast member; and delete the multicast member association on the upstream UPF network element of the UPF3 network element The outlet PDR and outlet FAR of the downstream port.
  • Step 4 If there is no other multicast member or source of the multicast group on the upstream UPF network element of the UPF3 network element, repeat the steps similar to those in step 2 and step 3 above (the difference is that the targeted UPF network element is different) , Until there is another multicast member or multicast source of the multicast group on an upstream UPF network element or until the UPF network element that the multicast source accesses (can be regarded as the target UPF network element).
  • step 3 the steps similar to step 3 above (the difference is that the targeted UPF network element is different) for the target UPF network element ends; or, if The target UPF network element is a UPF network element accessed by a multicast source. For this UPF network element, it is also necessary to perform steps similar to step 2 and step 3 above (the difference is that the targeted UPF network element is different).
  • the group communication method includes the following steps:
  • the first terminal has access to the UPF3 network element, and the configuration of the multicast group to which the first terminal joins has been created on the UPF3 network element, including the multicast group FAR and related rule groups.
  • the configuration of the multicast group to which the first terminal joins may also be created on the UPF2 network element, including the multicast group FAR and related rule groups.
  • the establishment method refer to FIG. 29 ⁇ ⁇ ⁇ Examples. Among them, the UPF3 network element and the UPF2 network element are connected.
  • the first terminal to leave the multicast group.
  • One is to initiate a session release procedure for the first terminal, and the other is to explicitly initiate an IGMP leave message for the first terminal to announce the departure of the multicast group.
  • the manner in which the first terminal initiates the session release process includes the following steps S3401a-S3403a:
  • the first terminal sends a session release request to the AMF network element.
  • the AMF network element receives the session release request from the first terminal.
  • the AMF network element sends an SM context update request to the SMF network element.
  • the SMF network element receives the SM context update request from the AMF network element.
  • the above SM context update request may also be replaced with a PDU session update request, which is not specifically limited in this embodiment of the present application.
  • the SMF network element determines that the first terminal has initiated multicast group communication, the SMF network element sends a 5GLAN service update request (5GLAN service update request) to the GMF network element.
  • the GMF network element receives the 5GLAN service update request from the SMF network element.
  • the 5GLAN service update request is used to request the GMF network element to update the forwarding information of the multicast group.
  • the first terminal explicitly initiates the IGMP leave message, and the way of declaring leaving the multicast group includes the following steps S3401b-S3403b:
  • the first terminal sends an IGMP leave message to the UPF3 network element through the access device.
  • the UPF3 network element receives the IGMP leave message from the first terminal.
  • the IGMP leave message includes the address of the multicast group.
  • the first terminal only sends IGMP leave messages to the UPF3 network element as a multicast member, while members of the multicast source or non-multicast group do not send IGMP leave to the UPF3 network element
  • the message is described here in a unified manner, and will not be repeated below.
  • the method for the first terminal to obtain the address of the multicast group can refer to the existing implementation method, which will not be repeated here.
  • the UPF3 network element recognizes the IGMP leave message, and then sends the IGMP leave message to the connected SMF network element.
  • the SMF network element receives the IGMP leave message from the UPF1 network element.
  • the IGMP leave message may be carried in the N4 interface message sent by the UPF3 network element to the SMF network element and sent to the SMF network element, which is not specifically limited in this embodiment of the present application.
  • the SMF network element recognizes that it is an IGMP message. At the same time, through the context of the first terminal stored on the SMF network element, it is found that the first terminal has previously joined the multicast communication.
  • the GMF network element sends a 5GLAN service update request.
  • the GMF network element receives the 5GLAN service update request from the SMF network element.
  • the 5GLAN service update request carries the IGMP leave message and the identifier of the first terminal.
  • the 5GLAN service update request may carry the identifier of the UPF3 network element and the session port identifier 13.
  • the GMF network element can learn the multicast group where the first terminal is about to leave, and can continue to perform the following steps:
  • the GMF network element adjusts the multicast forwarding rules on the UPF3 network element and upstream UPF network elements according to the context information of the multicast group stored on the GMF network element.
  • the adjustment method is as described before this process, and will not be repeated here.
  • the GMF network element sends a 5GLAN service release response to the SMF network element.
  • the SMF network element receives the 5GLAN service release response from the GMF network element.
  • the GMF network element sends a 5GLAN service update response to the SMF network element.
  • the SMF network element receives the 5GLAN service update response from the GMF network element.
  • the 5GLAN service release response or 5GLAN service update response includes the identifier of the UPF network element that needs to adjust the multicast group configuration information, and the multicast group configuration adjustment information corresponding to the identifier of the corresponding UPF network element.
  • the multicast group configuration adjustment information includes the identifier of the upstream port, which is used to delete the upstream port and the upstream port The ingress PDR on the network; or, when you need to delete the egress PDR and egress FAR of the downstream port of a UPF network element, the multicast group configuration adjustment information includes the identifier of the downstream port, which is used to delete the downstream port and the downstream port The entry PDR on the Internet; or, when you need to delete the multicast group FAR on a UPF network element, the multicast group configuration adjustment information includes the identifier of the multicast group FAR; or, you need to update the UPF network element on
  • the rule group on the upstream port or the downstream port created during the PDU session establishment process needs to be deleted at the same time. No longer.
  • the multicast group configuration adjustment information when leaving through the IGMP leave message, when the entry PDR of the upstream port of a certain UPF network element needs to be deleted, the multicast group configuration adjustment information includes the identifier of the upstream port and the entry applied to the upstream port PDR identification; or, when it is necessary to delete the egress PDR and egress FAR of the downstream port of a certain UPF network element, the multicast group configuration adjustment information includes the identifier of the downstream port and the identifier of the egress PDR applied to the downstream port , Optionally carrying the identifier of the outlet FAR indicated by the outlet PDR; or, when the multicast group FAR on a certain UPF network element needs to be deleted, the multicast group configuration adjustment information includes the identifier of the multicast group FAR; Or, when the multicast group FAR on a certain UPF network element needs to be updated, the multicast group configuration adjustment information includes the updated multicast group FAR.
  • the SMF network element adjusts the identifier of the UPF network element of the multicast group configuration information, and the multicast group configuration adjustment information corresponding to the identifier of the corresponding UPF network element, and sends the corresponding UPF network element to the corresponding UPF network element. Identify the corresponding multicast group configuration adjustment information.
  • the communication between the SMF network element and the UPF3 network element is taken as an example for description.
  • the SMF network element sends an N4 session modification request to the UPF3 network element according to the identifier of the UPF3 network element.
  • the UPF3 network element receives the N4 session modification request from the SMF network element.
  • the N4 session modification request includes multicast group configuration adjustment information corresponding to the identifier of the UPF3 network element.
  • the multicast group configuration adjustment information corresponding to the identifier of the UPF3 network element may include, for example, the identifier of the downstream port corresponding to the identifier of the UPF3 network element.
  • the multicast group configuration adjustment information corresponding to the identifier of the UPF3 network element may also include the updated application, for example Multicast group FAR3 on UPF3 network element.
  • the multicast group configuration adjustment information corresponding to the identifier of the UPF3 network element may further include the application in UPF3 The identifier of the multicast group FAR3 on the network element and the identifier of the upstream port corresponding to the identifier of the UPF3 network element.
  • the multicast group configuration adjustment information corresponding to the identifier of the UPF3 network element may include, for example, the identifier of the downstream port corresponding to the identifier of the UPF3 network element and the application to the UPF3 network element
  • the identifier of the exit PDR on the downstream port of Optional optionally includes the identifier of the exit FAR indicated by the exit PDR.
  • the multicast group configuration adjustment information corresponding to the identifier of the UPF3 network element may also include the updated application, for example Multicast group FAR3 on UPF3 network element.
  • the multicast group configuration adjustment information corresponding to the identifier of the UPF3 network element may further include the application in UPF3 The identifier of the multicast group FAR3 on the network element, the identifier of the upstream port corresponding to the identifier of the UPF3 network element, and the identifier of the ingress PDR applied on the upstream port of the UPF3 network element.
  • the UPF3 network element adjusts the multicast group configuration on the UPF3 network element according to the multicast group configuration adjustment information.
  • the UPF3 NE may delete the exit PDR applied to the downstream port of the UPF3 NE according to the identifier of the downstream port and the identifier of the outlet PDR applied to the downstream port Identify the corresponding exit PDR and the exit FAR indicated by the exit PDR.
  • the UPF3 network element may delete the downstream port and the egress PDR and egress FAR of the downstream port according to the identifier of the downstream port.
  • the UPF3 network element updates the application on the multicast group FAR3 on the UPF3 network element according to the updated application Multicast group FAR3 on the UPF3 network element.
  • the UPF3 network element deletes the application based on the identity of the multicast group FAR3 applied to the UPF3 network element The multicast group FAR3 on the UPF3 network element; and, when leaving via the IGMP leave message, the UPF3 network element deletes the application of the UPF3 network element based on the identification of the upstream port and the entry PDR applied on the upstream port The ingress PDR corresponding to the identifier of the ingress PDR of the upstream port; when leaving through the session release process, the UPF3 network element deletes the upstream port and the ingress PDR on the upstream port according to the identifier of the upstream port.
  • the UPF3 network element sends an N4 session modification response to the SMF network element.
  • the SMF network element receives the N4 session modification response from the UPF1 network element.
  • the N4 session modification response message is used to announce the completion of configuration update.
  • steps S3406-S3408 exemplarily take the multicast group configuration update process on the UPF3 network element as an example for description.
  • the update process of the multicast group configuration on other UPF network elements that need to adjust the multicast group configuration information can refer to the above steps S3406-S3408, which will not be repeated here.
  • a schematic diagram of the configuration of the multicast group may be as shown in (a) in FIG. 35.
  • a schematic diagram of the configuration of the multicast group may be as shown in (b) in FIG. 35.
  • the outlet PDR3 and the outlet FAR3 on the downstream port 3 shown in (a) of FIG. 35 are deleted.
  • the updated multicast group FAR3 deletes the rule that copies the received multicast message belonging to the multicast group and sends it to the downstream port 3 (that is, the session port 33).
  • terminal 3 in (b) in FIG. 35 does not join the multicast group, it is only a simple illustration of session port 33 on the UPF3 network element that terminal 3 accesses after terminal 3 establishes a PDU session
  • session port 33 on the UPF3 network element that terminal 3 accesses after terminal 3 establishes a PDU session
  • FIG. 12 For the specific PDU session establishment process, reference may be made to the embodiment shown in FIG. 12, which will not be repeated here.
  • a schematic diagram of the configuration of the multicast group may be as shown in (a) of FIG. 36.
  • the configuration diagram of the multicast group may be as shown in (b) in FIG. 36. It can be seen that the exit PDR4 and the exit FAR4 on the downstream port 4 of the UPF3 NE shown in (a) of FIG. 36 are deleted; the upstream port 2 of the UPF3 NE shown in (a) of FIG. 36 The entry PDR2 is deleted.
  • the egress PDR1 and egress FAR1 on the downstream port 1 of the UPF2 network element shown in (a) in FIG. 36 are deleted.
  • the multicast group FAR3 applied to the UPF3 network element is deleted, and the updated multicast group FAR2 applied to the UPF2 network element is deleted and the received multicast message belonging to the multicast group is copied and sent to The rule on this downstream port 1. It should be noted that, since terminal 4 in (b) in FIG.
  • a schematic diagram of the configuration of the multicast group may be as shown in (a) of FIG. 37.
  • the configuration diagram of the multicast group may be as shown in (b) in FIG. 37. It can be seen that the exit PDR4 and the exit FAR4 on the downstream port 4 of the UPF3 NE shown in (a) of FIG. 37 are deleted; the upstream port 2 of the UPF3 NE shown in (a) of FIG. 37 The entry PDR2 is deleted.
  • the outlet PDR1 and outlet FAR1 on the downstream port 1 of the UPF2 network element shown in (a) in FIG. 37 are deleted; the inlet PDR1 on the upstream port 1 of the UPF2 network element shown in (a) in FIG. 37 is deleted .
  • the multicast group FAR3 applied to the UPF3 network element is deleted, and the multicast group FAR2 applied to the UPF2 network element is deleted. It should be noted that, since the terminal 4 in (b) in FIG.
  • the multicast members of the multicast group since the multicast members of the multicast group leave, it is only necessary to adjust (update or delete) the multicast group FAR on the associated UPF network element and adjust (delete) the associated UPF network element On the ingress PDR, egress PDR and egress FAR corresponding to the multicast member, or adjust (delete) the egress PDR and egress FAR corresponding to the multicast member on the associated UPF network element, other groups in the multicast group The entrance PDR, exit PDR, and exit FAR corresponding to the broadcast members are not changed. Therefore, when there are many multicast members in the multicast group, the configuration workload caused by the change in the number of multicast members can be greatly increased, and the configuration workload caused by the change in the number of multicast members can be greatly reduced.
  • the actions of the GMF network element, SMF network element or UPF3 network element in the above steps S3401 to S3408 can be executed by the processor 1101 in the communication device 1100 shown in FIG. 11 calling the application program code stored in the memory 1103.
  • the embodiment does not limit this.
  • the group communication system shown in FIG. 8 is applied to the 5G network shown in FIG. 9, the group management function network element is a GMF network element, and the session management network element is an SMF network element (such as the first session management The network element is SMF1 network element, the second session management network element is SMF2 network element), the user plane network element is UPF network element (such as the first user plane network element is UPF1 network element, the second user plane network element is UPF2 network element ), Taking the scenario of multicast member movement as an example.
  • the following situations may exist (taking the multicast member to leave as the first terminal, the original UPF network element that the first terminal accesses is the UPF3 network element, and the newly selected UPF network element is UPF1 network element as an example):
  • Case 1 The newly selected UPF network element (assuming UPF1 network element) of the first terminal has other multicast members or multicast sources of the multicast group, then:
  • Step 1 Modify the multicast group FAR1 on the UPF1 network element and add a rule that points to the downstream port of the multicast member.
  • Step 2 Configure the egress PDR and egress FAR of the downstream port of the multicast member applied to the UPF1 network element.
  • Step 1 Configure the multicast group FAR1 applied to the UPF1 network element and configure the egress PDR and egress FAR of the multicast member's downstream port applied to the UPF1 network element.
  • the multicast group FAR1 includes Rules for downstream ports.
  • Step 2 Configure the ingress PDR applied to the upstream port of the multicast member on the UPF1 network element.
  • Step 3 Update the multicast group FAR on the UPF network element upstream of the UPF1 network element, add a rule that points to the downstream port associated with the multicast member; and configure the multicast member to apply to the upstream UPF network element of the UPF1 network element The outlet PDR and outlet FAR of the associated downstream port.
  • Step 4 If there is no other multicast member or source of the multicast group on the upstream UPF network element of the UPF1 network element, repeat the steps similar to those in step 2 and step 3 above (the difference is that the targeted UPF network element is different) , Until there is another multicast member or multicast source of the multicast group on an upstream UPF network element or until the UPF network element that the multicast source accesses (can be regarded as the target UPF network element).
  • step 3 the steps similar to step 3 above (the difference is that the targeted UPF network element is different) for the target UPF network element ends; or, if The target UPF network element is a UPF network element accessed by a multicast source. For this UPF network element, it is also necessary to perform steps similar to step 2 and step 3 above (the difference is that the targeted UPF network element is different).
  • Step 1 Modify the multicast group FAR3 on the UPF3 network element and delete the rule pointing to the downstream port of the multicast member.
  • Step 2 Delete the egress PDR and egress FAR of the downstream port of the multicast member on the UPF3 network element.
  • the UPF network element (assumed to be UPF3 network element) originally accessed by the first terminal does not have other multicast members or multicast sources of the multicast group, then:
  • Step 1 Delete the multicast group FAR3 on the UPF3 network element, and delete the egress PDR and egress FAR of the multicast member's downstream port on the UPF3 network element.
  • Step 2 Delete the entry PDR of the upstream port of the multicast member on the UPF3 network element.
  • Step 3 Modify the multicast group FAR on the upstream UPF network element of the UPF3 network element, delete the rule pointing to the downstream port associated with the multicast member; and delete the multicast member association on the upstream UPF network element of the UPF3 network element The outlet PDR and outlet FAR of the downstream port.
  • Step 4 If there is no other multicast member or source of the multicast group on the upstream UPF network element of the UPF3 network element, repeat the steps similar to those in step 2 and step 3 above (the difference is that the targeted UPF network element is different) , Until there is another multicast member or multicast source of the multicast group on an upstream UPF network element or until the UPF network element that the multicast source accesses (can be regarded as the target UPF network element).
  • step 3 the steps similar to step 3 above (the difference is that the targeted UPF network element is different) for the target UPF network element ends; or, if The target UPF network element is a UPF network element accessed by a multicast source. For this UPF network element, it is also necessary to perform steps similar to step 2 and step 3 above (the difference is that the targeted UPF network element is different).
  • case 1 and case 2 in the scenario where the multicast members move, the above cases 1 and 3, or the above cases 1 and 4 or the above cases 2 and 3, or the above cases 2 and 3 may be included four.
  • the related implementation of case 1 and case 2 can refer to the embodiment shown in FIG. 29, and the related implementation of case 3 and case 4 can refer to the embodiment shown in FIG. 34, the difference lies in the signaling process of interaction between network elements The difference will not be elaborated here.
  • the signaling process for interaction between corresponding network elements in the scenario where the multicast member moves is similar to the signaling process for interaction between corresponding network elements in the scenario where the terminal member in the 5GLAN group in the broadcast scenario moves,
  • the multicast members of the multicast group move, it is only necessary to adjust (create, update or delete) the multicast group FAR on the associated UPF network element and adjust (create, update or delete)
  • the ingress PDR, egress PDR, and egress FAR corresponding to the multicast member on the associated UPF network element, or adjusting (creating, updating, or deleting) the egress PDR and egress corresponding to the multicast member on the associated UPF network element FAR is sufficient.
  • the ingress PDR, egress PDR and egress FAR corresponding to other multicast members in the multicast group will not change. Therefore, when there are many multicast members in the multicast group, the configuration workload caused by the change in the number of multicast members can be greatly increased, and the configuration workload caused by the change in the number of multicast members can be greatly reduced.
  • FIGS. 29 to 37 respectively exemplarily show the correspondence in the multicast scenario when the terminal members in the multicast group change (such as joining the multicast group, leaving the multicast group, and moving within the multicast group)
  • the group communication method mainly focuses on the configuration of the control plane. The following is a description of how user plane network elements forward group multicast messages.
  • the way in which the user plane NE forwards group multicast messages is similar to the way in which the user plane NE forwards group broadcast messages.
  • the difference is that the entrance PDR in the broadcast scenario is used to identify the group belonging to a LAN group.
  • the ingress PDR in a multicast scenario is used to identify multicast messages belonging to a multicast group.
  • the identification method of the multicast message please refer to the aforementioned multicast introduction part, which will not be repeated here.
  • the mobile multicast source is used as the first terminal, the original UPF network element that the first terminal accesses is the UPF3 network element, and the first terminal corresponds to UPF3 Session port 3 on the network element.
  • the newly selected UPF network element is UPF1 network element.
  • the first terminal corresponds to session port 1 on the UPF1 network element.
  • the SMF network element may be requested to establish a tunnel from the UPF1 network element to the UPF3 network element.
  • the GMF network element can generate the forwarding rules PDR1 and FAR1 applied to the entrance of the session port 1 of the UPF1 network element, where PDR1 is used to determine that the packet sent by the first terminal belongs to the multicast group, FAR1 is used to forward the multicast message to the tunnel port connected to the UPF3 network element.
  • the GMF network element generates the rule PDR3 applied to the entrance of the tunnel port of the UPF3 network element, where PDR3 is used to identify that the received packet belongs to the multicast group, and set the FAR ID to UPF3 network in PDR3 Multicast FAR on the meta.
  • the above-mentioned embodiments of the present application are all exemplified by taking the broadcast message or the multicast message that the entry PDR is used to identify that the message belongs to a certain group as an example.
  • the function of the above-mentioned entrance PDR may also be split. For example, as shown in FIG. 38, at the entrance (for example, the entrance PDR), only the group is identified, and after identification, the designated module is processed. .
  • the identification of unicast, multicast and broadcast within the group is performed by the group PDR of the group, and the forwarding of the message is performed by the group FAR, which is not specifically limited in the embodiments of the present application.
  • the group management function network element, user plane network element or session management network element includes a hardware structure and / or a software module corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed by hardware or computer software driven hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
  • the embodiments of the present application can divide the function modules of the group management function network element, user plane network element or session management network element according to the above method example, for example, each function module can be divided corresponding to each function, or two or two More than one function is integrated in one processing module.
  • the above integrated modules may be implemented in the form of hardware or software function modules. It should be noted that the division of the modules in the embodiments of the present application is schematic, and is only a division of logical functions. In actual implementation, there may be another division manner.
  • FIG. 39 shows a schematic structural diagram of a group management function network element 390.
  • the group management function network element 390 includes a transceiver module 3902 and a processing module 3901.
  • the processing module 3901 is configured to acquire the identifier of the first user plane network element to be accessed by the first terminal, the context information of the LAN group, and the first session port identifier when the first terminal initiates access to the LAN group,
  • the context information includes a list of identifications of user plane network elements accessed by a terminal that has currently connected to the local area network group in the terminal member list of the LAN group
  • the first session port identifier is used on the first user plane network element The identifier of the first session port accessed by the first terminal.
  • the processing module 3901 is also used to create a rule group applied to the first session port for the LAN group; and, the group management function network element creates or updates the application to the first user plane network element for the LAN group according to the context information LAN group FAR on the Internet; where the rule group includes the entrance PDR, the exit PDR and the exit FAR; the exit PDR includes the exit FAR identification, and the entrance PDR includes the local area network group FAR identification; wherein, the entrance PDR is used to identify Broadcast message of LAN group, FAR of LAN group is used to copy and forward the broadcast message to the specified exit; PDR of the exit is used to identify the type of broadcast message, FAR of the exit is used to add an outer message header to the broadcast message And sent through the corresponding port after marking the transport layer.
  • the transceiver module 3902 is used to send a first message to the session management network element, and the first message is used to configure a rule group on the first session port of the first user plane network element and configure or update the first user plane network
  • the group management function network element 390 is presented in the form of dividing each function module in an integrated manner.
  • the "module” herein may refer to a specific ASIC, circuit, processor and memory that execute one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.
  • the group management function network element 390 may take the form shown in FIG. 11.
  • the processor 1101 in FIG. 11 may call the computer execution instruction stored in the memory 1103 to cause the group management function network element 390 to perform the group communication method in the foregoing method embodiment.
  • the functions / implementation processes of the transceiver module 3902 and the processing module 3901 in FIG. 39 can be implemented by the processor 1101 in FIG. 11 calling the computer execution instructions stored in the memory 1103.
  • the function / implementation process of the processing module 3901 in FIG. 39 can be implemented by the processor 1101 in FIG. 11 calling a computer execution instruction stored in the memory 1103, and the function / implementation process of the transceiver module 3902 in FIG. 11 to achieve the communication interface 1104.
  • the group management function network element 390 provided in this embodiment can perform the above-mentioned group communication method, the technical effects that can be obtained can refer to the above-mentioned method embodiments, which will not be repeated here.
  • an embodiment of the present application further provides an apparatus (for example, the apparatus may be a chip system), and the apparatus includes a processor for supporting a group management function network element to implement the foregoing group communication method. For example, a rule group applied to the first session port is created for a local area network group.
  • the device also includes a memory. The memory is used to store program instructions and data necessary for the network element of the group management function. Of course, the memory may not be in the device.
  • the device is a chip system, it may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in the embodiments of the present application.
  • FIG. 40 shows a schematic structural diagram of a first user plane network element 400.
  • the first user plane network element 400 includes a transceiver module 4002 and a processing module 4001.
  • the transceiver module 4002 is configured to receive a first message from a session management network element when the first terminal initiates access to a local area network group.
  • the first message includes a first session port identifier and is applied to the corresponding The rule group on the first session port and the created or updated LAN group FAR applied on the first user plane network element, where the first session port is identified as the first user plane network element for the first terminal
  • the identification of the first session port accessed; the rule group includes the entrance PDR, the exit PDR, and the exit FAR; the exit PDR includes the exit FAR identification, and the entrance PDR includes the local area network group FAR identification; wherein, the entrance PDR is used for identification Broadcast messages belonging to the LAN group.
  • the LAN group FAR is used to copy the broadcast message and forward it to the designated exit; the export PDR is used to identify the type of broadcast message, and the export FAR is used to add an outer message to the broadcast message
  • the header and the transport layer mark are sent out through the corresponding port; the processing module 4001 is used to create a first session port according to the first session port identifier and configure a rule group on the first session port; and, the processing module 4001 is used to Create a LAN group FAR on the first user plane network element according to the created application on the first user plane network element LAN group FAR; or, the first user plane network element on the first user plane according to the updated application
  • the LAN group FAR on the network element updates the LAN group FAR on the first user plane network element.
  • the first user plane network element 400 is presented in the form of dividing each functional module in an integrated manner.
  • the "module” herein may refer to a specific ASIC, circuit, processor and memory that execute one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.
  • the first user plane network element 400 may adopt the form shown in FIG. 11.
  • the processor 1101 in FIG. 11 may invoke the computer execution instruction stored in the memory 1103 to cause the first user plane network element 400 to execute the group communication method in the foregoing method embodiment.
  • the functions / implementation processes of the transceiver module 4002 and the processing module 4001 in FIG. 40 can be implemented by the processor 1101 in FIG. 11 calling the computer execution instructions stored in the memory 1103.
  • the function / implementation process of the processing module 4001 in FIG. 40 can be implemented by the processor 1101 in FIG. 11 calling the computer execution instructions stored in the memory 1103, and the function / implementation process of the transceiver module 4002 in FIG. 40 can be implemented through the diagram 11 to achieve the communication interface 1104.
  • the first user plane network element 400 provided in this embodiment can perform the above group communication method, the technical effects that can be obtained can refer to the above method embodiments, and details are not described herein again.
  • an embodiment of the present application further provides an apparatus (for example, the apparatus may be a chip system), and the apparatus includes a processor for supporting the first user plane network element to implement the foregoing group communication method.
  • the apparatus includes a processor for supporting the first user plane network element to implement the foregoing group communication method.
  • a first session port is created according to the first session port identifier, and a rule group is configured on the first session port.
  • the device also includes a memory.
  • the memory is used to store necessary program instructions and data of the first user plane network element.
  • the memory may not be in the device.
  • the device is a chip system, it may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in the embodiments of the present application.
  • FIG. 41 shows a schematic structural diagram of a session management network element 410.
  • the session management network element 410 includes a receiving module 4102 and a sending module 4101.
  • the receiving module 4102 is configured to receive a first message from a group management function network element when the first terminal initiates access to a local area network group.
  • the first message includes the identifier of the first user plane network element and the first user The first session port identifier corresponding to the ID of the face network element, the rule group applied to the first session port corresponding to the first session port identifier, and the created or updated LAN group applied to the first user plane network element FAR, where the first session port is a session port on the first user plane network element for the first terminal to access;
  • the rule group includes the entrance PDR, the exit PDR, and the exit FAR;
  • the exit PDR includes the exit FAR identification, the entrance
  • the PDR includes the identification of the LAN group FAR; among them, the entrance PDR is used to identify the broadcast messages belonging to the LAN group, the LAN group FAR is used to copy the broadcast message and forward it to the designated exit; the exit PDR is used to identify the broadcast The type of the message.
  • the export FAR is used to add an outer message header and mark the transport layer to the broadcast message and send it through the corresponding port.
  • the sending module 4101 is configured to send a second message to the first user plane network element according to the identifier of the first user plane network element.
  • the second message includes the first session port identifier, the rule group on the first session port, and the creation or The updated local area network group FAR applied on the first user plane network element.
  • the session management network element 410 is presented in the form of dividing each functional module in an integrated manner.
  • the "module” herein may refer to a specific ASIC, circuit, processor and memory that execute one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.
  • the session management network element 410 may adopt the form shown in FIG. 11.
  • the processor 1101 in FIG. 11 may call the computer execution instruction stored in the memory 1103 to cause the session management network element 410 to execute the group communication method in the foregoing method embodiment.
  • the function / implementation process of the receiving module 4102 and the sending module 4101 in FIG. 41 can be implemented by the processor 1101 in FIG. 11 calling the computer execution instructions stored in the memory 1103.
  • the functions / implementation processes of the receiving module 4102 and the sending module 4101 in FIG. 41 can be implemented through the communication interface 1104 in FIG. 11.
  • the session management network element 410 provided in this embodiment can perform the above group communication method, the technical effects that can be obtained can refer to the above method embodiments, and details are not described herein again.
  • an embodiment of the present application further provides an apparatus (for example, the apparatus may be a chip system), and the apparatus includes a processor for supporting a session management network element to implement the foregoing group communication method.
  • the first user plane network element is determined according to the identifier of the first user plane network element.
  • the device also includes a memory. The memory is used to store necessary program instructions and data of the session management network element. Of course, the memory may not be in the device.
  • the device is a chip system, it may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in the embodiments of the present application.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server or data center Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers and data centers that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)) or the like.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a DVD
  • a semiconductor medium for example, a solid state disk (SSD)

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供群组通信方法、设备及系统，可以在群组内的终端成员较多时，大大减少了由于终端成员数量的变化导致的配置工作量。方法包括：在第一终端发起接入局域网群组的情况下，群组管理功能网元获取该第一终端即将接入的第一用户面网元的标识、该局域网群组的上下文信息以及第一会话端口标识；为局域网群组创建应用在该第一会话端口上的规则组；以及，根据该上下文信息，为该局域网群组创建或更新应用在该第一用户面网元上的局域网群组转发动作规则FAR；向会话管理网元发送第一消息，该第一消息用于在该第一用户面网元的第一会话端口上配置该规则组，以及在该第一用户面网元上配置或更新该局域网群组FAR。

Description

群组通信方法、设备及系统
本申请要求于2018年11月19日提交国家知识产权局、申请号为201811378645.3、申请名称为“群组通信方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及群组通信方法、设备及系统。
背景技术
第五代(5th generation，5G)局域网(local area network，5GLAN)服务是目前的5G网络提供的一个服务，主要应用于家庭通信，企业办公，工厂制造，车联网，电网改造和公安机关等。该5GLAN服务能够为一个群组中的两个或者多个终端提供互联网协议(internet protocol，IP)类型或者非IP类型(如以太类型)的私有通信。比如，工厂中的设备可以组成一个群组，群组中的设备之间可以相互发送以太数据包；或者，企业中一个部门中的雇员的办公设备(如手机，计算机或笔记本电脑等)可以组成一个群组，互相发送IP数据包，等等。若两个终端不在同一个群组，则相互之间不能够通信。
针对该5GLAN服务，第三代合作伙伴计划(3rd generation partnership project，3GPP)技术规则(technical rule，TR)23.734提出要支持5GLAN的一对一和一对多通信。具体的，要支持5GLAN的一对一和一对多通信，要求3GPP网络支持基于群组的单播、组播和广播；支持对组播和广播报文进行复制分发；以及支持任意终端作为组播源。
为满足该需求，3GPP技术标准(technical standard，TS)29.244定义了用户面转发报文的方式，其架构如图1所示。其工作机制为，用户面功能(user plane function，UPF)网元从入口(如N3端口)接收到报文后，根据用户报文的5G用户面协议标记(如隧道端点标识(tunnel endpoint identifier，TEID))确定报文所属的会话。然后UPF网元使用该会话的N4会话上下文(N4 session context)中的分组检测规则(packet detection rule，PDR)(可能是一个或多个)与报文的特性信息进行匹配，找到与之匹配的PDR。该PDR指定报文对应的转发动作规则(forwarding action rule，FAR)、服务质量(quality of services，QoS)执行规则(QoS enforcement rule，QER)和统计信息上报规则(usage reporting rule，URR)。进而UPF网元可以根据FAR对报文执行丢弃(drop)、转发(forward)、缓存(buffer)、上报控制面(notify)或者复制(duplicate)等。UPF网元可以根据QER对报文执行QoS操作。UPF网元可以根据URR对报文执行统计信息上报。最后，报文从出口(如N6端口)发送出去。其中，UPF网元根据FAR对报文执行转发处理的过程中，关键动作包括指定出口标识和出口动作。出口动作例如可以包括添加外层消息头(outer header creation)、传输层标记(transport level marking)、转发策略(forwarding policy)或者头增强(header enrichment)等。
然而，若将上述方案应用于群组通信，由于上述方案需要在入口指定出口标识和出口的动作，而入口是与某个终端绑定的，因此5GLAN群组内每增加或减少一个终 端成员，就需要在现有的该5GLAN群组所有终端成员接入的UPF网元的入口上增加或删除将报文转发到该新终端成员的PDR和FAR等。进而，当5GLAN群组内的终端成员较多时，终端成员数量的变化导致的配置工作量将大幅增加。
发明内容
本申请实施例提供群组通信方法、设备及系统，可以在群组内的终端成员较多时，大大减少了由于终端成员数量的变化导致的配置工作量。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种群组通信方法，该方法包括：在第一终端发起接入局域网群组的情况下，群组管理功能网元获取该第一终端即将接入的第一用户面网元的标识、该局域网群组的上下文信息以及第一会话端口标识，其中，该上下文信息中包括该局域网群组的终端成员列表中当前已经接入该局域网群组的终端所接入的用户面网元的标识列表，该第一会话端口标识为该第一用户面网元上用于该第一终端接入的第一会话端口的标识；该群组管理功能网元为局域网群组创建应用在该第一会话端口上的规则组；以及，该群组管理功能网元根据该上下文信息，为该局域网群组创建或更新应用在该第一用户面网元上的局域网群组转发动作规则FAR；其中，该规则组中包括入口分组检测规则PDR，出口PDR和出口FAR；该出口PDR中包括该出口FAR的标识，该入口PDR中包括该局域网群组FAR的标识；其中，该入口PDR用于识别属于该局域网群组的广播报文，该局域网群组FAR用于将该广播报文复制后转发到指定的出口；该出口PDR用于识别该广播报文的类型，该出口FAR用于对该广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；该群组管理功能网元向会话管理网元发送第一消息，该第一消息用于在该第一用户面网元的第一会话端口上配置该规则组，以及在该第一用户面网元上配置或更新该局域网群组FAR。基于该方案，由于局域网群组内的终端入网时，只需要调整(创建或更新)相关联的用户面网元上的局域网群组FAR，以及调整(创建或更新)相关联的用户面网元上与该终端成员对应的入口PDR、出口PDR和出口FAR即可，局域网群组内其他终端成员对应的入口PDR、出口PDR和出口FAR不发生改变。从而可以在局域网群组内入网的终端成员较多时，避免终端成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于终端成员数量的变化导致的配置工作量。
在一种可能的设计中，该方法还包括：在该标识列表中包括第二用户面网元的标识，且该第一用户面网元的标识不在该标识列表中的情况下，该群组管理功能网元获取第一隧道端口标识和第二隧道端口标识，该第一隧道端口标识为第一隧道在该第一用户面网元上的第一隧道端口的标识，该第二隧道端口标识为该第一隧道在该第二用户面网元上的第二隧道端口的标识，该第一隧道为该第一用户面网元和该第二用户面网元之间的隧道；该群组管理功能网元为该局域网群组创建应用在该第一隧道端口上的该规则组，以及，该群组管理功能网元为该局域网群组创建应用在该第二隧道端口上的该规则组，以及，该群组管理功能网元更新应用在该第二用户面网元上的该局域网群组FAR；相应的，该第一消息还用于在该第一隧道端口上配置该规则组；以及在该第二隧道端口上配置该规则组，以及在该第二用户面网元上更新该局域网群组FAR。基于该方案，可以实现跨用户面网元的群组通信。
在一种可能的设计中，该方法还包括：在该第一终端在该局域网群组内从接入该第一用户面网元更新为接入第三用户面网元的情况下，该群组管理功能网元获取第三会话端口标识，该第三会话端口标识为该第三用户面网元上用于该第一终端接入的第三会话端口的标识；该群组管理功能网元为该局域网群组创建应用在该第三会话端口上的规则组；以及，该群组管理功能网元根据该上下文信息，创建或更新应用在该第三用户面网元上的该局域网群组FAR；该群组管理功能网元向该会话管理网元发送第三消息，该第三消息用于在该第三会话端口上配置该规则组，以及在该第三用户面网元上配置或更新该局域网群组FAR，以及删除该第一会话端口上的该规则组，以及删除或更新应用在该第一用户面网元上的该局域网群组FAR，其中，更新后的应用在该第一用户面网元上的该局域网群组FAR是该群组管理功能网元根据该上下文信息，更新应用在该第一用户面网元上的该局域网群组FAR得到的。基于该方案，由于局域网群组内已经入网的终端成员在局域网群组内移动时，只需要调整(创建、更新或删除)相关联的UPF网元上的局域网群组FAR，以及调整(创建、更新或删除)相关联的用户面网元上与该终端成员对应的入口PDR、出口PDR和出口FAR即可，局域网群组内其他已经入网的终端成员对应的入口PDR、出口PDR和出口FAR不发生改变。从而可以在局域网群组内入网的终端成员较多时，避免终端成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于终端成员数量的变化导致的配置工作量。
在一种可能的设计中，该方法还包括：在该标识列表中包括第四用户面网元的标识，且该第一用户面网元上没有该局域网群组的终端成员列表中除该第一终端之外的其他终端接入的情况下，该群组管理功能网元更新应用在该第四用户面网元上的该局域网群组FAR；相应的，该第三消息还用于删除该第一用户面网元和该第四用户面网元之间的第二隧道，以及，删除该第一用户面网元的第三隧道端口上的该规则组，以及删除该第四用户面网元的第四隧道端口上的该规则组，以及更新应用在该第四用户面网元上的该局域网群组FAR，其中，该第三隧道端口为该第二隧道在该第一用户面网元上的隧道端口，该第四隧道端口为该第二隧道在该第四用户面网元上的隧道端口。基于该方案，可以实现跨用户面网元的群组通信。
在一种可能的设计中，该方法还包括：在该标识列表中包括第四用户面网元的标识，且该第三用户面网元的标识不在该标识列表中的情况下，该群组管理功能网元获取第五隧道端口标识和第六隧道端口标识，该第五隧道端口标识为第三隧道在该第三用户面网元上的第五隧道端口的标识，该第六隧道端口标识为该第三隧道在该第四用户面网元上的第六隧道端口的标识，该第三隧道为该第三用户面网元和该第四用户面网元之间的隧道；该群组管理功能网元为该局域网群组创建应用在该第五隧道端口上的该规则组，以及，该群组管理功能网元为该局域网群组创建应用在该第六隧道端口上的该规则组，以及，该群组管理功能网元更新应用在该第四用户面网元上的该局域网群组FAR；相应的，该第三消息还用于在该第五隧道端口上配置该规则组；以及在该第六隧道端口上配置该规则组，以及在该第四用户面网元上更新该局域网群组FAR。基于该方案，可以实现跨用户面网元的群组通信。
在一种可能的设计中，该方法还包括：在该第一终端将离开该局域网群组的情况下，该群组管理功能网元向该会话管理网元发送第五消息，该第五消息用于删除应用 在该第一会话端口上的该规则组，以及删除或更新应用在该第一用户面网元上的该局域网群组FAR，其中，更新后的应用在该第一用户面网元上的该局域网群组FAR是该群组管理功能网元根据该上下文信息，更新应用在该第一用户面网元上的该局域网群组FAR得到的。基于该方案，由于局域网群组内的终端成员离网时，只需要调整(更新或删除)相关联的用户面网元上的局域网群组FAR，以及调整(更新或删除)相关联的用户面网元上与该终端成员对应的入口PDR、出口PDR和出口FAR即可，局域网群组内其他成员对应的入口PDR、出口PDR和出口FAR不发生改变。从而可以在局域网群组内入网的终端成员较多时，避免终端成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于终端成员数量的变化导致的配置工作量。
在一种可能的设计中，该方法还包括：在该标识列表中包括第五用户面网元的标识，且该第一用户面网元上没有该局域网群组的终端成员列表中除该第一终端之外的其他终端接入的情况下，该群组管理功能网元更新应用在该第五用户面网元上的该局域网群组FAR；相应的，该第五消息还用于删除该第一用户面网元和该第五用户面网元之间的第四隧道，以及，删除该第一用户面网元的第七隧道端口上的该规则组，以及删除该第五用户面网元的第八隧道端口上的该规则组，以及更新应用在该第五用户面网元上的该局域网群组FAR，其中，该第七隧道端口为该第四隧道在该第一用户面网元上的隧道端口，该第八隧道端口为该第四隧道在该第五用户面网元上的隧道端口。基于该方案，可以实现跨用户面网元的群组通信。
第二方面，提供了一种群组通信方法，该方法包括：在第一终端发起接入局域网群组的情况下，第一用户面网元接收来自会话管理网元的第一消息，该第一消息包括第一会话端口标识，应用在该第一会话端口标识对应的第一会话端口上的规则组、以及创建或更新后的应用在该第一用户面网元上的局域网群组转发动作规则FAR，其中，该第一会话端口标识为该第一用户面网元上用于该第一终端接入的第一会话端口的标识；该规则组中包括入口分组检测规则PDR，出口PDR和出口FAR；该出口PDR中包括该出口FAR的标识，该入口PDR中包括该局域网群组FAR的标识；其中，该入口PDR用于识别属于该局域网群组的广播报文，该局域网群组FAR用于将该广播报文复制后转发到指定的出口；该出口PDR用于识别该广播报文的类型，该出口FAR用于对该广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；该第一用户面网元根据该第一会话端口标识创建该第一会话端口，并在该第一会话端口上配置该规则组；以及，该第一用户面网元根据创建的应用在该第一用户面网元上的局域网群组FAR，在该第一用户面网元上创建该局域网群组FAR；或者，该第一用户面网元根据更新后的应用在该第一用户面网元上的局域网群组FAR，更新该第一用户面网元上的该局域网群组FAR。其中，第二方面或下述第二方面中任一种可能的实现方式的技术效果可参考上述第一方面，在此不再赘述。
在一种可能的设计中，该第一消息还包括第一隧道端口标识和应用在该第一隧道端口标识对应的第一隧道端口上的该规则组，其中，该第一隧道端口标识为第一隧道在该第一用户面网元上的第一隧道端口的标识，该第一隧道为该第一用户面网元和该第二用户面网元之间的隧道；该方法还包括：该第一用户面网元根据该第一隧道端口标识创建该第一隧道端口，并在该第一隧道端口上配置该规则组。
在一种可能的设计中，该方法还包括：在该第一终端不再由该第一用户面网元提供服务的情况下，该第一用户面网元接收来自该会话管理网元的第二消息，该第二消息包括该第一会话端口标识，以及该第二消息包括应用在该第一用户面网元上的该局域网群组FAR的标识或者更新后的应用在该第一用户面网元上的该局域网群组FAR；该第一用户面网元根据该第一会话端口标识，删除该第一会话端口和应用在该第一会话端口的该规则组；以及，该第一用户面网元根据应用在该第一用户面网元上的该局域网群组FAR的标识，删除应用在该第一用户面网元上的该局域网群组FAR；或者，该第一用户面网元根据更新后的应用在该第一用户面网元上的该局域网群组FAR，更新该第一用户面网元上的该局域网群组FAR。
在一种可能的设计中，该第二消息还包括第一隧道端口标识，其中，该第一隧道端口标识为第一隧道在该第一用户面网元上的第一隧道端口的标识，该第一隧道为该第一用户面网元和该第二用户面网元之间的隧道；该方法还包括：该第一用户面网元根据该第一隧道端口标识，删除该第一隧道端口和应用在该第一隧道端口的该规则组。
第三方面，提供了一种群组通信方法，该方法包括：在第一终端发起接入局域网群组的情况下，会话管理网元接收来自群组管理功能网元的第一消息，该第一消息包括该第一用户面网元的标识、与该第一用户面网元的标识对应的第一会话端口标识，应用在该第一会话端口标识对应的第一会话端口上的规则组、以及创建或更新后的应用在该第一用户面网元上的局域网群组转发动作规则FAR，其中，该第一会话端口为该第一用户面网元上用于该第一终端接入的会话端口；该规则组中包括入口分组检测规则PDR，出口PDR和出口FAR；该出口PDR中包括该出口FAR的标识，该入口PDR中包括该局域网群组FAR的标识；其中，该入口PDR用于识别属于该局域网群组的广播报文，该局域网群组FAR用于将该广播报文复制后转发到指定的出口；该出口PDR用于识别该广播报文的类型，该出口FAR用于对该广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；该会话管理网元根据该第一用户面网元的标识，向该第一用户面网元发送第二消息，该第二消息包括该第一会话端口标识，该第一会话端口上的规则组、以及创建或更新后的应用在该第一用户面网元上的局域网群组FAR。其中，第三方面或下述第三方面中任一种可能的实现方式的技术效果可参考上述第一方面，在此不再赘述。
在一种可能的设计中，该第一消息还包括与该第一用户面网元的标识对应的第一隧道端口标识和应用在该第一隧道端口标识对应的第一隧道端口上的该规则组，以及第二用户面网元的标识、与第二用户面网元的标识对应的第二隧道端口标识、应用在该第二隧道端口标识对应的第二隧道端口上的该规则组、和更新后的应用在该第二用户面网元上的局域网群组FAR；其中，该第一隧道端口为第一隧道在该第一用户面网元上的隧道端口，该第二隧道端口为第一隧道在该第二用户面网元上的隧道端口，该第一隧道为该第一用户面网元和该第二用户面网元之间的隧道；相应的，该第一消息还包括该第一隧道端口标识和该第一隧道端口上的该规则组；该方法还包括：该会话管理网元根据该第二用户面网元的标识，向该第二用户面网元发送第三消息，该第三消息包括该第二隧道端口标识、该第二隧道端口上的该规则组、和更新后的应用在该第二用户面网元上的局域网群组FAR。
在一种可能的设计中，该方法还包括：在该第一终端在该局域网群组内从接入该第一用户面网元更新为接入第三用户面网元的情况下，该会话管理网元接收来自该群组管理功能网元的第四消息，该第四消息包括该第一用户面网元的标识，与该第一用户面网元的标识对应的该第一会话端口标识，以及该第四消息包括应用在该第一用户面网元上的该局域网群组FAR的标识或者更新后的应用在该第一用户面网元上的该局域网群组FAR，以及，该第四消息包括该第三用户面网元的标识，以及与该第三用户面网元的标识对应的第三会话端口标识、应用在该第三会话端口标识对应的第三会话端口的该规则组、以及创建或更新后的应用在该第三用户面网元上的局域网群组FAR，其中，该第三会话端口为该第三用户面网元上用于该第一终端接入的会话端口；该会话管理网元根据该第一用户面网元的标识，向该第一用户面网元发送第五消息，该第五消息包括该第一会话端口标识，以及该第五消息包括应用在该第一用户面网元上的该局域网群组FAR的标识或者更新后的应用在该第一用户面网元上的该局域网群组FAR；以及，该会话管理网元根据该第三用户面网元对的标识，向该第三用户面网元发送第六消息，该第六消息包括该第三会话端口标识、该第三会话端口的该规则组、以及创建或更新后的应用在该第三用户面网元上的局域网群组FAR。
在一种可能的设计中，该方法还包括：该第四消息还包括与该第一用户面网元的标识对应的第三隧道端口标识，第四用户面网元的标识，与该第四用户面网元的标识对应的第四隧道端口标识、以及更新后的应用在该第四用户面网元上的该局域网群组FAR，其中，该第三隧道端口标识为第二隧道在该第一用户面网元上的隧道端口标识，该第四隧道端口标识为该第二隧道在该第四用户面网元上的隧道端口标识；相应的，该第五消息还包括该第三隧道端口标识；该方法还包括：该会话管理网元根据该第四用户面网元的标识，向该第四用户面网元发送第七消息，该第七消息包括该第四隧道端口标识、以及更新后的应用在该第四用户面网元上的该局域网群组FAR。
在一种可能的设计中，该第四消息还包括与该第三用户面网元的标识对应的第五隧道端口标识和应用在该第五隧道端口标识对应的第五隧道端口的该规则组；以及，该第四消息还包括第四用户面网元的标识，与该第四用户面网元的标识对应的第六隧道端口标识、应用在该第六隧道端口标识对应的第六隧道端口的该规则组、以及更新后的应用在该第四用户面网元上的局域网群组FAR；该第五隧道端口为第三隧道在该第三用户面网元上的隧道端口，该第六隧道端口为该第三隧道在该第四用户面网元上的隧道端口，该第三隧道为该第三用户面网元和该第四用户面网元之间的隧道；相应的，该第六消息还包括该第五隧道端口标识和该第五隧道端口的该规则组；该方法还包括：该会话管理网元根据该第四用户面网元的标识，向该第四用户面网元发送第八消息，该第八消息包括该第六隧道端口标识、该第六隧道端口的该规则组、以及更新后的应用在该第四用户面网元上的局域网群组FAR。
在一种可能的设计中，在该第一终端将离开该局域网群组的情况下，该会话管理网元接收来自该群组管理功能网元的第九消息，该第九消息包括该第一用户面网元的标识，与该第一用户面网元的标识对应的该第一会话端口标识，以及该第九消息包括应用在该第一用户面网元上的该局域网群组FAR的标识或者更新后的应用在该第一用户面网元上的该局域网群组FAR；该会话管理网元根据该第一用户面网元的标识， 向该第一用户面网元发送第十消息，该第十消息包括该第一会话端口标识，以及该第五消息包括应用在该第一用户面网元上的该局域网群组FAR的标识或者更新后的应用在该第一用户面网元上的该局域网群组FAR。
在一种可能的设计中，该第九消息还包括与该第一用户面网元的标识对应的第七隧道端口标识，第五用户面网元的标识，与该第五用户面网元的标识对应的第八隧道端口标识、以及更新后的应用在该第五用户面网元上的该局域网群组FAR，其中，该第七隧道端口标识为第四隧道在该第一用户面网元上的隧道端口标识，该第八隧道端口标识为该第四隧道在该第四用户面网元上的隧道端口标识，该第四隧道为该第一用户面网元和该第五用户面网元之间隧道；相应的，该第十消息还包括该第七隧道端口标识；该发送模块，还用于根据该第五用户面网元的标识，向该第五用户面网元发送第十一消息，该第十一消息包括该第八隧道端口标识、以及更新后的应用在该第五用户面网元上的该局域网群组FAR。
第四方面，提供了一种群组通信方法，该方法包括：在第一终端加入组播组的情况下，群组管理功能网元获取第一终端接入的第一用户面网元的标识和第一会话标识，第一会话端口标识为该第一用户面网元上用于第一终端接入的第一会话端口的标识；群组管理功能网元为该组播组创建应用在第一会话端口的出口PDR和出口FAR，以及群组管理功能网元为该组播组创建或更新应用在第一用户面网元上的组播组FAR，组播组FAR用于将该组播组的组播报文复制后转发到指定的出口；出口PDR用于识别组播报文的类型，出口FAR用于对组播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；群组管理功能网元向会话管理网元发送第一消息，该第一消息用于在第一会话端口上配置该出口PDR和出口FAR，以及在第一用户面网元上配置或更新组播组FAR。基于该方案，由于组播组的组播成员加入时，只需要调整(更新或创建)相关联的用户面网元上的组播组FAR，以及调整(创建)相关联的UPF网元上与该组播成员对应的入口PDR、出口PDR和出口FAR，或者调整(创建)相关联的UPF网元上与该组播成员对应的出口PDR和出口FAR即可，组播组内其他组播成员对应的入口PDR、出口PDR和出口FAR不发生改变。从而可以在组播组内的组播成员较多时，避免组播成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于组播成员数量的变化导致的配置工作量。
第五方面，提供了一种群组通信方法，该方法包括包括：第一用户面网元接收来自会话管理网元的第一消息，第一消息包括第一会话端口标识，应用在第一会话端口标识对应的第一会话端口上的出口PDR和出口FAR、以及创建或更新后的应用在第一用户面网元上的组播组转发动作规则FAR，其中，第一会话端口标识为第一用户面网元上用于第一终端接入的第一会话端口的标识；组播组FAR用于将该组播组的组播报文复制后转发到指定的出口；出口PDR用于识别组播报文的类型，出口FAR用于对组播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；第一用户面网元根据第一会话端口标识在第一会话端口上配置出口PDR和出口FAR；以及，第一用户面网元根据创建的应用在第一用户面网元上的组播组FAR，在第一用户面网元上创建组播组FAR；或者，第一用户面网元根据更新后的应用在第一用户面网元上的组播组FAR，更新第一用户面网元上的组播组FAR。其中，第五方面的技术效果可参考 上述第四方面，在此不再赘述。
第六方面，提供了一种群组通信方法，该方法包括包括：在第一终端加入组播组的情况下，会话管理网元接收来自群组管理功能网元的第一消息，该第一消息包括第一终端接入的第一用户面网元的标识，与第一用户面网元的标识对应的第一会话端口标识、应用在第一会话端口标识对应的第一会话端口上的出口PDR和出口FAR、以及创建或更新后的应用在第一用户面网元上的组播组转发动作规则FAR；会话管理网元根据第一用户面网元的标识，向第一用户面网元发送第一会话端口标识、该第一会话端口上的出口PDR和出口FAR、以及创建或更新后的应用在第一用户面网元上的组播组FAR。其中，第六方面的技术效果可参考上述第四方面，在此不再赘述。
第七方面，提供了一种群组管理功能网元，该群组管理功能网元具有实现上述第一方面或第四方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，提供了一种群组管理功能网元，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该群组管理功能网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该群组管理功能网元执行如上述第一方面或第四方面中任一项所述的群组通信方法。
第九方面，提供了一种群组管理功能网元，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第一方面或第四方面中任一项所述的群组通信方法。
第十方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面或第四方面中任一项所述的群组通信方法。
第十一方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面或第四方面中任一项所述的群组通信方法。
第十二方面，提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持群组管理功能网元实现上述第一方面或第四方面中所涉及的功能，例如为局域网群组创建应用在所述第一会话端口上的规则组。在一种可能的设计中，该装置还包括存储器，该存储器，用于保存群组管理功能网元必要的程序指令和数据。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第七方面至第十二方面中任一种设计方式所带来的技术效果可参见上述第一方面或第三方面中不同设计方式所带来的技术效果，此处不再赘述。
第十三方面，提供了一种第一用户面网元，该第一用户面网元具有实现上述第二方面或第五方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十四方面，提供了一种第一用户面网元，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该第一用户面网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该第一用户面网元执行如上述第二方面或第五方面中任一项所述的群组通信方法。
第十五方面，提供了一种第一用户面网元，包括：处理器；所述处理器用于与存 储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第二方面或第五方面中任一项所述的群组通信方法。
第十六方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第二方面或第五方面中任一项所述的群组通信方法。
第十七方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第二方面或第五方面中任一项所述的群组通信方法。
第十八方面，提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持第一用户面网元实现上述第二方面或第五方面中所涉及的功能，例如根据所述第一会话端口标识创建所述第一会话端口，并在所述第一会话端口上配置所述规则组。在一种可能的设计中，该装置还包括存储器，该存储器，用于保存第一用户面网元必要的程序指令和数据。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第十三方面至第十八方面中任一种设计方式所带来的技术效果可参见上述第二方面或第三方面中不同设计方式所带来的技术效果，此处不再赘述。
第十九方面，提供了一种会话管理网元，该会话管理网元具有实现上述第三方面或第六方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第二十方面，提供了一种会话管理网元，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该会话管理网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该会话管理网元执行如上述第三方面或第六方面中任一项所述的群组通信方法。
第二十一方面，提供了一种会话管理网元，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第三方面或第六方面中任一项所述的群组通信方法。
第二十二方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第三方面或第六方面中任一项所述的群组通信方法。
第二十三方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第三方面或第六方面中任一项所述的群组通信方法。
第二十四方面，提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持会话管理网元实现上述第三方面或第六方面中所涉及的功能，例如根据第一用户面网元的标识，确定第一用户面网元。在一种可能的设计中，该装置还包括存储器，该存储器，用于保存会话管理网元必要的程序指令和数据。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第十九方面至第二十四方面中任一种设计方式所带来的技术效果可参见上述第三方面或第三方面中不同设计方式所带来的技术效果，此处不再赘述。
第二十五方面，提供了一种群组通信系统，该群组通信系统包括群组管理功能网元、会话管理功能网元和第一用户面网元。该群组管理功能网元用于执行上述第一方 面或第四方面中，或者本申请实施例提供的方案中由群组管理功能网元执行的步骤。该第一用户面网元用于执行上述第二方面或第五方面中，或者本申请实施例提供的方案中由第一用户面网元执行的步骤。该会话管理网元用于执行上述第三方面或第六方面中，或者本申请实施例提供的方案中由会话管理网元所执行的步骤。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为现有的3GPP TS29.244定义的用户面转发报文的流程示意图；
图2a为本申请实施例提供的广播场景下的通信示意图；
图2b为本申请实施例提供的组播场景下的通信示意图；
图3a为本申请实施例提供的会话端口或隧道端口的分布示意图一；
图3b为本申请实施例提供的会话端口或隧道端口的分布示意图二；
图4为本申请实施例提供的入口和出口示意图；
图5为本申请实施例提供的群组通信方法的思想架构示意图一；
图6为本申请实施例提供的群组FAR的示意图；
图7a为本申请实施例提供的规则组的示意图；
图7b为本申请实施例提供的组播转发树的结构示意图；
图7c为本申请实施例提供的组播场景下UPF网元的配置示意图一；
图8为本申请实施例提供的一种群组通信系统的架构示意图；
图9为本申请实施例提供的一种5G网络架构示意图；
图10为现有的5GLAN服务的用户面架构示意图；
图11为本申请实施例提供的通信设备的结构示意图；
图12为本申请实施例提供的群组通信方法流程示意图一；
图13为本申请实施例提供的广播场景下UPF网元的配置示意图一；
图14为本申请实施例提供的广播场景下UPF网元的配置示意图二；
图15为本申请实施例提供的广播场景下UPF网元的配置示意图三；
图16为本申请实施例提供的群组通信方法流程示意图二；
图17为本申请实施例提供的广播场景下UPF网元的配置示意图四；
图18为本申请实施例提供的广播场景下UPF网元的配置示意图五；
图19为本申请实施例提供的广播场景下UPF网元的配置示意图六；
图20为本申请实施例提供的广播场景下UPF网元的配置示意图七；
图21为本申请实施例提供的广播场景下UPF网元的配置示意图八；
图22为本申请实施例提供的广播场景下UPF网元的配置示意图九；
图23为本申请实施例提供的群组通信方法流程示意图三；
图24为本申请实施例提供的广播场景下UPF网元的配置示意图十；
图25为本申请实施例提供的广播场景下UPF网元的配置示意图十一；
图26为本申请实施例提供的广播场景下UPF网元的配置示意图十二；
图27为本申请实施例提供的广播场景下UPF网元的配置示意图十三；
图28为本申请实施例提供的广播场景下的报文转发示意图；
图29为本申请实施例提供的群组通信方法流程示意图四；
图30为本申请实施例提供的组播场景下UPF网元的配置示意图二；
图31为本申请实施例提供的组播场景下UPF网元的配置示意图三；
图32为本申请实施例提供的组播场景下UPF网元的配置示意图四；
图33为本申请实施例提供的组播场景下UPF网元的配置示意图五；
图34为本申请实施例提供的群组通信方法流程示意图五；
图35为本申请实施例提供的组播场景下UPF网元的配置示意图六；
图36为本申请实施例提供的组播场景下UPF网元的配置示意图七；
图37为本申请实施例提供的组播场景下UPF网元的配置示意图八；
图38为本申请实施例提供的群组通信方法的思想架构示意图二；
图39为本申请实施例提供的群组管理功能网元的结构示意图；
图40为本申请实施例提供的第一用户面网元的结构示意图；
图41为本申请实施例提供的会话管理网元的结构示意图。
具体实施方式
为了方便理解本申请实施例的技术方案，首先给出本申请相关技术的简要介绍如下。
第一，广播：
广播是一对所有的通信方式，在网络中一个LAN(例如可以是5GLAN)对应一个广播域。签约到该LAN的终端可以组成一个LAN群组，其中，签约到该LAN的终端可以称之为LAN群组的终端成员，也就是说，终端是在签约过程中加入LAN群组(可以是加入一个或多个LAN群组)的，相关实现可参考现有的方案，在此不予赘述。其中，LAN群组的终端成员入网(即建立用户面连接，典型的入网方式是终端发起分组数据单元(packet data unit，PDU)会话建立请求,以下实施例均以入网方式为终端发起PDU会话建立请求为例进行说明)之后，该终端成员可以视为已经入网，入网之后的终端成员之间可以相同通信。具体实现可参考本申请下述实施例，在此不再赘述。
其中，LAN群组中已经入网的任何终端都可以作为广播源，发送广播报文；同时可以作为广播成员，接收广播报文。比如，假设LAN群组中已经入网的终端成员包括终端1、终端2、终端3、终端4、终端5和终端6。以终端1作为广播源为例，则对应的通信示意图可以如图2a所示，即终端1发送的广播报文可以分别传输到LAN群组中的终端2、终端3、终端4、终端5和终端6。
其中，本申请实施例中的广播地址可以是目的IP地址为全为1，如255.255.255.255；或者，本申请实施例中的广播地址也可以是目的媒体访问控制(media access control，MAC)地址为全为1，如255.255.255.255，具体可参考现有的广播地址的定义，在此不予赘述。
第二，组播：
本申请实施例中，一个组播源和多个组播成员，可以组成一个组播组(也可以简称组播组)。其中，以组播组地址为目的地址，发送IP报文的信源称为组播源，接收组播数据的组播用户称为组播成员。即组播是有方向的，方向是从组播源到组播成员。组播源和组播成员的角度不可转变，否则属于不同的组播组。比如，假设LAN群组中的终端成员包括终端1、终端2、终端3、终端4、终端5和终端6。以终端1作为组 播源，终端3、终端5和终端6作为组播成员组成一个组播组为例，则对应的通信示意图可以如图2b所示，即终端1发送的组播报文可以分别传输到组播组中的终端2、终端5和终端6。
其中，本申请实施例中，组播源是由开放式系统互联(open system interconnection，OSI)模型的应用层确定的，终端若要接收组播数据，可以显式地通过发送因特网组管理协议(internet group management protocol，IGMP)加入(join)消息到网络中，网络记录该终端加入一个组播组之后，才会向其转发该组播源发出的组播数据，也就是说，组播成员是动态加入组播组的，具体的加入过程可参考后续方法实施例，在此不再赘述。
其中，本申请实施例中的组播地址可以是由互联网数字分配机构(the internet assigned numbers authority，IANA)分配的组播IP版本4(IP version 4，IPv4)地址，范围在224.0.0.0～239.255.255.255区间内；或者，本申请实施例中的组播地址也可以是48bit中高48bit的最后一位恒定为1的组播MAC地址，或者，本申请实施例中的组播地址也可以是其他地址，具体可参考现有的组播地址的定义，在此不予赘述。
第三，群组：
本申请实施例中的群组可以包括上述的LAN群组和组播组，在此统一说明，以下不再赘述。
第四，用户面网元上的会话端口与隧道端口：
本申请实施例中，用户面网元上的会话端口是一个逻辑端口，具体可以是在终端建立PDU会话时，用户面网元根据会话管理网元或者用户面网元的分配的会话端口标识建立的核心网隧道端口，也可以理解为终端的PDU会话在核心网侧的锚点。其功能是用于将终端锚定在该用户面网元(即连接一个终端)，从而通过该会话端口接收该终端发送的报文以及通过该会话端口向该终端发送报文。示例性的，这里的会话端口标识例如可以是TEID。
示例性的，如图3a所示，在终端1建立PDU会话时，假设终端1接入的用户面网元为用户面网元1，则用户面网元1可以根据会话管理网元或者用户面网元1分配的会话端口标识1建立会话端口1。或者，在终端2建立PDU会话时，假设终端2接入的用户面网元为用户面网元1，则用户面网元1可以根据会话管理网元或者用户面网元1分配的会话端口标识2建立会话端口2。或者，在终端3建立PDU会话时，假设终端3接入的用户面网元为用户面网元1，则用户面网元1可以根据会话管理网元或者用户面网元1分配的会话端口标识3建立会话端口3。或者，在终端n建立PDU会话时，假设终端n接入的用户面网元为用户面网元1，则用户面网元1可以根据会话管理网元或者用户面网元1分配的会话端口标识n建立会话端口n，等。
本申请实施例中，用户面网元上的隧道端口是一个逻辑端口，具体可以是在一个LAN群组内的某个终端建立PDU会话时，该终端接入的用户面网元与该LAN群组内的其他终端接入的用户面网元之间建立第一隧道之后，该终端接入的用户面网元与该群组内的其他终端接入的用户面网元分别根据会话管理网元分配的第一隧道端口标识和第二隧道端口标识创建的LAN群组粒度的隧道，其中，第一隧道标识为第一隧道在该终端接入的用户面网元侧的隧道端口，第二隧道标识为第一隧道在该群组内的其他 终端接入的用户面网元侧的隧道端口。该隧道端口的功能是用于通过该隧道端口接收来自连接的用户面网元的该LAN群组的报文，并且通过该隧道端口向连接的用户面网元发送该LAN群组的报文。示例性的，这里的第一隧道端口标识例如可以是TEID1，第二隧道端口标识例如可以是TEID2。
示例性的，如图3b所示，假设LAN群组内的终端入网的先后顺序分别为终端3、终端4、终端1、终端2和终端5。则在终端3建立PDU会话时，假设终端3接入的用户面网元为用户面网元2，则用户面网元2可以根据会话管理网元或者用户面网元2分配的会话端口标识3建立会话端口3。在终端4建立PDU会话时，假设终端4接入的用户面网元为用户面网元2，则用户面网元2可以根据会话管理网元或者用户面网元2分配的会话端口标识4建立会话端口4。在终端1建立PDU会话时，假设终端1接入的用户面网元为用户面网元1，则用户面网元1可以根据会话管理网元或者用户面网元1分配的会话端口标识1建立会话端口1。同时，由于已经存在LAN群组内的终端3和终端4接入用户面网元2，因此会话管理网元需要发起在用户面网元1和用户面网元2之间建立隧道1，进而用户面网元1可以根据会话管理网元分配的隧道1在用户面网元1侧的隧道端口标识1建立隧道端口1，用户面网元2可以根据会话管理网元分配的隧道1在用户面网元2侧的隧道端口标识2建立隧道端口2。在终端2建立PDU会话时，假设终端2接入的用户面网元为用户面网元1，则虽然已经存在LAN群组内的终端3和终端4接入用户面网元2，但是由于终端1建立PDU会话时已经在用户面网元1建立隧道端口1，在用户面网元2建立隧道端口2，通过隧道端口1和隧道端口2可以接收或发送该LAN群组的广播报文或者LAN群组下的某个组播组的组播报文，因此此时用户面网元1仅需要根据会话管理网元或者用户面网元1分配的会话端口标识2建立会话端口2即可。在终端5建立PDU会话时，假设终端5接入的用户面网元为用户面网元3，则用户面网元3可以根据会话管理网元或者用户面网元3分配的会话端口标识5建立会话端口5。同时，由于已经存在LAN群组内的终端3和终端4接入用户面网元2、以及LAN群组内的终端1和终端2接入用户面网元1，因此会话管理网元需要发起在用户面网元3和用户面网元2之间建立隧道2，进而用户面网元3可以根据会话管理网元分配的隧道2在用户面网元3侧的隧道端口标识4建立隧道端口4，用户面网元2可以根据会话管理网元分配的隧道2在用户面网元2侧的隧道端口标识3建立隧道端口3。
需要说明的是，这里示例性的以终端5建立PDU会话时，在用户面网元2和用户面网元3之间建立隧道2为例进行说明。当然，终端5建立PDU会话时，也可以在用户面网元1和用户面网元3之间建立隧道3。但是为了防止广播风暴，不需要同时建立隧道2和隧道3。比如，在建立隧道2之后，终端1发送的报文可以通过用户面网元2的转发至用户面网元3，从而可以发送给终端5，在此统一说明，以下不再赘述。
第五，用户面网元上的成员端口
本申请实施中，用户面网元上的成员端口是指一个群组在用户面网元上的端口集合，包括上述的会话端口或隧道端口中的至少一个。成员端口的功能和角色是相同的，对于一个LAN群组，一个用户面网元上所有可以接收或发送该LAN群组的广播报文的端口都属于成员端口；对于一个组播组，一个用户面网元上所有发送该组播组的组 播报文的端口都属于成员端口。其中，与成员端口连接的终端或用户面网元可以称之为成员。
示例性的，假设群组内的所有终端接入同一个用户面网元，则对于该群组，该用户面网元上的成员端口仅包括该群组的会话端口，不包括该群组的隧道端口。比如，如图3a所示，假设一个群组内包括终端1、终端2、终端3、……、终端n共n个终端，这n个终端均接入用户面网元1，则在广播场景下，由于任何终端都可以作为广播源，同时可以作为广播成员，因此，用户面网元1上包括会话端口1、会话端口2、会话端口3、……、会话端口n共n个成员端口，用户面网元1上的成员包括终端1、终端2、终端3、……、终端n共n个成员。或者，在组播场景下，由于组播是有方向的，方向是从组播源到组播成员，因此，假设终端1为组播源，则用户面网元1上包括会话端口2、会话端口3、……、会话端口n共(n-1)个成员端口，用户面网元1上的成员包括终端2、终端3、……、终端n共(n-1)个成员。
或者，如图3b所示，假设一个LAN群组内包括终端1、终端2、终端3和终端4和终端5共5个终端，其中，终端1和终端2接入用户面网元1，终端3和终端4接入用户面网元2，终端5接入用户面网元3。则在广播场景下，由于任何终端都可以作为广播源，同时可以作为广播成员，因此，用户面网元1上的成员端口包括会话端口1、会话端口2和隧道端口1共3个成员端口,用户面网元1上的成员包括终端1、终端2和用户面网元2共3个成员。用户面网元2上的成员端口包括隧道端口2、隧道端口3、会话端口3和会话端口4共4个成员端口，用户面网元2上的成员包括用户面网元1、用户面网元3、终端3和终端4共4个成员。用户面网元3上的成员端口包括隧道端口4和会话端口5共2个成员端口，用户面网元3上的成员包括用户面网元2和终端5共2个成员。
或者，如图3b所示，假设一个组播组包括终端1，终端2和终端5。其中，终端1作为组播源，终端2和终端5作为组播成员，则在组播场景下，由于组播是有方向的，方向是从组播源到组播成员，因此，用户面网元1上的成员端口包括会话端口2和隧道端口1共2个成员端口。用户面网元1上的成员包括终端2和用户面网元2共2个成员。用户面网元2上的成员端口包括隧道端口3、会话端口3和会话端口4共3个成员端口，用户面网元2上的成员包括用户面网元3、终端3和终端4共3个成员。用户面网元3上的成员端口包括会话端口5共1个成员端口，用户面网元3上的成员包括终端5共1个成员。
综上，本申请实施例中，在一个用户面网元上，某个LAN群组的成员端口的数量与该LAN群组在该用户面网元上对应的所有会话端口和隧道端口的总和相等；而某个组播组的成员端口的数量等于该组播组在该用户面网元上的所有发送该组播组的组播报文的端口的数量。
第六，入口和出口：
本申请实施例中的入口，是指用户面网元上接收报文的端口，出口是指用户面网元上发送报文的端口。入口和出口同属于一个逻辑端口的两个方向，这里的逻辑端口可以是上述的会话端口或隧道端口。此外，由上述成员端口的定义可知，在组播场景下，这里的出口同时也是成员端口，在此统一说明，以下不再赘述。
示例性的，在广播场景下，以上述图3b中的用户面网元1为例，则入口可以是会话端口1，出口可以是会话端口2和隧道端口1；或者，入口可以是会话端口2，出口可以是会话端口1和隧道端口1；或者，入口可以是隧道端口1，出口可以是会话端口1和会话端口2。也就是说，广播场景下，一个端口可以既作为入口，也可以作为出口。
或者，在组播场景下，假设终端1为组播源，终端2和终端5作为组播成员，则以上述图3b中的用户面网元1为例，则入口可以是会话端口1，出口可以是会话端口2和隧道端口1；或者，以上述图3b中的用户面网元2为例，则入口可以是隧道端口2，出口可以是隧道端口3；或者，以上述图3b中的用户面网元3为例，则入口可以是隧道端口4，出口可以是会话端口5。
需要说明的是，图4仅是为了方便说明，将入口和出口分开进行示意。当然，入口和出口可以对应同一个物理接口，也可以对应不同的物理接口，本申请实施例对此不作具体限定。以下各实施例中类似，在此统一说明，以下不再赘述。
第七，上游端口和下游端口：
本申请实施例中的上游端口和下游端口是为了方便群组通信场景下的描述而引入的。其中，组播场景下，上游端口可以对应上述的入口，与组播源直接或间接相连，下游端口可以对应上述的出口，与组播成员直接或间接相连，在此统一说明，以下不再赘述。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
首先，给出本申请实施例提供的群组通信方法、设备及系统的主旨思想。
如图5所示，为本申请实施例提供的群组通信方法、设备及系统的主旨思想的框架示意图。本申请实施例中，将用户面网元上的入口(inress)功能简化，在用户面网元上新增群组转发功能和出口(egress)功能。
其中，用户面网元上的入口功能包括通过应用在会话端口或隧道端口上的入口PDR识别报文属于某个群组的广播报文或组播报文。比如，图5中应用在会话端口3 或隧道端口3的入口PDR包括入口PDR1、入口PDR2、......、入口PDRn。通过入口PDR1可以识别属于群组1的广播报文，通过入口PDR2可以识别属于群组2的广播报文，通过入口PDRn可以识别属于群组2的组播报文等。其中，通过入口PDR识别属于某个群组的广播报文或组播报文的功能将在后续实施例中详细阐述，在此不再赘述。
其中，用户面网元上的群组转发功能通过群组FAR(group FAR)实现。入口PDR中包括对应群组的群组FAR的标识，即入口PDR指向对应群组的群组FAR。如图5中的入口PDR2指向群组FAR2。本申请实施例中的群组FAR包括以下字段：
第一，群组FAR的标识字段，该群组FAR的标识例如可以是群组标识，该群组标识例如可以是虚拟本地局域网(virtual LAN，VLAN)标识或者组播组标识等。
第二，群组类型字段，该群组类型例如可以是广播或者组播。
第三，转发动作桶(forwarding action buckets)字段，这里的转发动作桶可以理解为转发动作(forwarding action rule，FA)的集合。比如，如图6所示，群组FAR的标识为1，类型为广播的群组FAR中可以包括FA1、FA2、……、FAm，m为正整数。其中，一个群组的群组FAR中FA的数量与群组FAR所在的用户面网元上该群组的出口的数量相同。如图6中，群组FAR中的m个FA对应m个出口，分别为出口1、出口2、……、出口m。其中，每个FA的主要作用是指定对应的出口，也就是报文从哪个出口发送出去。
需要说明的是，图6中群组FAR中的多个FA仅是为了便于理解，将FAR的规则分解后的一种示例，在实现过程中，也可能不需要将群组FAR的规则进行拆分后分别与图6中的FA对应，在此统一说明，以下不再赘述。
本申请实施例中，群组FAR的处理逻辑是，根据群组FAR所在的用户面网元上该群组的出口的数量，将报文复制成同等数量的多份后，转发到群组FAR指定的出口，即所有成员端口。当然，若群组FAR中包括多个FA，则群组FAR的处理逻辑是，根据FA的数量，将报文复制成等同FA数量的多份，每个FA处理一份报文的拷贝副本。处理结果包括将报文转发到该FA指定的出口。其中，在群组FAR进行报文转发过程中，如果检查发现群组FAR指定的出口是报文的入口(即接收报文的端口与发送报文的端口是同一个端口，比如端口标识相同)，为了避免广播风暴，则默认将其丢弃。综上，通过群组FAR可以完成群组相关的广播和组播通信。
其中，用户面网元上的出口功能通过应用在会话端口或隧道端口中的出口PDR和出口FAR实现。出口PDR中包括出口FAR的标识，即出口PDR指向出口FAR。如图5或图6中的出口PDR11指向出口FAR11，出口PDR12指向出口FAR12等，在此不再一一举例说明。其中，出口PDR用于识别报文的类型，如基于IP报文的差分服务代码点(differentiated services code point，DSCP)字段，或以太网帧的802.1p比特识别报文的优先级，具体的实现方式将在后续方法实施例中详细阐述，在此不再赘述。其中，该报文的类型例如可以是通过报文对应的业务优先级进行划分的，如业务优先级共分为八个等级，分别为第一业务优先级，第二业务优先级，……，第八业务优先级。此时，出口PDR1可以用于识别第一业务优先级的报文，出口PDR2可以用于识别第二业务优先级的报文，出口PDR3可以用于识别第三业务优先级的报文。出口FAR用于对报文添加外层消息头(outer header creation)以及进行传输层标记(transport level  marking)之后，将报文从出口PDR所在的端口转发出去。比如，当出口PDR所在的端口是会话端口时，可以为报文添加通用分组无线服务(General packet radio service，GPRS)隧道协议(GPRS tunnelling protocol，GTP)头，以及在GTP头设置隧道端点标识(tunnel endpoint identity，TEID)和服务质量(quality of service，QoS)流标识(QoS flow identity，QFI)之后将报文从该出口PDR所在的会话端口发送给群组内的终端。或者，当出口PDR所在的端口是隧道端口(tunnel endpoint)时，可以为报文添加隧道头，以及在隧道头设置隧道端口标识和QoS标记之后将报文从该出口PDR所在的隧道端口发送给其他用户面网元等，本申请实施例对此不作具体限定。
需要说明的是，图5所示的实施例以报文在会话端口1或隧道端口1匹配到出口PDR12，在会话端口2或隧道端口2匹配到出口PDR22为例进行示意，因此报文分别从出口PDR12所指示的出口FAR12，以及出口PDR22所指示的出口FAR22发送给其他终端或用户面网元。
需要说明的是，图5所示的实施例仅是示例性的以一个终端或用户面网元发出的报文为例进行说明。当然，在广播场景下，图5中出口FAR连接的终端或用户面网元也可以如图5中入口PDR连接的终端或用户面网元一样，在与其连接的用户面网元上分别包括上述入口功能，群组转发功能和出口(egress)功能，具体可参考上述描述，在此不再一一举例说明。
基于上述主旨思想，在群组内的终端成员变化时(如LAN群组的终端成员入网，组播组的组播成员加入，LAN群组的终端成员离网，组播组的组播成员离开，LAN群组中已经入网的终端成员移动，或者组播组的组播成员移动)，只需要调整(创建、更新或删除)相关联的用户面网元上该群组的群组FAR，以及调整(创建、更新或删除)相关联的用户面网元上与该终端成员关联的出口PDR与出口FAR，或者与该终端成员关联的入口PDR、出口PDR和出口FAR即可，群组内其他终端成员所关联的入口PDR、出口PDR和出口FAR不发生改变。具体实现方案将参考后续方法实施例，在此不再赘述。这样，在群组内的终端成员较多时，可以避免终端成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于终端成员数量的变化导致的配置工作量。
然后，给出本申请下述实施例中规则组的简要说明。
本申请实施例中的规则组适用于群组通信为广播(即群组为LAN群组)的场景下。
其中，如上所述，由于LAN群组中已经入网的任何终端都可以作为广播源，同时可以作为广播成员，因此用户面网元上该LAN群组的每个成员端口上均配置有包括入口PDR、出口PDR和出口FAR在内的规则组。如图7a的(a)中，会话端口1上配置有包括入口PDR1、出口PDR1和出口FAR1在内的规则组1，隧道端口2上配置有包括入口PDR2、出口PDR2和出口FAR2在内的规则组2。如图5部分所述，入口PDR属于入口部分，出口PDR和出口FAR属于出口部分，因此，用户面网元上该LAN群组的每个成员端口上既可以接收报文，也可以发送报文。其中，入口PDR、出口PDR和出口FAR的相关说明可参考上述实施例部分，在此不再赘述。用户面网元上LAN群组信息(包括规则组和上述的LAN群组FAR)的具体配置方式以及LAN群组广播报文的转发方式将在后续方法实施例部分详细阐述，在此不再赘述。
需要说明的是，本申请实施例中，若一个用户面网元上包括该群组的多个成员端口，则每个成员端口中包括的入口PDR均指向该用户面网元上该群组的群组FAR。如图7a的(a)中，会话端口1上的入口PDR1和隧道端口2上的入口PDR2指向同一个LAN群组FAR1。其中，入口PDR1用于识别来自某个终端的属于某个该LAN群组的广播报文，入口PDR2用于识别来自某个用户面网元的属于该LAN群组的广播报文。在此统一说明，以下不再赘述。
需要说明的是，图7a的(a)中仅是示例性的给出了一个应用在用户面网元的会话端口上的规则组，以及一个应用在用户面网元的隧道端口上的规则组。当然，由于一个用户面网元上可能存在不同的终端接入，且每个终端可能对应一个或多个会话，所以可能一个用户面网元上可能包括多个会话端口或多个隧道端口。此外，由于一个终端可以接入不同的群组，因此每个会话端口可能包括多个上述规则组1，每个隧道端口上可能配置多个规则组2。比如，图5中的会话端口3或隧道端口3上配置多个入口PDR，这个多个入口PDR分别归属于多个规则组1，在此统一说明，以下不再赘述。
需要说明的是，为简化附图，以下附图均不在规则组中用虚线示意出哪是出口，哪是入口，比如如图7a的(b)所示。可以理解的是，指向入口PDR1的箭头实际上表征的是指向入口PDR1所在的入口位置，指向入口PDR2的箭头实际上表征的是指向入口PDR2所在的入口位置，指向出口PDR1的箭头实际上表征的是指向出口PDR1所在的出口位置，指向出口PDR2的箭头实际上表征的是指向出口PDR2所在的出口位置。这里的入口中可能包括多个入口PDR，要进行匹配之后才能确定对应哪个入口PDR(即上述的入口PDR识别报文属于某个群组的广播报文或组播报文)。同理，出口中可能包括多个出口PDR，要进行匹配之后才能确定对应哪个入口PDR(即上述的出口PDR用于识别报文的类型)，在此统一说明，以下不再赘述。
然后，给出本申请下述实施例中组播转发树的简要说明。
本申请实施例中的组播转发树适用于群组通信为组播(即群组为组播组)的场景下。
如图7b所示，为本申请实施例提供的一种组播转发树的结构示意图。该组播转发树包括组播源、组播成员(一个或多个)、以及组播源与组播成员之间的用户面网元(一个或多个)。比如，图7b中的组播源例如可以为终端1；组播成员例如可以是终端2、终端3和终端4；终端1和终端2之间的用户面网元例如可以是用户面网元1，终端1和终端3之间的用户面网元例如从上游方向到下游方向依次是用户面网元1和用户面网元2，终端1和终端4之间的用户面网元例如从上游方向到下游方向依次是用户面网元1和用户面网元2。其中，这里的上游方向是指组播源所在的方向，下游方向是指组播成员所在的方向，例如用户面网元1可以视为用户面网元2的上游用户面网元，用户面网元2可以视为用户面网元1的下游用户面网元，在此统一说明，以下不再赘述。
此外，结合上述上游方向和下游方向的定义，在图7b中，终端1可以作为用户面网元1的上游成员，用户面网元1作为用户面网元2和终端2的上游成员，用户面网元2可以作为终端3和终端4的上游成员。反之，终端3和终端4可以作为用户面网 元2的下游成员，用户面网元2和终端2可以作为用户面网元1的下游成员，用户面网元1可以作为终端1的下游成员，在此统一说明，以下不再赘述。
如上所述，由于组播是有方向的，方向是从组播源到组播成员。因此，对于图7b中的用户面网元1和用户面网元2，需要在每个用户面网元上配置组播组FAR，以及在各自的上游端口配置入口PDR，各自的下游端口上配置出口PDR和出口FAR，结果如图7c所示。即在用户面网元1和用户面网元2上分别配置组播组FAR1和组播组FAR2；以及，在用户面网元1的上游端口1上配置入口PDR1，在用户面网元1的下游端口1上配置出口PDR1和出口FAR1，在用户面网元1的下游端口2上配置出口PDR2和出口FAR2；以及，在用户面网元2的上游端口2上配置入口PDR2，在用户面网元2的下游端口3上配置出口PDR3和出口FAR3，在用户面网元2的下游端口4上配置出口PDR4和出口FAR4。其中，入口PDR、出口PDR和出口FAR的相关说明可参考上述实施例部分，在此不再赘述。用户面网元上组播组信息的具体配置方式以及组播组的组播报文的转发方式将在后续方法实施例部分详细阐述，在此不再赘述。
如图8所示，为本申请实施例提供的一种群组通信系统80，该群组通信系统80包括群组管理功能网元，与群组管理功能网元连接的一个或多个会话管理网元(如图8中的第一会话管理网元和第二会话管理网元)，以及与每个会话管理网元连接的一个或多个用户面网元(如图8中与第一会话管理网元连接的第一用户面网元、第二用户面网元和第三用户面网元，与第二会话管理网元连接的第四用户面网元)。
其中，群组管理功能网元，用于在群组内的终端成员变化时(如LAN群组的终端成员入网，组播组的组播成员加入，LAN群组的终端成员离网，组播组的组播成员离开，LAN群组中已经入网的终端成员移动，或者组播组的组播成员移动)，通过相关联的会话管理网元调整(创建、更新或删除)相关联的用户面网元上该群组的群组FAR，以及调整(创建、更新或删除)相关联的用户面网元上与该终端成员关联的出口PDR与出口FAR，或者与该终端成员关联的入口PDR、出口PDR和出口FAR。进而，在进行群组通信时，可以通过用户面网元上的入口PDR、出口PDR、出口FAR和群组FAR实现组播或广播通信，具体实现方案将参考后续方法实施例，在此不再赘述。
基于上述群组通信系统，可以在群组内的终端成员较多时，避免终端成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于终端成员数量的变化导致的配置工作量。
可选的，图8所示的群组通信系统可以应用于目前的5G网络或者未来的其他网络，本申请实施例对此不作具体限定。
示例性的，如图9所示，若图8所示的群组通信系统应用于目前的5G网络，则图8中的群组管理功能网元所对应的网元或者实体可以为5G网络架构中的群组管理功能(group management function，GMF)网元；图8中的会话管理网元(如第一会话管理网元或第二会话管理网元)所对应的网元或者实体可以为5G网络架构中的会话管理功能(session management function，SMF)网元；图8中的用户面网元(如第一用户面网元、第二用户面网元、第三用户面网元或第四用户面网元)所对应的网元或者实体可以为5G网络架构中的UPF网元。上述的本地局域网可以为5GLAN。可选的，从表达方式上看，本申请实施例中，5GLAN也可以称为LAN，LAN-类型服务(type  service)，LAN-虚拟网络(virtual network，VN),5GLAN-type service，5GLAN-VN，5GLAN群组(5GLAN group)，或者LAN Group等，本申请实施例5GLAN的名字不作具体限定。
其中，上述的GMF网元可以是5G网络架构中新增的一个网元，其功能为5GLAN群组管理，如基于终端的请求动态创建、修改、或删除一个群组。此外，上述的GMF网元的功能还可以包括管理用户面路径，设置用户面转发规则，以及实现群组间隔离功能等。当然，管理用户面路径，以及实现群组间隔离的功能也可以是通过新增一个路径管理功能(path management function，PMF)网元来完成，本申请实施例对此不作具体限定。本申请实施例以GMF网元的功能还可以包括管理用户面路径，以及实现群组间隔离的功能等为例进行说明。
此外，如图9所示，目前的5G网络还可以包括接入设备、接入和移动性管理功能(core access and mobility management function，AMF)网元、用户面功能(user plane function，UPF)网元、认证服务器功能(authentication server function，AUSF)网元、网络切片选择功能(network slice selection function，NSSF)网元、网络开放功能(network exposure function，NEF)网元、网络功能存储功能(network exposure function Repository Function，NRF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(Unified Data Management，UDM)网元以及应用功能(application function，AF)网元等，本申请实施例对此不作具体限定。
其中，如图9所示，终端通过接入设备接入5G网络，终端通过下一代网络(next generation，N)1接口(简称N1)与AMF网元通信；接入设备通过N2接口(简称N2)与AMF网元通信；接入设备通过N3接口(简称N3)与UPF网元通信；SMF网元通过N4接口(简称N4)与UPF网元通信；UPF网元通过N6接口(简称N6)接入数据网络。此外，图9所示的AUSF网元、AMF网元、SMF网元、NSSF网元、NEF网元、NRF网元、PCF网元、UDM网元或者AF网元等控制面网元也可以采用服务化接口进行交互。比如，AUSF网元对外提供的服务化接口可以为Nausf；AMF网元对外提供的服务化接口可以为Namf；SMF网元对外提供的服务化接口可以为Nsmf；NSSG网元对外提供的服务化接口可以为Nnssf；NEF网元对外提供的服务化接口可以为Nnef；NRF网元对外提供的服务化接口可以为Nnrf；PCF网元对外提供的服务化接口可以为Npcf；UDM网元对外提供的服务化接口可以为Nudm；AF网元对外提供的服务化接口可以为Naf。相关描述可以参考23501标准中的5G系统架构(5G system architecture)图，在此不予赘述。此外，LAN控制器对外提供的服务化接口可以为Nlan。
需要说明的是，图9所示的5G网络架构中，每个网元仅是示例性的示意出一个。在实际的5G网络部署中，每个网元可能会部署多个。比如，5G网络中可能部署多个SMF网元或者多个UPF网元，不同的SMF网元之间可以通过N16接口(简称N16)通信，或者通过AMF网元的转发进行通信，其中，AMF网元与SMF网元之间的接口为N11接口(简称N11)，AMF网元之间的接口为N14(简称N14)；不同的UPF网元之间可以通过N9接口(简称N9)或者Nx接口(简称Nx)通信。比如，上述的第一会话管理网元可以对应SMF1网元，上述的第二会话管理网元可以对应SMF2网元，SMF1网元和SMF2网元之间可以通过N16通信或者通过AMF网元的转发进行通 信。或者，比如，上述的第一用户面网元可以对应UPF1网元，上述的第二用户面网元可以对应UPF2网元，UPF1网元和UPF2网元之间可以通过N9或者Nx通信。
图10所示为现有的5GLAN服务的用户面架构示意图。其中，终端建立到提供5GLAN服务的UPF网元的会话，从而接入到提供5GLAN服务的UPF网元。如上所述，提供5GLAN服务的UPF网元可以通过N6与数据网络中现存的LAN互通，例如和LAN中的个人计算机(personal computer，PC)通信；或者，提供5GLAN服务的UPF网元也可以通过内部UPF网元与UPF网元之间的连接关联不同终端的会话，实现私有通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中所涉及到的终端(terminal)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端、用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)或者中继用户设备等。其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。为方便描述，本申请中，上面提到的设备统称为终端。
可选的，本申请实施例中所涉及的接入设备(包括上述的第一接入设备或第二接入设备)指的是接入核心网的设备，例如可以是基站，宽带网络业务网关(broadband network gateway，BNG)，汇聚交换机，非第三代合作伙伴计划(3rd generation partnership project，3GPP)接入设备等。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。
可选的，本申请实施例图8中的群组管理功能网元、会话管理网元(如第一会话管理网元或第二会话管理网元)或用户面网元(如第一用户面网元、第二用户面网元、第三用户面网元或第四用户面网元)可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
例如，本申请实施例图8中的群组管理功能网元、会话管理网元或用户面网元可以通过图11中的通信设备来实现。图11所示为本申请实施例提供的通信设备的硬件结构示意图。该通信设备1100包括处理器1101，通信线路1102，存储器1103以及至少一个通信接口(图11中仅是示例性的以包括通信接口1104为例进行说明)。
处理器1101可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路1102可包括一通路，在上述组件之间传送信息。
通信接口1104，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area  networks，WLAN)等。
存储器1103可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路1102与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器1103用于存储执行本申请方案的计算机执行指令，并由处理器1101来控制执行。处理器1101用于执行存储器1103中存储的计算机执行指令，从而实现本申请下述实施例提供的本地局域网通信方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器1101可以包括一个或多个CPU，例如图11中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备1100可以包括多个处理器，例如图11中的处理器1101和处理器1107。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，通信设备1100还可以包括输出设备1105和输入设备1106。输出设备1105和处理器1101通信，可以以多种方式来显示信息。例如，输出设备1105可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备1106和处理器1101通信，可以以多种方式接收用户的输入。例如，输入设备1106可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信设备1100可以是一个通用设备或者是一个专用设备。在具体实现中，通信设备1100可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备或有图11中类似结构的设备。本申请实施例不限定通信设备1100的类型。
下面将结合图1至图11对本申请实施例提供的群组通信方法进行具体阐述。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
首先，以图8所示的群组通信系统应用于如图9所示的5G网络，群组管理功能网元为GMF网元，会话管理网元为SMF网元，用户面网元为UPF网元(如第一用户面网元为UPF1网元，第二用户面网元为UPF2网元)，5GLAN群组的终端成员入网的场景为例，如图12所示，为本申请实施例提供的一种群组通信方法，该群组通信方 法包括如下步骤：
S1201、第一终端通过接入设备向AMF网元发送PDU会话建立请求(PDU session establishment request)消息。相应的，AMF网元接收来自第一终端的PDU会话建立请求消息。该PDU会话建立请求消息用于请求建立第一会话(也可以称之为第一PDU会话，以下简称第一会话)。
其中，该PDU会话建立请求消息中包括第一终端的标识和5GLAN ID，该5GLAN ID为5GLAN群组的标识，用于指示第一终端接入5GLAN群组。
可选的，本申请实施例中，第一终端的标识例如可以是第一终端的用户永久标识符(subscription permanent identifier，SUPI)，或通用公共用户标识符(generic public subscription identity，GPSI)等，本申请实施例对此不作具体限定。该说明也可以类似的适用于本申请广播场景下的其他实施例中的其他终端。比如，下述终端2的标识可以是终端2的SUPI或GPSI，在此统一说明，以下不再赘述。
可选的，该PDU会话建立请求还可以携带第一会话的会话标识，具体可参考现有的实现方式，本申请实施例对此不作具体限定。本申请实施例示例性的以该PDU会话建立请求不携带第一会话的会话标识为例进行说明。
S1202、AMF网元为第一终端选择SMF网元之后，向SMF网元发送PDU会话创建会话管理(session management，SM)上下文请求(PDU session create SM context)消息。相应的，SMF网元接收来自AMF网元的PDU会话创建SM上下文消息。
其中，PDU会话创建SM上下文求消息包括上述第一终端的标识和5GLAN ID。
S1203、SMF网元根据5GLAN ID获知第一终端需要接入5GLAN群组，进而向GMF网元发送5GLAN服务请求(5GLAN service request)消息。相应的，GMF网元接收来自SMF网元的5GLAN服务请求消息。
其中，该5GLAN服务请求消息包括第一终端的标识和5GLAN ID，用于第一终端请求接入5GLAN ID对应的5GLAN群组。
S1204、GMF网元根据5GLAN服务请求消息，获知第一终端请求接入5GLAN ID对应的5GLAN群组，进而获取5GLAN ID对应的5GLAN群组的上下文信息。
可选的，GMF网元可以根据本地保存的或者核心网中其他网元(如UDM)保存的签约信息，判断所述第一终端是否具有接入所述5GLAN ID对应的5GLAN群组的权限。当确定所述第一终端不具有接入所述5GLAN ID对应的5GLAN群组的权限时，所述GMF网元可以直接拒绝5GLAN服务请求消息。
可选的，本申请实施例中，GMF网元获取5GLAN ID对应的5GLAN群组的上下文信息例如可以是：建立5GLAN ID对应的5GLAN群组的上下文信息，或者读取GMF网元上存储的5GLAN ID对应的5GLAN群组的上下文信息。比如，在第一终端为第一个接入该5GLAN群组的终端的情况下，GMF网元需要根据从UDM网元获取的或者GMF网元上存储的5GLAN ID对应的5GLAN签约信息，建立5GLAN ID对应的5GLAN群组的上下文信息；或者，比如，在第一终端请求接入该5GLAN ID对应5GLAN群组时，已经存在其他终端接入该5GLAN群组的情况下，GMF网元可以读取GMF网元上存储的5GLAN ID对应的5GLAN群组的上下文信息。
可选的，本申请实施例中，5GLAN群组的上下文信息中可以包括5GLAN群组的 终端成员列表(list)中当前已经接入该5GLAN群组的终端的标识、已经接入该5GLAN群组的终端所接入的UPF网元的标识，以及每个终端在接入的用户面网元上的会话端口标识。
其中，该5GLAN群组的终端成员列表中包括一个或多个签约到该5GLAN群组的终端。示例性的，假设5GLAN群组的标识为5GLAN ID1，则该5GLAN群组的终端成员列表可以如表一所示，包括与5GLAN ID1对应的多个终端的标识。
表一
Figure PCTCN2019119475-appb-000001
需要说明的是，表一仅是一种示例性的表格存储形式，还可能存在其他的表格存储形式或者非表格的存储形式。比如，如表二所示，终端的标识与5GLAN群组的标识一一对应存储，本申请实施例对于对应关系的存储形式不作具体限定。该说明适用于本申请所有实施例，在此统一说明，以下不再赘述。
表二
5GLAN ID 终端标识
5GLAN ID1 终端1的标识
5GLAN ID1 终端2的标识
5GLAN ID1 终端3的标识
5GLAN ID1 ……
5GLAN ID1 终端n的标识
需要说明的是，本申请实施例中，5GLAN群组的终端成员列表中已经接入该5GLAN群组的终端可以视为该5GLAN群组中已经入网的终端，5GLAN群组的终端成员列表中未接入该5GLAN群组的终端可以视为该5GLAN群组中未入网(或者称之为离网)的终端，该说明适用于本申请所有实施例，在此统一说明，以下不再赘述。
此外，需要说明的是，本申请实施例中的入网也可以理解为上线，离网也可以理解为下线，本申请实施例对此不作具体限定。
示例性的，假设在第一终端入网之前，上述表一或表二中的终端5已经入网，则上述5GLAN群组的上下文信息可以如表三所示；或者，假设在第一终端入网之前，上述表一或表二中的终端5和终端2已经入网，则上述5GLAN群组的上下文信息可以如表四所示。其中，表三或表四中包括已经接入该5GLAN群组的终端的标识、已经接入该5GLAN群组的终端所接入的UPF网元的标识，以及每个终端在接入的用户面网元上的会话端口标识。
表三
Figure PCTCN2019119475-appb-000002
表四
Figure PCTCN2019119475-appb-000003
当然，本申请实施例中，若第一终端为5GLAN群组的终端成员列表中第一个请求接入该5GLAN群组的终端，即在第一终端入网之前，该5GLAN群组的终端成员列表中还没有入网的终端，则此时GMF网元上还没有该5GLAN群组的上下文信息，在此统一说明，以下不再赘述。
可选的，本申请实施例中，5GLAN群组的上下文信息中还可能还包括已经入网的终端所接入的UPF网元上的成员列表以及每个成员对应的成员端口标识，该UPF网元上的成员可能是接入的终端，也可能是已经入网的终端所选择的其他UPF网元，本申请实施例对此不作具体限定。示例性的，假设5GLAN群组的标识为5GLAN ID1，则5GLAN群组的标识、已经入网的终端所接入的UPF网元的标识、以及UPF网元上的成员列表以及每个成员对应的成员端口标识的对应关系可以如表五所示。
表五
Figure PCTCN2019119475-appb-000004
此外，可选的，本申请实施例中的5GLAN群组的上下文信息还可能包含其他信息，如QoS需求等，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中，终端接入的UPF网元也可以理解终端创建PDU会话时的锚点UPF网元，终端通过该锚点UPF网元与其他网元(或者UE)进行通信，在本申请实施例中具体可以是为终端提供5GLAN服务的UPF网元，该说明适用于本申请所有实施例，在此统一说明，以下不再赘述。
S1205、GMF网元获取能够为第一终端提供5GLAN服务的UPF网元的标识，这里假设为UPF1网元。
可选的，一种可能的实现方式中，GMF网元可以向SMF网元请求能够为第一终端提供5GLAN服务的UPF网元的标识。比如，GMF网元向SMF网元发送请求消息 1，该请求消息1中包括第一终端的标识和5GLAN群组的上下文信息，该请求消息1用于请求第一会话的会话端口标识以及能够为第一终端提供5GLAN服务的UPF网元的标识。其中，可选的，该请求消息1中还可能包括GMF网元建议SMF网元选择的UPF网元的标识。这样，SMF网元接收来自GMF网元的请求消息1之后，可以根据第一终端的标识，为第一会话分配会话端口标识11，并根据5GLAN群组的上下文信息(可选的，可以结合GMF网元建议SMF网元选择的UPF网元的标识)，为第一终端选择UPF网元。这里假设第一终端接入的UPF网元为UPF1网元，进而SMF网元可以向GMF网元发送响应消息1，该响应消息1中包括第一终端的标识、UPF1网元的标识以及会话端口标识11。从而GMF网元可以获得SMF网元为第一终端选择的UPF1网元的标识，以及SMF网元为第一终端的第一会话分配的会话端口标识11。其中，这里的会话端口标识11例如可以是TEID1。
可选的，本申请实施例中，SMF网元也可以为第一会话分配会话标识(如PDU session ID)，具体可参考现有的实现方式，在此不再赘述。
示例性的，若第一终端为5GLAN群组的终端成员列表中第一个请求接入该5GLAN群组的终端，则此时SMF网元可以按照现有技术选择UPF网元并将选择的UPF网元确定为能够为第一终端提供5GLAN服务的UPF网元。例如，SMF网元可以按照现有标准TS23.501 V15.2.0 6.3.3章节中的方法为第一终端选择提供5GLAN服务的UPF网元。
或者，示例性的，若该5GLAN群组的上下文信息中包括该5GLAN群组的终端成员列表中已经入网的其他终端所选择的UPF网元的标识，则SMF网元可以将能够提供该5GLAN服务的UPF网元中暂未有该5GLAN群组的其他终端成员接入的UPF网元确定为能够为第一终端提供5GLAN服务的UPF网元；或者，SMF网元可以将某个有该5GLAN群组的其他终端成员接入但是接入的终端成员较少的UPF网元确定为能够为第一终端提供5GLAN服务的UPF网元。当然，SMF也可以在现有技术的基础上结合该5GLAN群组的终端成员列表中已经入网的其他终端所选择的UPF网元的标识信息为第一终端选择提供5GLAN服务的UPF网元，本申请实施例对此不作具体限定。
或者，可选的，另一种可能的实现方式中，GMF网元可以自行为第一终端选择提供5GLAN服务的UPF网元。该情况下，GMF网元可以临时为第一会话分配一个会话端口标识，后续SMF网元完成用户面会话建立和群组转发规则安装后，再通知GMF网元，进而GMF网元再更新5GLAN群组的上下文信息中第一会话的会话端口标识，本申请实施例对此不作具体限定。
当然，上述实施例仅是示例性的提供了几种GMF网元获取能够为第一终端提供5GLAN服务的UPF网元的标识的方式，GMF网元也可能通过其他方式获取能够为第一终端提供5GLAN服务的UPF网元的标识，本申请实施例对此不作具体限定。
此外，本申请后续实施例均是示例性的以SMF网元为第一终端选择提供5GLAN服务的UPF网元的场景为例进行说明，在此统一说明，以下不再赘述。
其中，在GMF网元获取会话端口标识11和UPF1网元的标识之后，可以更新第一终端未入网之前GMF网元上存储的5GLAN群组的上下文信息，或者在GMF网元上建立5GLAN群组的上下文信息。比如，假设第一终端为终端1，若第一终端为5GLAN 群组的终端成员列表中第一个请求接入该5GLAN群组的终端，则在第一终端入网之后，在GMF网元上建立的5GLAN群组的上下文信息例如可以如六所示；或者，假设第一终端为终端1，第一终端入网之前，GMF网元上存储的5GLAN群组的上下文信息如表三所示，则第一终端入网之后，更新后的5GLAN群组的上下文信息可以如表七所示；或者，假设第一终端为终端1，第一终端入网之前，GMF网元上存储的5GLAN群组的上下文信息如表四所示，则第一终端入网之后，更新后的5GLAN群组的上下文信息可以如表八所示。
表六
Figure PCTCN2019119475-appb-000005
表七
Figure PCTCN2019119475-appb-000006
表八
Figure PCTCN2019119475-appb-000007
以下分三个场景对本申请实施例提供的群组通信方法继续进行阐述。
需要说明的是，以下各实施例所涉及到的规则组(如规则组11或规则组12等)以及5GLAN group FAR(如group FAR1或group FAR2等)的相关说明可参考前述实施例介绍部分，在此不再赘述。其中，规则组11和规则组12中11和12仅是为了区分是应用在不同的成员端口上的规则组，group FAR1和group FAR2仅是为了区分是应用在不同UPF网元上的5GLAN group FAR，也可以用第一和第二等进行区分，本申请实施例对此不作具体限定。该说明适用于后续所有实施例，在此统一说明，以下不再赘述。
场景一，若GMF网元确定第一终端为5GLAN群组的终端成员列表中第一个请求接入该5GLAN群组的终端，则本申请实施例提供的群组通信方法还包括如下步骤S1206a-S1210a：
S1206a、GMF网元为该5GLAN群组创建应用在UPF1网元上的会话端口11上的规则组11，以及，GMF网元为该5GLAN群组创建应用在UPF1网元上的5GLAN group FAR，记作group FAR1。
其中，规则组11中包括入口PDR11、出口PDR11和出口FAR11。
可选的，这里的group FAR1中可以包括FA11，该FA11用于将接收到的属于该5GLAN群组的广播报文复制后发送到会话端口11上。
S1207a、GMF网元向SMF网元发送5GLAN服务响应消息1。相应的，SMF网元接收来自GMF网元的5GLAN服务响应消息1。其中，该5GLAN服务响应消息1中包括UPF1网元的标识，与UPF1网元的标识对应的会话端口标识11、规则组11和group FAR1。
可选的，本申请实施例中，UPF网元(如UPF1网元或UPF2网元或UPF3网元等)的标识例如可以是UPF网元的IP地址，本申请实施例对此不作具体限定。该说明也可以类似的适用于本申请所有实施例中的UPF网元，在此统一说明，以下不再赘述。
S1208a、SMF网元根据5GLAN服务响应消息1中UPF1网元的标识，向对应的UPF1网元发送N4会话建立请求(N4 session establishment request)消息1。相应的，UPF1网元接收来自SMF网元的N4会话建立请求消息1。
其中，N4会话建立请求消息1包括配置信息1，该配置信息1包括会话端口标识11、规则组11和group FAR1。
S1209a、UPF1网元建立第一会话，并根据配置信息1中的会话端口标识11和规则组11，在UPF1网元的会话端口11上配置规则组11，以及根据配置信息1中的group FAR1在UPF1网元上配置group FAR1。
其中，本申请实施例中，UPF1网元建立第一会话包括根据会话端口标识11创建会话端口11。相关描述可参考前述实施例介绍部分，在此不再赘述。
示例性的，假设第一终端为终端1，group FAR1的标识为1，则根据上述流程，第一终端入网之后，UPF1网元上的5GLAN群组的配置示意图可以如图13所示。
S1210a、UPF1网元向SMF网元发送N4会话建立响应(N4 session establishment response)消息1。相应的，SMF网元接收来自UPF1网元的N4会话建立请求响应消息1。
其中，该N4会话建立请求响应消息1用于通告N4会话建立和规则安装完成。
或者，场景二，若GMF网元确定5GLAN群组中已经有其他终端成员加入5GLAN群组，且SMF网元为第一终端选择接入的UPF网元与已经接入5GLAN群组的其他终端成员选择的UPF网元相同(如5GLAN群组的上下文信息如上述表三所示)，则本申请实施例提供的群组通信方法还包括如下步骤S1206b-S1210b：
S1206b-S1210b、与步骤S1206a-S1210a类似，区别比如在于，步骤S1206a-S1210a中是创建应用在UPF1网元上的5GLAN group FAR，而步骤S1206b-S1210b中是更新应用在UPF1网元上的5GLAN group FAR，其余相关描述可参考上述步骤S1206a-S1210a，在此不再赘述。
示例性的，假设在第一终端入网之前，GMF网元上存储的5GLAN群组的上下文信息如上述表三所示。其中，表三中的终端5入网的方式与上述步骤S1206a-S1210a 中的终端1类似，在UPF1网元的会话端口51上配置了规则组51以及在UPF1网元上配置了group FAR1，group FAR1中包括FA51，规则组51中包括入口PDR51、出口PDR51和出口FAR51，即UPF1网元上的5GLAN群组的配置示意图如图14中的(a)所示。其中，FA51用于将接收到的属于5GLAN ID对应的5GLAN群组的广播报文复制后发送到会话端口51上。
此时，假设第一终端为终端1，group FAR1的标识为1，则根据上述流程，终端1入网之后，此时UPF1网元上的5GLAN群组的配置示意图可以如图14中的(b)所示。
或者，场景三，若GMF网元确定5GLAN群组中已经有其他终端成员加入5GLAN群组，且SMF网元为第一终端选择了一个不存在该5GLAN群组的其他终端成员接入的UPF网元(如5GLAN群组的上下文信息如上述表四所示)，则该情况表示5GLAN群组可以跨越多个UPF网元，进而本申请实施例提供的群组通信方法还包括如下步骤S1209c-S1218c：
S1206c、GMF网元向SMF网元发送请求消息2。相应的，SMF网元接收来自GMF网元的请求消息2。其中，该请求消息2用于请求在UPF1网元与UPF2之间建立第一隧道。所述第一隧道用于传输所述5GLAN群组内群组成员之间的通信数据。
S1207c、SMF网元向GMF网元发送响应消息2。相应的，GMF网元接收来自SMF网元的响应消息2。
其中，该响应消息2中包括隧道端口标识41和隧道端口标识42。这里的隧道端口41为UPF1网元与UPF2网元之间的第一隧道在UPF1网元侧的端口；这里的隧道端口42为UPF1网元与UPF2网元之间的第一隧道在UPF2网元侧的端口。示例性的，隧道端口标识41例如可以为TEID41，隧道端口标识42例如可以为TEID42。需要说明的是，隧道标识可以是由SMF网元分配的，也可以是由对应的UPF网元分配的(例如UPF1网元分配第一隧道在UPF2网元侧的端口隧道端口标识41；UPF2网元分配第一隧道在UPF2网元侧的端口隧道端口标识42)，本申请实施例不做限制。
S1208c、GMF网元为该5GLAN群组创建应用在UPF1网元上的会话端口11上的规则组11；以及，GMF网元为该5GLAN群组创建应用在UPF1网元上的5GLAN group FAR，记作group FAR1；以及，GMF网元为该5GLAN群组创建应用在UPF1网元上的隧道端口41上的规则组41；以及，GMF网元为该5GLAN群组创建应用在UPF2网元上的隧道端口42上的规则组42；以及，GMF网元为该5GLAN群组更新应用在UPF2网元上的5GLAN group FAR，记作group FAR2。
可选的，这里的group FAR1中可以包括FA11和FA41，该FA11用于将接收到的属于5GLAN ID对应的5GLAN群组的广播报文复制后发送到会话端口11上，该FA41用于将接收到的属于5GLAN ID对应的5GLAN群组的广播报文复制后发送到隧道端口41上。
可选的，这里的group FAR2中可以包括FA42，该FA42用于将接收到的属于5GLAN ID对应的5GLAN群组的广播报文复制后发送到隧道端口42上。
S1209c、GMF网元向SMF网元发送5GLAN服务响应消息2。相应的，SMF网元接收来自GMF网元的5GLAN服务响应消息2。其中，该5GLAN服务响应消息2中包括UPF1网元的标识，与UPF1网元的标识对应的group FAR1、会话端口标识11和 规则组11、隧道端口标识41和规则组41，UPF2网元的标识，与UPF2网元的标识对应的更新后的group FAR2、隧道端口标识42和规则组42。
S1210c、SMF网元根据5GLAN服务响应消息2中UPF1网元的标识，向对应的UPF1网元发送N4会话建立请求消息2。相应的，UPF1网元接收来自SMF网元的N4会话建立请求消息2。
其中，N4会话建立请求消息2包括配置信息2，该配置信息2包括group FAR1、会话端口标识11和规则组11、隧道端口标识41和规则组41。
S1211c、UPF1网元建立第一会话和第一隧道，并根据配置信息2中的会话端口标识11和规则组11，在UPF1网元的会话端口11上配置规则组11，以及根据配置信息2中的group FAR1，在UPF1网元上配置group FAR1；以及根据配置信息2中的隧道端口标识41和规则组41，在UPF1网元的隧道端口41上配置规则组41。
其中，本申请实施例中，UPF1网元建立第一会话例如可以包括根据会话端口标识11创建会话端口11；UPF1网元建立第一隧道例如可以包括根据隧道端口标识41创建隧道端口41。相关描述可参考前述实施例介绍部分，在此不再赘述。
S1212c、UPF1网元向SMF网元发送N4会话建立响应消息2。相应的，SMF网元接收来自UPF1网元的N4会话建立请求响应消息2。
其中，该N4会话建立请求响应消息2用于通告N4会话建立和规则安装完成。
S1213c、SMF网元根据5GLAN服务响应消息2中UPF2网元的标识，向对应的UPF2网元发送N4会话修改请求(N4 session modification request)消息。相应的，UPF1网元接收来自SMF网元的N4会话修改请求消息。
其中，N4会话修改请求消息包括配置信息3，该配置信息3包括更新后的group FAR2、隧道端口标识42和规则组42。
S1214c、UPF2网元建立到UPF1网元的第一隧道，并根据配置信息3中的隧道端口标识42和规则组42，在UPF2网元的隧道端口42上配置规则组42，以及根据配置信息3中的更新后的group FAR2，更新UPF2网元上的group FAR2。
其中，本申请实施例中，UPF2网元建立第一隧道例如可以包括根据隧道端口标识42创建隧道端口42。相关描述可参考前述实施例介绍部分，在此不再赘述。
S1215c、UPF2网元向SMF网元发送N4会话修改响应消息。相应的，SMF网元接收来自UPF2网元的N4会话修改响应消息。
其中，该N4会话修改响应消息用于通告N4会话修改和规则安装完成。
需要说明的是，上述步骤S1213c与步骤S1210c之间没有必然的执行先后顺序。可以是先执行步骤S1213c，再执行步骤S1210c；也可以是先执行步骤S1210c，再执行步骤S1213c；还可以是同时执行步骤S1213c和步骤S1210c，本申请实施例对此不作具体限定。
示例性的，假设在第一终端入网之前，GMF网元上存储的5GLAN群组的上下文信息如上述表四所示。其中，表四中的终端5和终端2入网的方式与上述步骤S1206b-S1210b中的终端2和终端5入网的方式类似，在UPF2网元的会话端口22上配置了规则组22，在UPF2网元的会话端口52上配置了规则组52，以及在UPF2网元上配置了group FAR2，group FAR2中包括FA4和FA5，规则组22中包括入口PDR22、 出口PDR22和出口FAR22，规则组52中包括入口PDR52、出口PDR52和出口FAR52，即UPF2网元上的5GLAN群组的配置示意图如图15中的(a)所示。其中，FA52用于将接收到的属于5GLAN ID对应的5GLAN群组的广播报文复制后发送到会话端口52上，FA22用于将接收到的属于5GLAN ID对应的5GLAN群组的广播报文复制后发送到会话端口22上。
此时，假设第一终端为终端1，group FAR1的标识为1，则根据上述流程，终端1入网之后，group FAR1的标识为1，则此时UPF1网元和UPF2网元上的5GLAN群组的配置示意图可以如图15中的(b)所示。
可选的，本申请实施例中，若UPF1网元为第一会话分配会话端口端口标识111，则有两种方案与SMF网元为第一会话分配的会话端口标识11保持一致。
一种是UPF1网元自己维护本端为第一会话分配的会话端口端口标识111与SMF网元为第一会话分配的会话端口标识11的对应关系。
另一种是UPF1网元将UPF网元上配置的会话端口标识11和规则组11的对应关系更新为会话端口端口标识111和规则组11的对应关系，同时UPF1网元将本端为第一会话分配的会话端口端口标识111发送给SMF网元(比如通过上述步骤S1210a中的N4会话建立响应消息1或上述步骤S1212c中的N4会话建立响应消息2)，以使得SMF网元删除自己为第一会话分配的会话端口标识11，使用UPF1网元为第一会话分配的会话端口端口标识111。同时SMF网元向GMF网元发起更新请求，该更新请求包括会话端口端口标识111，以使得GMF网元可以将第一会话对应的会话端口标识11更新为会话端口端口标识111。
S1216、完成PDU会话建立的其他流程。
基于上述群组通信方法，由于5GLAN群组内的终端入网时，只需要调整(创建或更新)相关联的UPF网元上的5GLAN群组FAR，以及调整(创建或更新)相关联的UPF网元上与该终端成员对应的入口PDR、出口PDR和出口FAR即可，5GLAN群组内其他终端成员对应的入口PDR、出口PDR和出口FAR不发生改变。从而可以在5GLAN群组内入网的终端成员较多时，避免终端成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于终端成员数量的变化导致的配置工作量。
其中，上述步骤S1201至S1216中的GMF网元、SMF网元、UPF1网元或者UPF2网元的动作可以由图11所示的通信设备1100中的处理器1101调用存储器1103中存储的应用程序代码来执行，本实施例对此不作任何限制。
或者，以图8所示的群组通信系统应用于如图9所示的5G网络，群组管理功能网元为GMF网元，会话管理网元为SMF网元，用户面网元为UPF网元(如第一用户面网元为UPF1网元，第二用户面网元为UPF2网元，第三用户面网元为UPF3网元)，5GLAN群组内已经入网的终端成员移动的场景为例，如图16所示，为本申请实施例提供的一种群组通信方法，该群组通信方法包括如下步骤：
前置条件，第一终端已经接入UPF1网元，UPF1网元上已创建5GLAN群组的配置，包括group FAR1和相关的规则组；5GLAN群组内的其他UPF网元上也可能已创建5GLAN群组的配置，包括相关的group FAR和相关的规则组，建立方法如图12所示的实施例，在此不再赘述。其中，UPF1网元和UPF2网元连通。
S1601、第一终端从第一接入设备切换到第二接入设备。
S1602、第二接入设备向AMF网元发送路径切换请求(path switch request)。相应的，AMF网元接收来自第二接入设备的路径切换请求。
可选的，上述路径切换请求也可以替换为切换通告(handover)，本申请实施例对此不作具体限定。
S1603、AMF网元向SMF网元发送PDU会话更新请求(PDU session update request)。相应的，SMF网元接收来自AMF网元的PDU会话更新请求。
可选的，上述PDU会话更新请求也可以替换为PDU会话SM上下文更新请求(PDU session SM context update request)，本申请实施例对此不作具体限定。
其中，上述步骤S1601-S1603的具体实现可参考现有的实现方式，在此不再赘述。
S1604、SMF网元根据PDU会话更新请求，确定更新UPF网元，如将为第一终端提供服务的UPF网元由UPF1网元更换为UPF3网元。同时，若SMF网元确定第一终端发起了5GLAN群组通信，则SMF网元向GMF网元发送5GLAN服务更新请求(5GLAN service update request)。相应的，GMF网元接收来自SMF网元的5GLAN服务更新请求。
其中，该5GLAN服务更新请求包括第一终端的标识、UPF3网元(即目标UPF网元)的标识和第一会话的会话端口标识11。
可选的，该5GLAN服务更新请求还可以包括UPF1网元(即源UPF网元)的标识。
S1605、GMF网元根据5GLAN服务更新请求，获知为第一终端提供服务的UPF网元由UPF1网元更换为UPF3网元，则为该5GLAN群组创建应用在UPF3网元的会话端口31上的规则组31，以及根据5GLAN群组的上下文信息，为该5GLAN群组创建或更新应用在UPF3网元上的5GLAN group FAR，记作group FAR3。其中，创建或更新后的group FAR3中包括用于将接收到的属于该5GLAN群组的广播报文复制后发送到UPF3网元的会话端口31上的规则。
可选的，本申请实施例中，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中存在其他终端接入UPF1网元的情况下，GMF网元还为该5GLAN群组更新应用在UPF1网元上的group FAR1。其中，更新后的group FAR1中用于将接收到的属于该5GLAN群组的广播报文复制后发送到UPF1网元的会话端口11上的规则被删除。
其中，5GLAN群组的上下文信息的相关描述可参考图12所示的实施例，在此不再赘述。
S1606、GMF网元向SMF网元发送5GLAN服务更新响应(5GLAN service update response)。相应的，SMF网元接收来自GMF网元的5GLAN服务更新响应。
其中，该5GLAN服务更新响应中包括UPF3网元的标识，与UPF3网元的标识对应的group FAR3、会话端口标识31和规则组31，用于在UPF3网元的会话端口31上配置规则组31，以及在UPF3网元上配置或更新group FAR3。同时，该5GLAN服务更新响应中包括UPF1网元的标识、与UPF1网元的标识对应的会话端口标识11，用于删除UPF1网元的会话端口11和会话端口11上的规则组11。可选的，该5GLAN 服务更新响应中可以包括规则组11的标识，本申请实施例对此不作局具体限定。
此外，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中没有其他终端接入UPF1网元的情况下，该5GLAN服务更新响应中还包括与UPF1网元的标识对应的group FAR1的标识，用于删除UPF1网元上的group FAR1。或者，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中存在其他终端接入UPF1网元的情况下，该5GLAN服务更新响应中还包括与UPF1网元的标识对应的更新后的group FAR1，用于更新UPF1网元上的group FAR1。
S1607、SMF网元根据5GLAN服务更新响应中UPF3网元的标识，向对应的UPF3网元发送N4会话建立请求消息1。相应的，UPF3网元接收来自SMF网元的N4会话建立请求消息1。
其中，该N4会话建立请求消息1中包括配置信息，该配置信息包括与UPF3网元的标识对应的group FAR3、会话端口标识31和规则组31。
S1608、UPF3网元建立第一会话，并根据步骤S1607中的配置信息中的会话端口标识31和规则组31，在UPF3网元的会话端口31上配置规则组31，以及根据步骤S1607中的配置信息中的group FAR3，在UPF3网元上配置或更新group FAR3。
其中，本申请实施例中，UPF3网元建立第一会话包括根据会话端口标识31创建会话端口31。相关描述可参考前述实施例介绍部分，在此不再赘述。
S1609、SMF网元根据5GLAN服务更新响应中UPF1网元的标识，向对应的UPF1网元发送N4会话释放请求(N4 session release request)1。相应的，UPF1网元接收来自SMF网元的N4会话释放请求1。
其中，在UPF1网元上当前存在其他终端接入的情况下，该N4会话释放请求1包括指示1，该指示信息1包括与UPF1网元的标识对应的会话端口标识11和更新后的group FAR1。
或者，在UPF1网元上当前没有其他终端接入的情况下，该N4会话释放请求1包括指示信息2，该指示信息2包括与UPF1网元的标识对应的会话端口标识11和group FAR1的标识。可选的，该N4会话释放请求1中可以包括规则组11的标识，本申请实施例对此不作局具体限定。
S1610、UPF1网元释放第一会话，并根据指示信息1或指示信息2中的会话端口标识11，删除UPF1网元上的会话端口11以及会话端口11上的规则组11。同时，UPF1网元根据指示信息1中的更新后的group FAR1，更新UPF1网元上的group FAR1，或者UPF1网元根据指示信息2中的group FAR1的标识，删除UPF1网元上的group FAR1。
其中，本申请实施例中，UPF1网元释放第一会话包括根据会话端口标识11删除会话端口11。
示例性的，假设第一终端为终端1，则第一终端在5GLAN群组内移动之前，UPF1网元上的5GLAN群组的配置示意图可以如图17中的(a)所示。其中，在UPF1网元的会话端口11上配置了规则组11，在UPF1网元上配置了group FAR1。其中，规则组11中包括入口PDR11，出口PDR11和出口FAR111，group FAR1中包括FA11，FA11用于将接收到的属于5GLAN ID对应的5GLAN群组的广播报文复制后发送到会话端 口11上。则根据上述流程，第一终端在5GLAN群组内移动之后，UPF1网元和UPF3网元上的5GLAN群组的配置示意图可以如图17中的(b)所示。
需要说明的是，这里仅是示例性的给出第一终端在5GLAN群组内移动之前，5GLAN群组中已经入网的终端成员所选择的UPF网元上的5GLAN群组的配置示意图的相关描述，后续第一终端在5GLAN群组内移动之前或者下述图23所示的实施例中第一终端离网(即释放第一终端的第一会话)之前，UPF网元上类似的5GLAN群组的配置示意图的描述可参考此处描述，在此统一说明，以下不再一一赘述。
或者，示例性的，假设第一终端为终端1，则第一终端在5GLAN群组内移动之前，UPF1网元上的5GLAN群组的配置示意图可以如图18中的(a)所示。则根据上述流程，第一终端在5GLAN群组内移动之后，UPF1网元和UPF3网元上的5GLAN群组的配置示意图可以如图18中的(b)所示。
可选的，本申请实施例中，在当前UPF1网元上没有其他终端接入，但是5GLAN群组的终端成员列表中当前已经入网的终端所选择的UPF网元的标识中包括除UPF1网元之外的其他UPF网元的情况下，若为第一终端提供服务的UPF网元由UPF1网元更新为UPF3网元，此时GMF网元还需要通过SMF网元通知UPF1网元以及其他UPF网元删除该5GLAN群组的相应隧道端口以及隧道端口上的规则组，以及删除应用在UPF1网元上的group FAR，以及更新应用在其他UPF网元上的group FAR。实现方式与上述步骤S1609-S1610类似，在此不再赘述。
示例性的，假设第一终端为终端1，第一终端在5GLAN群组内移动之前，5GLAN群组的终端成员列表中当前已经入网的终端所选择的UPF网元的标识包括UPF1网元的标识、UPF2网元的标识和UPF3网元的标识，UPF1网元、UPF2网元和UPF3网元上的5GLAN群组的配置示意图如图19中的(a)所示。则根据上述流程，第一终端在5GLAN群组内移动之后,各UPF网元上的5GLAN群组的配置示意图如图19中的(b)所示。可以看出，UPF1网元和UPF3网元之间的隧道对应的隧道端口41上的规则组41和隧道端口43上的规则组43均被删除；以及，UPF3网元上的group FAR3也被更新，其中，group FAR3中的FA43被删除，FA43用于将接收到的属于该5GLAN群组的广播报文复制后发送到UPF3网元的隧道端口43上。此外，UPF1网元上暂时没有针对该5GLAN群组的配置，因此在图19中的(b)中未示出。
或者，示例性的，假设第一终端为终端1，第一终端在5GLAN群组内移动之前，5GLAN群组的终端成员列表中当前已经入网的终端所选择的UPF网元的标识包括UPF1网元的标识和UPF3网元的标识，UPF1网元和UPF3网元上的5GLAN群组的配置示意图如图20中的(a)所示。则根据上述流程，第一终端在5GLAN群组内移动之后,各UPF网元上的5GLAN群组的配置示意图如图20中的(b)所示。可以看出，UPF1网元和UPF3网元之间的隧道对应的隧道端口41上的规则组41和隧道端口43上的规则组43均被删除；以及，UPF3网元上的group FAR3也被更新，其中，group FAR3中的FA43被删除，FA43用于将接收到的属于该5GLAN群组的广播报文复制后发送到UPF3网元的隧道端口43上。此外，UPF1网元上暂时没有针对该5GLAN群组的配置，因此在图20中的(b)中未示出。
可选的，本申请实施例中，在5GLAN群组的终端成员列表中当前已经入网的终 端所选择的UPF网元的标识中不包括UPF3网元的情况下，若为第一终端提供服务的UPF网元由UPF1网元更新为UPF3网元，此时GMF网元还需要请求SMF网元建立UPF3网元与其他UPF网元之间的隧道，进而在接收来自SMF网元的隧道端口标识之后，通过SMF网元配置应用在UPF3网元和其他UPF网元上的隧道端口上的规则组，以及创建应用在UPF3网元上的group FAR3，以及更新应用在其他UPF网元上的group FAR。其中，这里的其他UPF网元例如可以是UPF1网元，或者5GLAN群组的终端成员列表中当前已经入网的终端所选择的UPF网元的标识除UPF1之外的UPF网元。实现方式与上述步骤S1607和S1608的方式类似，在此不再赘述。
示例性的，假设第一终端为终端1，第一终端在5GLAN群组内移动之前，5GLAN群组的终端成员列表中当前已经入网的终端所选择的UPF网元的标识包括仅UPF1网元的标识，UPF1网元上的5GLAN群组的配置示意图如图21中的(a)所示。则根据上述流程，第一终端在5GLAN群组内移动之后,各UPF网元上的5GLAN群组的配置示意图如图21中的(b)所示。可以看出，UPF1网元上配置了在UPF1网元与UPF3网元之间的隧道对应的隧道端口41上的规则组41；UPF3网元上配置了在UPF1网元与UPF3网元之间的隧道对应的隧道端口43上的规则组43；以及，UPF3网元上配置了group FAR3；以及UPF1网元上的group FAR1也被更新，其中，group FAR1中新增FA41，FA41用于将接收到的属于该5GLAN群组的广播报文复制后发送到UPF1网元的隧道端口41上。
或者，示例性的，假设第一终端为终端1，第一终端在5GLAN群组内移动之前，5GLAN群组的终端成员列表中当前已经入网的终端所选择的UPF网元的标识包括UPF1网元和UPF2网元的标识，UPF1网元和UPF2网元上的5GLAN群组的配置示意图如图22中的(a)所示。则根据上述流程，第一终端在5GLAN群组内移动之后,各UPF网元上的5GLAN群组的配置示意图如图22中的(b)所示。可以看出，UPF2网元上配置了在UPF2网元与UPF3网元之间的隧道对应的隧道端口62上的规则组62；UPF3网元上配置了在UPF2网元与UPF3网元之间的隧道对应的隧道端口63上的规则组63；以及，UPF3网元上配置了group FAR3；以及UPF2网元上的group FAR2也被更新，其中，group FAR2中新增FA62，FA62用于将接收到的属于该5GLAN群组的广播报文复制后发送到UPF2网元的隧道端口62上。此外，由于图22所示的实施例中，第一终端移动之后，在当前UPF1网元上没有其他终端接入，因此需要删除UPF1网元和UPF2网元之间的隧道对应的隧道端口51上的规则组51和隧道端口52上的规则组52，以及group FAR2中的FA52被删除，FA52用于将接收到的属于该5GLAN群组的广播报文复制后发送到UPF2网元的隧道端口52上，相关实现可参考上述实施例，在此不再赘述。
S1611、完成切换的其他流程。
基于上述群组通信方法，由于5GLAN群组内已经入网的终端成员在5GLAN群组内移动时，只需要调整(创建、更新或删除)相关联的UPF网元上的5GLAN群组FAR，以及调整(创建、更新或删除)相关联的UPF网元上与该终端成员对应的入口PDR、出口PDR和出口FAR即可，5GLAN群组内其他已经入网的终端成员对应的入口PDR、出口PDR和出口FAR不发生改变。从而可以在5GLAN群组内入网的终端成员较多时， 避免终端成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于终端成员数量的变化导致的配置工作量。
其中，上述步骤S1601至S1611中的GMF网元、SMF网元、UPF1网元或者UPF3网元的动作可以由图11所示的通信设备1100中的处理器1101调用存储器1103中存储的应用程序代码来执行，本实施例对此不作任何限制。
或者，以图8所示的群组通信系统应用于如图9所示的5G网络，群组管理功能网元为GMF网元，会话管理网元为SMF网元，用户面网元为UPF网元(如第一用户面网元为UPF1网元，第二用户面网元为UPF2网元，第三用户面网元为UPF3网元)，5GLAN群组的终端成员离网的场景为例，如图23所示，为本申请实施例提供的一种群组通信方法，该群组通信方法包括如下步骤：
前置条件，第一终端已经接入UPF1网元，UPF1网元上已创建5GLAN群组的配置，包括group FAR1和相关的规则组；5GLAN群组内的其他UPF网元上也可能已创建5GLAN群组的配置，包括相关的group FAR和相关的规则组，建立方法如图12所示的实施例，在此不再赘述。其中，UPF1网元和UPF2网元连通。
S2301、第一终端向AMF网元发送会话释放请求。相应的，AMF网元接收来自第一终端的会话释放请求。
S2302、AMF网元向SMF网元发送SM上下文更新请求。相应的，SMF网元接收来自AMF网元的SM上下文更新请求。
可选的，上述SM上下文更新请求也可以替换为PDU会话更新请求，本申请实施例对此不作具体限定。
其中，上述步骤S2301-S2302的具体实现可参考现有的实现方式，在此不再赘述。
S2303、若SMF网元确定第一终端发起了5GLAN群组通信，则SMF网元向GMF网元发送5GLAN服务释放请求(5GLAN service release request)。相应的，GMF网元接收来自SMF网元的5GLAN服务释放请求。
其中，该5GLAN服务释放请求用于指示释放第一终端的第一会话。
一种可能的实现方式中，该5GLAN服务释放请求这条消息本身具备指示释放会话的功能，此时，该5GLAN服务释放请求中可以包括第一终端的标识。或者，一种可能的实现方式中，该5GLAN服务释放请求包括指示信息和第一终端的标识，该指示信息用于指示释放会话。
可选的，该5GLAN服务释放请求中还可以包括上述第一终端入网时接入的UPF1网元的标识，本申请实施例对此不作具体限定。
其中，GMF网元根据5GLAN服务更新请求，获知第一终端将释放第一会话，进而可以执行相关的操作。以下分两个场景对本申请实施例提供的群组通信方法继续进行阐述。
场景一，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中没有其他终端接入其他UPF网元的情况下，则本申请实施例提供的群组通信方法还包括如下步骤S2304a-S2307a：
S2304a、可选的，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中存在其他终端接入UPF1网元的情况下， GMF网元还为该5GLAN群组更新应用在UPF1网元上的group FAR1。其中，更新后的group FAR1中用于将接收到的属于该5GLAN群组的广播报文复制后发送到UPF1网元的会话端口11上的规则被删除。
其中，5GLAN群组的上下文信息的相关描述可参考图12所示的实施例，在此不再赘述。
S2305a、GMF网元向SMF网元发送5GLAN服务释放响应(5GLAN service release response)1。相应的，SMF网元接收来自GMF网元的5GLAN服务释放响应1。
其中，该5GLAN服务释放响应1中包括UPF1网元的标识、与UPF1网元的标识对应的会话端口标识11，用于删除UPF1网元的会话端口11以及会话端口11上的规则组11。可选的，该5GLAN服务释放响应1中可以包括规则组11的标识，本申请实施例对此不作具体限定。
此外，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中没有其他终端接入UPF1网元的情况下，该5GLAN服务释放响应1中还包括与UPF1网元的标识对应的group FAR1的标识，用于删除UPF1网元上的group FAR1。或者，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中存在其他终端接入UPF1网元的情况下，该5GLAN服务释放响应1中还包括与UPF1网元的标识对应的更新后的group FAR1，用于更新UPF1网元上的group FAR1。
S2306a、SMF网元根据5GLAN服务释放响应1中UPF1网元的标识，向对应的UPF1网元发送N4会话释放请求1。相应的，UPF1网元接收来自SMF网元的N4会话释放请求1。
其中，在当前UPF1网元上存在其他终端接入的情况下，该N4会话释放请求1包括指示1，该指示信息1包括与UPF1网元的标识对应的会话端口标识11和更新后的group FAR1。
或者，在当前UPF1网元上没有其他终端接入的情况下，该N4会话释放请求1包括指示信息2，该指示信息2包括与UPF1网元的标识对应的会话端口标识11和group FAR1的标识。
可选的，该N4会话释放请求1中可以包括规则组11的标识，本申请实施例对此不作具体限定。
S2307a、UPF1网元释放第一会话，并根据指示信息1或指示信息2中的会话端口标识11和规则组11的标识，删除UPF1网元的会话端口11以及会话端口11上的规则组11。同时，UPF1网元根据指示信息1中的更新后的group FAR1，更新UPF1网元上的group FAR1，或者UPF1网元根据指示信息2中的group FAR1的标识，删除UPF1网元上的group FAR1。
其中，本申请实施例中，UPF1网元释放第一会话包括根据会话端口标识11删除会话端口11。
示例性的，假设第一终端为终端1，则第一终端离网之前，UPF1网元上的5GLAN群组的配置示意图可以如图24中的(a)所示，则根据上述流程，第一终端离网之后，UPF1网元上该5GLAN群组的配置示意图可以如图24中的(b)所示，即UPF1网元 上暂时没有该5GLAN群组的配置信息。
或者，示例性的，假设第一终端为终端1，第一终端离网之前，UPF1网元上的5GLAN群组的配置示意图可以如图25中的(a)所示，则根据上述流程，第一终端离网之后，UPF1网元上该5GLAN群组的配置示意图可以如图25中的(b)所示。
或者，场景二，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中存在其他终端接入其他UPF网元的情况下，这里假设存在其他终端接入UPF2网元，则本申请实施例提供的群组通信方法还包括如下步骤S2304b-S2309b：
S2304b、可选的，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中存在其他终端接入UPF1网元的情况下，GMF网元还为该5GLAN群组更新应用在UPF1网元上的group FAR1。其中，更新后的group FAR1中用于将接收到的属于该5GLAN群组的广播报文复制后发送到UPF1网元的会话端口11上的规则被删除。
可选的，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中不存在其他终端接入UPF1网元的情况下，该GMF网元还为该5GLAN群组更新应用在UPF2网元上的group FAR2。其中，更新后的group FAR2中用于将接收到的属于该5GLAN群组的广播报文复制后发送到隧道端口42的规则被删除。
其中，隧道端口42为UPF1网元和UPF2网元之间的第一隧道在UPF2网元侧的隧道端口。
S2305b、GMF网元向SMF网元发送5GLAN服务释放响应2。相应的，SMF网元接收来自GMF网元的5GLAN服务释放响应2。
其中，该5GLAN服务释放响应2中包括UPF1网元的标识、与UPF1网元的标识对应的会话端口标识11，用于删除UPF1网元的会话端口11以及会话端口11上的规则组11。可选的，该GLAN服务释放响应2中可以包括规则组11的标识，本申请实施例对此不作具体限定。
此外，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中存在其他终端接入UPF1网元的情况下，该5GLAN服务释放响应中还包括与UPF1网元的标识对应的更新后的group FAR1，用于更新UPF1网元上的group FAR1。
或者，在GMF网元根据GMF网元上存储的5GLAN群组的上下文信息，确定该5GLAN群组的终端成员列表中没有其他终端接入UPF1网元的情况下，该5GLAN服务释放响应2中还包括与UPF1网元的标识对应的group FAR1的标识，用于删除UPF1网元上的group FAR1。以及，该5GLAN服务释放响应2中还包括与UPF1网元的标识对应的隧道端口41的标识，用于删除UPF1网元的隧道端口41以及隧道端口41上的规则组41。以及，该5GLAN服务释放响应2中还包括与UPF2网元的标识对应的隧道端口42的标识，用于删除UPF2网元的隧道端口42以及隧道端口42上的规则组42。可选的，该5GLAN服务释放响应2中可以包括规则组41的标识和规则组42的标识，本申请实施例对此不作具体限定。
S2306b、SMF网元根据5GLAN服务释放响应2中UPF1网元的标识，向对应的UPF1网元发送N4会话释放请求2。相应的，UPF1网元接收来自SMF网元的N4会话释放请求2。
其中，在当前UPF1网元上存在其他终端接入的情况下，该N4会话释放请求2包括指示信息3，该指示信息3包括与UPF1网元的标识对应的会话端口标识11和更新后的group FAR1。可选的，该N4会话释放请求2中可以包括规则组11的标识，本申请实施例对此不作具体限定。
或者，在当前UPF1网元上没有其他终端接入的情况下，该N4会话释放请求2包括指示4，该指示信息4包括与UPF1网元的标识对应的会话端口标识11、隧道端口41的标识和group FAR1的标识。可选的，该N4会话释放请求2中可以包括规则组11的标识和规则组41的标识，本申请实施例对此不作具体限定。
S2307b、UPF1网元释放第一会话，并根据会话端口标识11，删除UPF1网元的会话端口11以及会话端口11的规则组11。以及，UPF1网元根据group FAR1的标识删除应用在UPF1网元上的group FAR1，或者UPF1网元根据更新后的group FAR1，更新应用在UPF1网元上的group FAR1。
可选的，在当前UPF1网元上不存在其他终端接入的情况下，UPF1网元还可以根据隧道端口41的标识，删除隧道端口41和隧道端口41上的规则组41。
S2308b、可选的，在当前UPF1网元上不存在其他终端接入的情况下，SMF网元根据5GLAN服务释放响应2中UPF2网元的标识，向对应的UPF2网元发送N4会话修改请求3。相应的，UPF2网元接收来自SMF网元的N4会话修改请求3。
其中，该N4会话修改请求3包括指示信息5，该指示信息5包括与UPF2网元的标识对应的更新后的group FAR2，用于更新应用在UPF2网元上的group FAR2。
此外，该指示信息5还包括与UPF2网元的标识对应的隧道端口42的标识，用于删除UPF2网元的隧道端口42和隧道端口42上的规则组42。
S2309b、可选的，UPF2网元根据更新后的group FAR2，更新应用在UPF2网元上的group FAR2；以及，UPF2网元根据隧道端口42的标识，删除UPF2网元的隧道端口42和隧道端口42上的规则组42。
示例性的，假设第一终端为终端1，第一终端离网之前，UPF1网元上的5GLAN群组的配置示意图可以如图26中的(a)所示，则根据上述流程，第一终端离网之后，UPF1网元上该5GLAN群组的配置示意图可以如图26中的(b)所示。可以看出，UPF1网元和UPF3网元之间的隧道对应的隧道端口41上的规则组41和隧道端口43上的规则组43均被删除；以及，UPF3网元上的group FAR3也被更新，其中，group FAR3中的FA43被删除，FA43用于将接收到的属于该5GLAN群组的广播报文复制后发送到UPF3网元的隧道端口43上。此外，UPF1网元上暂时没有针对该5GLAN群组的配置，因此在图26中的(b)中未示出。
或者，示例性的，假设第一终端为终端1，第一终端离网之前，UPF1网元上的5GLAN群组的配置示意图可以如图27中的(a)所示，则根据上述流程，第一终端离网之后，UPF1网元上该5GLAN群组的配置示意图可以如图27中的(b)所示。
S2310、完成释放的其他流程。
基于上述群组通信方法，由于5GLAN群组内的终端成员离网时，只需要调整(更新或删除)相关联的UPF网元上的5GLAN群组FAR，以及调整(更新或删除)相关联的UPF网元上与该终端成员对应的入口PDR、出口PDR和出口FAR即可，5GLAN群组内其他成员对应的入口PDR、出口PDR和出口FAR不发生改变。从而可以在5GLAN群组内入网的终端成员较多时，避免终端成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于终端成员数量的变化导致的配置工作量。
其中，上述步骤S2301至S2310中的GMF网元、SMF网元、UPF1网元或者UPF2网元的动作可以由图11所示的通信设备1100中的处理器1101调用存储器1103中存储的应用程序代码来执行，本实施例对此不作任何限制。
其中，上述图12至图27分别示例性的给出了广播场景下，5GLAN群组内的终端成员发生变化时(如终端成员入网，终端成员离网，已经入网的终端成员移动)对应的群组通信方法，主要以控制面的配置为主进行说明。下面给出用户面网元如何转发群组广播报文的相关说明如下。
假设当前5GLAN群组的标识为1的5GLAN群组1内的终端1、终端2和终端3已经入网。其中，终端1和终端2接入UPF1网元，终端3接入UPF2网元。UPF1和UPF2网元上的5GLAN群组的配置示意图如图28所示。其中，关于UPF1和UPF2网元上的5GLAN群组的配置说明可参考图17所示的实施例中关于5GLAN群组的配置说明部分，在此不再详细描述。若以终端1发送报文1为例进行说明，则UPF网元转发群组广播报文的方法包括如下步骤：
第一，终端1通过5G用户面协议(即经过接入设备的转发)将报文1发送至UPF1网元。这里假设报文1的目的地址为全1(代表是广播报文)，源地址为终端1的地址。
第二，UPF1网元接收到来自终端1的报文1之后，可以根据该报文1的5G用户面协议标记(如TEID)确定报文1对应的会话端口，这里假设报文1对应的会话端口为会话端口11。则UPF1网元可以使用应用在会话端口11上的规则组11中的入口PDR(可能是一个或多个)与报文1的特性信息进行匹配，找到与之匹配的入口PDR。
其中，本申请实施例中，入口PDR识别报文的方法例如可以是根据5G用户面协议标记识别报文属于某个5GLAN群组，以及根据广播报文的识别规则识别报文是广播报文。
可选的，这里的5G用户面协议标记例如可以是TEID，或者TEID+QFI，本申请实施例对此不作具体限定。
可选的，在报文1为IP报文的情况下，广播报文的识别规则例如可以是目的IP地址为全1；或者，在报文1为以太网帧的情况下，广播报文的识别规则例如可以是目的MAC地址为全1，本申请实施例对此不作具体限定。
示例性的，这里假设报文1的5G用户面协议标记为TEID＝0x005b8433，QFI＝3，报文1的目的(destination)IP＝255.255.255.255，而入口PDR11的功能为识别属于5GLAN群组1的广播报文，则UPF1网元找到的与之匹配的入口PDR则为入口PDR11。
第三，UPF1网元根据入口PDR1中包括的5GLAN群组的标识，查找到对应的5GLAN群组FAR，通过该5GLAN群组FAR处理来自终端1的报文1。具体的，UPF1 网元根据UPF1网元上5GLAN群组1对应的成员端口的数量总和将报文复制成同等数量的多份进行处理后，将报文转发到5GLAN群组FAR指定的出口。比如，在图28中，UPF1网元可以根据入口PDR1中包括的5GLAN群组的标识1，查找到对应的5GLAN群组FAR为group FAR1，进而通过group FAR1处理来自终端1的报文1。其中，图28假设group FAR1中包括三个FA，分别为FA11、FA21和FA41，其中，FA11用于将报文1转发到会话端口11的出口上，FA21用于将报文1转发到会话端口21的出口上，FA41用于将报文1转发到隧道端口41的出口上.其中，由于会话端口11的出口为报文1的入口，因此转发到会话端口11的出口上的报文将被丢弃。
第四，UPF1网元根据会话端口21上的出口PDR和出口FAR(可能是多组出口PDR和出口FAR)对报文1进行进一步处理；以及，UPF1网元根据隧道端口41上的出口PDR和出口FAR(可能是多组出口PDR和处理FAR)对报文1进行进一步处理。其中，UPF1网元根据会话端口21上的出口PDR和出口FAR对报文1进行处理的方式与UPF1网元根据隧道端口41上的出口PDR和出口FAR对报文1进行进一步处理的方式类似，这里示例性的以UPF1网元根据会话端口21上的出口PDR和出口FAR对报文1进行处理的方式进行说明。
其中，UPF1网元可以使用会话端口21上的出口PDR与报文1的类型信息进行匹配，找到与之匹配的出口PDR。如基于IP报文的差分服务代码点(differentiated services code point，DSCP)字段或以太网帧的802.1p比特识别报文1的优先级。这里假设报文1的优先级为第一优先级，会话端口21上的出口PDR11用于识别第一优先级的报文，则此时UPF1网元找到的与之匹配的出口PDR则为出口PDR11。
第五，UPF1网元根据出口PDR11中包括的出口FAR11的标识，查找到对应的出口FAR11，通过出口FAR11对报文1添加外层消息头以及进行传输层标记之后，将报文1从会话端口11转发出去，进而终端2可以接收到报文1。其中，出口FAR11对报文添加外层消息头以及进行传输层标记的方式可参考图5所示的实施例部分，在此不再赘述。
类似的，UPF2网元接收到报文1之后的处理方式与UPF1网元接收到报文1的处理方式类似，区别在于UPF2网元接收到来自UPF1网元的报文1之后，可以根据该报文1的隧道头以及在隧道头设置的隧道端口标识，确定报文1对应的隧道端口，这里假设报文1对应的隧道端口为隧道端口42。其余相关描述可参考上述UPF1网元上报文的转发处理流程，在此不再赘述。
需要说明的是，本申请实施例上述广播场景下的控制面配置流程和用户面网元转发群组广播报文流程可以解耦。也就是说，基于本申请实施例上述广播场景下的控制面配置流程，也可以存在其他的用户面网元转发群组广播报文流程；或者，基于本申请实施例上述广播场景下的用户面网元转发群组广播报文流程，也可以存在其他的控制面配置流程，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例上述广播场景下的控制面配置流程以不同的UPF网元由同一个SMF网元进行管理为例进行说明。当然，不同的UPF网元也可能由不同的SMF网元，此时GMF网元需要分别向不同的SMF网元发送上述5GLAN服务响应消息或者5GLAN服务更新响应或者5GLAN释放响应等，进而通过相应的SMF网元 向其管理的UPF网元发送上述控制面配置流程中SMF网元向UPF网元发送的消息，本申请实施例对该场景不进行详细阐述。此外，该说明也适用于以下组播场景，在此统一说明，以下不再赘述。
下面以组播场景为例，给出本申请实施例提供的群组通信的方法。
首先，以图8所示的群组通信系统应用于如图9所示的5G网络，群组管理功能网元为GMF网元，会话管理网元为SMF网元(如第一会话管理网元为SMF1网元，第二会话管理网元为SMF2网元)，用户面网元为UPF网元(如第一用户面网元为UPF1网元，第二用户面网元为UPF2网元)，组播成员加入组播组的场景为例，则组播成员加入的场景下，可能存在以下两个情况(以将要加入的组播成员为第一终端为例)：
情况一、第一终端接入的UPF网元(假设为UPF1网元)上还有该组播组的其他组播成员或组播源，则：
步骤一，修改UPF1网元上的组播组FAR1，增加指向该组播成员的下游端口的规则。
步骤二，配置应用在UPF1网元上该组播成员的下游端口的出口PDR和出口FAR。
情况二，第一终端接入的UPF网元(假设为UPF1网元)上没有该组播组的其他组播成员或组播源，则：
步骤一，配置应用在UPF1网元上的组播组FAR1，以及配置应用在UPF1网元上该组播成员的下游端口的出口PDR和出口FAR，组播组FAR1中包括指向该组播成员的下游端口的规则。
步骤二，配置应用在UPF1网元上该组播成员的上游端口的入口PDR。
步骤三，更新UPF1网元的上游UPF网元上的组播组FAR，增加指向该组播成员关联的下游端口的规则；以及，配置应用在UPF1网元的上游UPF网元上该组播成员关联的下游端口的出口PDR和出口FAR。
步骤四，若UPF1网元的上游UPF网元上没有该组播组的其他组播成员或组播源，则循环执行上述步骤二和步骤三类似的步骤(区别在于针对的UPF网元不同)，直至某个上游UPF网元上有该组播组的其他组播成员或组播源或者直至组播源接入的UPF网元(可以视为目标UPF网元)。其中，若该目标UPF网元上有该组播组的其他组播成员，则对于该目标UPF网元执行上述步骤三类似的步骤(区别在于针对的UPF网元不同)之后结束；或者，若该目标UPF网元为组播源接入的UPF网元，则对于该UPF网元，还需要在执行上述步骤二和步骤三类似的步骤(区别在于针对的UPF网元不同)之后结束。
下面示例性的给出组播成员加入的场景下，本申请实施例提供的一种群组通信方法。如图29所示，该群组通信方法包括如下步骤：
前置条件，第一终端已经接入UPF1网元，UPF1网元上已创建5GLAN群组的配置，建立方法如图12所示的实施例，在此不再赘述。此外，UPF2网元上可能也已创建5GLAN群组的配置，建立方法如图12所示的实施例，在此不再赘述。其中，UPF1网元和UPF2网元连通。
S2901、第一终端通过接入设备向UPF1网元发送因特网组管理协议(internet group  management protocol，IGMP)加入(join)消息。相应的，UPF1网元接收来自第一终端的IGMP加入消息。
其中，该IGMP加入消息包括组播组的地址(也可以简称组播地址)。
可选的，该IGMP加入消息还可以包括组播源的地址。
需要说明的是，本申请实施例中，第一终端仅作为组播成员才会向UPF1网元发送IGMP加入消息，而组播源或者非组播组的成员不会向UPF1网元发送IGMP加入消息，在此统一说明，以下不再赘述。
其中，第一终端获取组播源的地址和组播组的地址的方式可参考现有的实现方式，在此不再赘述。
S2902、UPF1网元识别IGMP加入消息，进而向连接的SMF网元发送该IGMP加入消息。相应的，SMF网元接收来自UPF1网元的IGMP加入消息。
其中，本申请实施例中，IGMP加入消息可以是携带在UPF1网元向SMF网元发送的N4接口消息中发送给SMF网元的，本申请实施例对此不作具体限定。
S2903、SMF网元识别IGMP加入消息，进而向GMF网元发送5GLAN服务请求消息。相应的，GMF网元接收来自SMF网元的5GLAN服务请求消息。
其中，该5GLAN服务请求消息携带IGMP加入消息、第一终端的标识、UPF1网元的标识以及会话端口标识11。
可选的，本申请实施例中，第一终端的标识例如可以是第一终端的地址。该第一终端的地址例如可以是第一终端的IP地址或者第一终端的IP地址等，本申请实施例对此不作具体限定。该说明也可以类似的适用于本申请组播场景下其他实施例中的其他终端。比如，下述终端3的标识可以是终端3的地址，该地址例如可以是IP地址或者MAC地址，在此统一说明，以下不再赘述。
S2904、GMF网元解析IGMP加入消息之后获得组播源的地址和组播组的地址。进而GMF网元可以根据组播组的地址(可选的结合组播源的地址)，获取该组播组的上下文信息。
其中，GMF网元获取获取该组播组的上下文信息例如可以是：建立该组播组的上下文信息，或者读取GMF网元上存储的该组播组的上下文信息。比如，在第一终端为第一个接入该组播组的组播成员的情况下，GMF网元需要建立该组播组的上下文信息；或者，在第一终端不是第一个接入该组播组的组播成员的情况下，GMF网元可以读取GMF网元上存储的该组播组的上下文信息。
可选的，本申请实施例中，组播组的上下文信息中可以包括组播转发树的信息，比如包括组播源的标识、组播成员的标识，以及，组播源和每个组播成员之间的UPF网元(可能是一个或多个)的标识。其中，该组播转发树的相关描述可参考前述实施例介绍部分，在此不再赘述。
示例性的，假设终端2和终端3已经加入组播源为终端1的组播组，组播转发树以及组播转发树的UPF网元上该组播组的配置示意图如图30所示，则该组播组的上下文信息中包括的组播转发树的信息可以如表九所示，包括组播源的标识，组播源的下游成员的标识，组播源的下游成员的下游成员的标识，以此类推。
表九
Figure PCTCN2019119475-appb-000008
其中，这里组播源的标识具体可以是上述组播源的地址，下游成员的标识具体也可以是下游成员的IP地址，在此统一说明，以下不再赘述。
其中，表九中下游成员的相关定义可参考前述实施例中组播转发树的介绍部分，在此不再赘述。
可选的，本申请实施例中，组播组的上下文信息中还可以包括组播源和每个组播成员之间的UPF网元上该组播组的上游端口标识和下游端口标识。比如，结合上述图30，则该组播组的上下文信息中还可以包括与组播源和每个组播成员之间的UPF网元的标识对应的上游成员标识、上游端口标识、下游成员标识和下游端口标识，如表十所示。
表十
Figure PCTCN2019119475-appb-000009
S2905、GMF网元根据该组播组的上下文信息，结合5GLAN服务请求消息中携带的UPF1网元的标识以及会话端口标识11，创建应用在UPF1网元的下游端口上的出口PDR和出口FAR，以及更新应用在UPF1网元上的组播组FAR1。其中，该下游端口的标识为会话端口标识11。更新后的组播组FAR1中增加将接收到的属于该组播组的组播报文复制后发送到该下游端口上的规则。
示例性的，假设第一终端为终端3，第一终端加入组播组之前，组播组的配置示意图可以如图31中的(a)所示。其中，图31中的(a)中的终端3未加入组播组，因此仅是简单示意了一下终端3建立PDU会话之后，终端3接入的UPF1网元上的会话端口11，具体的PDU会话建立流程可参考图12所示的实施例，在此不再赘述。此时假设会话端口标识11对应的下游端口为下游端口3，则第一终端加入组播组之后，在完成后续的步骤S2906-S2908的配置流程之后，组播组的配置示意图可以如图31中的(b)所示。即，在UPF1网元上的会话端口标识11对应的下游端口3上配置了出口PDR3和出口FAR3，同时更新后的组播组FAR1中增加将接收到的属于该组播组的组播报文复制后发送到该下游端口3上的规则。
可选的，本申请实施例中，若组播源接入的UPF网元与UPF1网元不是同一个UPF 网元，则GMF网元还需要执行下述操作：
GMF网元确定UPF1网元上是否有该组播组对应的上游端口，若没有，则创建应用在UPF1网元的上游端口上的入口PDR。其中，该上游端口的标识为UPF1网元与UPF1网元的上游UPF网元之间的隧道在UPF网元侧的隧道端口标识。
此外，GMF网元根据该组播组的上下文信息，依次遍历UPF1网元的上游UPF网元，直至目标UPF网元，其中，目标UPF网元为存在组播组对应的上游端口的UPF网元或者组播源接入的UPF网元。
进而，若目标UPF网元为存在组播组对应的上游端口的UPF网元，则针对目标UPF网元和UPF1网元之间的任意一个UPF网元，GMF网元分别创建应用在每个UPF网元的上游端口的入口PDR，以及创建应用在每个UPF网元的下游端口的出口PDR和出口FAR，以及创建应用在每个UPF网元上的组播组FAR，以及针对目标UPF网元，GMF网元创建应用在目标UPF网元的下游端口的出口PDR和出口FAR，以及更新应用在目标UPF网元上的组播组FAR。其中，创建或更新后的组播组FAR中包括将接收到的属于该组播组的组播报文复制后发送到该UPF网元的下游端口上的规则。
或者，若目标UPF网元为组播源接入的UPF网元，针对目标UPF网元、以及目标UPF网元和UPF1网元之间的任意一个UPF网元，GMF网元分别创建应用在每个UPF网元的上游端口的入口PDR，以及创建应用在每个UPF网元的下游端口的出口PDR和出口FAR，以及创建应用在每个UPF网元上的组播组FAR。其中，创建的组播组FAR中包括将接收到的属于该组播组的组播报文复制后发送到该UPF网元的下游端口上的规则。
其中，上述的上游端口或下游端口若为隧道端口，则对应的端口标识为隧道端口标识。上述的上游端口若为会话端口，即目标UPF网元为组播源接入的UPF网元的场景下目标UPF网元上的上游端口，则对应的端口标识为组播源建立PDU会话时在该目标UPF网元上创建的会话端口所对应的会话端口标识，在此统一说明，以下不再赘述。
示例性的，假设第一终端为终端4，第一终端加入组播组之前，组播组的配置示意图可以如图32中的(a)所示。其中，图32中的(a)中的终端4未加入组播组，因此仅是简单示意了一下终端4建立PDU会话之后，终端4接入的UPF1网元上的会话端口11和隧道端口41，以及与UPF1网元连接的UPF2网元上的隧道端口42，具体的PDU会话建立流程可参考图12所示的实施例，在此不再赘述。此时，假设会话端口标识11对应的下游端口为下游端口4，则第一终端加入组播组之后，在完成后续的步骤S2906-S2908的配置流程之后，组播组的配置示意图可以如图32中的(b)所示。即，在UPF1网元上的会话端口标识11对应的会话端口11(即图32中的(b)中的下游端口4)上配置了出口PDR4和出口FAR4，以及在UPF1网元的隧道端口41上配置了入口PDR2，同时更新后的组播组FAR1中增加将接收到的属于该组播组的组播报文复制后发送到该下游端口4上的规则。此外，在UPF2网元的隧道端口42(即图32中的(b)中的下游端口1)上配置了出口PDR1和出口FAR1，同时更新后的组播组FAR2中增加将接收到的属于该组播组的组播报文复制后发送到该下游端口1上的规则。
或者，示例性的，假设第一终端为终端4，第一终端加入组播组之前，组播组的配置示意图可以如图33中的(a)所示。其中，图33中的(a)中的终端4未加入组播组，因此仅是简单示意了一下终端4建立PDU会话之后，终端4接入的UPF1网元上的会话端口11和隧道端口41，以及与UPF1网元连接的UPF2网元上的隧道端口42和会话端口12，具体的PDU会话建立流程可参考图12所示的实施例，在此不再赘述。此时，假设会话端口标识11对应的下游端口为下游端口4，则第一终端加入组播组之后，在完成后续的步骤S2906-S2908的配置流程之后，组播组的配置示意图可以如图33中的(b)所示。即，在UPF1网元上的会话端口标识11对应的会话端口11(即图33中的(b)中的下游端口4)上配置了出口PDR4和出口FAR4，以及在UPF1网元的隧道端口41(即图33中的(b)中的上游端口2)上配置了入口PDR2，同时更新后的组播组FAR1中增加将接收到的属于该组播组的组播报文复制后发送到该下游端口4上的规则。此外，在UPF2网元的隧道端口42(即图33中的(b)中的下游端口1)上配置了出口PDR1和出口FAR1，在UPF2网元的会话端口12(即图33中的(b)中的上游端口1)上配置了入口PDR1，同时更新后的组播组FAR2中增加将接收到的属于该组播组的组播报文复制后发送到该下游端口1上的规则。
需要说明的是，根据上述的前置条件可知，本申请实施例提供的群组通信方法以组播成员为上述广播场景下5GLAN群组中已经入网的终端成员为例进行说明，因此在建立组播组时不需要建立UPF网元与UPF网元之间的隧道。当然，本申请实施例中的组播成员也可以不限定为上述广播场景下5GLAN群组中已经入网的终端成员，此时在组播组内的终端成员变化时(如本实施例中组播组的组播成员加入时，或者下述实施例中组播组的组播成员离开时，或者下述实施例中组播组的组播成员移动时)，可能需要建立UPF网元与UPF网元之间的隧道，以及在相应的UPF网元上创建隧道端口；或者，需要删除UPF网元与UPF网元之间的隧道，以及删除相应的用户面网元上的隧道端口，具体的实现方式可参考上述广播场景下的相关描述，本申请实施例对该场景不做详细说明。
S2906、GMF网元向SMF网元发送5GLAN服务响应消息。相应的，SMF网元接收来自GMF网元的5GLAN服务响应消息。
其中，该5GLAN服务响应消息携带UPF1网元的标识，与该UPF1网元的标识对应的下游端口的标识，应用在UPF1网元的该下游端口上的出口PDR和出口FAR，以及更新后的应用在UPF1网元上的组播组FAR1。
可选的，本申请实施例中，若组播源接入的UPF网元与UPF1网元不是同一个UPF网元，且目标UPF网元为存在组播组对应的上游端口的UPF网元，该5GLAN服务响应消息还可以携带与UPF1网元的标识对应的上游端口的标识，应用在UPF1网元的上游端口上的入口PDR，UPF1网元与目标UPF网元之间的每个UPF网元的标识；以及与相应的UPF网元的标识对应的下游端口的标识，应用在该下游端口上的出口PDR和出口FAR，上游端口的标识，应用在该上游端口上的入口PDR，更新后的应用在该UPF网元上的组播组FAR；以及目标UPF网元的标识，与目标UPF网元的标识对应的下游端口的标识，应用在该下游端口上的出口PDR和出口FAR，更新后的应用在该目标UPF网元上的组播组FAR。
或者，可选的，本申请实施例中，若组播源接入的UPF网元与UPF1网元不是同一个UPF网元，且目标UPF网元为组播源接入的UPF网元，该5GLAN服务响应消息还可以携带与UPF1网元的标识对应的上游端口的标识，应用在UPF1网元的上游端口上的入口PDR，UPF1网元与目标UPF网元之间的每个UPF网元的标识以及目标UPF网元的标识；以及与相应的UPF网元的标识对应的下游端口的标识，应用在该下游端口上的出口PDR和出口FAR，上游端口的标识，应用在该上游端口上的入口PDR，创建或更新后的应用在该UPF网元上的组播组FAR。
S2907、SMF网元根据UPF1网元的标识，向UPF1网元发送N4会话修改请求消息。相应的，UPF1网元接收来自SMF网元的N4会话修改请求消息。
其中，该N4会话修改请求消息包括与该UPF1网元的标识对应的下游端口的标识，应用在UPF1网元的该下游端口上的出口PDR和出口FAR，以及更新后的应用在UPF1网元上的组播组FAR1。
S2908、UPF1网元根据下游端口的标识以及应用在UPF1网元的该下游端口上的出口PDR和出口FAR，在UPF1网元的该下游端口上配置出口PDR和出口FAR；以及UPF1网元根据更新后的组播组FAR1，更新应用在UPF1网元上的组播组FAR1。
S2909、UPF1网元向SMF网元发送N4会话修改响应。相应的，SMF网元接收来自UPF1网元的N4会话修改响应。
其中，该N4会话修改响应消息用于通告N4会话修改和规则安装完成。
可选的，本申请实施例中，若组播源接入的UPF网元与UPF1网元不是同一个UPF网元，则上述N4会话修改请求消息还包括与UPF1网元的标识对应的上游端口的标识，以及应用在UPF1网元的上游端口上的入口PDR。相应的，UPF1网元还可以根据上游端口的标识以及应用在UPF1网元的该上游端口上的入口PDR，在UPF1网元的该上游端口上配置入口PDR。
可选的，本申请实施例中，若组播源接入的UPF网元与UPF1网元不是同一个UPF网元，且目标UPF网元为存在组播组对应的上游端口的UPF网元，则SMF网元还需要根据UPF1网元与目标UPF网元之间的每个UPF网元的标识，向相应的UPF网元发送对应的下游端口的标识，应用在该下游端口上的出口PDR和出口FAR，上游端口的标识，应用在该上游端口上的入口PDR，以及更新后的应用在该UPF网元上的组播组FAR。这样，每个UPF网元可以根据下游端口的标识以及应用在该下游端口上的出口PDR和出口FAR，在该UPF网元的下游端口上配置出口PDR和出口FAR；以及，每个UPF网元可以根据上游端口的标识和应用在该上游端口上的入口PDR，在该UPF网元的上游端口上配置入口PDR，以及每个UPF网元可以根据更新后的组播组FAR，更新应用在该UPF网元上的组播组FAR。
此外，SMF网元需要向目标UPF网元发送与目标UPF网元的标识对应的下游端口的标识，应用在该下游端口上的出口PDR和出口FAR，以及更新后的应用在该目标UPF网元上的组播组FAR。这样，目标UPF网元可以根据下游端口的标识以及应用在该下游端口上的出口PDR和出口FAR，在该目标UPF网元的下游端口上配置出口PDR和出口FAR；以及目标UPF网元可以根据更新后的组播组FAR，更新应用在该目标UPF网元上的组播组FAR。
可选的，本申请实施例中，若组播源接入的UPF网元与UPF1网元不是同一个UPF网元，且目标UPF网元为组播源接入的UPF网元，则SMF网元需要分别根据UPF1网元与目标UPF网元之间的每个UPF网元的标识以及目标UPF网元的标识，向对应的UPF网元发送与相应的UPF网元的标识对应的下游端口的标识，应用在该下游端口上的出口PDR和出口FAR，上游端口的标识，应用在该上游端口上的入口PDR，创建或更新后的应用在该UPF网元上的组播组FAR。这样，每个UPF网元可以根据下游端口的标识以及应用在该下游端口上的出口PDR和出口FAR，在该UPF网元的下游端口上配置出口PDR和出口FAR；以及，每个UPF网元可以根据上游端口的标识和应用在该上游端口上的入口PDR，在该UPF网元的上游端口上配置入口PDR，以及每个UPF网元可以根据更新后的组播组FAR，更新应用在该UPF网元上的组播组FAR。
基于上述群组通信方法，由于组播组的组播成员加入时，只需要调整(更新或创建)相关联的UPF网元上的组播组FAR，以及调整(创建)相关联的UPF网元上与该组播成员对应的入口PDR、出口PDR和出口FAR，或者调整(创建)相关联的UPF网元上与该组播成员对应的出口PDR和出口FAR即可，组播组内其他组播成员对应的入口PDR、出口PDR和出口FAR不发生改变。从而可以在组播组内的组播成员较多时，避免组播成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于组播成员数量的变化导致的配置工作量。
其中，上述步骤S2901至S2909中的GMF网元、SMF网元或UPF1网元的动作可以由图11所示的通信设备1100中的处理器1101调用存储器1103中存储的应用程序代码来执行，本实施例对此不作任何限制。
可选的，以图8所示的群组通信系统应用于如图9所示的5G网络，群组管理功能网元为GMF网元，会话管理网元为SMF网元(如第一会话管理网元为SMF1网元，第二会话管理网元为SMF2网元)，用户面网元为UPF网元(如第一用户面网元为UPF1网元，第二用户面网元为UPF2网元)，组播成员离开组播组的场景为例。则组播成员离开的场景下，可能存在以下两个情况(以将要离开的组播成员为第一终端为例)：
情况三、第一终端原来接入的UPF网元(假设为UPF3网元)上还有该组播组的其他组播成员或组播源，则：
步骤一，修改UPF3网元上的组播组FAR3，删除指向该组播成员的下游端口的规则。
步骤二，删除UPF3网元上该组播成员的下游端口的出口PDR和出口FAR。
情况四，第一终端原来接入的UPF网元(假设为UPF3网元)上没有该组播组的其他组播成员或组播源，则：
步骤一，删除UPF3网元上的组播组FAR3，删除UPF3网元上该组播成员的下游端口的出口PDR和出口FAR。
步骤二，删除UPF3网元上该组播成员的上游端口的入口PDR。
步骤三，修改UPF3网元的上游UPF网元上的组播组FAR，删除指向该组播成员关联的下游端口的规则；以及，删除UPF3网元的上游UPF网元上该组播成员关联的 下游端口的出口PDR和出口FAR。
步骤四，若UPF3网元的上游UPF网元上没有该组播组的其他组播成员或组播源，则循环执行上述步骤二和步骤三类似的步骤(区别在于针对的UPF网元不同)，直至某个上游UPF网元上有该组播组的其他组播成员或组播源或者直至组播源接入的UPF网元(可以视为目标UPF网元)。其中，若该目标UPF网元上有该组播组的其他组播成员，则对于该目标UPF网元执行上述步骤三类似的步骤(区别在于针对的UPF网元不同)之后结束；或者，若该目标UPF网元为组播源接入的UPF网元，则对于该UPF网元，还需要在执行上述步骤二和步骤三类似的步骤(区别在于针对的UPF网元不同)之后结束。
下面示例性的给出组播成员离开的场景下，本申请实施例提供的一种群组通信方法。如图34所示，该群组通信方法包括如下步骤：
前置条件，第一终端已经接入UPF3网元，UPF3网元上已创建该第一终端加入的组播组的配置，包括组播组FAR和相关的规则组，建立方法可参考图29所示的实施例，在此不再赘述；UPF2网元上也可能已创建该第一终端加入的组播组的配置，包括组播组FAR和相关的规则组，建立方法可参考图29所示的实施例。其中，UPF3网元和UPF2网元连通。
第一终端离开组播组的方式有两种，一种为第一终端发起会话释放流程，另一种为第一终端显式发起IGMP离开消息，宣告离开组播组。
其中，第一终端发起会话释放流程的方式包括如下步骤S3401a-S3403a：
S3401a、第一终端向AMF网元发送会话释放请求。相应的，AMF网元接收来自第一终端的会话释放请求。
S3402a、AMF网元向SMF网元发送SM上下文更新请求。相应的，SMF网元接收来自AMF网元的SM上下文更新请求。
可选的，上述SM上下文更新请求也可以替换为PDU会话更新请求，本申请实施例对此不作具体限定。
其中，上述步骤S3401a-S3402a的具体实现可参考现有的实现方式，在此不再赘述。
S3403a、若SMF网元确定第一终端发起了组播组通信，则SMF网元向GMF网元发送5GLAN服务更新请求(5GLAN service update request)。相应的，GMF网元接收来自SMF网元的5GLAN服务更新请求。
其中，该5GLAN服务更新请求用于请求GMF网元更新该组播组的转发信息。
或者，第一终端显式发起IGMP离开消息，宣告离开组播组的方式包括如下步骤S3401b-S3403b：
S3401b、第一终端通过接入设备向UPF3网元发送IGMP离开消息。相应的，UPF3网元接收来自第一终端的IGMP离开消息。
其中，该IGMP离开消息包括组播组的地址。
需要说明的是，本申请实施例中，第一终端仅作为组播成员才会向UPF3网元发送IGMP离开消息，而组播源或者非组播组的成员不会向UPF3网元发送IGMP离开消息，在此统一说明，以下不再赘述。
其中，第一终端获取组播组的地址的方式可参考现有的实现方式，在此不再赘述。
S3402b、UPF3网元识别IGMP离开消息，进而向连接的SMF网元发送该IGMP离开消息。相应的，SMF网元接收来自UPF1网元的IGMP离开消息。
其中，本申请实施例中，IGMP离开消息可以是携带在UPF3网元向SMF网元发送的N4接口消息中发送给SMF网元的，本申请实施例对此不作具体限定。
S3403b、SMF网元识别是IGMP消息，同时通过SMF网元上存储的第一终端的上下文，发现第一终端之前加入了组播通信，于是获知第一终端即将离开加入的组播组，进而向GMF网元发送5GLAN服务更新请求。相应的，GMF网元接收来自SMF网元的5GLAN服务更新请求。
其中，该5GLAN服务更新请求携带IGMP离开消息和第一终端的标识。
可选的，该5GLAN服务更新请求可以携带UPF3网元的标识以及会话端口标识13。
基于上述步骤S3401a-S3403a或S3401b-S3403b，GMF网元可以获知第一终端即将离开所在的组播组，进而可以继续执行下述步骤：
S3404、GMF网元根据GMF网元上存储的该组播组的上下文信息，调整UPF3网元及上游各UPF网元上的组播转发规则。调整方法如本流程之前的描述，在此不再赘述。
其中，对应的上游端口或下游端口的确定方式可参考图29所示的实施例，在此不再赘述。
S3405、对应上述方式A的流程，GMF网元向SMF网元发送5GLAN服务释放响应。相应的，SMF网元接收来自GMF网元的5GLAN服务释放响应。或者，对应上述方式B的流程，GMF网元向SMF网元发送5GLAN服务更新响应。相应的，SMF网元接收来自GMF网元的5GLAN服务更新响应。
其中，该5GLAN服务释放响应或5GLAN服务更新响应中包括需要调整组播组配置信息的UPF网元的标识，以及与相应UPF网元的标识对应的组播组配置调整信息。比如，在通过会话释放流程离开时，需要删除某个UPF网元的上游端口的入口PDR时，该组播组配置调整信息包括该上游端口的标识，用于删除该上游端口，以及该上游端口上的入口PDR；或者，需要删除某个UPF网元的下游端口的出口PDR和出口FAR时，该组播组配置调整信息包括该下游端口的标识，用于删除该下游端口，以及该下游端口上的该入口PDR；或者，需要删除某个UPF网元上的组播组FAR时，该组播组配置调整信息包括该组播组FAR的标识；或者，需要更新某个UPF网元上的组播组FAR时，该组播组配置调整信息包括更新后的组播组FAR。
可选的，本申请实施例中，在删除上游端口或下游端口时，可选的，需要同时删除PDU会话建立过程中创建的该上游端口或下游端口上的规则组，在此统一说明，以下不再赘述。
或者，比如，在通过IGMP离开消息方式离开时，需要删除某个UPF网元的上游端口的入口PDR时，该组播组配置调整信息包括该上游端口的标识以及应用在该上游端口上的入口PDR的标识；或者，需要删除某个UPF网元的下游端口的出口PDR和出口FAR时，该组播组配置调整信息包括该下游端口的标识，以及应用在该下游端口 上的出口PDR的标识，可选的可以携带该出口PDR所指示的出口FAR的标识；或者，需要删除某个UPF网元上的组播组FAR时，该组播组配置调整信息包括该组播组FAR的标识；或者，需要更新某个UPF网元上的组播组FAR时，该组播组配置调整信息包括更新后的组播组FAR。
S3406、SMF网元根据需要调整组播组配置信息的UPF网元的标识，以及与相应UPF网元的标识对应的组播组配置调整信息，向对应的UPF网元发送与该UPF网元的标识对应的组播组配置调整信息。这里示例性的以SMF网元与UPF3网元通信为例进行说明。则SMF网元根据UPF3网元的标识，向UPF3网元发送N4会话修改请求。相应的，UPF3网元接收来自SMF网元的N4会话修改请求。
其中，该N4会话修改请求包括与UPF3网元的标识对应的组播组配置调整信息。比如，在通过会话释放流程离开时，与UPF3网元的标识对应的组播组配置调整信息例如可以包括与该UPF3网元的标识对应的下游端口的标识。可选的，在UPF3网元上还有该组播组的其他组播成员或组播源的情况下，与UPF3网元的标识对应的组播组配置调整信息例如还可以包括更新后的应用在UPF3网元上的组播组FAR3。或者，可选的，在UPF3网元上没有该组播组的其他组播成员或组播源的情况下，与UPF3网元的标识对应的组播组配置调整信息例如还可以包括应用在UPF3网元上的组播组FAR3的标识、与该UPF3网元的标识对应的上游端口的标识。
或者，比如，在通过IGMP离开消息方式离开时，与UPF3网元的标识对应的组播组配置调整信息例如可以包括与该UPF3网元的标识对应的下游端口的标识，以及应用在UPF3网元的下游端口上的出口PDR的标识，可选的包括该出口PDR所指示的出口FAR的标识。可选的，在UPF3网元上还有该组播组的其他组播成员或组播源的情况下，与UPF3网元的标识对应的组播组配置调整信息例如还可以包括更新后的应用在UPF3网元上的组播组FAR3。或者，可选的，在UPF3网元上没有该组播组的其他组播成员或组播源的情况下，与UPF3网元的标识对应的组播组配置调整信息例如还可以包括应用在UPF3网元上的组播组FAR3的标识、与该UPF3网元的标识对应的上游端口的标识，以及应用在UPF3网元的上游端口上的入口PDR的标识。
S3407、UPF3网元根据组播组配置调整信息，调整UPF3网元上的组播组配置。
示例性的，在通过IGMP离开消息方式离开时，UPF3网元可以根据下游端口的标识，以及应用在该下游端口上的出口PDR的标识，删除应用在UPF3网元的该下游端口的出口PDR的标识对应的出口PDR，以及出口PDR所指示的出口FAR。
或者，示例性的，在通过会话释放流程离开时，UPF3网元可以根据下游端口的标识，删除该下游端口以及该下游端口的出口PDR和出口FAR。
可选的，在UPF3网元上还有该组播组的其他组播成员或组播源的情况下，UPF3网元根据更新后的应用在UPF3网元上的组播组FAR3，更新应用在UPF3网元上的组播组FAR3。
或者，可选的，在UPF3网元上没有该组播组的其他组播成员或组播源的情况下，UPF3网元根据应用在UPF3网元上的组播组FAR3的标识，删除应用在UPF3网元上的组播组FAR3；以及，在通过IGMP离开消息方式离开时，UPF3网元根据上游端口的标识，以及应用在该上游端口上的入口PDR的标识，删除应用在UPF3网元的该上 游端口的该入口PDR的标识对应的入口PDR；在通过会话释放流程离开时，UPF3网元根据上游端口的标识，删除该上游端口以及该上游端口上的入口PDR。
S3408、UPF3网元向SMF网元发送N4会话修改响应。相应的，SMF网元接收来自UPF1网元的N4会话修改响应。
其中，该N4会话修改响应消息用于通告配置更新完成。
需要说明的是，上述步骤S3406-S3408示例性的以UPF3网元上的组播组配置更新流程为例进行说明。需要调整组播组配置信息的其他UPF网元上的组播组配置更新流程可参考上述步骤S3406-S3408，在此不再赘述。
示例性的，假设第一终端为终端3，第一终端未离开组播组之前，组播组的配置示意图可以如图35中的(a)所示。此时，根据上述流程，假设下游端口3对应会话端口33，则在第一终端离开组播组之后，组播组的配置示意图可以如图35中的(b)所示。可以看出，图35中的(a)所示的下游端口3上的出口PDR3和出口FAR3被删除。同时更新后的组播组FAR3中删除将接收到的属于该组播组的组播报文复制后发送到该下游端口3(即会话端口33)上的规则。需要说明的是，由于图35中的(b)中的终端3未加入组播组，因此仅是简单示意了一下终端3建立PDU会话之后，终端3接入的UPF3网元上的会话端口33，具体的PDU会话建立流程可参考图12所示的实施例，在此不再赘述。
或者，示例性的，假设第一终端为终端4，第一终端离开组播组之前，组播组的配置示意图可以如图36中的(a)所示。此时，根据上述流程，假设下游端口4对应会话端口43，则在第一终端离开组播组之后，组播组的配置示意图可以如图36中的(b)所示。可以看出，图36中的(a)所示的UPF3网元的下游端口4上的出口PDR4和出口FAR4被删除；图36中的(a)所示的UPF3网元的上游端口2上的入口PDR2被删除。图36中的(a)所示的UPF2网元的下游端口1上的出口PDR1和出口FAR1被删除。此外，应用在UPF3网元上的组播组FAR3被删除，应用在UPF2网元上的更新后的组播组FAR2中删除将接收到的属于该组播组的组播报文复制后发送到该下游端口1上的规则。需要说明的是，由于图36中的(b)中的终端4未加入组播组，因此仅是简单示意了一下终端4建立PDU会话之后，终端4接入的UPF3网元上的会话端口43和隧道端口41，以及与UPF1网元连接的UPF2网元上的隧道端口42，具体的PDU会话建立流程可参考图12所示的实施例，在此不再赘述。
或者，示例性的，假设第一终端为终端4，第一终端加入组播组之前，组播组的配置示意图可以如图37中的(a)所示。此时，根据上述流程，假设下游端口4对应会话端口43，则在第一终端离开组播组之后，组播组的配置示意图可以如图37中的(b)所示。可以看出，图37中的(a)所示的UPF3网元的下游端口4上的出口PDR4和出口FAR4被删除；图37中的(a)所示的UPF3网元的上游端口2上的入口PDR2被删除。图37中的(a)所示的UPF2网元的下游端口1上的出口PDR1和出口FAR1被删除；图37中的(a)所示的UPF2网元的上游端口1上的入口PDR1被删除。此外，应用在UPF3网元上的组播组FAR3被删除，应用在UPF2网元上的组播组FAR2被删除。需要说明的是，由于图37中的(b)中的终端4未加入组播组，因此仅是简单示意了一下终端4建立PDU会话之后，终端4接入的UPF3网元上的会话端口43 和隧道端口41，以及与UPF1网元连接的UPF2网元上的隧道端口42和会话端口12，具体的PDU会话建立流程可参考图12所示的实施例，在此不再赘述。
基于上述群组通信方法，由于组播组的组播成员离开时，只需要调整(更新或删除)相关联的UPF网元上的组播组FAR，以及调整(删除)相关联的UPF网元上与该组播成员对应的入口PDR、出口PDR和出口FAR，或者调整(删除)相关联的UPF网元上与该组播成员对应的出口PDR和出口FAR即可，组播组内其他组播成员对应的入口PDR、出口PDR和出口FAR不发生改变。从而可以在组播组内的组播成员较多时，避免组播成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于组播成员数量的变化导致的配置工作量。
其中，上述步骤S3401至S3408中的GMF网元、SMF网元或UPF3网元的动作可以由图11所示的通信设备1100中的处理器1101调用存储器1103中存储的应用程序代码来执行，本实施例对此不作任何限制。
可选的，以图8所示的群组通信系统应用于如图9所示的5G网络，群组管理功能网元为GMF网元，会话管理网元为SMF网元(如第一会话管理网元为SMF1网元，第二会话管理网元为SMF2网元)，用户面网元为UPF网元(如第一用户面网元为UPF1网元，第二用户面网元为UPF2网元)，组播成员移动的场景为例。则组播成员移动的场景下，可能存在以下几种情况(以将要离开的组播成员为第一终端，第一终端原来接入的UPF网元为UPF3网元，新选择的UPF网元为UPF1网元为例)：
情况一、第一终端新选择的UPF网元(假设为UPF1网元)上有该组播组的其他组播成员或组播源，则：
步骤一，修改UPF1网元上的组播组FAR1，增加指向该组播成员的下游端口的规则。
步骤二，配置应用在UPF1网元上该组播成员的下游端口的出口PDR和出口FAR。
情况二，第一终端新选择的UPF网元(假设为UPF1网元)上没有该组播组的其他组播成员或组播源，则：
步骤一，配置应用在UPF1网元上的组播组FAR1，以及配置应用在UPF1网元上该组播成员的下游端口的出口PDR和出口FAR，组播组FAR1中包括指向该组播成员的下游端口的规则。
步骤二，配置应用在UPF1网元上该组播成员的上游端口的入口PDR。
步骤三，更新UPF1网元的上游UPF网元上的组播组FAR，增加指向该组播成员关联的下游端口的规则；以及，配置应用在UPF1网元的上游UPF网元上该组播成员关联的下游端口的出口PDR和出口FAR。
步骤四，若UPF1网元的上游UPF网元上没有该组播组的其他组播成员或组播源，则循环执行上述步骤二和步骤三类似的步骤(区别在于针对的UPF网元不同)，直至某个上游UPF网元上有该组播组的其他组播成员或组播源或者直至组播源接入的UPF网元(可以视为目标UPF网元)。其中，若该目标UPF网元上有该组播组的其他组播成员，则对于该目标UPF网元执行上述步骤三类似的步骤(区别在于针对的UPF网元不同)之后结束；或者，若该目标UPF网元为组播源接入的UPF网元，则对于该UPF网元，还需要在执行上述步骤二和步骤三类似的步骤(区别在于针对的UPF 网元不同)之后结束。
情况三、第一终端原来接入的UPF网元(假设为UPF3网元)上还有该组播组的其他组播成员或组播源，则：
步骤一，修改UPF3网元上的组播组FAR3，删除指向该组播成员的下游端口的规则。
步骤二，删除UPF3网元上该组播成员的下游端口的出口PDR和出口FAR。
情况四，第一终端原来接入的UPF网元(假设为UPF3网元)上没有该组播组的其他组播成员或组播源，则：
步骤一，删除UPF3网元上的组播组FAR3，删除UPF3网元上该组播成员的下游端口的出口PDR和出口FAR。
步骤二，删除UPF3网元上该组播成员的上游端口的入口PDR。
步骤三，修改UPF3网元的上游UPF网元上的组播组FAR，删除指向该组播成员关联的下游端口的规则；以及，删除UPF3网元的上游UPF网元上该组播成员关联的下游端口的出口PDR和出口FAR。
步骤四，若UPF3网元的上游UPF网元上没有该组播组的其他组播成员或组播源，则循环执行上述步骤二和步骤三类似的步骤(区别在于针对的UPF网元不同)，直至某个上游UPF网元上有该组播组的其他组播成员或组播源或者直至组播源接入的UPF网元(可以视为目标UPF网元)。其中，若该目标UPF网元上有该组播组的其他组播成员，则对于该目标UPF网元执行上述步骤三类似的步骤(区别在于针对的UPF网元不同)之后结束；或者，若该目标UPF网元为组播源接入的UPF网元，则对于该UPF网元，还需要在执行上述步骤二和步骤三类似的步骤(区别在于针对的UPF网元不同)之后结束。
其中，本申请实施例中，组播成员移动的场景下，可能包括上述情况一和情况三，或者包括上述情况一和情况四，或者包括上述情况二和情况三，或者包括上述情况二和情况四。其中，其中情况一和情况二的相关实现可参考图29所示的实施例，情况三和情况四的相关实现可参考图34所示的实施例，区别在于网元之间交互的信令流程等不同，在此不再详细阐述。
此外，组播成员移动的场景下对应的网元之间交互的信令流程与广播场景下5GLAN群组内已经入网的终端成员移动的场景下对应的网元之间交互的信令流程类似，相关描述可参考图16所示的实施例，在此不再赘述。
基于上述群组通信方法，由于组播组的组播成员移动时，只需要调整(创建、更新或删除)相关联的UPF网元上的组播组FAR，以及调整(创建、更新或删除)相关联的UPF网元上与该组播成员对应的入口PDR、出口PDR和出口FAR，或者调整(创建、更新或删除)相关联的UPF网元上与该组播成员对应的出口PDR和出口FAR即可，组播组内其他组播成员对应的入口PDR、出口PDR和出口FAR不发生改变。从而可以在组播组内的组播成员较多时，避免组播成员数量的变化导致的配置工作量将大幅增加的问题，大大减少了由于组播成员数量的变化导致的配置工作量。
其中，上述图29至图37分别示例性的给出了组播场景下，组播组内的终端成员发生变化时(如加入组播组，离开组播组，在组播组内移动)对应的群组通信方法， 主要以控制面的配置为主进行说明。下面给出用户面网元如何转发群组组播报文的相关说明如下。
其中，用户面网元转发群组组播报文的方式与上述用户面网元转发群组广播报文的方式类似，区别在于：广播场景下的入口PDR用于识别属于某个LAN群组的广播报文，组播场景下的入口PDR用于识别属于某个组播组的组播报文。其中，组播报文的识别方式可参考前述组播介绍部分，在此不再赘述。
需要说明的是，上述组播场景均是示例性的以组播成员的调整为例进行说明。当然，本申请实施例也可以应用于组播源移动的场景下，本申请实施例对此不作具体限定。
此外，一种可能的实现方式中，在组播源移动的场景下，以移动的组播源为第一终端，第一终端原来接入的UPF网元为UPF3网元，第一终端对应UPF3网元上的会话端口3，新选择的UPF网元为UPF1网元，第一终端对应UPF1网元上的会话端口1为例，则GMF网元在确定发生移动的第一终端为组播源之后，可以向SMF网元请求建立UPF1网元到UPF3网元的隧道。GMF网元获得隧道标识之后，可以生成应用在UPF1网元的会话端口1的入口上的转发规则PDR1和FAR1，其中PDR1用于判断第一终端发出的报文属于该组播组的报文，FAR1用于将该组播报文转发到与UPF3网元相连的隧道端口上。同时GMF网元生成应用在UPF3网元的隧道端口的入口上的规则PDR3，其中PDR3用于识别接收到的报文属于该组播组的报文，并在PDR3中将FAR ID设置为UPF3网元上的组播FAR。
此外，需要说明的是，本申请上述实施例均是示例性的以入口PDR用于识别报文属于某个群组的广播报文或组播报文为例进行说明。可选的，本申请实施例中，也可以将上述入口PDR的功能进行拆分，比如如图38所示，在入口(例如可以是入口PDR)只识别群组，识别后交给指定模块处理。比如，群组内单播、组播和广播的识别由群组的group PDR来完成，报文的转发由group FAR完成，本申请实施例对此不作具体限定。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述群组管理功能网元或用户面网元或会话管理网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对群组管理功能网元或用户面网元或会话管理网元进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，图39示出了一种群组管理 功能网元390的结构示意图。该群组管理功能网元390包括收发模块3902和处理模块3901。处理模块3901，用于在第一终端发起接入局域网群组的情况下，获取第一终端即将接入的第一用户面网元的标识、局域网群组的上下文信息以及第一会话端口标识，其中，上下文信息中包括局域网群组的终端成员列表中当前已经接入局域网群组的终端所接入的用户面网元的标识列表，第一会话端口标识为第一用户面网元上用于第一终端接入的第一会话端口的标识。处理模块3901，还用于为局域网群组创建应用在第一会话端口上的规则组；以及，群组管理功能网元根据上下文信息，为局域网群组创建或更新应用在第一用户面网元上的局域网群组FAR；其中，规则组中包括入口PDR，出口PDR和出口FAR；出口PDR中包括出口FAR的标识，入口PDR中包括局域网群组FAR的标识；其中，入口PDR用于识别属于局域网群组的广播报文，局域网群组FAR用于将广播报文复制后转发到指定的出口；出口PDR用于识别广播报文的类型，出口FAR用于对广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去。收发模块3902，用于向会话管理网元发送第一消息，第一消息用于在第一用户面网元的第一会话端口上配置规则组，以及在第一用户面网元上配置或更新局域网群组FAR。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该群组管理功能网元390以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该群组管理功能网元390可以采用图11所示的形式。
比如，图11中的处理器1101可以通过调用存储器1103中存储的计算机执行指令，使得群组管理功能网元390执行上述方法实施例中的群组通信方法。
具体的，图39中的收发模块3902和处理模块3901的功能/实现过程可以通过图11中的处理器1101调用存储器1103中存储的计算机执行指令来实现。或者，图39中的处理模块3901的功能/实现过程可以通过图11中的处理器1101调用存储器1103中存储的计算机执行指令来实现，图39中的收发模块3902的功能/实现过程可以通过图11中的通信接口1104来实现。
由于本实施例提供的群组管理功能网元390可执行上述群组通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例还提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持群组管理功能网元实现上述群组通信方法。例如为局域网群组创建应用在所述第一会话端口上的规则组。在一种可能的设计中，该装置还包括存储器。该存储器，用于保存群组管理功能网元必要的程序指令和数据。当然，存储器也可以不在该装置中。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
或者，比如，以采用集成的方式划分各个功能模块的情况下，图40示出了一种第一用户面网元400的结构示意图。该第一用户面网元400包括收发模块4002和处理模 块4001。收发模块4002，用于在第一终端发起接入局域网群组的情况下，接收来自会话管理网元的第一消息，第一消息包括第一会话端口标识，应用在第一会话端口标识对应的第一会话端口上的规则组、以及创建或更新后的应用在第一用户面网元上的局域网群组FAR，其中，第一会话端口标识为第一用户面网元上用于第一终端接入的第一会话端口的标识；规则组中包括入口PDR，出口PDR和出口FAR；出口PDR中包括出口FAR的标识，入口PDR中包括局域网群组FAR的标识；其中，入口PDR用于识别属于局域网群组的广播报文，局域网群组FAR用于将广播报文复制后转发到指定的出口；出口PDR用于识别广播报文的类型，出口FAR用于对广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；处理模块4001，用于根据第一会话端口标识创建第一会话端口，并在第一会话端口上配置规则组；以及，处理模块4001，用于根据创建的应用在第一用户面网元上的局域网群组FAR，在第一用户面网元上创建局域网群组FAR；或者，第一用户面网元根据更新后的应用在第一用户面网元上的局域网群组FAR，更新第一用户面网元上的局域网群组FAR。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该第一用户面网元400以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该第一用户面网元400可以采用图11所示的形式。
比如，图11中的处理器1101可以通过调用存储器1103中存储的计算机执行指令，使得第一用户面网元400执行上述方法实施例中的群组通信方法。
具体的，图40中的收发模块4002和处理模块4001的功能/实现过程可以通过图11中的处理器1101调用存储器1103中存储的计算机执行指令来实现。或者，图40中的处理模块4001的功能/实现过程可以通过图11中的处理器1101调用存储器1103中存储的计算机执行指令来实现，图40中的收发模块4002的功能/实现过程可以通过图11中的通信接口1104来实现。
由于本实施例提供的第一用户面网元400可执行上述群组通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例还提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持第一用户面网元实现上述群组通信方法。例如根据第一会话端口标识创建第一会话端口，并在第一会话端口上配置规则组。在一种可能的设计中，该装置还包括存储器。该存储器，用于保存第一用户面网元必要的程序指令和数据。当然，存储器也可以不在该装置中。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
或者，比如，以采用集成的方式划分各个功能模块的情况下，图41示出了一种会话管理网元410的结构示意图。该会话管理网元410包括接收模块4102和发送模块4101。接收模块4102，用于在第一终端发起接入局域网群组的情况下，接收来自群组管理功能网元的第一消息，第一消息包括第一用户面网元的标识、与第一用户面网元 的标识对应的第一会话端口标识，应用在第一会话端口标识对应的第一会话端口上的规则组、以及创建或更新后的应用在第一用户面网元上的局域网群组FAR，其中，第一会话端口为第一用户面网元上用于第一终端接入的会话端口；规则组中包括入口PDR，出口PDR和出口FAR；出口PDR中包括出口FAR的标识，入口PDR中包括局域网群组FAR的标识；其中，入口PDR用于识别属于局域网群组的广播报文，局域网群组FAR用于将广播报文复制后转发到指定的出口；出口PDR用于识别广播报文的类型，出口FAR用于对广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去。发送模块4101，用于根据第一用户面网元的标识，向第一用户面网元发送第二消息，第二消息包括第一会话端口标识，第一会话端口上的规则组、以及创建或更新后的应用在第一用户面网元上的局域网群组FAR。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该会话管理网元410以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该会话管理网元410可以采用图11所示的形式。
比如，图11中的处理器1101可以通过调用存储器1103中存储的计算机执行指令，使得会话管理网元410执行上述方法实施例中的群组通信方法。
具体的，图41中的接收模块4102和发送模块4101的功能/实现过程可以通过图11中的处理器1101调用存储器1103中存储的计算机执行指令来实现。或者，图41中的接收模块4102和发送模块4101的功能/实现过程可以通过图11中的通信接口1104来实现。
由于本实施例提供的会话管理网元410可执行上述群组通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例还提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持会话管理网元实现上述群组通信方法。例如根据第一用户面网元的标识确定第一用户面网元。在一种可能的设计中，该装置还包括存储器。该存储器，用于保存会话管理网元必要的程序指令和数据。当然，存储器也可以不在该装置中。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中 心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (44)

  1. 一种群组通信方法，其特征在于，所述方法包括：
    在第一终端发起接入局域网群组的情况下，群组管理功能网元获取所述第一终端即将接入的第一用户面网元的标识、所述局域网群组的上下文信息以及第一会话端口标识，其中，所述上下文信息中包括所述局域网群组的终端成员列表中当前已经接入所述局域网群组的终端所接入的用户面网元的标识列表，所述第一会话端口标识为所述第一用户面网元上用于所述第一终端接入的第一会话端口的标识；
    所述群组管理功能网元为局域网群组创建应用在所述第一会话端口上的规则组；以及，所述群组管理功能网元根据所述上下文信息，为所述局域网群组创建或更新应用在所述第一用户面网元上的局域网群组转发动作规则FAR；其中，所述规则组中包括入口分组检测规则PDR，出口PDR和出口FAR；所述出口PDR中包括所述出口FAR的标识，所述入口PDR中包括所述局域网群组FAR的标识；其中，所述入口PDR用于识别属于所述局域网群组的广播报文，所述局域网群组FAR用于将所述广播报文复制后转发到指定的出口；所述出口PDR用于识别所述广播报文的类型，所述出口FAR用于对所述广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；
    所述群组管理功能网元向会话管理网元发送第一消息，所述第一消息用于在所述第一会话端口上配置所述规则组，以及在所述第一用户面网元上配置或更新所述局域网群组FAR。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述标识列表中包括第二用户面网元的标识，且所述第一用户面网元的标识不在所述标识列表中的情况下，所述群组管理功能网元获取第一隧道端口标识和第二隧道端口标识，所述第一隧道端口标识为第一隧道在所述第一用户面网元上的第一隧道端口的标识，所述第二隧道端口标识为所述第一隧道在所述第二用户面网元上的第二隧道端口的标识，所述第一隧道为所述第一用户面网元和所述第二用户面网元之间的隧道；
    所述群组管理功能网元为所述局域网群组创建应用在所述第一隧道端口上的所述规则组，以及，所述群组管理功能网元为所述局域网群组创建应用在所述第二隧道端口上的所述规则组，以及，所述群组管理功能网元更新应用在所述第二用户面网元上的所述局域网群组FAR；
    相应的，所述第一消息还用于在所述第一隧道端口上配置所述规则组；以及在所述第二隧道端口上配置所述规则组，以及在所述第二用户面网元上更新所述局域网群组FAR。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    在所述第一终端在所述局域网群组内从接入所述第一用户面网元更新为接入第三用户面网元的情况下，所述群组管理功能网元获取第三会话端口标识，所述第三会话端口标识为所述第三用户面网元上用于所述第一终端接入的第三会话端口的标识；
    所述群组管理功能网元为所述局域网群组创建应用在所述第三会话端口上的规则组；以及，所述群组管理功能网元根据所述上下文信息，创建或更新应用在所述第三用户面网元上的所述局域网群组FAR；
    所述群组管理功能网元向所述会话管理网元发送第三消息，所述第三消息用于在所述第三会话端口上配置所述规则组，以及在所述第三用户面网元上配置或更新所述局域网群组FAR，以及删除所述第一会话端口上的所述规则组，以及删除或更新应用在所述第一用户面网元上的所述局域网群组FAR，其中，更新后的应用在所述第一用户面网元上的所述局域网群组FAR是所述群组管理功能网元根据所述上下文信息，更新应用在所述第一用户面网元上的所述局域网群组FAR得到的。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    在所述标识列表中包括第四用户面网元的标识，且所述第一用户面网元上没有所述局域网群组的终端成员列表中除所述第一终端之外的其他终端接入的情况下，所述群组管理功能网元更新应用在所述第四用户面网元上的所述局域网群组FAR；
    相应的，所述第三消息还用于删除所述第一用户面网元和所述第四用户面网元之间的第二隧道，以及，删除所述第一用户面网元的第三隧道端口上的所述规则组，以及删除所述第四用户面网元的第四隧道端口上的所述规则组，以及更新应用在所述第四用户面网元上的所述局域网群组FAR，其中，所述第三隧道端口为所述第二隧道在所述第一用户面网元上的隧道端口，所述第四隧道端口为所述第二隧道在所述第四用户面网元上的隧道端口。
  5. 根据权利要求3或4所述的方法，其特征在于，所述方法还包括：
    在所述标识列表中包括第四用户面网元的标识，且所述第三用户面网元的标识不在所述标识列表中的情况下，所述群组管理功能网元获取第五隧道端口标识和第六隧道端口标识，所述第五隧道端口标识为第三隧道在所述第三用户面网元上的第五隧道端口的标识，所述第六隧道端口标识为所述第三隧道在所述第四用户面网元上的第六隧道端口的标识，所述第三隧道为所述第三用户面网元和所述第四用户面网元之间的隧道；
    所述群组管理功能网元为所述局域网群组创建应用在所述第五隧道端口上的所述规则组，以及，所述群组管理功能网元为所述局域网群组创建应用在所述第六隧道端口上的所述规则组，以及，所述群组管理功能网元更新应用在所述第四用户面网元上的所述局域网群组FAR；
    相应的，所述第三消息还用于在所述第五隧道端口上配置所述规则组；以及在所述第六隧道端口上配置所述规则组，以及在所述第四用户面网元上更新所述局域网群组FAR。
  6. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    在所述第一终端将离开所述局域网群组的情况下，所述群组管理功能网元向所述会话管理网元发送第五消息，所述第五消息用于删除应用在所述第一会话端口上的所述规则组，以及删除或更新应用在所述第一用户面网元上的所述局域网群组FAR，其中，更新后的应用在所述第一用户面网元上的所述局域网群组FAR是所述群组管理功能网元根据所述上下文信息，更新应用在所述第一用户面网元上的所述局域网群组FAR得到的。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    在所述标识列表中包括第五用户面网元的标识，且所述第一用户面网元上没有所 述局域网群组的终端成员列表中除所述第一终端之外的其他终端接入的情况下，所述群组管理功能网元更新应用在所述第五用户面网元上的所述局域网群组FAR；
    相应的，所述第五消息还用于删除所述第一用户面网元和所述第五用户面网元之间的第四隧道，以及，删除所述第一用户面网元的第七隧道端口上的所述规则组，以及删除所述第五用户面网元的第八隧道端口上的所述规则组，以及更新应用在所述第五用户面网元上的所述局域网群组FAR，其中，所述第七隧道端口为所述第四隧道在所述第一用户面网元上的隧道端口，所述第八隧道端口为所述第四隧道在所述第五用户面网元上的隧道端口。
  8. 一种群组通信方法，其特征在于，所述方法包括：
    在第一终端发起接入局域网群组的情况下，第一用户面网元接收来自会话管理网元的第一消息，所述第一消息包括第一会话端口标识，应用在所述第一会话端口标识对应的第一会话端口上的规则组、以及创建或更新后的应用在所述第一用户面网元上的局域网群组转发动作规则FAR，其中，所述第一会话端口标识为所述第一用户面网元上用于所述第一终端接入的第一会话端口的标识；所述规则组中包括入口分组检测规则PDR，出口PDR和出口FAR；所述出口PDR中包括所述出口FAR的标识，所述入口PDR中包括所述局域网群组FAR的标识；其中，所述入口PDR用于识别属于所述局域网群组的广播报文，所述局域网群组FAR用于将所述广播报文复制后转发到指定的出口；所述出口PDR用于识别所述广播报文的类型，所述出口FAR用于对所述广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；
    所述第一用户面网元根据所述第一会话端口标识创建所述第一会话端口，并在所述第一会话端口上配置所述规则组；
    以及，所述第一用户面网元根据创建的应用在所述第一用户面网元上的局域网群组FAR，在所述第一用户面网元上创建所述局域网群组FAR；或者，所述第一用户面网元根据更新后的应用在所述第一用户面网元上的局域网群组FAR，更新所述第一用户面网元上的所述局域网群组FAR。
  9. 根据权利要求8所述的方法，其特征在于，所述第一消息还包括第一隧道端口标识和应用在所述第一隧道端口标识对应的第一隧道端口上的所述规则组，其中，所述第一隧道端口标识为第一隧道在所述第一用户面网元上的第一隧道端口的标识，所述第一隧道为所述第一用户面网元和第二用户面网元之间的隧道；所述方法还包括：
    所述第一用户面网元根据所述第一隧道端口标识创建所述第一隧道端口，并在所述第一隧道端口上配置所述规则组。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    在所述第一终端不再由所述第一用户面网元提供服务的情况下，所述第一用户面网元接收来自所述会话管理网元的第二消息，所述第二消息包括所述第一会话端口标识，以及所述第二消息包括应用在所述第一用户面网元上的所述局域网群组FAR的标识或者更新后的应用在所述第一用户面网元上的所述局域网群组FAR；
    所述第一用户面网元根据所述第一会话端口标识，删除所述第一会话端口和应用在所述第一会话端口的所述规则组；以及，
    所述第一用户面网元根据应用在所述第一用户面网元上的所述局域网群组FAR 的标识，删除应用在所述第一用户面网元上的所述局域网群组FAR；或者，所述第一用户面网元根据更新后的应用在所述第一用户面网元上的所述局域网群组FAR，更新所述第一用户面网元上的所述局域网群组FAR。
  11. 根据权利要求10所述的方法，其特征在于，所述第二消息还包括第一隧道端口标识，其中，所述第一隧道端口标识为第一隧道在所述第一用户面网元上的第一隧道端口的标识，所述第一隧道为所述第一用户面网元和第二用户面网元之间的隧道；所述方法还包括：
    所述第一用户面网元根据所述第一隧道端口标识，删除所述第一隧道端口和应用在所述第一隧道端口的所述规则组。
  12. 一种群组通信方法，其特征在于，所述方法包括：
    在第一终端发起接入局域网群组的情况下，会话管理网元接收来自群组管理功能网元的第一消息，所述第一消息包括第一用户面网元的标识、与所述第一用户面网元的标识对应的第一会话端口标识，应用在所述第一会话端口标识对应的第一会话端口上的规则组、以及创建或更新后的应用在所述第一用户面网元上的局域网群组转发动作规则FAR，其中，所述第一会话端口为所述第一用户面网元上用于所述第一终端接入的会话端口；所述规则组中包括入口分组检测规则PDR，出口PDR和出口FAR；所述出口PDR中包括所述出口FAR的标识，所述入口PDR中包括所述局域网群组FAR的标识；其中，所述入口PDR用于识别属于所述局域网群组的广播报文，所述局域网群组FAR用于将所述广播报文复制后转发到指定的出口；所述出口PDR用于识别所述广播报文的类型，所述出口FAR用于对所述广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；
    所述会话管理网元根据所述第一用户面网元的标识，向所述第一用户面网元发送第二消息，所述第二消息包括所述第一会话端口标识，所述第一会话端口上的规则组、以及创建或更新后的应用在所述第一用户面网元上的局域网群组FAR。
  13. 根据权利要求12所述的方法，其特征在于，所述第一消息还包括与所述第一用户面网元的标识对应的第一隧道端口标识和应用在所述第一隧道端口标识对应的第一隧道端口上的所述规则组，以及第二用户面网元的标识、与第二用户面网元的标识对应的第二隧道端口标识、应用在所述第二隧道端口标识对应的第二隧道端口上的所述规则组、和更新后的应用在所述第二用户面网元上的局域网群组FAR；其中，所述第一隧道端口为第一隧道在所述第一用户面网元上的隧道端口，所述第二隧道端口为第一隧道在所述第二用户面网元上的隧道端口，所述第一隧道为所述第一用户面网元和所述第二用户面网元之间的隧道；
    相应的，所述第一消息还包括所述第一隧道端口标识和所述第一隧道端口上的所述规则组；所述方法还包括：
    所述会话管理网元根据所述第二用户面网元的标识，向所述第二用户面网元发送第三消息，所述第三消息包括所述第二隧道端口标识、所述第二隧道端口上的所述规则组、和更新后的应用在所述第二用户面网元上的局域网群组FAR。
  14. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    在所述第一终端在所述局域网群组内从接入所述第一用户面网元更新为接入第三 用户面网元的情况下，所述会话管理网元接收来自所述群组管理功能网元的第四消息，所述第四消息包括所述第一用户面网元的标识，与所述第一用户面网元的标识对应的所述第一会话端口标识，以及所述第四消息包括应用在所述第一用户面网元上的所述局域网群组FAR的标识或者更新后的应用在所述第一用户面网元上的所述局域网群组FAR，以及，所述第四消息包括所述第三用户面网元的标识，以及与所述第三用户面网元的标识对应的第三会话端口标识、应用在所述第三会话端口标识对应的第三会话端口的所述规则组、以及创建或更新后的应用在所述第三用户面网元上的局域网群组FAR，其中，所述第三会话端口为所述第三用户面网元上用于所述第一终端接入的会话端口；
    所述会话管理网元根据所述第一用户面网元的标识，向所述第一用户面网元发送第五消息，所述第五消息包括所述第一会话端口标识，以及所述第五消息包括应用在所述第一用户面网元上的所述局域网群组FAR的标识或者更新后的应用在所述第一用户面网元上的所述局域网群组FAR；
    以及，所述会话管理网元根据所述第三用户面网元对的标识，向所述第三用户面网元发送第六消息，所述第六消息包括所述第三会话端口标识、所述第三会话端口的所述规则组、以及创建或更新后的应用在所述第三用户面网元上的局域网群组FAR。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    所述第四消息还包括与所述第一用户面网元的标识对应的第三隧道端口标识，第四用户面网元的标识，与所述第四用户面网元的标识对应的第四隧道端口标识、以及更新后的应用在所述第四用户面网元上的所述局域网群组FAR，其中，所述第三隧道端口标识为第二隧道在所述第一用户面网元上的隧道端口标识，所述第四隧道端口标识为所述第二隧道在所述第四用户面网元上的隧道端口标识；
    相应的，所述第五消息还包括所述第三隧道端口标识；所述方法还包括：
    所述会话管理网元根据所述第四用户面网元的标识，向所述第四用户面网元发送第七消息，所述第七消息包括所述第四隧道端口标识、以及更新后的应用在所述第四用户面网元上的所述局域网群组FAR。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第四消息还包括与所述第三用户面网元的标识对应的第五隧道端口标识和应用在所述第五隧道端口标识对应的第五隧道端口的所述规则组；以及，所述第四消息还包括第四用户面网元的标识，与所述第四用户面网元的标识对应的第六隧道端口标识、应用在所述第六隧道端口标识对应的第六隧道端口的所述规则组、以及更新后的应用在所述第四用户面网元上的局域网群组FAR；所述第五隧道端口为第三隧道在所述第三用户面网元上的隧道端口，所述第六隧道端口为所述第三隧道在所述第四用户面网元上的隧道端口，所述第三隧道为所述第三用户面网元和所述第四用户面网元之间的隧道；
    相应的，所述第六消息还包括所述第五隧道端口标识和所述第五隧道端口的所述规则组；所述方法还包括：
    所述会话管理网元根据所述第四用户面网元的标识，向所述第四用户面网元发送第八消息，所述第八消息包括所述第六隧道端口标识、所述第六隧道端口的所述规则组、以及更新后的应用在所述第四用户面网元上的局域网群组FAR。
  17. 根据权利要求12或13所述的方法，其特征在于，在所述第一终端将离开所述局域网群组的情况下，所述会话管理网元接收来自所述群组管理功能网元的第九消息，所述第九消息包括所述第一用户面网元的标识，与所述第一用户面网元的标识对应的所述第一会话端口标识，以及所述第九消息包括应用在所述第一用户面网元上的所述局域网群组FAR的标识或者更新后的应用在所述第一用户面网元上的所述局域网群组FAR；
    所述会话管理网元根据所述第一用户面网元的标识，向所述第一用户面网元发送第十消息，所述第十消息包括所述第一会话端口标识，以及第五消息包括应用在所述第一用户面网元上的所述局域网群组FAR的标识或者更新后的应用在所述第一用户面网元上的所述局域网群组FAR。
  18. 根据权利要求17所述的方法，其特征在于，所述第九消息还包括与所述第一用户面网元的标识对应的第七隧道端口标识，第五用户面网元的标识，与所述第五用户面网元的标识对应的第八隧道端口标识、以及更新后的应用在所述第五用户面网元上的所述局域网群组FAR，其中，所述第七隧道端口标识为第四隧道在所述第一用户面网元上的隧道端口标识，所述第八隧道端口标识为所述第四隧道在第四用户面网元上的隧道端口标识，所述第四隧道为所述第一用户面网元和所述第五用户面网元之间隧道；
    相应的，所述第十消息还包括所述第七隧道端口标识；
    所述会话管理网元，还用于根据所述第五用户面网元的标识，向所述第五用户面网元发送第十一消息，所述第十一消息包括所述第八隧道端口标识、以及更新后的应用在所述第五用户面网元上的所述局域网群组FAR。
  19. 一种群组管理功能网元，其特征在于，所述群组管理功能网元包括：处理模块和收发模块；
    所述处理模块，用于在第一终端发起接入局域网群组的情况下，获取所述第一终端即将接入的第一用户面网元的标识、所述局域网群组的上下文信息以及第一会话端口标识，其中，所述上下文信息中包括所述局域网群组的终端成员列表中当前已经接入所述局域网群组的终端所接入的用户面网元的标识列表，所述第一会话端口标识为所述第一用户面网元上用于所述第一终端接入的第一会话端口的标识；
    所述处理模块，还用于为局域网群组创建应用在所述第一会话端口上的规则组；以及，所述群组管理功能网元根据所述上下文信息，为所述局域网群组创建或更新应用在所述第一用户面网元上的局域网群组转发动作规则FAR；其中，所述规则组中包括入口分组检测规则PDR，出口PDR和出口FAR；所述出口PDR中包括所述出口FAR的标识，所述入口PDR中包括所述局域网群组FAR的标识；其中，所述入口PDR用于识别属于所述局域网群组的广播报文，所述局域网群组FAR用于将所述广播报文复制后转发到指定的出口；所述出口PDR用于识别所述广播报文的类型，所述出口FAR用于对所述广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；
    所述收发模块，用于向会话管理网元发送第一消息，所述第一消息用于在所述第一用户面网元的第一会话端口上配置所述规则组，以及在所述第一用户面网元上配置或更新所述局域网群组FAR。
  20. 根据权利要求19所述的群组管理功能网元，其特征在于，在所述标识列表中包括第二用户面网元的标识，且所述第一用户面网元的标识不在所述标识列表中的情况下，所述处理模块，还用于获取第一隧道端口标识和第二隧道端口标识，所述第一隧道端口标识为第一隧道在所述第一用户面网元上的第一隧道端口的标识，所述第二隧道端口标识为所述第一隧道在所述第二用户面网元上的第二隧道端口的标识，所述第一隧道为所述第一用户面网元和所述第二用户面网元之间的隧道；
    所述处理模块，还用于为所述局域网群组创建应用在所述第一隧道端口上的所述规则组，以及，所述群组管理功能网元为所述局域网群组创建应用在所述第二隧道端口上的所述规则组，以及，所述群组管理功能网元更新应用在所述第二用户面网元上的所述局域网群组FAR；
    相应的，所述第一消息还用于在所述第一隧道端口上配置所述规则组；以及在所述第二隧道端口上配置所述规则组，以及在所述第二用户面网元上更新所述局域网群组FAR。
  21. 根据权利要求19或20所述的群组管理功能网元，其特征在于，
    在所述第一终端在所述局域网群组内从接入所述第一用户面网元更新为接入第三用户面网元的情况下，所述处理模块，还用于获取第三会话端口标识，所述第三会话端口标识为所述第三用户面网元上用于所述第一终端接入的第三会话端口的标识；
    所述处理模块，还用于为所述局域网群组创建应用在所述第三会话端口上的规则组；以及，所述群组管理功能网元根据所述上下文信息，创建或更新应用在所述第三用户面网元上的所述局域网群组FAR；
    所述收发模块，还用于向所述会话管理网元发送第三消息，所述第三消息用于在所述第三会话端口上配置所述规则组，以及在所述第三用户面网元上配置或更新所述局域网群组FAR，以及删除所述第一会话端口上的所述规则组，以及删除或更新应用在所述第一用户面网元上的所述局域网群组FAR，其中，更新后的应用在所述第一用户面网元上的所述局域网群组FAR是所述群组管理功能网元根据所述上下文信息，更新应用在所述第一用户面网元上的所述局域网群组FAR得到的。
  22. 根据权利要求21所述的群组管理功能网元，其特征在于，在所述标识列表中包括第四用户面网元的标识，且所述第一用户面网元上没有所述局域网群组的终端成员列表中除所述第一终端之外的其他终端接入的情况下，所述处理模块，还用于更新应用在所述第四用户面网元上的所述局域网群组FAR；
    相应的，所述第三消息还用于删除所述第一用户面网元和所述第四用户面网元之间的第二隧道，以及，删除所述第一用户面网元的第三隧道端口上的所述规则组，以及删除所述第四用户面网元的第四隧道端口上的所述规则组，以及更新应用在所述第四用户面网元上的所述局域网群组FAR，其中，所述第三隧道端口为所述第二隧道在所述第一用户面网元上的隧道端口，所述第四隧道端口为所述第二隧道在所述第四用户面网元上的隧道端口。
  23. 根据权利要求21或22所述的群组管理功能网元，其特征在于，在所述标识列表中包括第四用户面网元的标识，且所述第三用户面网元的标识不在所述标识列表中的情况下，所述处理模块，还用于获取第五隧道端口标识和第六隧道端口标识，所 述第五隧道端口标识为第三隧道在所述第三用户面网元上的第五隧道端口的标识，所述第六隧道端口标识为所述第三隧道在所述第四用户面网元上的第六隧道端口的标识，所述第三隧道为所述第三用户面网元和所述第四用户面网元之间的隧道；
    所述处理模块，还用于为所述局域网群组创建应用在所述第五隧道端口上的所述规则组，以及，所述群组管理功能网元为所述局域网群组创建应用在所述第六隧道端口上的所述规则组，以及，所述群组管理功能网元更新应用在所述第四用户面网元上的所述局域网群组FAR；
    相应的，所述第三消息还用于在所述第五隧道端口上配置所述规则组；以及在所述第六隧道端口上配置所述规则组，以及在所述第四用户面网元上更新所述局域网群组FAR。
  24. 根据权利要求19或20所述的群组管理功能网元，其特征在于，在所述第一终端将离开所述局域网群组的情况下，所述收发模块，还用于向所述会话管理网元发送第五消息，所述第五消息用于删除应用在所述第一会话端口上的所述规则组，以及删除或更新应用在所述第一用户面网元上的所述局域网群组FAR，其中，更新后的应用在所述第一用户面网元上的所述局域网群组FAR是所述群组管理功能网元根据所述上下文信息，更新应用在所述第一用户面网元上的所述局域网群组FAR得到的。
  25. 根据权利要求24所述的群组管理功能网元，其特征在于，在所述标识列表中包括第五用户面网元的标识，且所述第一用户面网元上没有所述局域网群组的终端成员列表中除所述第一终端之外的其他终端接入的情况下，所述处理模块，还用于更新应用在所述第五用户面网元上的所述局域网群组FAR；
    相应的，所述第五消息还用于删除所述第一用户面网元和所述第五用户面网元之间的第四隧道，以及，删除所述第一用户面网元的第七隧道端口上的所述规则组，以及删除所述第五用户面网元的第八隧道端口上的所述规则组，以及更新应用在所述第五用户面网元上的所述局域网群组FAR，其中，所述第七隧道端口为所述第四隧道在所述第一用户面网元上的隧道端口，所述第八隧道端口为所述第四隧道在所述第五用户面网元上的隧道端口。
  26. 一种第一用户面网元，其特征在于，所述第一用户面网元包括：处理模块和收发模块；
    所述收发模块，用于在第一终端发起接入局域网群组的情况下，接收来自会话管理网元的第一消息，所述第一消息包括第一会话端口标识，应用在所述第一会话端口标识对应的第一会话端口上的规则组、以及创建或更新后的应用在所述第一用户面网元上的局域网群组转发动作规则FAR，其中，所述第一会话端口标识为所述第一用户面网元上用于所述第一终端接入的第一会话端口的标识；所述规则组中包括入口分组检测规则PDR，出口PDR和出口FAR；所述出口PDR中包括所述出口FAR的标识，所述入口PDR中包括所述局域网群组FAR的标识；其中，所述入口PDR用于识别属于所述局域网群组的广播报文，所述局域网群组FAR用于将所述广播报文复制后转发到指定的出口；所述出口PDR用于识别所述广播报文的类型，所述出口FAR用于对所述广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；
    所述处理模块，用于根据所述第一会话端口标识创建所述第一会话端口，并在所 述第一会话端口上配置所述规则组；
    以及，所述处理模块，用于根据创建的应用在所述第一用户面网元上的局域网群组FAR，在所述第一用户面网元上创建所述局域网群组；或者，所述第一用户面网元根据更新后的应用在所述第一用户面网元上的局域网群组FAR，更新所述第一用户面网元上的所述局域网群组FAR。
  27. 根据权利要求26所述的第一用户面网元，其特征在于，所述第一消息还包括第一隧道端口标识和应用在所述第一隧道端口标识对应的第一隧道端口上的所述规则组，其中，所述第一隧道端口标识为第一隧道在所述第一用户面网元上的第一隧道端口的标识，所述第一隧道为所述第一用户面网元和第二用户面网元之间的隧道；
    所述处理模块，还用于根据所述第一隧道端口标识创建所述第一隧道端口，并在所述第一隧道端口上配置所述规则组。
  28. 根据权利要求26或27所述的第一用户面网元，其特征在于，
    在所述第一终端不再由所述第一用户面网元提供服务的情况下，所述收发模块，还用于接收来自所述会话管理网元的第二消息，所述第二消息包括所述第一会话端口标识，以及所述第二消息包括应用在所述第一用户面网元上的所述局域网群组FAR的标识或者更新后的应用在所述第一用户面网元上的所述局域网群组FAR；
    所述处理模块，还用于根据所述第一会话端口标识，删除所述第一会话端口和应用在所述第一会话端口的所述规则组；以及，
    所述处理模块，还用于根据应用在所述第一用户面网元上的所述局域网群组FAR的标识，删除应用在所述第一用户面网元上的所述局域网群组FAR；或者，所述第一用户面网元根据更新后的应用在所述第一用户面网元上的所述局域网群组FAR，更新所述第一用户面网元上的所述局域网群组FAR。
  29. 根据权利要求28所述的第一用户面网元，其特征在于，所述第二消息还包括第一隧道端口标识，其中，所述第一隧道端口标识为第一隧道在所述第一用户面网元上的第一隧道端口的标识，所述第一隧道为所述第一用户面网元和第二用户面网元之间的隧道；
    所述处理模块，还用于根据所述第一隧道端口标识，删除所述第一隧道端口和应用在所述第一隧道端口的所述规则组。
  30. 一种会话管理网元，其特征在于，所述会话管理网元包括：接收模块和发送模块；
    所述接收模块，用于在第一终端发起接入局域网群组的情况下，接收来自群组管理功能网元的第一消息，所述第一消息包括第一用户面网元的标识、与所述第一用户面网元的标识对应的第一会话端口标识，应用在所述第一会话端口标识对应的第一会话端口上的规则组、以及创建或更新后的应用在所述第一用户面网元上的局域网群组转发动作规则FAR，其中，所述第一会话端口为所述第一用户面网元上用于所述第一终端接入的会话端口；所述规则组中包括入口分组检测规则PDR，出口PDR和出口FAR；所述出口PDR中包括所述出口FAR的标识，所述入口PDR中包括所述局域网群组FAR的标识；其中，所述入口PDR用于识别属于所述局域网群组的广播报文，所述局域网群组FAR用于将所述广播报文复制后转发到指定的出口；所述出口PDR 用于识别所述广播报文的类型，所述出口FAR用于对所述广播报文添加外层消息头以及进行传输层标记后通过相应端口发送出去；
    所述发送模块，用于根据所述第一用户面网元的标识，向所述第一用户面网元发送第二消息，所述第二消息包括所述第一会话端口标识，所述第一会话端口上的规则组、以及创建或更新后的应用在所述第一用户面网元上的局域网群组FAR。
  31. 根据权利要求30所述的会话管理网元，其特征在于，所述第一消息还包括与所述第一用户面网元的标识对应的第一隧道端口标识和应用在所述第一隧道端口标识对应的第一隧道端口上的所述规则组，以及第二用户面网元的标识、与第二用户面网元的标识对应的第二隧道端口标识、应用在所述第二隧道端口标识对应的第二隧道端口上的所述规则组、和更新后的应用在所述第二用户面网元上的局域网群组FAR；其中，所述第一隧道端口为第一隧道在所述第一用户面网元上的隧道端口，所述第二隧道端口为第一隧道在所述第二用户面网元上的隧道端口，所述第一隧道为所述第一用户面网元和所述第二用户面网元之间的隧道；
    相应的，所述第一消息还包括所述第一隧道端口标识和所述第一隧道端口上的所述规则组；
    所述发送模块，还用于根据所述第二用户面网元的标识，向所述第二用户面网元发送第三消息，所述第三消息包括所述第二隧道端口标识、所述第二隧道端口上的所述规则组、和更新后的应用在所述第二用户面网元上的局域网群组FAR。
  32. 根据权利要求30或31所述的会话管理网元，其特征在于，在所述第一终端在所述局域网群组内从接入所述第一用户面网元更新为接入第三用户面网元的情况下，所述接收模块，还用于接收来自所述群组管理功能网元的第四消息，所述第四消息包括所述第一用户面网元的标识，与所述第一用户面网元的标识对应的所述第一会话端口标识，以及所述第四消息包括应用在所述第一用户面网元上的所述局域网群组FAR的标识或者更新后的应用在所述第一用户面网元上的所述局域网群组FAR，以及，所述第四消息包括所述第三用户面网元的标识，以及与所述第三用户面网元的标识对应的第三会话端口标识、应用在所述第三会话端口标识对应的第三会话端口的所述规则组、以及创建或更新后的应用在所述第三用户面网元上的局域网群组FAR，其中，所述第三会话端口为所述第三用户面网元上用于所述第一终端接入的会话端口；
    所述发送模块，还用于根据所述第一用户面网元的标识，向所述第一用户面网元发送第五消息，所述第五消息包括所述第一会话端口标识，以及所述第五消息包括应用在所述第一用户面网元上的所述局域网群组FAR的标识或者更新后的应用在所述第一用户面网元上的所述局域网群组FAR；
    以及，所述发送模块，还用于根据所述第三用户面网元对的标识，向所述第三用户面网元发送第六消息，所述第六消息包括所述第三会话端口标识、所述第三会话端口的所述规则组、以及创建或更新后的应用在所述第三用户面网元上的局域网群组FAR。
  33. 根据权利要求32所述的会话管理网元，其特征在于，
    所述第四消息还包括与所述第一用户面网元的标识对应的第三隧道端口标识，第四用户面网元的标识，与所述第四用户面网元的标识对应的第四隧道端口标识、以及 更新后的应用在所述第四用户面网元上的所述局域网群组FAR，其中，所述第三隧道端口标识为第二隧道在所述第一用户面网元上的隧道端口标识，所述第四隧道端口标识为所述第二隧道在所述第四用户面网元上的隧道端口标识；
    相应的，所述第五消息还包括所述第三隧道端口标识；
    所述发送模块，还用于根据所述第四用户面网元的标识，向所述第四用户面网元发送第七消息，所述第七消息包括所述第四隧道端口标识、以及更新后的应用在所述第四用户面网元上的所述局域网群组FAR。
  34. 根据权利要求32或33所述的会话管理网元，其特征在于，所述第四消息还包括与所述第三用户面网元的标识对应的第五隧道端口标识和应用在所述第五隧道端口标识对应的第五隧道端口的所述规则组；以及，所述第四消息还包括第四用户面网元的标识，与所述第四用户面网元的标识对应的第六隧道端口标识、应用在所述第六隧道端口标识对应的第六隧道端口的所述规则组、以及更新后的应用在所述第四用户面网元上的局域网群组FAR；所述第五隧道端口为第三隧道在所述第三用户面网元上的隧道端口，所述第六隧道端口为所述第三隧道在所述第四用户面网元上的隧道端口，所述第三隧道为所述第三用户面网元和所述第四用户面网元之间的隧道；
    相应的，所述第六消息还包括所述第五隧道端口标识和所述第五隧道端口的所述规则组；
    所述发送模块，还用于根据所述第四用户面网元的标识，向所述第四用户面网元发送第八消息，所述第八消息包括所述第六隧道端口标识、所述第六隧道端口的所述规则组、以及更新后的应用在所述第四用户面网元上的局域网群组FAR。
  35. 根据权利要求30或31所述的会话管理网元，其特征在于，在所述第一终端将离开所述局域网群组的情况下，所述接收模块，用于接收来自所述群组管理功能网元的第九消息，所述第九消息包括所述第一用户面网元的标识，与所述第一用户面网元的标识对应的所述第一会话端口标识，以及所述第九消息包括应用在所述第一用户面网元上的所述局域网群组FAR的标识或者更新后的应用在所述第一用户面网元上的所述局域网群组FAR；
    所述发送模块，用于根据所述第一用户面网元的标识，向所述第一用户面网元发送第十消息，所述第十消息包括所述第一会话端口标识，以及所述第五消息包括应用在所述第一用户面网元上的所述局域网群组FAR的标识或者更新后的应用在所述第一用户面网元上的所述局域网群组FAR。
  36. 根据权利要求35所述的会话管理网元，其特征在于，所述第九消息还包括与所述第一用户面网元的标识对应的第七隧道端口标识，第五用户面网元的标识，与所述第五用户面网元的标识对应的第八隧道端口标识、以及更新后的应用在所述第五用户面网元上的所述局域网群组FAR，其中，所述第七隧道端口标识为第四隧道在所述第一用户面网元上的隧道端口标识，所述第八隧道端口标识为所述第四隧道在所述第四用户面网元上的隧道端口标识，所述第四隧道为所述第一用户面网元和所述第五用户面网元之间隧道；
    相应的，所述第十消息还包括所述第七隧道端口标识；
    所述发送模块，还用于根据所述第五用户面网元的标识，向所述第五用户面网元 发送第十一消息，所述第十一消息包括所述第八隧道端口标识、以及更新后的应用在所述第五用户面网元上的所述局域网群组FAR。
  37. 一种群组通信系统，其特征在于，所述群组通信系统包括如权利要求19-25任一项所述的群组管理功能网元、权利要求26-29任一项所述的第一用户面网元、以及权利要求30-36任一项所述的会话管理网元。
  38. 一种通信装置，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述通信装置运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述通信装置执行如权利要求1-7任一项，或8-11任一项，或12-18任一项所述的群组通信方法。
  39. 一种处理装置，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于从所述存储器调用并运行所述计算机程序，以执行如权利要求1-7任一项，或8-11任一项，或12-18任一项所述的群组通信方法。
  40. 一种处理器，其特征在于，用于执行如权利要求1-7任一项，或8-11任一项，或12-18任一项所述的群组通信方法。
  41. 一种芯片系统，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于从所述存储器调用并运行所述计算机程序，使得安装有所述芯片系统的设备执行如权利要求1-7任一项，或8-11任一项，或12-18任一项所述的群组通信方法。
  42. 一种计算机可读存储介质，包括计算机程序，当其在计算机上运行时，使得所述计算机执行如权利要求1-7任一项，或8-11任一项，或12-18任一项所述的群组通信方法。
  43. 一种计算机程序产品，所述计算机程序产品包括计算机程序，当所述计算机程序在计算机上运行时，使得计算机执行如权利要求1-7任一项，或8-11，或12-18任一项所述的群组通信方法。
  44. 一种装置，其特征在于，所述装置用来执行如权利要求1-7任一项，或8-11任一项，或12-18任一项所述的群组通信方法。
PCT/CN2019/119475 2018-11-19 2019-11-19 群组通信方法、设备及系统 WO2020103828A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19887489.3A EP3876494B1 (en) 2018-11-19 2019-11-19 Group communication method, device and system
US17/324,928 US11653180B2 (en) 2018-11-19 2021-05-19 Group communications method and system, and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811378645.3A CN111200791B (zh) 2018-11-19 2018-11-19 群组通信方法、设备及系统
CN201811378645.3 2018-11-19

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/324,928 Continuation US11653180B2 (en) 2018-11-19 2021-05-19 Group communications method and system, and device

Publications (1)

Publication Number Publication Date
WO2020103828A1 true WO2020103828A1 (zh) 2020-05-28

Family

ID=70747309

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/119475 WO2020103828A1 (zh) 2018-11-19 2019-11-19 群组通信方法、设备及系统

Country Status (4)

Country Link
US (1) US11653180B2 (zh)
EP (1) EP3876494B1 (zh)
CN (1) CN111200791B (zh)
WO (1) WO2020103828A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113163511A (zh) * 2021-06-28 2021-07-23 中移(上海)信息通信科技有限公司 信息处理方法、装置、网络网元、终端及可读存储介质

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109729125B (zh) * 2017-10-30 2021-06-15 华为技术有限公司 会话建立方法、设备及系统
US11343653B2 (en) 2019-01-15 2022-05-24 Ofinno, Llc Session establishment to join a group communication
EP3895385B1 (en) * 2019-01-15 2024-06-26 Telefonaktiebolaget LM Ericsson (publ) Methods and apparatuses for supporting a local area network (lan)
CN112105088B (zh) * 2019-06-17 2023-04-07 华为技术有限公司 多播通信方法、装置及系统
CN110121155B (zh) * 2019-06-17 2021-05-14 腾讯科技（深圳）有限公司 虚拟网络群组的广播方法、装置、设备及系统
CN113660102B (zh) * 2019-06-17 2022-10-21 腾讯科技（深圳）有限公司 虚拟网络群组的组播组的组播方法、装置、设备及系统
JP7026866B2 (ja) * 2020-01-21 2022-02-28 三菱電機株式会社 コントローラ、通信装置、通信システム、制御回路、記憶媒体および通信方法
EP4109939A4 (en) * 2020-03-18 2023-04-12 Huawei Technologies Co., Ltd. MESSAGE TRANSFER METHOD AND APPARATUS
CN113973076B (zh) * 2020-07-24 2023-01-06 华为技术有限公司 一种多播切换方法及装置
CN114268910B (zh) * 2020-09-15 2023-04-18 成都鼎桥通信技术有限公司 集群网络的群组信息下发方法及设备
CN112511403A (zh) * 2020-12-14 2021-03-16 深圳艾灵网络有限公司 一种虚拟局域网通信方法、设备及存储介质
CN112751871A (zh) * 2020-12-30 2021-05-04 京信网络系统股份有限公司 数据传输方法、装置、网络设备和存储介质
CN112822717B (zh) * 2020-12-31 2023-04-28 联想未来通信科技(重庆)有限公司 一种动态控制报文缓冲的方法、装置及系统
CN114845356A (zh) * 2021-01-30 2022-08-02 华为技术有限公司 通信方法及装置
CN114979964B (zh) * 2021-02-26 2023-04-04 华为技术有限公司 一种通信方法及装置
CN115209354B (zh) * 2021-04-09 2024-01-30 华为技术有限公司 通信方法和通信装置
CN114040450A (zh) * 2021-09-28 2022-02-11 华为技术有限公司 一种通信方法及装置
WO2023151042A1 (zh) * 2022-02-11 2023-08-17 Oppo广东移动通信有限公司 一种无线通信方法及装置、通信设备
CN117376980A (zh) * 2022-06-29 2024-01-09 中兴通讯股份有限公司 数据连续传输方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018126981A1 (zh) * 2017-01-05 2018-07-12 华为技术有限公司 计费管理方法、用户面功能实体以及控制面功能实体
US20180199243A1 (en) * 2017-01-06 2018-07-12 Samsung Electronics Co., Ltd Intra-rat handover for next generation system
WO2018137232A1 (zh) * 2017-01-26 2018-08-02 华为技术有限公司 数据处理的方法、控制面节点和用户面节点
WO2018195803A1 (zh) * 2017-04-26 2018-11-01 华为技术有限公司 一种报文处理方法及相关设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2572473B1 (en) * 2010-05-19 2014-02-26 Telefonaktiebolaget L M Ericsson (PUBL) Methods and apparatus for use in an openflow network
WO2018045501A1 (zh) * 2016-09-07 2018-03-15 华为技术有限公司 本地分组数据网络的动态创建方法、装置及系统
CN108632787B (zh) * 2017-03-23 2023-05-23 中兴通讯股份有限公司 群组间通信方法及装置，资源配置方法、装置以及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018126981A1 (zh) * 2017-01-05 2018-07-12 华为技术有限公司 计费管理方法、用户面功能实体以及控制面功能实体
US20180199243A1 (en) * 2017-01-06 2018-07-12 Samsung Electronics Co., Ltd Intra-rat handover for next generation system
WO2018137232A1 (zh) * 2017-01-26 2018-08-02 华为技术有限公司 数据处理的方法、控制面节点和用户面节点
WO2018195803A1 (zh) * 2017-04-26 2018-11-01 华为技术有限公司 一种报文处理方法及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3876494A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113163511A (zh) * 2021-06-28 2021-07-23 中移(上海)信息通信科技有限公司 信息处理方法、装置、网络网元、终端及可读存储介质
CN113163511B (zh) * 2021-06-28 2021-10-26 中移(上海)信息通信科技有限公司 信息处理方法、装置、网络网元、终端及可读存储介质

Also Published As

Publication number Publication date
US11653180B2 (en) 2023-05-16
EP3876494A4 (en) 2021-12-22
US20210274323A1 (en) 2021-09-02
CN111200791B (zh) 2021-07-09
CN111200791A (zh) 2020-05-26
EP3876494B1 (en) 2023-04-19
EP3876494A1 (en) 2021-09-08

Similar Documents

Publication Publication Date Title
WO2020103828A1 (zh) 群组通信方法、设备及系统
WO2020224463A1 (zh) 一种数据分析方法及装置
WO2020147760A1 (zh) 一种局域网通信方法、装置及系统
WO2020220747A1 (zh) 一种tsn业务的处理方法、装置及系统
WO2020103834A1 (zh) 时延敏感网络通信方法及其装置
WO2020073752A1 (zh) 一种通信方法及装置
WO2020073919A1 (zh) 报文传输方法及装置
WO2021037017A1 (zh) 通信处理方法、通信处理装置以及系统
WO2020063213A1 (zh) 本地局域网通信方法、设备及系统
WO2020221266A1 (zh) 一种通信方法及装置
US20220109962A1 (en) Multicast communication method, and apparatus and system
WO2020103833A1 (zh) 信息传输方法及其装置
WO2019042184A1 (zh) 数据传输方法、设备及系统
WO2020048469A1 (zh) 一种通信的方法及装置
WO2021012736A1 (zh) 一种会话管理网元的选择方法、装置及系统
US11818641B2 (en) Local area network communication method, device, and system
WO2022105897A1 (zh) 业务路径建立方法、通信装置及存储介质
WO2020220799A1 (zh) 一种通信方法、装置及系统
WO2019105203A1 (zh) 一种接入本地网络的方法和设备
US20220263879A1 (en) Multicast session establishment method and network device
WO2022222745A1 (zh) 一种通信方法及装置
WO2023124875A1 (zh) 一种通信方法及装置
WO2021057342A1 (zh) 一种网络切片的计费方法及装置
WO2022089503A1 (zh) 应用接入网络的方法、装置及系统
WO2021057020A1 (zh) 一种网络切片的计费方法及装置

Legal Events

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

Ref document number: 19887489

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019887489

Country of ref document: EP

Effective date: 20210604