CN112470543A - Apparatus and method for performing group communication - Google Patents

Abstract

An apparatus and method for performing group communication are provided. A method for performing group communication of user equipment, comprising: sending a connection establishment request to a network node in a group establishment system; and establishing each connection of each group in the group communication system according to the connection establishment request.

Description

Apparatus and method for performing group communication

Technical Field

The present disclosure relates to the field of communication systems, and more particularly, to an apparatus and method for performing group communication.

Background

In Long Term Evolution (LTE) and New Radio (NR) systems, a public network system such as a Public Land Mobile Network (PLMN) based public land network is generally deployed. However, in some cases, such as offices, homes, and factories, a local user or administrator often arranges a local network for more efficient and secure management. The members of the local network group may communicate in a point-to-point manner or a point-to-multipoint manner.

Therefore, there is a need for an apparatus and method to perform group communication.

Disclosure of Invention

An object of the present disclosure is to propose an apparatus and method for performing group communication, which can provide good group communication performance and high reliability, and provide a solution how to transmit user data and provide corresponding control information and/or programs within a 5G system.

In a first aspect of the present disclosure, a user equipment in group communication includes a memory, a transceiver, and a processor coupled to the memory and the transceiver, the processor configured to control the transceiver to transmit a connection establishment request to a network node in the group communication system, and the processor configured to establish each connection of each group in the group communication system according to the connection establishment request.

In a second aspect of the present disclosure, a method for performing group communication of user equipments includes: sending a connection establishment request to a network node in the group communication system, and establishing each connection of each group in the group communication system according to the connection establishment request.

In a third aspect of the present disclosure, a network node in group communication comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver, the processor being configured to control the transceiver to receive a connection establishment request from a User Equipment (UE) in the group communication system, and the processor being configured to process (hand of) a connection of the UE in the group communication system.

In a fourth aspect of the present disclosure, a method for performing group communication of network nodes comprises: receiving a connection establishment request from a User Equipment (UE) in the group communication system, and processing a connection of the UE in the group communication.

In a fifth aspect of the disclosure, a non-transitory machine-readable storage medium has stored thereon instructions which, when executed by a computer, cause the computer to perform the above-described method.

In a sixth aspect of the present disclosure, a terminal device includes a processor and a memory configured to store a computer program, the processor being configured to execute the computer program stored in the memory to perform the method described above.

In a seventh aspect of the disclosure, a network node comprises a processor and a memory configured to store a computer program, the processor being configured to execute the computer program stored in the memory to perform the above method.

Drawings

In order to more clearly illustrate embodiments of the present disclosure or related art, the following drawings will be described in brief introduction to the embodiments. It is understood that the drawings are merely exemplary of the disclosure and that one of ordinary skill in the art may derive other drawings based on these drawings without undue experimentation.

Fig. 1 is a block diagram of a user equipment and a network performing group communication according to an embodiment of the present disclosure.

Fig. 2 is a flowchart illustrating a method for performing group communication of user equipments according to an embodiment of the present disclosure.

Fig. 3 is a flow chart illustrating a method for performing group communication of network nodes according to an embodiment of the present disclosure.

Fig. 4 is a schematic diagram illustrating a 5G system architecture with a centralized user pane architecture represented using reference points showing how various network functions interact with each other, according to an embodiment of the disclosure.

Fig. 5 is a schematic diagram illustrating a 5G system architecture with a distributed user pane architecture represented using reference points showing how various network functions interact with each other, according to an embodiment of the disclosure.

Fig. 6 is a schematic diagram of an exemplary illustration of a point-to-multipoint communication user plane topology according to an embodiment of the disclosure.

Fig. 7 is a diagram of an exemplary illustration of a point-to-multipoint communication group PDU session according to an embodiment of the present disclosure.

Fig. 8 is a block diagram of a system for wireless communication in accordance with an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure, technical contents, structural features, objects, and effects thereof are described in detail below with reference to the accompanying drawings. In particular, the terminology used in the embodiments of the present invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.

Fig. 1 illustrates that in some embodiments, a User Equipment (UE) 10 and a network node 20 performing group communication according to embodiments of the present disclosure are provided. The UE 10 may include a processor 11, a memory 12, and a transceiver 13. The network node 20 may comprise a processor 21, a memory 22 and a transceiver 23. The processor 11 or 21 may be configured to implement the proposed functions, procedures, and/or methods described in this specification. Layers of the radio interface protocol may be implemented in the processor 11 or 21. The memory 12 or 22 is operatively coupled with the processor 11 or 21 and stores various information to operate the processor 11 or 21. The transceiver 13 or 23 is operatively coupled with the processor 11 or 21, and the transceiver 13 or 23 transmits and/or receives a radio signal.

The processor 11 or 21 may comprise an application-specific integrated circuit (ASIC), other chipset, logic circuit and/or data processing device. The memory 12 or 22 may include read-only memory (ROM), Random Access Memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. The transceiver 13 or 23 may include a baseband circuit to process radio frequency signals. When the embodiments are implemented in software, the techniques described in this disclosure may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described in this disclosure. These modules may be stored in memory 12 or 22 and executed by processor 11 or 21. The memory 12 or 22 may be implemented within the processor 11 or 21 or external to the processor 11 or 21, where they may be coupled to the processor 11 or 21 by various means known in the art.

According to the sideline (sidelink) technology developed under 3rd generation partnership project (3 GPP) release 14, 15 and beyond, communication between UEs involves Vehicle-to-all (V2X) communication, including Vehicle-to-Vehicle (V2V), Vehicle-to-pedestrian (V2P) and Vehicle-to-infrastructure/network (V2I/N). The UEs communicate directly with each other through a side-chain interface such as the PC5 interface.

In some embodiments, the processor 11 is configured to control the transceiver 13 to receive a send connection establishment request to the network node 20 in the group communication system, and the processor 11 is configured to establish each connection of each group in the group communication system according to the connection establishment request.

In some embodiments, the processor 11 is configured to establish a plurality of connections for a plurality of groups in the group communication system to which the UE 10 belongs according to the connection establishment request. In some embodiments, each connection of each group in the group communication system terminates at the network node 20, or the network node 20 and the processor 11 of the UE 10. In some embodiments, the connection setup request is a Protocol Data Unit (PDU) session setup request, the PDU session setup request includes a PDU session Identification (ID) and/or group related information, and the connection includes a PDU session.

In some embodiments, the group related information includes a group index and an index of UEs within the group. In some embodiments, the connection is configured to a centralized user plane architecture that uses a Session-and-service continuity (SSC) mode. In some embodiments, when the connection type is Internet protocol version four (IPv 4), IPv6, or IPv4v6, the processor 11 is configured to receive an IP address and/or prefix of the connection from the network node 20.

In some embodiments, the connection type is an ethernet type PDU session. In some embodiments, if a group communication system shares the connection with another group communication system, an IP address and/or prefix of the connection is assigned to another UE of the other group communication system. In some embodiments, the processor 21 is configured to receive a connection establishment request from a User Equipment (UE) 10 in a group communication system, and the processor 21 is configured to process connections of the UE 10 in the group communication system.

In some embodiments, the network node 20 further comprises a Session Management Function (SMF) configured to check whether the connection establishment request conforms to the group to which the UE 10 belongs. In some embodiments, the network node 20 further comprises a Protocol data unit session anchor (PSA) User Plane Function (UPF) configured to terminate each connection of the UEs 10 in the group communication system. In some embodiments, the connection setup request is a Protocol Data Unit (PDU) session setup request, the PDU session setup request includes a PDU session Identification (ID) and/or group related information, and the connection includes a PDU session. In some embodiments, the group related information includes a group index and an index of UEs within the group.

In some embodiments, the SMF is configured to retrieve and request to receive update notifications regarding group-related information from a Universal data management entity (UDM). In some embodiments, the SMF is configured to: the connection establishment request is rejected if the group related information is not part of an explicit group to which the UE 10 belongs according to the group data in the SMF requested from the UDM. In some embodiments, the connection is configured to a centralized user plane architecture that uses a Session-and-service continuity (SSC) mode. In some embodiments, the network node 20 further comprises an Access and mobility management function (AMF) configured to consider the group local configuration information if an appropriate SMF is selected for the group to which the UE 10 belongs.

In some embodiments, the network node 20 further comprises a UPF configured to: the group local configuration information is considered if the appropriate UPF is selected for the group to which the UE belongs. In some embodiments, the PSA UPF is configured to implement a Quality of experience (QoS) handling procedure for group user data transmissions in a group communication system, and the SMF, based on local configuration or Policy Control Function (PCF) information, provides different QoS configurations for unicast and multicast communications. In some embodiments, the QoS enforcement for the uplink and downlink traffic flows is different, and the SMF provides different QoS configurations for the uplink and downlink traffic flows. In some embodiments, in the case of multicasting, the SMF provides the PSA UPF with a uniform QoS configuration for downlink traffic flows to different UEs in the group of the group communication system, and the PSA UPF enforces a uniform QoS policy for the downlink traffic flows to the different UEs in the group.

In some embodiments, the SMF is configured to provide a Packet Detection Rule (PDR) and a Forwarding Action Rule (FAR) to the PSA UPF. In some embodiments, the PDR includes group information and associated FAR information, and the FAR includes destination interface information for the group. In some embodiments, the destination interface information includes an Nx interface or an N6 interface associated with the group.

In some embodiments, in the case of unicast communication, the PSA UPF detects user data from one PDU session belonging to the group and detects that the destination address is an assigned address of other UEs in the group, and forwards the user data to the PDU session of the associated UE in the group. In some embodiments, the network node 20 also includes a serving UPF and other UPFs, where the connection for each group member UE terminates at the serving UPF and associated UE.

In some embodiments, the network node 20 further comprises an SMF configured to configure the serving UPF as the PSA UPF of the associated UE, and the PSA UPF is an anchor point for the UE to connect with other UPFs serving other UEs within the group of the group communication system. In some embodiments, when the connection type is an Internet protocol version four (IPv 4), IPv6 or IPv4v6 PDU session, the processor 21 is configured to send the IP address and/or prefix of the connection to the UE 10. In some embodiments, for an IPv4, IPv6, or IPv4v6 type PDU session, the PSA UPF is an IP anchor point assigned to the IP address and/or prefix of the UE 10. In some embodiments, the connection type is an ethernet type PDU session.

In some embodiments, for an ethernet-type PDU session, the SMF instructs the UPF to route downlink traffic based on the Media Access Control (MAC) address used by the UE 10 for uplink traffic. In some embodiments, if a group communication system shares the connection with another group communication system, an IP address and/or prefix of the connection is assigned to another UE of the other group communication system.

Fig. 2 illustrates a method 200 for performing group communication of user equipment according to an embodiment of the disclosure. The method 200 comprises the following steps: at block 202, sending a connection establishment request to a network node in a group communication system; and at block 204, establishing each connection for each group in the group communication system in accordance with the connection establishment request.

In some embodiments, the method further comprises establishing a plurality of connections for a plurality of groups in a group communication system to which the UE belongs according to the connection establishment request. In some embodiments, the method further comprises terminating each connection of each group in the group communication system using the network node, or the network node and the UE. In some embodiments, the connection setup request is a Protocol Data Unit (PDU) session setup request, the PDU session setup request includes a PDU session Identification (ID) and/or group related information, and the connection includes a PDU session.

In some embodiments, the group related information includes a group index and an index of UEs within the group. In some embodiments, the connection is configured to a centralized user plane architecture that uses a Session-and-service continuity (SSC) mode. In some embodiments, when the connection type is Internet protocol version four (IPv 4), IPv6, or IPv4v6, the method includes receiving an IP address and/or prefix of the connection from the network node. In some embodiments, the connection type is an ethernet type PDU session.

In some embodiments, if a group communication system shares the connection with another group communication system, an IP address and/or prefix of the connection is assigned to another UE of the other group communication system.

Fig. 3 illustrates a method 300 for performing group communication of network nodes according to an embodiment of the disclosure. The method 300 includes: at block 302, a connection establishment request from a User Equipment (UE) in a group communication system is received, and at block 304, a connection for the UE in the group communication system is handled.

In some embodiments, the method further comprises checking, using a Session Management Function (SMF), whether the connection establishment request conforms to a group to which the UE belongs. In some embodiments, the method further includes terminating each connection of the UEs in the group communication system using a Protocol data unit session anchor (PSA) User Plane Function (UPF).

In some embodiments, the connection setup request is a Protocol Data Unit (PDU) session setup request, the PDU session setup request includes a PDU session Identification (ID) and/or group related information, and the connection includes a PDU session. In some embodiments, the group related information includes a group index and an index of UEs within the group.

In some embodiments, the method further comprises retrieving and requesting, using the SMF, to receive an update notification regarding the group-related information from a Unified data management entity (UDM). In some embodiments, the method further comprises: rejecting the connection establishment request using the SMF if the group related information is not part of an explicit group to which the UE belongs according to the group data in the SMF requested from the UDM. In some embodiments, the connection is configured to a centralized user plane architecture that uses a Session-and-service continuity (SSC) mode.

In some embodiments, the method further comprises: if an appropriate SMF is selected for the group to which the UE belongs, the group local configuration information is considered using an Access and mobility management function (AMF). In some embodiments, the method further comprises: if an appropriate UPF is selected for the group to which the UE belongs, then the group local configuration information is considered using SMF. In some embodiments, the method further includes implementing a Quality of service (QoS) processing procedure for group user data transmissions in the group communication system using the PSA UPF, and the SMF providing different QoS configurations for unicast and multicast communications based on local configuration or Policy Control Function (PCF) information.

In some embodiments, the QoS enforcement for the uplink and downlink traffic flows is different, and the SMF provides different QoS configurations for the uplink and downlink traffic flows. In some embodiments, in the case of multicast, the method comprises: the method further includes providing, using the SMF, a unified QoS configuration for downlink traffic flows for different UEs in a group in the group communication system to the PSA UPF, and enforcing, using the PSA UPF, a unified QoS policy for the downlink traffic flows to the different UEs in the group. In some embodiments, the method further comprises providing a Packet Detection Rule (PDR) and a Forwarding Action Rule (FAR) to the PSA UPF using the SMF.

In some embodiments, the method further comprises: the PDR includes group information and associated FAR information, and the FAR includes destination interface information for the group. In some embodiments, the destination interface information includes an Nx interface or an N6 interface associated with the group. In some embodiments, in the case of unicast communication, the method comprises detecting user data from one PDU session belonging to the group using PSA UPF and detecting that the destination address is an assigned address of other UEs in the group, and the method further comprises forwarding the user data to the PDU session of the associated UE in the group using PSA UPF.

In some embodiments, the method further comprises terminating the connection of each group member UE using the serving UPF and the associated UE. In some embodiments, the method further includes configuring the serving UPF as a PSA UPF for the associated UE using the SMF, and the PSA UPF is an anchor point for other UPF connections of the UE with other UEs within the group serving the group communication system. In some embodiments, when the connection type is an Internet protocol version four (IPv 4), IPv6, or IPv4v6 PDU session, the method includes sending the IP address and/or prefix of the connection to the UE. In some embodiments, for an IPv4, IPv6, or IPv4v6 type PDU session, the PSA UPF is an IP anchor point assigned to the IP address and/or prefix of the UE.

In some embodiments, the method further comprises the connection type being a PDU session of the ethernet type. In some embodiments, the method further includes, for an ethernet-type PDU session, using the SMF to instruct the UPF to route downlink traffic flows based on a Media Access Control (MAC) address used by the UE for uplink traffic flows. In some embodiments, if a group communication system shares the connection with another group communication system, an IP address and/or prefix of the connection is assigned to another UE of the other group communication system.

Fig. 4 illustrates, in some embodiments, a 5G system architecture with a centralized user pane architecture using reference points to represent how various network functions interact with each other, in accordance with embodiments of the present disclosure.

A 5G system architecture is defined to support data connectivity and services, enabling deployments to use technologies such as network function virtualization and software defined networking. The 5G system architecture may utilize service-based interaction between certain Control Plane (CP) network functions. In some embodiments, some technical solutions are to separate User Plane (UP) functions from Control Plane (CP) functions, allowing independent scalability, evolution, and flexible deployment, e.g., centralized or distributed (remote) locations. In some embodiments, some technical solutions are to modularize the functional design, e.g., to achieve flexible and efficient network slicing. In some embodiments, some technical solutions define procedures (i.e., a set of interactions between network functions) as services wherever applicable, thereby making their reuse possible. In some embodiments, some technical solutions are to enable each network function to interact directly with other NFs when needed. This architecture does not preclude the use of intermediate functionality to help route control plane messages (e.g., like DRAs).

In some embodiments, some technical solutions are to minimize dependencies between AN Access Network (AN) and a Core Network (CN). The architecture is defined by a converged core network with a common AN-CN interface that integrates different access types, e.g., 3GPP access and non-3 GPP access. In some embodiments, some technical solutions will support a unified authentication framework. In some embodiments, some technical solutions will support "stateless" NF, where "compute" resources are separated from "store" resources. In some embodiments, some technical solutions will support capability exposure. In some embodiments, some technical solutions will support concurrent access to local and centralized services. To support low latency services and access to the local data network, an UP function may be deployed near the access network. In some embodiments, some technical solutions will support roaming in visited Public Land Mobile Networks (PLMNs) with locally routed traffic flows as well as locally breakout traffic flows.

The specification describes the architecture of a 5G system. The 5G architecture is defined as service-based, with the interaction between network functions represented as follows. Based on the service representation, a network function (e.g., an AMF) within the control plane makes its services accessible to other authorized network functions. This representation also includes point-to-point reference points, if necessary. Reference point representation, illustrating the interactions that exist between NF services in a network function described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF and SMF). The service based interface and reference points are shown in fig. 4. Network functions within the control plane of the 5G core network interact only using service-based interfaces.

In some embodiments, the 5G system architecture includes Network Functions (NFs), such as Authentication server function (AUSF) 401, Access and mobility management function (AMF) 402, Network Slice Selection Function (NSSF) 403, Policy control function (Policy control function, AMF) 404, Session Management Function (SMF) 405, Unified data management entity (UDM) 406, User plane function (User plane function, UPF)407, Application function (Application function, AF)408, User Equipment (UE) such as UE 1409, UE 2410, UE 1, etc. (User equipment UE), (wireless Access Network), (PCF) 24 AN, and (PCF) 8652, and upn 8652.

In some embodiments, in a centralized user plane architecture, a single SMF 405 and a single PSA UPF 413 are responsible for all PDU sessions for 5GLAN group communications. The PDU session for each group member UE terminates at PSA UPF 413. The PSA UPF 413 is the user plane anchor point for the user plane path within the 5GLAN group. All traffic flows of UEs participating in the 5GLAN group go through the PSA UPF 413. PSA UPF 413 may be an anchor point for multiple 5GLAN groups.

In some embodiments, in the processing of PDU sessions for 5GLAN communications, the SMF 405 is responsible for managing PDU sessions belonging to the 5GLAN group, including establishing, modifying and releasing PDU sessions, which are established (according to UE requests), modified (according to UE and 5GC requests) and released (according to UE and 5GC requests) as specified in clause 5.6. The UE may provide the PDU session ID and group related information in a PDU session setup request message sent to the network. This PDU session is specific to that group. The group related information may be a combination of S-NSSAI and DNN, or may be an internal group index. The SMF is responsible for checking whether the UE request conforms to the group to which the UE belongs. To do this, it retrieves and requests to receive update notifications on SMF level group data from the UDM 406. Such group data may be a group index and an index of UEs within the group (e.g., GPSI). If the group related information is not part of an explicit group to which the UE belongs according to the group data in the SMF 405 requested from the UDM 406, the SMF 405 may reject the PDU session establishment. The UE establishes one PDU session for only one group, and the UE may establish multiple PDU sessions for multiple groups to which the UE belongs. SSC pattern 1 can be applied to a PDU session of a centralized user plane architecture.

In some embodiments, in address allocation for 5GLAN communications, for IPv4 or IPv6 or IPv4v6 type PDU sessions, the PSA UPF 413 is the IP anchor point assigned to the IP address/prefix of the UE. For an ethernet type PDU session, SMF 405 may instruct PSA UPF 413 to route DL traffic flows based on the UE's MAC address for UL traffic flows. For IP type PDU sessions, SMF 405 performs the IP address management and assignment procedure specified in 5.8.2.2. In addition, for IP type PDU sessions, SMF 405 assigns an IP address/prefix to the UE during the 5GLAN group PDU session setup. To support multicast within 5 GLANs, SMF 405 may assign a destination multicast address for the group and provide the multicast address to the UEs in the group and PSA UPF 413. If the SMF 405 does not assign a destination multicast address, the UE may use the wildcard address as the destination address for the multicast in the group. To support unicast within 5GLAN, the UE needs to know the destination address of the peer UE within the 5GLAN group, which may be implemented by the application layer.

In some embodiments, the SMF selection function described in clause 6.3.2 for normal services when SMF 405 is selected for 5GLAN group communication, among the SMF and UPF selection functions. The AMF 402 may also consider group local configuration information (if any) to select an appropriate SMF 405 for the group. When the UPF 407 is selected for 5GLAN group communication, the UPF selection function described in clause 6.3.3 for normal service is applied. The SMF 405 may also consider group local configuration information (if any) to select the appropriate UPF 407.

In some embodiments, the QoS model defined in clause 5.7 is applied to 5GLAN communications in QoS for 5GLAN communications. The PSA UPF 413 performs a QoS treatment process for group user data transmission. SMF based on local configuration or PCF information may provide different QoS configurations for unicast and multicast communications. The QoS enforcement for the uplink and downlink traffic flows may be different, and the SMF 405 provides different QoS configurations for the uplink and downlink traffic flows. In the case of multicast, the SMF 405 provides the PSA UPF 413 with a unified QoS configuration for the downlink traffic flows for the different UEs in the group, and the PSA UPF 413 enforces a unified QoS policy on the downlink traffic flows to the different UEs in the group.

In some embodiments, in group forwarding path management, PDU sessions for a 5GLAN group constitute a group user data forwarding path. The SMF 405 provides the PDR and FAR to the PSA UPF 413. The PDR includes group information (e.g., group PDU session ID or CN tunnel information) and related FAR information. The FAR contains the destination interface for the group (i.e., local forwarding) and the destination interface information contains all Nx interfaces or N6 interfaces associated with the group. In case of multicast communication, the PSA UPF 413 detects user data from one PDU session belonging to the group and detects a destination address for multicast, and the PSA UPF 413 forwards the user data to other PDU sessions in the group. In case of unicast communication, the PSA UPF 413 detects user data from one PDU session belonging to the group and detects that the destination address is an assigned address of other UEs in the group, and the PSA UPF 413 forwards the user data to the PDU session of the associated UE in the group. If there are other UPFs between the UE and the PSA UPF 413, one CN tunnel is allocated for the PDU session between the other UPF and the PSA UPF 413, and the CN tunnel is dedicated to the group associated with the PDU session. The CN tunnel is released with the PDU session release. The CN tunnel management of the 5GLAN group is performed as specified in clause 5.8.2.10.

Fig. 5 illustrates that, in some embodiments, a 5G system architecture in the case of a distributed user pane architecture uses reference points to represent how various network functions interact with each other, in accordance with embodiments of the present disclosure.

In some embodiments, the 5G system architecture includes Network Functions (NF), such as Authentication server function (AUSF) 501, Access and mobility management function (Access and mobility management function, AMF)502, Network Slice Selection Function (NSSF) 503, Policy control function (Policy control function, AMF) 504, Session Management Function (SMF) 505, Unified Data management entity (Unified Data management, UDM)506, User plane function (User plane function, UPF)507, Application function (Application function, AF)508, User equipment (User equipment, UE) such as UE 1509, wireless Access Network (R) AN (R) 514, Network N512, Network N24, N8632, and Data Network N24, N6332.

In some embodiments, in a 5-GLAN architecture for a distributed user plane architecture, a single SMF 505 and multiple UPFs 507 are responsible for all PDU sessions for 5-GLAN group communications. The PDU session for each group member UE terminates at the serving UPF and associated UE. The SMF 505 may configure the serving UPF as the PSA UPF for the associated UE, and the PSA UPF is the anchor point for the UE to connect with other (PSA) UPFs serving other UEs within the group.

In some embodiments, in the handling of PDU sessions for 5GLAN communications, the SMF is responsible for managing PDU sessions belonging to the 5GLAN group, including setting up, modifying and releasing PDU sessions, which are set up (according to UE requests), modified (according to UE and 5GC requests) and released (according to UE and 5GC requests). The SMF 505 is responsible for checking whether the UE request conforms to the group to which the UE belongs. To do this, it retrieves and requests from the UDM 506 to receive an update notification on SMF level group data. In the PDU session setup request message sent to the network, the UE provides the PDU session ID and group related information. This PDU session is specific to that group. The group related information may be a combination of S-NSSAI and DNN, or may be an internal group index. If the group related information is not part of an explicit group to which the UE belongs according to the group data in the SMF requested from the UDM 506, the SMF 505 may reject the PDU session establishment. The UE establishes one PDU session for only one group, and the UE may establish multiple PDU sessions for multiple groups to which the UE belongs.

In some embodiments, in address assignment for 5GLAN communications, the PSA UPF is the IP anchor point assigned to the IP address/prefix of the UE for the IPv4 or IPv6 or IPv4v6 type PDU sessions. For an ethernet type PDU session, SMF 505 may instruct UPF 507 to route DL traffic flows based on the UE's MAC address for UL traffic flows. For IP type PDU sessions, SMF 505 performs the IP address management and assignment procedure specified in 5.8.2.2. In addition, the SMF 505 allocates an IP address/prefix to the UE during the 5GLAN group PDU session setup. To support multicast within 5 GLANs, the SMF 505 may assign a destination multicast address for the group and provide the multicast address to the UEs in the group. If SMF 505 does not assign a destination multicast address, a wildcard address may be used as the destination address for the multicast in the group. To support unicast within 5GLAN, the UE needs to know the destination address of the peer UE within the 5GLAN group, which may be implemented by the application layer.

In some embodiments, the SMF selection function described in clause 6.3.2 for normal services when SMF 505 is selected for 5-GLAN group communication, among the SMF and UPF selection functions. The AMF 502 may also consider group local configuration information (if any) to select an appropriate SMF 505 for the group. When the UPF 507 is selected for 5GLAN group communication, the UPF selection function described in clause 6.3.3 for normal services is applied. The SMF 505 may also consider group local configuration information (if any) to select the appropriate UPF 507.

In some embodiments, the QoS model defined in clause 5.7 is applied to 5GLAN communications in QoS for 5GLAN communications. The PSA UPF performs a QoS treatment process for group user data transmissions. SMF based on local configuration or PCF information may provide different QoS configurations for unicast and multicast communications. The QoS enforcement for the uplink and downlink traffic flows may be different, and the SMF 505 provides different QoS configurations for the uplink and downlink traffic flows. In the case of multicast, the SMF 505 provides the PSA UPF with a uniform QoS configuration for the downlink traffic flow targets of the different UEs in the group, and the PSA UPF enforces a uniform QoS policy on the downlink traffic flows to the different UEs in the group.

In some embodiments, in the group forwarding path management, the PDU sessions of the UEs in the group, the CN tunnel on the Nx interface of the group constitutes the group user data forwarding path. The SMF 505 is responsible for establishing and managing CN tunnels over the Nx interface between different PSA UPFs for different UEs within a 5GLAN group. The SMF 505 provides all CN tunnel information to each PSA UPF within the group and updates the CN tunnel information if the CN tunnel changes due to, for example, a PDU session of the group being established or released. The SMF 505 configures the PDR and FAR for each PSA UPF. The PDR includes group information (e.g., group PDU session ID or CN tunnel information) and related FAR information. The FAR contains the destination interface for the group and the destination interface information contains all Nx interfaces or N6 interfaces associated with the group. The PDU session and CN tunnel are specific to the group. In case of multicast communication, the PSA UPF of the sending UE detects user data from one PDU session associated with the group and detects that the destination address is for multicast, and forwards the user data to all other PSA UPFs according to the CN tunnel information configured for the group. The other PSA UPF forwards the usage data to the group-associated PDU session. The PDR table and FAR table are shown below.

In some embodiments, in the case of unicast communication, the sending UE's PSA UPF detects user data from one PDU session associated with the group and detects that the destination address is that of another UE in another (PSA) UPF in the group, which forwards the user data to the (PSA) UPF over the Nx interface. With this alternative, the SMF provides all UE addresses in the group to each PSA UPF in the group, and the PSA UPF information (e.g., CN tunnel information) for each address is associated (the PDU session associated with that address is terminated). For ethernet type PDUs, when a PDU session is established, the UE reports the MAC address to the SMF, which informs the relevant PSA UPF.

In some embodiments, the sending UE's PSA UPF detects user data from one PDU session associated with the group and detects that the destination address is the address of another UE in the (PSA) UPF in the group, i.e. the PSA UPF forwards the user data to the PDU session of the destination UE.

In some embodiments, the PSA UPF of the sending UE detects user data from one PDU session associated with the group, the PSA UPF forwards the user data to all other PSA UPFs according to the configured CN tunnel information of the group. Other PSA UPF detects the destination address of the user data, if the destination address is the address of the PDU session terminated by the PSA UPF, the PSA UPF forwards the user data to the PDU session; otherwise, the PSA UPF discards the user data.

Fig. 6-7 illustrate that, in some embodiments, point-to-multipoint group communication is provided. In some embodiments, to support one-to-many communication in a group, a group-specific Packet data network (PDU) session is introduced. Fifth generation systems (5 GS) may support group-specific PDU session establishment, release, modification, and group/group member addition or deletion. It should be appreciated that Session plane function (SMF) node 108 is responsible for group-specific PDU Session management. Different members of the group may be served by the same User Plane Function (UPF) node (e.g., UPF1 node 106) or different UPF nodes (e.g., UPF1 node 106 and UPF2 node 112). In one set, the scenes may be shown in fig. 6-8. UE-T102 is a transmitter UE, while UE-R1104 and UE-R2110 are receiver UEs, with the same UPF1 node 106 serving both UE-T102 and UE-R1104, and UE-R2110 served by UPF2 node 112. Data from the UE-T102 is transmitted in the Fifth generation system (5 GS) and routed by UPF nodes (e.g., UPF1 node 106 and UPF2 node 112).

The group-specific PDU session terminates at the member and serving UPF. When a group is established by an Application Function (AF) or a UE, a group-specific PDU session will be established for each group member added to the group as the group is created. SMF node 108 is enhanced to support group-based PDU session management functions, including group-based PDU session establishment. After the group is created, the group members are added to the group, and a group-specific PDU session is established for the newly added members. SMF node 108 is responsible for establishing routing tunnels between UPF nodes serving newly joined members and UPF nodes serving authorized sending members.

In some embodiments, the process describes a one-to-many communication PDU session establishment procedure. It is understood that a group is managed by the same SMF. The group creation and group member joining process is based on other solutions, which are not mentioned in this context. This embodiment is an example, and the present disclosure is not limited thereto.

When a group is created, the group members UE-T102 and UE-R1104 are added to the group and UE-T102 is authorized to send one-to-many data to the members in the group. UE-T102 initiates a group-specific PDU session setup request including a request for S-NSSAI, group information, etc. In detail, the group information may be, for example, a group index, group-specific Data Network Name (DNN) information, or group-specific application server information.

Upon receiving the request from the UE-T102, the SMF node 108 selects the UPF1 node 106 as the serving UPF for the particular group based on the S-NSSAI information and the group information. SMF node 108 sends a session setup request to UPF1 node 106 including Core Network (CN) tunnel information regarding the allocation of the N3 interface. The UPF1 node 106 acknowledges by sending a session setup response message. SMF node 108 sends a PDU session acceptance to UE-T102. In the case where the PDU session type is IPv4 or IPv6 or IPv4v6, SMF node 108 assigns an IP address/prefix for the PDU session, and that address/prefix is used for that group-specific. Alternatively, if the group shares a PDU session with other groups, a group-specific address is also assigned to at least one UE in the other groups.

When the UE-R2110 is added to the group, the UE-R2110 initiates a PDU session setup request to the SMF node 108 that includes S-NSSAI information and group information. The SMF node 108 selects the UPF2 node 112 as the serving UPF for the UE-R2110 and determines to establish a routing tunnel between the UPF1 node 106 serving the UE-T102 and the UPF2 node 112. SMF node 108 sends a session establishment request to UPF2 node 112 including the assigned CN tunnel information. The CN tunnel information includes the UPF2 address of the tunnel between the UPF1 node 106 and the UPF2 node 112 and the UPF2 address of the N3 tunnel. The UPF2 node 112 acknowledges by sending a session setup response message. The SMF node 108 establishes a routing tunnel between the UPF1 node 106 and the UPF2 node 112 and provides the UPF2 address of the tunnel between the UPF1 node 106 and the UPF2 node 112 to the UPF1 node 106. Further, SMF node 108 provides UE-T102 with the PDU session and association information for the routing tunnel. The SMF node 108 sends a PDU session acceptance to the UE-R2110. In the case where the PDU session type is IPv4 or IPv6 or IPv4v6, the SMF node 108 assigns an IP address/prefix for the PDU session, the address/prefix being group-specific for the UE-R2110. If there is another PDU session for the group of UE-R2110, the existing PDU session can be reused for the newly joined group, i.e., multiple groups can share one PDU session for receiving members in the group.

Further, the UE-T102 sends group data to the UPF1 node 106, and the UPF1 node determines to receive the UE-R1104, UE-R2110, based on the routing association information provided at block 8, and routes the data to the tunnels corresponding to the UE-R1104 and UE-R2110, respectively. If the PDU session is shared by multiple groups, the UPF1 node 106 determines to receive the UE-R1104, UE-R2110 for group information based on the group specific address information.

Fig. 8 is a block diagram of an example system 700 for wireless communication in accordance with an embodiment of the present disclosure. Embodiments described in this disclosure may be implemented into a system using any suitably configured hardware and/or software. Fig. 8 shows a system 700 that includes Radio Frequency (RF) circuitry 710, baseband circuitry 720, application circuitry 730, memory/storage 740, a display 750, a camera 760, a sensor 770, and an input/output (I/O) interface 780, coupled to each other at least as shown.

The application circuitry 730 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general purpose processors and special purpose processors, such as a graphics processor and an application processor. The processor may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

Baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may comprise a baseband processor. The baseband circuitry may handle various radio control functions that may enable communication with one or more radio networks through the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, and the like. In some embodiments, the baseband circuitry may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Network (WMAN), Wireless Local Area Network (WLAN), Wireless Personal Area Network (WPAN). Embodiments of radio communications in which the baseband circuitry is configured to support more than one wireless protocol may be referred to as multi-mode baseband circuitry.

In various embodiments, baseband circuitry 720 may include circuitry to operate on signals that are not strictly considered to be in baseband frequencies. For example, in some embodiments, the baseband circuitry may include circuitry to operate on signals having an intermediate frequency between the baseband frequency and the radio frequency.

The RF circuitry 710 is capable of communicating with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, and the like to facilitate communication with the wireless network.

In various embodiments, RF circuitry 710 may include circuitry to operate on signals that are not strictly considered to be at radio frequencies. For example, in some embodiments, the RF circuitry may include circuitry to operate on signals having an intermediate frequency between a baseband frequency and a radio frequency.

In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part in one or more of RF circuitry, baseband circuitry, and/or application circuitry. As used in this disclosure, "Circuit" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic Circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), executing one or more software or firmware programs that provide the described functionality, a combinational logic Circuit, and/or other suitable hardware components. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with, one or more software or firmware modules.

In some embodiments, some or all of the constituent components of the baseband circuitry, the application circuitry, and/or the memory/storage devices may be implemented together on a System on a chip (SOC).

Memory/storage 740 may be used to load and store data and/or instructions, for example, for a system. The memory/storage of one embodiment may comprise any combination of suitable volatile memory (e.g., Dynamic Random Access Memory (DRAM)) and/or non-volatile memory (e.g., flash memory).

In various embodiments, I/O interface 780 may include one or more user interfaces designed to enable a user to interact with the system and/or peripheral component interfaces designed to enable peripheral components to interact with the system. The user interface may include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, and the like. The peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a Universal Serial Bus (USB) port, an audio jack, and a power interface.

In various embodiments, the sensors 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of or interact with baseband circuitry and/or RF circuitry to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites.

In various embodiments, display 750 may include displays, such as liquid crystal displays and touch screen displays. In various embodiments, system 700 may be a mobile computing device, such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, and the like. In various embodiments, the system may have more or fewer components and/or different architectures. Where appropriate, the methods described in this disclosure may be implemented as computer programs. The computer program may be stored on a storage medium such as a non-transitory storage medium.

In the disclosed embodiments, an apparatus and method for performing group communication can provide good group communication performance and high reliability, and provide a solution how to transmit user data within a 5G system and provide corresponding control information and/or procedures. The disclosed embodiments are a combination of techniques/processes that may be employed in 3GPP specifications to create an end product.

Those of ordinary skill in the art will appreciate that each of the units, algorithms, and steps described and disclosed in the embodiments of the present disclosure may be implemented using electronic hardware, or a combination of software and electronic hardware for a computer. Whether these functions are executed in hardware or software depends on the application conditions and design requirements of the technical plan.

Those of ordinary skill in the art may implement the functionality of each particular application in different ways without departing from the scope of the present disclosure. It will be appreciated by a person skilled in the art that since the working processes of the above-described system, device and unit are substantially the same, he/she may refer to the working processes of the system, device and unit in the above-described embodiments. For ease of description and simplicity, these operations will not be described in detail.

It should be understood that the systems, devices, and methods disclosed in embodiments of the present disclosure may be implemented in other ways. The above embodiments are merely exemplary. The partitioning of cells is based solely on logic functions, while other partitions exist in the implementation. Multiple units or components may be combined or integrated in another system. It is also possible to omit or skip certain features. In another aspect, the shown or discussed mutual coupling, direct coupling or communicative coupling operates indirectly or communicatively through some port, device or element, whether electrically, mechanically or otherwise.

Units that are separate components for explanation are physically separate or not physically separate. The unit for displaying is a physical unit or not, i.e. located in one location or distributed over multiple network units. Some or all of the cells are used for purposes of the embodiments. Also, each functional unit in each embodiment may be integrated in one processing unit, physically separated, or integrated in one processing unit having two or more units.

If the software functional unit is implemented and used and sold as a product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical plan proposed by the present disclosure can be implemented in the form of a software product, in essence, or in part. Alternatively, a part of the technical plan that is advantageous to the conventional technology may be implemented in the form of a software product. The software product in a computer is stored in a storage medium that includes a plurality of commands for a computing device (e.g., a personal computer, server, or network device) to perform all or some of the steps disclosed by embodiments of the present disclosure. The storage medium includes a USB disk, a removable hard disk, a Read-only memory (ROM), a Random Access Memory (RAM), a floppy disk or other medium capable of storing program codes.

While the disclosure has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the disclosure is not to be limited to the disclosed embodiment, but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims (69)

1. A user equipment, UE, in a group communication system, comprising:

a memory;

a transceiver; and

a processor coupled to the memory and the transceiver,

wherein the processor is configured to:

controlling the transceiver to send a connection establishment request to a network node in a group communication system; and

establishing each connection of each group in the group communication system according to the connection establishment request.

2. The UE of claim 1, wherein the processor is configured to establish a plurality of connections for a plurality of groups in the group communication system to which the UE belongs in accordance with the connection establishment request.

3. The UE of claim 1 or 2, wherein each connection of each group in the group communication system terminates at the network node, or at the processor of the UE and the network node.

4. The UE of any of claims 1 to 3, wherein the connection establishment request is a Protocol Data Unit (PDU) session establishment request including a PDU session Identification (ID) and/or group related information, the connection including a PDU session.

5. The UE of claim 4, wherein the group-related information comprises a group index and UE indices within the group.

6. The UE of any of claims 1-5, wherein the connection is configured to a centralized user plane architecture that uses a session and service continuous SSC mode.

7. The UE of any of claims 1 to 6, wherein, when the connection type is Internet protocol version four IPv4, IPv6 or IPv4v6, the processor is configured to receive an IP address and/or prefix of the connection from the network node.

8. The UE of any of claims 1 to 6, wherein the connection type is an Ethernet type PDU session.

9. The UE of claim 7, wherein if the group communication system shares the connection with another group communication system, an IP address and/or prefix of the connection is assigned to another UE of the other group communication system.

10. A method for performing group communication for user equipment, UE, comprising:

sending a connection establishment request to a network node in the group communication system; and

establishing each connection of each group in the group communication system according to the connection establishment request.

11. The method of claim 10, further comprising: and establishing a plurality of connections for a plurality of groups in the group communication system to which the UE belongs according to the connection establishment request.

12. The method of claim 10 or 11, further comprising: terminating each connection of each group in the group communication system using the network node or the network node and the UE.

13. The method according to any of claims 10 to 12, wherein the connection establishment request is a PDU session establishment request, the PDU session establishment request comprises a PDU session identification ID and/or group related information, and the connection comprises a PDU session.

14. The method of claim 13, wherein the group-related information comprises a group index and UE indices within the group.

15. The method of any of claims 10 to 14, wherein the connection is configured to a centralized user plane architecture using a session and service continuous SSC pattern.

16. The method according to any of claims 10 to 15, wherein when the connection type is internet protocol version four IPv4, IPv6 or IPv4v6, the method comprises receiving an IP address and/or prefix of the connection from the network node.

17. The method according to any of claims 10 to 15, wherein the connection type is an ethernet type PDU session.

18. The method of claim 16, wherein if the group communication system shares the connection with another group communication system, an IP address and/or prefix of the connection is assigned to another UE of the other group communication system.

19. A network node in a group communication system, comprising:

a memory;

a transceiver; and

a processor coupled to the memory and the transceiver,

wherein the processor is configured to:

controlling the transceiver to receive a connection establishment request from a user equipment, UE, in the group communication system; and

processing connections for the UEs in the group communication system.

20. The network node of claim 19, further comprising: a session management function, SMF, configured to check whether the connection establishment request conforms to a group to which the UE belongs.

21. The network node according to claim 19 or 20, further comprising: a protocol data unit session anchor (PSA) User Plane Function (UPF) configured to terminate each connection of the UEs in the group communication system.

22. The network node according to any of claims 19 to 21, wherein the connection establishment request is a protocol data unit, PDU, session establishment request comprising a PDU session identification, ID, and/or group related information, and the connection comprises a PDU session.

23. The network node of claim 22, wherein the group-related information comprises a group index and UE indices within the group.

24. The network node according to claim 22 or 23, wherein the SMF is configured to retrieve and request to receive an update notification on the group related information from a unified data management entity, UDM.

25. The network node of claim 24, wherein the SMF is configured to reject the connection establishment request if the group related information is not part of an explicit group to which the UE belongs from group data in the SMF requested from the UDM.

26. The network node of any of claims 19 to 25, wherein the connection is configured to a centralized user plane architecture using a session and service continuous SSC pattern.

27. The network node of any of claims 20 to 26, further comprising: an access and mobility management function, AMF, configured to: group local configuration information is considered if an appropriate SMF is selected for the group to which the UE belongs.

28. The network node of claims 20 to 27, further comprising a UPF, the SMF being configured to: if an appropriate UPF is selected for the group to which the UE belongs, group local configuration information is considered.

29. The network node of any of claims 21 to 28, wherein the PSA UPF is configured to implement quality of service QoS handling procedures for group user data transmissions in the group communication system, and to provide different QoS configurations for unicast and multicast communications based on SMF of local configuration or policy control function PCF information.

30. The network node of claim 29, wherein QoS enforcement for uplink and downlink traffic flows is different, and the SMF provides the different QoS configurations for the uplink and downlink traffic flows.

31. The network node of claim 29 or 30, wherein, in the case of multicasting, the SMF provides a unified QoS configuration of downlink traffic flows for different UEs in a group of the group communication system to the PSA UPF, and the PSA UPF enforces a unified QoS policy for the downlink traffic flows to different UEs in the group.

32. The network node according to any of claims 21 to 31, wherein the SMF is configured to provide a packet detection rule PDR and a forwarding action rule FAR to the PSA UPF.

33. The network node of claim 32, wherein the PDR comprises group information and related FAR information, and the FAR comprises destination interface information for the group.

34. The network node of claim 33, wherein the destination interface information comprises an Nx interface or an N6 interface associated with the group.

35. The network node according to any of claims 21 to 34, wherein in case of unicast communication, the PSA UPF detects user data in one PDU session belonging to the group and detects that the destination address is an assigned address of other UEs in the group, the PSA UPF forwarding the user data to the PDU session of the associated UE in the group.

36. The network node of claim 19, further comprising a serving UPF and other UPFs, the connection for each group member UE terminating at the serving UPF and the associated UE.

37. The network node of claim 36, further comprising: an SMF configured to configure the serving UPF as a PSA UPF for the associated UE, and the PSA UPF is an anchor point for the UE to connect with other UPFs serving other UEs within the group of the group communication system.

38. The network node of any of claims 19 to 37, wherein, when the connection type is an internet protocol version four IPv4, IPv6 or IPv4v6 PDU session, the processor is configured to send the IP address and/or prefix of the connection to the UE.

39. The network node of claim 38, wherein the PSA UPF is an IP anchor point assigned to the IP address and/or prefix of the UE for an IPv4, IPv6, or IPv4v6 type PDU session.

40. The network node according to any of claims 19 to 37, wherein the connection type is an ethernet type PDU session.

41. The network node of claim 40, wherein, for the Ethernet-type PDU session, the SMF instructs the UPF to route downlink traffic flows based on a Media Access Control (MAC) address used by the UE for uplink traffic flows.

42. The network node of claim 40, wherein if the group communication system shares the connection with another group communication system, an IP address and/or prefix of the connection is assigned to another UE of the other group communication system.

43. A method for performing group communication of network nodes, comprising:

receiving a connection establishment request from a User Equipment (UE) in the group communication system; and

processing connections for the UEs in the group communication system.

44. The method of claim 43, further comprising: checking, using a session management function, SMF, whether the connection establishment request conforms to a group to which the UE belongs.

45. The method of claim 43 or 44, further comprising: terminating each connection of the UEs in the group communication system using a protocol data unit session anchor (PSA) User Plane Function (UPF).

46. The method according to any of claims 43 to 45, wherein the connection setup request is a protocol data unit, PDU, session setup request comprising a PDU session identification, ID, and/or group related information, and the connection comprises a PDU session.

47. The method of claim 46, wherein the group-related information comprises a group index and UE indices within the group.

48. The method of claim 46 or 47, further comprising: retrieving and requesting reception of an update notification regarding the group related information from a unified data management entity, UDM, using the SMF.

49. The method of claim 48, further comprising: rejecting the connection establishment request using the SMF if the group related information is not part of an explicit group to which the UE belongs according to group data in the SMF requested from the UDM.

50. The method of any one of claims 43 to 49, wherein the connection is configured to a centralized user plane architecture using a session and service continuous SSC mode.

51. The method of any of claims 44-50, further comprising: if an appropriate SMF is selected for the group to which the UE belongs, group local configuration information is taken into account using an access and mobility management function AMF.

52. The method of claims 44 to 50, further comprising: if an appropriate UPF is selected for the group to which the UE belongs, then group local configuration information is considered using the SMF.

53. The method of any of claims 45-52, further comprising: using the PSA UPF to implement quality of service QoS handling procedures for group user data transmissions in the group communication system, and SMF based on local configuration or policy control function PCF information to provide different QoS configurations for unicast and multicast communications.

54. The method of claim 53, wherein QoS enforcement for uplink and downlink traffic flows is different, and the SMF provides the different QoS configurations for the uplink and downlink traffic flows.

55. The method according to claim 53 or 54, wherein in case of multicasting, the method comprises: providing, using the SMF, a unified QoS configuration for downlink traffic flows for different UEs of a group of the group communication system to the PSA UPF, and the method further comprises enforcing, using the PSA UPF, a unified QoS policy for downlink traffic flows to different UEs of the group.

56. The method of any of claims 45-55, further comprising: providing a packet detection rule PDR and a forwarding action rule FAR to the PSA UPF using the SMF.

57. The method as in claim 56 wherein the PDR comprises group information and related FAR information and the FAR comprises destination interface information for the group.

58. The method of claim 57, wherein the destination interface information comprises an Nx interface or an N6 interface associated with the group.

59. The method according to any one of claims 45 to 58, wherein in case of unicast communication, the method comprises: detecting user data in one PDU session belonging to the group using the PSA UPF and detecting that a destination address is an assigned address of other UEs in the group, and the method further comprises forwarding the user data to the PDU session of associated UEs in the group using the PSA UPF.

60. The method of claim 43, further comprising: terminating the connection for each group member UE using a serving UPF and the associated UE.

61. The method of claim 60, further comprising: configuring the serving UPF as a PSA UPF for the associated UE using SMF, and the PSA UPF is an anchor point for other UPF connections of the UE with other UEs within a group serving the group communication system.

62. The method of any one of claims 43 to 61, wherein, when the connection type is a PDU session of IPv4, IPv6 or IPv4v6, the method comprises sending the IP address and/or prefix of the connection to the UE.

63. The method of claim 62, wherein the PSA UPF is an IP anchor point assigned to the IP address and/or prefix of the UE for an IPv4, IPv6, or IPv4v6 type PDU session.

64. The method according to any of claims 43 to 61, wherein the connection type is an Ethernet type PDU session.

65. The method of claim 64, wherein for the Ethernet-type PDU session, the method comprises using the SMF to instruct the UPF to route downlink traffic flows based on a Media Access Control (MAC) address used by the UE for uplink traffic flows.

66. The method of claim 65, wherein if the group communication system shares the connection with another group communication system, an IP address and/or prefix of the connection is assigned to another UE of the other group communication system.

67. A non-transitory machine-readable storage medium having stored thereon instructions which, when executed by a computer, cause the computer to perform the method of any one of claims 10-18 and 43-66.

68. A terminal device, comprising: a processor and a memory configured to store a computer program, the processor being configured to execute the computer program stored in the memory to perform the method of any of claims 10 to 18.

69. A network node, comprising: a processor and a memory configured to store a computer program, the processor configured to execute the computer program stored in the memory to perform the method of any of claims 43 to 66.

Images