WO2020224559A1 - 群组管理方法、装置及系统 - Google Patents

群组管理方法、装置及系统 Download PDF

Info

Publication number
WO2020224559A1
WO2020224559A1 PCT/CN2020/088519 CN2020088519W WO2020224559A1 WO 2020224559 A1 WO2020224559 A1 WO 2020224559A1 CN 2020088519 W CN2020088519 W CN 2020088519W WO 2020224559 A1 WO2020224559 A1 WO 2020224559A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
identifier
internal
external
information
Prior art date
Application number
PCT/CN2020/088519
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 EP20802287.1A priority Critical patent/EP3955521A4/en
Publication of WO2020224559A1 publication Critical patent/WO2020224559A1/zh
Priority to US17/519,741 priority patent/US12063709B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data
    • 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
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1044—Group management mechanisms 
    • H04L67/1046—Joining mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication

Definitions

  • This application relates to the field of communication technology, and in particular to a group management method, device and system.
  • the traditional 3rd generation partnership project (3rd generation partnership project, 3GPP) provides Internet Protocol (IP) services that can adopt the server-client communication mode, that is, through the server Proxy forwarding completes the mutual communication between client and client.
  • IP Internet Protocol
  • terminal A sends a WeChat message to terminal B through the 3GPP network.
  • the message first reaches the WeChat application server outside the 3GPP network through the 3GPP network.
  • the message arrives through the base station.
  • UPF then UPF reaches the WeChat application server of the external DN.
  • the WeChat application server processes the WeChat message and sends the message to the terminal B through the 3GPP network, thereby completing the communication between the terminal A and the terminal B.
  • a virtual local area network service (virtual LAN service) is proposed in the 5th generation (5G) network.
  • the 3GPP network needs to be multiple in a group
  • the terminal provides multiple types of transmission services.
  • multi-type transmission services include services based on IP, Ethernet, or other non-IP technologies.
  • the virtual LAN service is the communication between terminal A and terminal B completed by the 3GPP network, usually without the deployment and participation of external application servers.
  • the route between terminal A and terminal B may be the base station of terminal A-terminal A-UPF-base station of terminal B-terminal B. It can be seen that, compared with the traditional technology, the messages of the terminals A and B may not pass through the external application server.
  • the embodiments of the present application provide a group management method, device, and system, which can dynamically create groups in the process of using virtual LAN service technology.
  • an embodiment of the present application provides a group management method, which consists of a data network element (for example, the UDM shown in FIG. 1) or a component in the data network element (for example, a chip system).
  • the method includes:
  • a first group request is received from the application function network element, the first group request includes indication information, an external group identifier, and first group information, and the indication information is used to indicate a group service type. If the group service type is to create a group, the internal group identifier corresponding to the external group identifier is obtained, and the internal group identifier, the external group identifier, and the first group information are associated.
  • the external group identifier is a group identifier that cannot be recognized by the internal network element of the core network; the internal group identifier is a group identifier that can be recognized inside the core network.
  • the group management method provided in the embodiment of the present application can receive the first group request from the application function network element.
  • the first group creation request carries indication information for indicating the group service type, first group information, and external group identifier.
  • the data network element can obtain the internal group ID corresponding to the external group ID based on the first group request, and combine the internal group ID, the external group ID, and the first group ID.
  • Group information is associated.
  • the user's operation of creating a group at the application layer is random.
  • the first group information, external group identification and Internal group identification which means that AF has the ability to dynamically create groups.
  • 3GPP network elements can distinguish different groups based on internal group identifiers, so as to target different groups.
  • the group is managed accordingly.
  • the data network element may also perform the following steps: send the internal group identifier and the first group information to one or more group members.
  • the data network element sends the newly allocated internal group identifier to the interface network element.
  • the data network element sends the URSP to one or more group members in the URSP update process.
  • the URSP includes the internal group identifier and the first group information (such as DNN, S-NSSAI, etc.), so that To update the URSP of group members.
  • the terminal when data arrives at the terminal, it can send a PDU session establishment request to the network device (such as AMF), and the PDU session establishment request carries the DNN of the group where the terminal is located, so that the network device (such as AMF) can recognize the Which group the terminal is in.
  • the network device such as AMF
  • this application provides a group management method, which consists of a data network element or a component (such as a chip system) in the data network element.
  • the method includes:
  • a second group request is received from the interface network element, the second group request includes an external group identifier and first group information, and the external group identifier is a group identifier that cannot be identified inside the core network.
  • the internal group identifier is a group identifier that can be identified within the core network.
  • the second group request does not carry indication information for indicating the group service type, which can reduce the signaling overhead of interaction between the interface network element and the data network element.
  • the UDM can also be dynamically triggered to obtain the internal group identifier corresponding to the external group identifier.
  • obtaining the internal group ID corresponding to the external group ID includes:
  • the group management mentioned in this application includes but is not limited to adding group members, deleting group members, and group member authority management.
  • the data network element can also perform the following steps:
  • the internal group identifier and external group identifier of group 1, and the internal group identifier and external group identifier of group 2 have been stored in the NEF. Then, after the UDM issues the internal group ID and external group ID of the newly allocated group 3 to the NEF, the NEF stores the internal group ID and the external group ID of the three groups. In this way, because NEF stores the internal group ID and external group ID of one or more groups, subsequently, when NEF receives the external group ID from AF, NEF can determine whether the internal group ID corresponding to the external group ID has been stored. Group ID. If the NEF does not store the internal group identifier corresponding to the external group identifier, the UDM is requested to allocate the internal group identifier for the newly created group.
  • the data network element may also perform the following steps: send the internal group identifier and the first group information to one or more group members.
  • an embodiment of the present application provides a group management method, which consists of an interface network element (the interface network element may be, for example, the NEF shown in FIG. 1) or a component in the interface network element (such as a chip system).
  • the method includes:
  • a third group request is received from the application function network element, the third group request includes an external group identifier and first group information, and the external group identifier is a group identifier that cannot be identified inside the core network. Determine whether the entry of the internal group identifier corresponding to the external group identifier has been stored. If the entry of the internal group identifier corresponding to the external group identifier is not stored, then the second group request is sent to the data network element.
  • the external group identifier and the first identifier of one or more group members are included.
  • the internal group identifier is a group identifier that can be identified within the core network.
  • an embodiment of the present application provides a group management device, which may be a data network element (for example, the UDM shown in FIG. 1) or a component in a data network element (for example, a chip system).
  • the device includes:
  • the communication interface is used to receive the first group request from the application function network element.
  • the first group request includes indication information, an external group identifier and first group information.
  • the indication information is used to indicate the group service type, and the external group
  • the identifier is a group identifier that cannot be recognized by the internal network element of the core network; the processor is used to obtain the internal group identifier corresponding to the external group identifier if the group service type is to create a group, and the internal group identifier is the core network
  • the internally identifiable group identifier; the internal group identifier, the external group identifier, and the first group information are associated.
  • the communication interface is also used to send the newly allocated internal group identifier to the interface network element.
  • the communication interface is also used to send the internal group identifier and the first group information to one or more group members.
  • this application provides a group management device, which is a data network element (for example, the UDM shown in FIG. 1) or a component in a data network element (for example, a chip system).
  • the device includes:
  • the communication interface is used to receive a second group request from the interface network element, the second group request includes an external group identifier and first group information, and the external group identifier is a group identifier that cannot be identified inside the core network; processing The device is used to obtain the internal group ID corresponding to the external group ID, the internal group ID is the group ID that can be recognized inside the core network; the internal group ID, the external group ID, and the first group information are associated .
  • the processor is configured to obtain the internal group identifier corresponding to the external group identifier, including: determining whether the entry of the internal group identifier corresponding to the external group identifier has been stored; if it is determined that it is not stored For the entry of the internal group identifier corresponding to the external group identifier, the internal group identifier corresponding to the external group identifier is obtained.
  • the communication interface is also used to send an internal group identifier to the interface network element to instruct the interface network element to store the internal group identifier.
  • the communication interface is also used to send the internal group identifier and the first group information to one or more group members.
  • an embodiment of the present application provides a group management device, which may be a data network element (for example, the NEF shown in FIG. 1) or a component in a data network element (for example, a chip system).
  • the device includes:
  • the communication interface is used to receive a third group request from the application function network element, the third group request includes an external group identifier and first group information, and the external group identifier is a group identifier that cannot be identified inside the core network;
  • the processor is used to determine whether the entry of the internal group ID corresponding to the external group ID has been stored, the internal group ID is a group ID that can be recognized inside the core network; the communication interface is also used if the external group ID is not stored.
  • the corresponding entry of the internal group identifier sends a second group request to the data network element.
  • the second group request includes the external group identifier and the first identifier of one or more group members.
  • the first group information includes at least one of the following information: the data network identifier of the group, the slice information of the group, the session type corresponding to the group, and one or The first identification of multiple group members.
  • the present application provides a group management device, which is used to implement the function of the data network element in any of the foregoing aspects, or is used to implement the function of the interface network element in any of the foregoing aspects.
  • the present application provides a group management device, which has the function of realizing the group management method of any one of the foregoing aspects.
  • This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • a group management device including: a processor and a memory; the memory is used to store computer-executed instructions, and when the group management device is running, the processor executes the computer-executed instructions stored in the memory, So that the group management device executes the group management method of any one of the above-mentioned aspects.
  • a group management device including: a processor; the processor is configured to be coupled with a memory, and after reading instructions in the memory, execute the group management method according to any one of the above aspects according to the instructions .
  • an embodiment of the present application provides a group management device.
  • the device may be a chip system.
  • the chip system includes a processor and a memory for realizing the function of the method described in any of the above aspects.
  • the chip system can be composed of chips, or can include chips and other discrete devices.
  • a group management device in a twelfth aspect, is provided.
  • the device may be a circuit system, the circuit system includes a processing circuit, and the processing circuit is configured to execute the group management method of any one of the foregoing aspects.
  • an embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute the method in any of the above aspects.
  • the embodiments of the present application also provide a computer program product, including instructions, which when run on a computer, cause the computer to execute the method in any of the above aspects.
  • an embodiment of the present application provides a system.
  • the system includes a data network element that executes the group management method of any one of the first aspect and the first aspect, and any one of the third aspect and the third aspect is executed.
  • the interface network element of the item group management method Alternatively, the system includes a data network element that executes the group management method of any one of the second aspect and the second aspect and an interface network element that executes the group management method of any one of the third aspect and the third aspect.
  • the system further includes an application function network element (for example, it may be the AF shown in FIG. 1).
  • the application function network element is used to receive a group request from the terminal, for example, a request to create a new group from the terminal. And send a group request to the data network element to trigger the data network element to allocate an internal group identifier for the new group.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the application
  • FIG. 2 is a schematic diagram of the structure of a group management system provided by an embodiment of the application.
  • FIG. 3 is a schematic flowchart of a contract method provided by an embodiment of the application.
  • FIG. 4 is a schematic flowchart of a contracting method provided by an embodiment of the application.
  • FIG. 5 is a schematic flowchart of a group management method provided by an embodiment of the application.
  • FIG. 6 is a schematic flowchart of a group management method provided by an embodiment of the application.
  • FIG. 7 is a schematic flowchart of a group management method provided by an embodiment of the application.
  • FIG. 8 is a schematic flowchart of a group management method provided by an embodiment of the application.
  • FIG. 9 is a schematic flowchart of a group management method provided by an embodiment of the application.
  • FIG. 10 is a schematic structural diagram of a group management apparatus provided by an embodiment of the application.
  • FIG. 11 is a schematic structural diagram of a group management apparatus provided by an embodiment of the application.
  • External group ID (external group ID): After the terminal dynamically creates a group at the application layer, the application server assigns a dynamic group ID to the application layer group.
  • the group ID assigned by the WeChat server can be It is called the external group ID.
  • users of terminals 1 to 6 create a WeChat group "academic discussion group”.
  • the WeChat application server After the WeChat application server detects the user's operation to create a WeChat group, it can assign an application layer group ID to the WeChat group. It uniquely identifies the WeChat group at the application layer.
  • Internal group ID (internal group ID): The network equipment in the 3GPP network usually cannot directly identify the external group ID, and therefore cannot understand the meaning of the ID, which results in the inability to distinguish between different groups, and thus cannot perform operations on the corresponding group. Manage and provide subsequent LAN services (LAN type service).
  • the AF can send a group request to the 3GPP network element, so that the 3GPP network element can generate the group's internal group identifier according to the group request.
  • the internal group identifier is a group identifier that can be recognized by the 3GPP core network element. In this way, 3GPP network elements can use internal group identifiers to perform group management and so on.
  • Group management for example, can add group members to the group, delete group members, and so on.
  • a single group management assistance information (Single network slice selection assistance information, S-NSSAI) is used to uniquely represent a network slice, and its information-element is shown in Table 1:
  • S-NSSAI information-element identifier, IEI
  • IEI element identifier
  • Length of S-NSSAI contents represents the length of the cell (it can be in bytes).
  • SST is used to indicate which network service the slice can provide.
  • Network services include but are not limited to eMBB services, uRLLC services, and mMTC services.
  • the SST length is 1 byte.
  • SST includes standardized (ie standard SST value (value)) and operator-defined (ie non-standard SST value) types. Refer to Table 2 below. Currently, only the content with SST value of 1-3 is defined in the agreement:
  • the SSTs of the two slices are the same, which means that the service types indicated by the SSTs of the two slices are the same, that is, the SST values are the same. For example, if the SST of slice 1 is eMBB (SST value is 1), and the SST of slice 2 is also eMBB (SST value is 1), then the SSTs of slice 1 and slice 2 are the same.
  • the group management method provided by the embodiment of the present application is applied to a communication system using a virtual LAN service technology.
  • the communication system includes: operation management (OAM) network elements, group management function (network slice selection function, NSSF), network exposure function (NEF), network storage function (network repository function, NRF) ), policy control function (PCF), application function (application function, AF), unified data management (unified data management, UDM), authentication server function (authentication server function, AUSF), access and mobility Management function (core access and mobility management function, AMF), session management function (session management function, SMF), access network (access network, AN) network elements, where AN includes wired access network and wireless access network ( Network elements or equipment such as radio access network (RAN), user plane function (UPF), data network (DN) network elements, and terminals.
  • OFAM operation management
  • NSSF network slice selection function
  • NEF network exposure function
  • NRF network storage function
  • PCF policy control function
  • application function application function, AF
  • unified data management
  • the terminal accesses the AN in a wireless or wired manner.
  • the wireless method can be, for example, access via wireless-fidelity (WiFi), or access via a cellular network (such as E-UTRA, NR, etc.).
  • WiFi wireless-fidelity
  • a cellular network such as E-UTRA, NR, etc.
  • SMF communicates with AMF through N11 (not shown in Figure 1) Communication, SMF communicates with UDM through N10 (not shown in Figure 1), SMF communicates with PCF through N7 (not shown in Figure 1); AMF communicates with AUSF through N12 (not shown in Figure 1), AUSF communicates with UDM through N13 (not shown in Figure 1).
  • the AF communicates with the PCF through N5 (not shown in Figure 1).
  • the above-mentioned network elements can communicate in a certain way (for example, the terminal communicates with AMF through N1).
  • the terminal communicates with AMF through N1.
  • the above only lists some of the ways of communication between the network elements. To simplify the description, In the embodiment of this application, the communication mode between other network elements will not be described in detail.
  • the terminals involved in the embodiments of the present application may include various handheld devices with communication functions, wearable devices, computing devices, or other processing devices connected to a modem; and may also include personal digital assistants (personal digital assistants). , PDA) computer, tablet computer, laptop computer (laptop computer), machine type communication (MTC) terminal, user equipment (UE), etc.
  • PDA personal digital assistant
  • MTC machine type communication
  • UE user equipment
  • a terminal it can also refer to a chip system such as a UE.
  • the embodiment of the present application does not limit the implementation form of the terminal.
  • each network element and the name of the interface between each network element in Figure 1 are just an example, and the name of each network element or the interface between each network element in a specific implementation may be other names, or network elements It can also be called an entity, which is not specifically limited in the embodiments of the present application. All or part of the network elements in Figure 1 may be physical physical network elements, or virtualized network elements, which are not limited here.
  • a certain network element obtains information from another network element (for example: B network element), which may mean that A network element directly receives information from B network element, or It means that A network element receives information from B network element via other network elements (for example: C network element).
  • B network element may mean that A network element directly receives information from B network element, or It means that A network element receives information from B network element via other network elements (for example: C network element).
  • C network element can transparently transmit the information, or process the information, for example: carry the information in different messages for transmission or filter the information , Only send the filtered information to A network element.
  • network element A when network element A sends information to network element B, it can mean that network element A sends information directly to network element B, or it can mean that network element A sends information to network element B via other network elements (for example, network element C). Yuan) sends information to the B network element.
  • the system 200 includes: a data network element 203 and an interface network element 204.
  • Interface network element 204 an interface for providing external application function network element 205 to interact with data network element 203. Specifically, it can be used to receive a group request from the application function network element 205, and send the group request to the data network element 203.
  • Data network element 203 It is used to assign an internal group identifier to the newly created group according to the group request from the application function network element 205, so that subsequent 3GPP network elements can be based on the identifiable internal The group identifier distinguishes different groups and performs group-related management. It is also used to send a notification message to the policy network element 202 so as to notify the policy network element 202 to update the URSP.
  • URSP is used to distinguish different groups.
  • Terminals 201 in different groups will be assigned different URSP rules.
  • the terminal 201 can determine which group it is in according to the URSP rule.
  • the group management system further includes: a terminal 201, an application function network element 205, a management network element 206, and a policy network element 202.
  • Application function network element 205 used to detect the operation of terminal 201 to create a group when terminal 201 dynamically establishes a group at the application layer, such as receiving a group request from terminal 201. It is also used to assign an external group ID to each newly created group based on the group request, that is, the External Group ID. It is also used to send a group request to the interface network element 204 to request the creation of the new group. It is also used to send a contract request to the management network element 206 to request registration and contract for virtual LAN services (virtual LAN services may also be referred to as LAN services in this document).
  • virtual LAN services may also be referred to as LAN services in this document.
  • the management network element 206 is used to receive a subscription request from the application function network element 205, and allocate information such as DNN/S-NSSAI for establishing a LAN group to the application function network element 205 according to the contract request.
  • the policy network element 202 is used to update the URSP according to the notification message from the data network element 203, and deliver the updated URSP to the terminal 201 corresponding to the LAN group.
  • Terminal 201 used to receive the URSP issued from the policy network element 202.
  • an APP on the terminal 201 triggers a LAN service
  • the terminal can query the LAN service according to the URSP (ie WeChat message service) corresponding to DNN/S-NSSAI and other information, and report DNN/S-NSSAI and other information when establishing a PDU session, so that the 3GPP network can identify which LAN group the terminal belongs to based on DNN/S-NSSAI and other information .
  • URSP ie WeChat message service
  • the application function network element in Figure 2 can be the AF in Figure 1
  • the interface network element can be the NEF in Figure 1
  • the data network element can be the UDM in Figure 1
  • the management network element can be the OAM in Figure 1.
  • the policy network element can be the PCF in Figure 1.
  • the connection relationship between the network elements shown in FIG. 2 may refer to the connection relationship between the corresponding network elements in FIG. 1. I won't repeat it here.
  • the embodiment of this application is applied to the system shown in Figure 1, that is, the application function network element is the AF shown in Figure 1, the interface network element is the NEF shown in Figure 1, the data network element is the UDM shown in Figure 1, and the policy network element is The PCF and the management network element shown in FIG. 1 are the OAM shown in FIG. 1 as an example to illustrate the technical solution of the embodiment of the present application.
  • the process of AF applying for LAN service from OAM is introduced.
  • This process is the basis of the group management method in the embodiment of this application.
  • AF can obtain the permission to use LAN services after obtaining the authorization of OAM.
  • AF can obtain the permission to dynamically create groups.
  • the process of AF applying for LAN service from OAM includes the following steps:
  • the AF sends a contract request (for example, a 5G-LAN service request) to the OAM.
  • a contract request for example, a 5G-LAN service request
  • OAM receives the subscription request from the AF network element.
  • the subscription request is used to request a subscription for LAN services.
  • the subscription request includes the application identifier (APP ID) supported by AF.
  • APP ID application identifier
  • the subscription request includes the identifier of the WeChat application supported by the WeChat application server.
  • the OAM determines the first configuration information (LAN configuration data) corresponding to the AF based on the application supported by the AF.
  • the first configuration information is used to indicate the subscription configuration of the group.
  • OAM may configure first configuration information of one or more groups for AF.
  • the first configuration information includes data network identifiers respectively corresponding to one or more groups.
  • the network data identification may be, for example, DNN, or other information used to identify the data network.
  • Different groups correspond to different data network identifiers. In this way, the data network identifier can uniquely identify a group.
  • the terminal can send a PDU session establishment request to the network device (such as AMF).
  • the PDU session establishment request carries the DNN of the group where the terminal is located, so that the network device (such as AMF) can identify where the terminal is. In a group.
  • the first configuration information further includes at least one of the following information: slice information corresponding to one or more groups, and session types corresponding to one or more groups.
  • the slice information of the group may be, for example, a single group management assistance information (single network slice selection assistance information, S-NSSAI).
  • groups are usually created based on service types, that is, service types of terminals in the same group are usually the same. Based on this, the service type (such as SST) of the S-NSSAI of each terminal in the same group is usually the same.
  • SST single network slice selection assistance information
  • the user creates group 1 through the APP on the terminal.
  • the terminal service requirements of this group 1 are high reliability and low latency.
  • Each terminal in this group 1 corresponds to the S-NSSAI
  • the SST may be uRLLC.
  • the user creates group 2.
  • the terminal in this group 2 needs a larger bandwidth to perform services, and the SST of the S-NSSAI corresponding to each terminal in the group 2 may be eMBB.
  • Each PDU session (session) supports one session type, which includes but is not limited to one of IPv4, IPv6, IPv4v6, Ethenet, and Unstructured.
  • groups are created based on APP types and service types.
  • APP such as WeChat
  • the session types of these terminals can be the same.
  • WeChat group created through a WeChat application
  • the service types of the terminals in the same group are usually the same, so the session types of the terminals in the same group are usually the same.
  • the first configuration information allocated by OAM is: ⁇ WeChat group 1: Use DNN1 to identify the WeChat group 1, and the service type of the terminal slice in WeChat group 1 is eMBB, The session type of the terminal in WeChat group 1 is Ethernet type;
  • WeChat group 2 Use DNN2 to identify the WeChat group 2, and the service type of terminal slices in WeChat group 2 is uRLLC, and the session type of terminals in WeChat group 2 is Ethernet Types of ⁇ .
  • the first configuration information of how many groups the OAM configures specifically for the AF is related to the AF contract conditions.
  • the contract condition may be, but is not limited to, for example, the contract fee.
  • the OAM can configure more group first configuration information for the AF.
  • OAM can configure the first configuration information of 1000 groups for the AF when the AF requests to sign up for the LAN service. In this way, the AF can obtain the first configuration information corresponding to the 1000 groups only once by requesting the LAN service, and the AF has the ability to create 1000 groups.
  • the OAM configures the first configuration information for the AF with fewer groups (for example, 10).
  • AF requests LAN services at a time and can have the ability to create 10 groups. If the user needs to create the 11th group at the application layer, the AF can send a subscription request to the OAM to request new first configuration information.
  • the OAM may only configure the first configuration information of the 11th group, or may configure the first configuration information of multiple groups (for example, configure the 11th to 100th groups).
  • the OAM sends a subscription response to the AF.
  • the AF receives the subscription response from the OAM.
  • the subscription response includes first configuration information corresponding to one or more groups respectively.
  • the external AF can dynamically subscribe to the operator’s OAM for LAN services according to its own needs, and then obtain the first configuration information such as DNN and S-NSSAI from the OAM, so that the subsequent AF can be based on the obtained first configuration information.
  • the configuration information dynamically creates a LAN group.
  • the AF can dynamically assign an external group identifier to the newly created group, and the core network side can dynamically assign an internal group identifier to the newly created group.
  • AF applies for LAN service from OAM, which can be specifically implemented as follows:
  • the AF sends a contract request to the OAM.
  • OAM receives the subscription request from the AF network element.
  • the subscription request is used to request the subscription to register for the LAN service, that is, to request the core network to allocate the second configuration information.
  • a detailed description of the second configuration information can be found below.
  • the subscription request includes the application identifiers supported by the AF and the external group identifiers of one or more groups allocated by the AF.
  • the WeChat application server is expected to subscribe to 100 groups of LAN services. In other words, AF is expected to have the ability to create 100 groups, then the WeChat application server can send a subscription request to OAM.
  • the request carries the identifier of the WeChat application and the 100 external group identifiers dynamically pre-allocated by the WeChat application server (for example, the external group identifiers pre-allocated by the WeChat application server for groups 1-100).
  • the subscription request may be a 5G-LAN service request, for example.
  • the OAM obtains second configuration information of one or more groups according to the external group identifiers of the one or more groups.
  • the second configuration information is used to indicate the subscription configuration of the group.
  • the second configuration information of the group includes: the internal group identification of the group and the data network identification of a single group.
  • the second configuration information of a single group further includes at least one of the following information: slice information of the single group, and session type corresponding to the single group.
  • OAM can allocate second configuration information corresponding to one or more groups to AF according to a preset strategy.
  • OAM can also send the above-mentioned one or more external group IDs and APP IDs to other network elements, so as to use
  • the computing power of other network elements calculates the second configuration information corresponding to one or more groups respectively, that is, the other network elements allocate the corresponding second configuration information to one or more groups.
  • the embodiments of this application do not limit this.
  • the OAM associates the external group identifier of each group with the second configuration information, and obtains the correspondence between the external group identifier of each group and the second configuration information.
  • OAM may also associate the external group identifier, the second configuration information, and the APP ID corresponding to the group.
  • OAM associates the group's external group identifier and the group's second configuration information (optionally, the group's APP ID).
  • the OAM sends the external group identifier and the corresponding second configuration information to the UDM (optionally, the APP ID corresponding to the group is also sent).
  • the UDM stores the correspondence between the external group identifier and the second configuration information.
  • UDM stores the above-mentioned corresponding relationship in a unified data repository (UDR).
  • the UDM stores the correspondence between the external group identifier, the second configuration information, and the APP ID of each group.
  • AF when AF triggers a 5G LAN service to the network side (for example, creating a 5G LAN group), AF provides UDM with an external group ID, and UDM can find the corresponding external group ID according to the corresponding relationship stored in UDR The internal group identifier, so that the network side uses the internal group identifier to perform group management, etc.
  • the OAM sends a subscription response to the AF.
  • the subscription response includes the foregoing second configuration information, which is used to indicate the subscription configuration of one or more groups.
  • the execution timing of S406 is not limited. In addition to the execution timing shown in FIG. 4, S406 may be directly executed after the second configuration information is obtained in S402. Alternatively, S406 may be executed after S403. Or execute S406 at other timings.
  • the OAM can dynamically allocate the second configuration information for the AF according to the external group identifier provided by the AF, associate the external group identifier with the second configuration information, and store the association in the UDM.
  • the AF sends the external group ID to the UDM, and the UDM searches for the internal group ID according to the stored correspondence relationship. If the corresponding internal group ID can be found, the internal group ID is directly used.
  • the group identifier performs group management, etc. If the internal group identifier corresponding to the group cannot be found, the corresponding internal group identifier is generated for the core network to use for subsequent LAN services.
  • the method provided in the embodiment of the present application enables the AF to dynamically allocate the external group identifier
  • the core network side can also dynamically allocate the network side layer group identifier. That is, it supports AF to dynamically create groups.
  • the embodiment of the present application also provides a group management method. Based on the contracting process shown in FIG. 3 or FIG. 4, referring to FIG. 5, the method for dynamically managing a group includes the following steps:
  • the AF sends a first group request to the NEF.
  • NEF receives the first group request from the AF.
  • the first group request includes indication information (indication) and external group ID (External Group ID).
  • the external group identifier is a group identifier that cannot be identified by the internal network element of the core network.
  • the indication information is used to indicate the group service type.
  • Group service types include, but are not limited to, creating groups, updating group parameters, deleting group members, adding group members, and group member authority management.
  • the first group request further includes first group information
  • the first group information further includes at least one of the following information: the data network identifier of the group, the slice information of the group, the session type corresponding to the group,
  • the group includes the first identification of one or more group members and the application identification corresponding to the group.
  • the first identifier includes, but is not limited to, a general public subscriber identity (GPSI). Each terminal corresponds to a GPSI.
  • GPSI general public subscriber identity
  • NEF sends an authentication request to UDM.
  • UDM receives an authentication request from NEF.
  • the authentication request is used to query whether the AF has subscribed to the LAN service, that is, to authenticate the AF.
  • S502 is an optional step.
  • the UDM sends an authentication response to the NEF.
  • NEF receives the authentication response from UDM.
  • the authentication response is used to indicate whether the AF has subscribed to the LAN service.
  • the UDM determines whether the AF has subscribed to the LAN service, and feeds back an authentication response to the NEF.
  • the authentication response indicates that the AF has subscribed to the LAN service, or the AF has not subscribed to the LAN service.
  • UDM does not directly indicate whether the AF has subscribed to the LAN service, but feeds back an authentication response to the NEF, and the authentication response includes the subscription information of the AF. In this way, the NEF can determine whether the AF has subscribed to the LAN service according to the subscription information of the AF.
  • S503 is an optional step.
  • the NEF sends the first group request to the UDM.
  • UDM receives the first group request from NEF.
  • NEF invokes the Nudm_Parameter Provision_xxx request service of UDM to send the second group request to UDM.
  • the NEF calls the Nudm_Parameter Provision_update request service of the UDM to send the second group request to the UDM.
  • the group service type is deleting group members
  • NEF invokes the Nudm_Parameter Provision_delete request service of UDM to send the second group request to UDM.
  • a generation strategy is pre-configured in UDM.
  • UDM generates internal group identification based on the generation strategy.
  • the generation strategy may be a preset algorithm.
  • the UDM calculates the internal group identifier based on the preset algorithm.
  • the UDM may also obtain the internal group identifier from other network elements after receiving the first group request. That is, other network elements calculate the internal group ID and feed back the calculation result to UDM.
  • UDM can calculate the internal group ID by itself, or directly obtain the calculated internal group ID from other network elements.
  • the embodiment of the present application does not limit the way the UDM obtains the internal group identifier.
  • the UDM itself calculates the internal group identifier corresponding to the newly created WeChat group.
  • the UDM determines the second identity of one or more group members according to the first identity of the one or more group members.
  • the UDM sends the second identification of one or more group members to the NEF.
  • S507 is an optional step.
  • the UDM associates the internal group identifier, the external group identifier, and the first group information.
  • the embodiment of the present application may use the following format to associate the internal group ID, the external group ID, and the first group information: ⁇ group 1 internal group ID 1, group 1 external group ID A , DNN1 of group 1, S-NSSAI of group 1, session type corresponding to group 1, and group 1 includes terminal 1 (the first identifier is xx) and terminal 2 (the first identifier is yy) ⁇ .
  • group 1 includes terminal 1 (the first identifier is xx) and terminal 2 (the first identifier is yy) ⁇ .
  • ⁇ group 1 internal group ID 1, group 1 external group ID A, group 1 DNN1, group 1 S-NSSAI1, group 1 includes terminal 1 (the first ID is xx ) And terminal 2 (the first identifier is yy) ⁇ .
  • other formats can also be used to express the association between the above-mentioned information, such as a table format. The embodiments of this application do not limit this.
  • the UDM sends a group response to the AF.
  • the AF receives the group response from the UDM.
  • the group response is used to indicate that the group is successfully created, which means that the UDM has associated the internal group ID, the external group ID, and the first group information.
  • the UDM first sends a group response to the NEF, and the group response carries the internal group identifier newly allocated by the UDM, and then the NEF sends the group response to the AF.
  • the NEF can obtain the internal group identifier corresponding to the external group identifier.
  • the UDM sends a notification message to the PCF.
  • the PCF receives notification messages from UDM.
  • the notification message carries at least one of the following information: internal group identification, application identification (APP ID) of the group, second identification of group members, data network identification, slice information, and session type.
  • APP ID application identification
  • the PCF generates a URSP according to the notification message.
  • the URSP includes at least one of the following information: internal group identification, group application identification, data network identification, slice information, and session type.
  • S512 and PCF respectively send URSP to one or more group members.
  • the group management method provided in the embodiment of the present application can receive the first group request from the application function network element.
  • the first group creation request carries indication information for indicating the group service type, first group information, and external group identifier.
  • the data network element can obtain the internal group ID corresponding to the external group ID based on the first group request, and combine the internal group ID, the external group ID, and the first group ID.
  • Group information is associated.
  • the user's operation of creating a group at the application layer is random.
  • the first group information, external group identification and Internal group identification which means that AF has the ability to dynamically create groups.
  • 3GPP network elements can distinguish different groups based on internal group identifiers, so as to target different groups.
  • the group is managed accordingly.
  • UDM after the UDM receives the first group request from the AF, if the group service type requested by the first group is to create a group, it means that the AF needs to create a new group , UDM directly obtains the internal group identifier corresponding to the newly created group to ensure that subsequent core network elements can identify different groups based on the internal group identifier. In this implementation, UDM does not need to execute logic such as judgment, and the logic implementation complexity of UDM is reduced.
  • the embodiment of the present application also provides a group management method.
  • the method for dynamically managing groups includes the following steps:
  • the AF sends a third group request to the NEF.
  • NEF receives the third group request from the AF.
  • the third group request carries the external group identifier and the first group information.
  • the first group information includes at least one of the following information: the data network identifier of the group, the slice information of the group, the session type corresponding to the group, the first identifier of one or more group members included in the group, and the group The APP ID.
  • AF calls NEF's Nnef_ParameterProvision_Update request service to send a third group request to NEF.
  • NEF sends an authentication request to UDM.
  • UDM receives an authentication request from NEF.
  • the UDM sends an authentication response to the NEF.
  • NEF receives the authentication response from UDM.
  • S503 is an optional step.
  • the NEF sends a second group request to the UDM.
  • UDM receives the second group request from NEF.
  • the second group request includes the external group identification and the first identification of one or more group members.
  • the second group request further includes at least one of the following information: DNN, S-NSSAI, session type, and application identifier.
  • the UDM determines whether an entry of the internal group identifier corresponding to the external group identifier has been stored.
  • one or more external group IDs and one or more internal group IDs are stored in the UDR. If the UDM cannot find the internal group ID corresponding to the external group ID in the UDR, then UDM obtains the internal group ID corresponding to the external group ID.
  • the UDM can use its own computing power or use the computing power of other network elements to calculate the internal group ID corresponding to the external group ID.
  • the UDM sends the internal group identifier corresponding to the external group identifier to the AF.
  • the UDM determines the second identity of one or more group members according to the first identity of the one or more group members.
  • the first identifier includes GPSI
  • the second identifier includes SUPI.
  • the 3GPP network element can identify the terminals included in the group based on SUPI.
  • the UDM sends the second identification of one or more group members to the NEF.
  • the NEF receives the second identification of one or more group members from the UDM.
  • the second group request sent by NEF to UDM does not include one or more of the data network identification of the group, the network slice information of the group, the session type corresponding to the group, and the application identification , NEF may also perform the following step S608:
  • the NEF sends a fourth group request to the UDM.
  • UDM receives the fourth group request from NEF.
  • the fourth group request includes the internal group ID of the group, the second ID of one or more group members, the data network ID, the network slice information of the group, the session type corresponding to the group, the APP ID in One or more.
  • NEF invokes the Nudm_ParameterProvision_Update request service of UDM to send the third group request to UDM.
  • NEF no longer sends the data network identification to UDM, but sends the internal group identification, One or more of at least one second identifier, network slice information of the group, session type corresponding to the group, and APP ID.
  • NEF can send one or more pieces of information required by UDM to one or more messages (for example, only through the second group request, or through multiple messages such as the second group request and the fourth group request).
  • the UDM associates the internal group identifier, the external group identifier, and the first group information to obtain a correspondence between the internal group identifier, the external group identifier, and the first group information.
  • the UDM stores the external group identifier, the internal group identifier, and the first group information.
  • the corresponding relationship between the external group ID, the internal group ID and the first group information of the newly created group is stored in the UDR.
  • the UDM sends a group response to the AF.
  • the UDM first sends a group response to the NEF, the group response carries the internal group identifier allocated by the UDM, and the NEF then sends the group response to the AF.
  • the UDM sends a notification message to the PCF.
  • the PCF receives notification messages from UDM.
  • the PCF generates a URSP according to the notification message.
  • S512 and PCF respectively send URSP to one or more group members.
  • one or more group members receive URSP from the PCF.
  • the terminals in the group can update the URSP, so that different routes can be determined according to different groups during subsequent LAN services.
  • UDM can also execute S506 and 507 first, and then execute S605.
  • S510 may be executed first, and then S509 may be executed.
  • UDM after receiving the external group ID of a certain group from AF, UDM can determine whether the internal group ID corresponding to the external group ID has been stored, and then determine which one to use The identifier identifies the group to ensure that subsequent core network elements can identify different groups.
  • the embodiment of the present application also provides a group management method.
  • the method of dynamically creating a group includes the following steps:
  • NEF sends a subscription message to UDM.
  • the UDM receives a subscription message from the NEF, and the subscription message is used to request to subscribe to the correspondence between the external group identifier, the internal group identifier, and the first group information.
  • the subscription means that the UDM can actively send the corresponding relationship to the NEF.
  • the UDM may actively send the updated corresponding relationship to the NEF. So that NEF can store the corresponding relationship.
  • this S701 is an optional step.
  • NEF may not subscribe to the UDM for the correspondence between the new internal group ID, the external group ID, and the first group information.
  • NEF since NEF can trigger UDM to generate a new internal group ID, UDM can also actively send the NEF that triggers the generation of a new internal group ID after generating a new internal group ID. Send the new internal group ID, external group ID and first group information.
  • the AF sends a third group request to the NEF.
  • NEF receives the third group request from the AF.
  • NEF sends an authentication request to UDM.
  • UDM receives an authentication request from NEF.
  • S502 is an optional step.
  • the UDM sends an authentication response to the NEF.
  • NEF receives the authentication response from UDM.
  • S503 is an optional step.
  • the NEF judges whether an internal group identifier corresponding to the external group identifier is stored.
  • UDM receives the second group request from NEF.
  • the second group request is used to request UDM to allocate an internal group identifier.
  • the UDM obtains the internal group identifier corresponding to the external group identifier.
  • the UDM determines the second identity of one or more group members according to the first identity of the one or more group members.
  • the UDM sends the second identification of one or more group members to the NEF.
  • the NEF sends a fourth group request to the UDM.
  • UDM receives the fourth group request from NEF.
  • the UDM associates the internal group identifier, the external group identifier, and the first group information to obtain a correspondence between the internal group identifier, the external group identifier, and the first group information.
  • the UDM sends a group response to the AF.
  • the UDM first sends a group response to the NEF, the group response carries the internal group identifier newly allocated by the UDM, and the NEF then sends the group response to the AF.
  • the UDM sends a notification message to the PCF.
  • the PCF receives notification messages from UDM.
  • the PCF generates a URSP according to the notification message.
  • S512 and PCF respectively send URSP to one or more group members.
  • NEF can subscribe to UDM for the corresponding relationship, so that when the corresponding relationship in UDM is updated, UDM notifies NEF of the external group ID and the new internal group converted from the external group ID Identifies the first group information corresponding to the external group identifier. Subsequently, after the NEF receives the external group identifier of a certain group from the AF, the NEF can determine whether the internal group identifier corresponding to the external group identifier has been stored.
  • the embodiment of the present application also provides a group management method.
  • the method of dynamically creating a group includes the following steps:
  • the AF sends a third group request to the NEF.
  • NEF receives the third group request from the AF.
  • NEF sends an authentication request to UDM.
  • UDM receives an authentication request from NEF.
  • S502 is an optional step.
  • the UDM sends an authentication response to the NEF.
  • NEF receives the authentication response from UDM.
  • S503 is an optional step.
  • the NEF obtains the internal group identification, external group identification, and first group information of one or more groups.
  • S804 can be specifically implemented as:
  • NEF sends an acquisition request to UDM.
  • UDM receives the acquisition request from NEF.
  • the acquisition request is used for the NEF to acquire the internal group identification, external group identification, and first group information of one or more groups after receiving the third group request from the AF.
  • the UDM sends the internal group identification, external group identification and first group information of one or more groups to the NEF.
  • the UDM sends the internal group identification, external group identification, and first group information of all stored groups to NEF.
  • NEF For example, UDM stores the internal group ID, external group ID, and first group information corresponding to groups 1-10, and UDM will store the internal group ID, external group ID, and first group information of these 10 groups.
  • the group information is delivered to NEF.
  • the NEF judges whether there is an internal group identifier corresponding to the external group identifier.
  • NEF queries whether there is an internal group ID corresponding to the external group ID based on the internal group ID, external group ID, and first group information of one or more groups obtained from UDM .
  • UDM receives the second group request from NEF.
  • the second group request is used to request UDM to allocate an internal group identifier.
  • the UDM obtains the internal group identifier corresponding to the external group identifier.
  • the UDM determines the second identity of one or more group members according to the first identity of the one or more group members.
  • the UDM sends the second identification of one or more group members to the NEF.
  • the NEF sends a fourth group request to the UDM.
  • S608 is an optional step.
  • the UDM associates the internal group identifier, the external group identifier, and the first group information.
  • the UDM stores the external group identifier, the internal group identifier, and the first group information.
  • the UDM stores the newly generated internal group identifier, the external group identifier corresponding to the internal group identifier, and the first group information corresponding to the internal group identifier.
  • the UDM sends a group response to the AF.
  • the UDM sends a notification message to the PCF.
  • the PCF receives notification messages from UDM.
  • the PCF generates a URSP according to the notification message.
  • S512 and PCF respectively send URSP to one or more group members.
  • NEF after NEF receives the external group ID of a certain group from AF, it can apply to UDM for the internal group ID, external group ID and second group ID of one or more groups in real time.
  • a correspondence relationship of group information, and determining whether the internal group identifier corresponding to the external group identifier has been stored based on the correspondence relationship can ensure that subsequent core network elements can identify different groups based on the internal group identifier.
  • the embodiment of the present application also provides a group management method.
  • the method of dynamically creating a group includes the following steps:
  • NEF receives the third group request from the AF.
  • the third group request may be a 5G LAN Internal Group ID Allocation Request.
  • the third group request carries at least one of the following: the data network identification of the group, the network slice information of the group, the session type corresponding to the group, the first identification of one or more group members, and the APP ID.
  • the third group request also carries indication information. Used to indicate the type of group service.
  • NEF sends an authentication request to UDM.
  • UDM receives an authentication request from NEF.
  • S502 is an optional step.
  • the UDM sends an authentication response to the NEF.
  • NEF receives the authentication response from UDM.
  • S503 is an optional step.
  • NEF sends a second group request to UDM.
  • UDM receives the second group request from NEF.
  • the second group request is used to request the creation of a group.
  • the second group request carries at least one of the following: the data network identifier of the group, the network slice information of the group, the session type corresponding to the group, at least one first identifier, APP ID.
  • the second group request also carries indication information for indicating the group service type.
  • the UDM obtains the internal group ID according to at least one of the following information: data network ID, slice information, session type, ID of at least one terminal, and APP ID.
  • UDM can calculate the internal group ID by itself, or obtain the internal group ID from other network elements. For example, UDM assigns an internal group ID to the group according to the data network ID and slice information of the group.
  • the UDM determines a second identification of one or more group members according to the first identification of one or more group members.
  • the UDM sends the second identification of one or more group members to the NEF.
  • the UDM associates the internal group identifier, the external group identifier, and the first group information.
  • the UDM stores the newly generated internal group identifier, the external group identifier corresponding to the internal group identifier, and the first group information corresponding to the internal group identifier.
  • the UDM sends the internal group identifier, the external group identifier and the first group information to the AF.
  • the UDM issues the newly generated internal group identifier, the external group identifier corresponding to the internal group identifier, and the first group information corresponding to the internal group identifier to NEF.
  • the AF receives the internal group identification, the external group identification and the first group information from the UDM.
  • the UDM sends a group response to the AF.
  • the group response can be 5G LAN Internal Group ID Allocation response.
  • the group response is used to indicate that the internal group ID, the external group ID, and the first group information have been associated.
  • S1009 and S509 can be implemented in one step. That is, the UDM can send the internal group ID, the external group ID, and the first group information to the AF through the group response.
  • the UDM sends a notification message to the PCF.
  • the PCF receives notification messages from UDM.
  • the PCF updates the URSP according to the notification message.
  • the PCF sends URSP to at least one terminal respectively.
  • UDM may not execute the judgment logic, but directly generate the internal group corresponding to the external group ID Mark, the logic implementation complexity of UDM has been reduced.
  • each device in the foregoing method embodiments may also be implemented by a chip that can be used in the device.
  • each device includes a hardware structure and/or software module corresponding to each function.
  • the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Those skilled in the art can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the technical solutions of the embodiments of the present application.
  • the embodiments of the present application can divide functional units of data network elements, interface network elements, application function network elements, terminals, policy network elements, management network elements, etc., according to the foregoing method examples.
  • each functional unit can be divided corresponding to each function.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • Fig. 10 shows a schematic block diagram of a group management apparatus provided in an embodiment of the present application.
  • the group management apparatus 1200 may exist in the form of software, or may be hardware, for example, may be a chip that can be used in a hardware device.
  • the group management apparatus 1200 includes a processing unit 1202 and a communication unit 1203.
  • the processing unit 1202 may be used to support the group management apparatus 1200 to execute S505 and S506 shown in FIG. 5, and/or other processes used in the solution described herein.
  • the communication unit 1203 is used to support communication between the group management apparatus 1200 and other network elements (such as interface network elements), for example, to perform S404 and S406 shown in FIG. 4 and/or other steps of the solution described herein.
  • the processing unit 1202 may be used to support the group management apparatus 1200 to execute S704 shown in FIG. 7 and/or other processes used in the solution described herein.
  • the communication unit 1203 is used to support communication between the group management apparatus 1200 and other network elements (for example, data network elements), for example, to perform S701, S502, S503 shown in FIG. 7 and/or other aspects of the solution described herein. step.
  • the processing unit 1202 may be used to support the group management apparatus 1200 to allocate a new external group identifier for the newly created group, and/or be used in other processes of the solution described herein.
  • the communication unit 1203 is used to support communication between the group management apparatus 1200 and other network elements (such as interface network elements), for example, to perform S501 and S509 shown in FIG. 5, and/or other steps of the solution described herein.
  • the processing unit 1202 may be used to support the group management apparatus 1200 to execute S511 shown in FIG. 5 and/or other processes used in the solution described herein.
  • the communication unit 1203 is used to support communication between the group management apparatus 1200 and other network elements, for example, execute S510 and S512 shown in FIG. 5, and/or other steps of the solution described herein.
  • the processing unit 1202 may be used to support the group management apparatus 1200 to perform S402 and S403 shown in FIG. 4, and/or other processes used in the solution described herein.
  • the communication unit 1203 is used to support communication between the group management apparatus 1200 and other network elements, for example, execute S401, S404 shown in FIG. 4, and/or other steps of the solution described herein.
  • the processing unit 1202 may be used to support the group management apparatus 1200 to learn about the group it belongs to according to the URSP, and/or other processes used in the solution described herein.
  • the communication unit 1203 is used to support communication between the group management apparatus 1200 and other network elements, for example, to perform S512 shown in FIG. 5 and/or other steps of the solution described herein.
  • the group management apparatus 1200 may further include a storage unit 1201 for storing program codes and data of the group management apparatus 1200, and the data may include but not limited to raw data or intermediate data.
  • the processing unit 1202 may be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processing (Digital Signal Processing, DSP), application-specific integration Circuit (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination of computing functions, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication unit 1203 may be a transceiver, a transceiving circuit, a communication interface, or the like.
  • the storage unit 1201 may be a memory.
  • the processing unit 1202 is a processor
  • the communication unit 1203 is a communication interface
  • the storage unit 1201 is a memory
  • the structure of the group management apparatus involved in the embodiment of the present application may be as shown in FIG. 11.
  • FIG. 11 shows a simplified schematic diagram of a possible design structure of a group management device involved in an embodiment of the present application.
  • the group management apparatus 1500 includes a processor 1502, a communication interface 1503, and a memory 1501.
  • the group management apparatus 1500 may further include a bus 1504.
  • the communication interface 1503, the processor 1502, and the memory 1501 may be connected to each other through a bus 1504.
  • the bus 1504 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 1504 can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only one line is used to represent in FIG. 11, but it does not mean that there is only one bus or one type of bus.
  • a person of ordinary skill in the art can understand that: in the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part.
  • the computer can be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • computer instructions can be transmitted from a website, computer, server, or data center through a cable (such as Coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to transmit to another website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media. Available media can be magnetic media (for example, floppy disks, hard drives, tapes), optical media (for example, Digital Video Disc (DVD)), or semiconductor media (for example, Solid State Disk (SSD)), etc.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical or other forms.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network devices (such as terminals) on. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each functional unit may exist independently, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of hardware plus software functional units.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Mathematical Physics (AREA)
  • Theoretical Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种群组管理方法、装置及系统，涉及通信技术领域，能够动态管理群组。该群组管理方法包括：从应用功能网元接收第一群组请求，第一群组请求包括指示信息、外部群组标识和第一群组信息，指示信息用于指示群组业务类型，外部群组标识为核心网内部网元不能够识别的群组标识。若群组业务类型为创建群组，则获取外部群组标识对应的内部群组标识，并对内部群组标识、外部群组标识，以及第一群组信息进行关联。内部群组标识为核心网内部能够识别的群组标识。该方法应用于群组管理的流程中。

Description

群组管理方法、装置及系统
本申请要求于2019年05月06日提交国家知识产权局、申请号为201910372920.9、发明名称为“群组管理方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及群组管理方法、装置及系统。
背景技术
目前，传统第三代合作伙伴计划(3rd generation partnership project，3GPP)提供的网络互连协议(internet protocol，IP)业务可以采用服务器(server)-客户端(client)的通信模式，即通过server的代理转发来完成client到client之间的相互通信。例如，在使用微信这一应用(application，APP)的过程中，终端A通过3GPP网络向终端B发送微信消息，该消息首先通过3GPP网络到达3GPP网络外的微信应用服务器，比如该消息通过基站到达UPF，再由UPF到达外部DN的微信应用服务器。进而，微信应用服务器对该微信消息进行处理，并通过3GPP网络将该消息发送给终端B，从而完成终端A和终端B之间的通信。
随着通信技术的发展，在第五代(5th generation，5G)网络中提出虚拟类本地区域网络服务(virtual local area network service，即virtual LAN service)，3GPP网络需要为一个群组中的多个终端提供多种类型的传输服务。其中，多类型传输服务包括基于IP、以太网(Ethernet)，或其他非IP技术的服务。即虚拟类LAN服务是由3GPP网络完成终端A和终端B之间的通信，通常不需要外部应用服务器的部署和参与。比如，在使用虚拟类LAN服务技术之后，终端A与终端B之间的路由可以为中终端A-终端A的基站-UPF-终端B的基站-终端B。可见，相比于传统技术，终端A、B的消息可以不经外部的应用服务器。
当前，并未就使用虚拟类LAN服务技术时，如何为UE建立和管理虚拟类LAN服务的会话提供相应解决方案。
发明内容
本申请实施例提供群组管理方法、装置及系统，能够在使用虚拟类LAN服务技术的过程中，动态的创建群组。
为达到上述目的，本申请实施例采用如下技术方案：
第一方面，本申请实施例提供一种群组管理方法，该方法由数据网元(比如可以为图1所示UDM)或数据网元中的组件(比如芯片系统)。该方法包括：
从应用功能网元接收第一群组请求，第一群组请求包括指示信息、外部群组标识和第一群组信息，指示信息用于指示群组业务类型。若群组业务类型为创建群组，则获取外部群组标识对应的内部群组标识，并对内部群组标识、外部群组标识，以及第一群组信息进行关联。外部群组标识为核心网内部网元不能够识别的群组标识；内部群组标识为核心网内部能够识别的群组标识。
本申请实施例提供的群组管理方法，可以从应用功能网元接收第一群组请求。第一群组创建请求携带用于指示群组业务类型的指示信息、第一群组信息，以及外部群组标识。如此，当应用功能网元请求创建群组时，数据网元能够基于第一群组请求，获取外部群组标识对应的内部群组标识，并将内部群组标识、外部群组标识和第一群组信息进行关联。一方面，用户在应用层创建群组的操作具有随机性，通过本申请实施例提供的群组管理方法，可以针对创建群组的动态需求，动态关联第一群组信息、外部群组标识和内部群组标识，这就意味着，能够使得AF具有动态创建群组的能力。另一方面，由于可以将用户在应用层创建的群组用3GPP网元能够识别的内部群组标识表示，所以，后续，3GPP网元能够基于内部群组标识区分不同群组，从而能够针对不同群组进行相应管理。
在一种可能的设计中，数据网元还可以执行如下步骤：向一个或多个群组成员发送内部群组标识和第一群组信息。
作为一种可能的实现方式，数据网元向接口网元发送新分配的内部群组标识。
作为一种可能的实现方式，数据网元在URSP更新流程中向一个或多个群组成员发送URSP，URSP包括内部群组标识和第一群组信息(比如DNN、S-NSSAI等)，以便于更新群组成员的URSP。
如此，当终端有数据到达时，可向网络设备(比如AMF)发送PDU会话建立请求，该PDU会话建立请求携带该终端所在群组的DNN，以便于网络设备(比如AMF)通过DNN识别出该终端在哪一群组中。
第二方面，本申请提供一种群组管理方法，该方法由数据网元或数据网元中的组件(比如芯片系统)。该方法包括：
从接口网元接收第二群组请求，第二群组请求包括外部群组标识和第一群组信息，外部群组标识为核心网内部不能够识别的群组标识。获取外部群组标识对应的内部群组标识，并将内部群组标识、外部群组标识，以及第一群组信息进行关联。内部群组标识为核心网内部能够识别的群组标识。
其中，与第一方面中各设计相比，第二群组请求不携带用于指示群组业务类型的指示信息，能够降低接口网元和数据网元之间交互的信令开销。并且，也能够动态触发UDM获取外部群组标识对应的内部群组标识。
在一种可能的设计中，获取外部群组标识对应的内部群组标识，包括：
判断是否已存储外部群组标识对应的内部群组标识的条目，若确定未存储外部群组标识对应的内部群组标识的条目，则获取外部群组标识对应的内部群组标识。
容易理解的是，通常，若UDM中未存储外部群组标识对应的内部群组标识，说明AF向UDM发送的是新建群组的请求，该新建群组并未记录在UDM中。此种情况下，UDM需为新建群组分配新的内部群组标识，以便于后续核心网基于该内部群组标识对该新建群组进行管理。
其中，本申请所提及的群组管理包括但不限于添加群组成员、删除群组成员、群组成员权限管理。
在一种可能的设计中，数据网元还可以执行如下步骤：
向接口网元发送外部群组标识和新分配的内部群组标识，以指示接口网元存储内部群组标识。
示例性的，NEF中已存储有群组1的内部群组标识和外部群组标识，以及群组2的内部群组标识和外部群组标识。则当UDM将新分配的群组3的内部群组标识和外部群组标识下发给NEF之后，NEF就存储有3个群组的内部群组标识和外部群组标识。如此，由于NEF中存储有一个或多个群组的内部群组标识和外部群组标识，后续，当NEF从AF接收外部群组标识，NEF可以判断是否已存储该外部群组标识对应的内部群组标识。若NEF未存储有该外部群组标识对应的内部群组标识，则请求UDM为新建群组分配内部群组标识。
在一种可能的设计中，数据网元还可以执行如下步骤：向一个或多个群组成员发送内部群组标识和第一群组信息。
第三方面，本申请实施例提供一种群组管理方法，该方法由接口网元(接口网元比如可以为图1所示NEF)或接口网元中的组件(比如芯片系统)。该方法包括：
从应用功能网元接收第三群组请求，第三群组请求包括外部群组标识和第一群组信息，外部群组标识为核心网内部不能够识别的群组标识。判断是否已存储外部群组标识对应的内部群组标识的条目，若未存储外部群组标识对应的内部群组标识的条目，则向数据网元发送第二群组请求，第二群组请求包括外部群组标识和一个或多个群组成员的第一标识。内部群组标识为核心网内部能够识别的群组标识。
第四方面，本申请实施例提供一种群组管理装置，该装置可以为数据网元(比如可以为图1所示UDM)或数据网元中的组件(比如芯片系统)。该装置包括：
通信接口，用于从应用功能网元接收第一群组请求，第一群组请求包括指示信息、外部群组标识和第一群组信息，指示信息用于指示群组业务类型，外部群组标识为核心网内部网元不能够识别的群组标识；处理器，用于若群组业务类型为创建群组，则获取外部群组标识对应的内部群组标识，内部群组标识为核心网内部能够识别的群组标识；对内部群组标识、外部群组标识，以及第一群组信息进行关联。
作为一种可能的实现方式，通信接口，还用于向接口网元发送新分配的内部群组标识。
在一种可能的设计中，通信接口，还用于向一个或多个群组成员发送内部群组标识和第一群组信息。
第五方面，本申请提供一种群组管理装置，该装置为数据网元(比如可以为图1所示UDM)或数据网元中的组件(比如芯片系统)。该装置包括：
通信接口，用于从接口网元接收第二群组请求，第二群组请求包括外部群组标识和第一群组信息，外部群组标识为核心网内部不能够识别的群组标识；处理器，用于获取外部群组标识对应的内部群组标识，内部群组标识为核心网内部能够识别的群组标识；将内部群组标识、外部群组标识，以及第一群组信息进行关联。
在一种可能的设计中，处理器，用于获取外部群组标识对应的内部群组标识，包括：用于判断是否已存储外部群组标识对应的内部群组标识的条目；若确定未存储外部群组标识对应的内部群组标识的条目，则获取外部群组标识对应的内部群组标识。
在一种可能的设计中，通信接口，还用于向接口网元发送内部群组标识，以指示接口网元存储内部群组标识。
在一种可能的设计中，通信接口，还用于向一个或多个群组成员发送内部群组标识和第一群组信息。
第六方面，本申请实施例提供一种群组管理装置，该装置可以为数据网元(比如可以 为图1所示NEF)或数据网元中的组件(比如芯片系统)。该装置包括：
通信接口，用于从应用功能网元接收第三群组请求，第三群组请求包括外部群组标识和第一群组信息，外部群组标识为核心网内部不能够识别的群组标识；处理器，用于判断是否已存储外部群组标识对应的内部群组标识的条目，内部群组标识为核心网内部能够识别的群组标识；通信接口，还用于若未存储外部群组标识对应的内部群组标识的条目，则向数据网元发送第二群组请求，第二群组请求包括外部群组标识和一个或多个群组成员的第一标识。
在上述各方面的一种可能的设计中，第一群组信息包括如下至少一项信息：群组的数据网络标识、群组的切片信息、群组对应的会话类型、群组包括的一个或多个群组成员的第一标识。
第七方面，本申请提供一种群组管理装置，用于实现上述任一方面中数据网元的功能，或者，用于实现上述任一方面中接口网元的功能。
第八方面，本申请提供一种群组管理装置，该装置具有实现上述任一方面中任一项的群组管理方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第九方面，提供一种群组管理装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该群组管理装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该群组管理装置执行如上述任一方面中任一项的群组管理方法。
第十方面，提供一种群组管理装置，包括：处理器；处理器用于与存储器耦合，并读取存储器中的指令之后，根据指令执行如上述任一方面中任一项的群组管理方法。
第十一方面，本申请实施例提供了一种群组管理装置，该装置可以为芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现上述任一方面所描述方法的功能。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第十二方面，提供一种群组管理装置，该装置可以为电路系统，电路系统包括处理电路，处理电路被配置为执行如上述任一方面中任一项的群组管理方法。
第十三方面，本申请实施例中还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述任一方面的方法。
第十四方面，本申请实施例中还提供一种计算机程序产品，包括指令，当其在计算机上运行时，使得计算机执行上述任一方面的方法。
第十五方面，本申请实施例提供了一种系统，系统包括执行第一方面以及第一方面的任一项的群组管理方法的数据网元和执行第三方面以及第三方面的任一项的群组管理方法的接口网元。或者，该系统包括执行第二方面以及第二方面的任一项的群组管理方法的数据网元和执行第三方面以及第三方面的任一项的群组管理方法的接口网元。可选的，该系统还包括应用功能网元(比如可以为图1所示AF)。应用功能网元用于从终端接收群组请求，比如从终端接收新建群组的请求。并向数据网元发送群组请求，以触发数据网元为新建群组分配内部群组标识。
附图说明
图1为本申请实施例提供的通信系统的架构示意图；
图2为本申请实施例提供的群组管理系统的架构示意图；
图3为本申请实施例提供的签约方法的流程示意图；
图4为本申请实施例提供的签约方法的流程示意图；
图5为本申请实施例提供的群组管理方法的流程示意图；
图6为本申请实施例提供的群组管理方法的流程示意图；
图7为本申请实施例提供的群组管理方法的流程示意图；
图8为本申请实施例提供的群组管理方法的流程示意图；
图9为本申请实施例提供的群组管理方法的流程示意图；
图10为本申请实施例提供的群组管理装置的结构示意图；
图11为本申请实施例提供的群组管理装置的结构示意图。
具体实施方式
本申请的说明书以及附图中的术语“第一”和“第二”等是用于区别不同的对象，或者用于区别对同一对象的不同处理，而不是用于描述对象的特定顺序。此外，本申请的描述中所提到的术语“包括”和“具有”以及它们的任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括其他没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。需要说明的是，本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
首先，对本申请实施例设计的技术术语进行介绍：
1、外部群组标识(external group ID)：当终端在应用层动态创建某一群组之后，应用服务器，为该应用层群组分配一个动态的群组标识，微信服务器分配的群组标识可称为外部群组标识。比如，终端1～终端6的用户创建微信群“学术讨论群”，微信应用服务器检测到用户创建微信群的操作之后，可以为该微信群分配一个应用层的群组标识，外部群组标识用于在应用层唯一标识该微信群。
2、内部群组标识(internal group ID)：3GPP网络中网络设备通常不能直接识别外部群组标识，也就不能理解该标识的含义，导致不能区别不同的群组，进而不能针对相应群组进行管理以及提供后续的LAN服务(LAN type service)。为了使得3GPP网络能够识别不同的群组，AF可以向3GPP网元发送群组请求，这样，3GPP网元可以根据群组请求生成群组的内部群组标识。内部群组标识为可以被3GPP核心网元识别的群组标识。如此，3GPP网元可以利用内部群组标识执行群组管理等。群组管理例如可以为群组添加群成员，删除群成员等。
3、单个群组管理辅助信息(Single network slice selection assistance information，S-NSSAI)，用于唯一表示一个网络切片，它的信元(information-element)如下表1所示：
表1
Figure PCTCN2020088519-appb-000001
Figure PCTCN2020088519-appb-000002
其中，某一S-NSSAI的信元中，S-NSSAI(information-element identifier，IEI)表示该信元的标识。
Length of S-NSSAI contents表示该信元的长度(可以以字节为单位)。
SST用于指示切片能够提供哪种网络服务。网络服务包括但不限于eMBB服务、uRLLC服务、mMTC服务。
可选的，SST长度为1个字节，当然，随着协议演进，SST长度可能有所变化。SST包括标准化(即标准SST值(value))和运营商自定义(即非标准SST值)的类型。参见下表2，目前，协议中仅定义了SST值为1-3的内容：
表2
Figure PCTCN2020088519-appb-000003
在本申请实施例中，两个切片的SST相同，指的是两个切片的SST所指示的服务类型相同，即SST数值相同。比如，切片1的SST为eMBB(SST value为1)，切片2的SST也为eMBB(SST value为1)，则切片1和切片2的SST相同。
本申请实施例提供的群组管理方法应用于使用虚拟类LAN服务技术的通信系统中。参见图1，为本申请实施例所适用的一种通信系统的示例性架构。该通信系统包括：运营管理(operation administration management，OAM)网元、群组管理功能(network slice selection function，NSSF)、网络开放功能(network exposure function，NEF)、网络存储功能(network repository function，NRF)、策略控制功能(policy control function，PCF)、应用功能(application function，AF)、统一数据管理(unified data management，UDM)、鉴权服务器功能(authentication server function，AUSF)、接入和移动性管理功能(core access and mobility management function，AMF)、会话管理功能(session management function，SMF)、接入网(access network，AN)网元，其中，AN包括有线接入网和无线接入网(radio access network，RAN)、用户面功能(user plane function，UPF)、数据网(data network，DN)网元等网元或设备以及终端。
其中，终端通过无线或有线方式接入AN，无线方式例如可以为通过无线保真(wireless-fidelity，WiFi)接入，还可以通过蜂窝网(例如E-UTRA、NR等)接入AN，终端通过N1与AMF通信；AN通过N3与UPF通信，AN通过N2与AMF通信；UPF通过N4与SMF通信，UPF通过N6与DN网元通信；SMF通过N11(图1中并未示出)与AMF通信，SMF通过N10(图1中并未示出)与UDM通信，SMF通过N7(图1中并未 示出)与PCF通信；AMF通过N12(图1中并未示出)与AUSF通信，AUSF通过N13(图1中并未示出)与UDM通信。AF通过N5(图1中并未示出)与PCF通信。
可以理解的是，根据5G系统部署的需求，上述网元之间可采用一定方式通信(例如，终端通过N1与AMF通信)，上述仅列举了部分网元之间通信的方式，为简化描述，本申请实施例不再对其他网元之间的通信方式进行赘述。
可选的，本申请实施例中所涉及到的终端可以包括各种具有通信功能的手持设备、可穿戴设备、计算设备或连接到调制解调器的其它处理设备；还可以包括个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、膝上型电脑(laptop computer)、机器类型通信(machine type communication，MTC)终端、用户设备(user equipment，UE)等。当然，提及终端时，也可以指诸如UE中的芯片系统。本申请实施例对终端的实现形式不做限定。
可选的，图1中的各个网元的名字以及各个网元之间的接口名字只是一个示例，具体实现中各个网元或者各个网元之间的接口的名字可能为其他名字，或者网元也可以称之为实体，本申请实施例对此不作具体限定。图1中的全部或者部分网元可以是物理上的实体网元，也可以是虚拟化的网元，在此不做限定。
在本申请的实施例中，某一网元(例如：A网元)获取来自另一网元(例如：B网元)的信息，可以指A网元直接从B网元接收信息，也可以指A网元经其他网元(例如：C网元)从B网元接收信息。当A网元经C网元从B网元接收信息时，C网元可以对信息进行透传，也可以将信息进行处理，例如：将信息携带在不同的消息中进行传输或者对信息进行筛选，只发送筛选后的信息给A网元。类似的，在本申请的各实施例中，A网元向B网元发送信息，可以指A网元直接向B网元发送信息，也可以指A网元经其他网元(例如：C网元)向B网元发送信息。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例提供一种群组管理系统。参见图2，该系统200包括：数据网元203和接口网元204。
接口网元204：用于提供外部的应用功能网元205与数据网元203交互的接口(interface)。具体的，可以用于从应用功能网元205接收群组请求，并向数据网元203发送该群组请求。
数据网元203：用于根据来自应用功能网元205的群组请求，并根据该群组请求为新建的群组分配一个内部群组标识，以便于后续3GPP网元能够基于该可识别的内部群组标识区分不同群组，执行群组相关管理。还用于向策略网元202发送通知消息，以便于通知策略网元202更新URSP。
其中，URSP用于区分不同群组。在不同群组中的终端201会被分配不同的URSP规则。终端201根据URSP规则可以确定自己在哪一群组中。
作为一种可能的实现方式，群组管理系统还包括：终端201、应用功能网元205、管理网元206、策略网元202。
应用功能网元205：用于当终端201在应用层动态建立群组的过程中，检测到终端201创建群组的操作，比如从终端201接收群组请求。还用于基于群组请求为每个新建的群组分配一个外部群组标识，即External Group ID。还用于向接口网元204发送群组请求，以请求创建该新的群组。还用于向管理网元206发送签约请求，以请求注册、签约虚拟类LAN服务(虚拟类LAN服务在本文中也可称为LAN服务)。
管理网元206：用于接收应用功能网元205的签约请求，并根据签约请求为应用功能网元205分配用于建立LAN群组的DNN/S-NSSAI等信息。
策略网元202：用于根据来自数据网元203的通知消息更新URSP，并将更新的URSP下发到LAN群组对应的终端201。
终端201：用于接收来自策略网元202下发的URSP。当终端201上某个APP触发LAN业务时，比如微信群内某一用户通的终端上的微信应用向微信群内的另一终端发送微信消息时，终端能根据URSP查询到该LAN业务(即微信消息业务)对应的DNN/S-NSSAI等信息，并在建立PDU session时上报DNN/S-NSSAI等信息，从而3GPP网络能够根据DNN/S-NSSAI等信息识别出该终端属于哪个LAN群组。
其中，图2中的应用功能网元可以为图1中的AF，接口网元可以为图1中的NEF，数据网元可以为图1中的UDM，管理网元可以为图1中的OAM，策略网元可以为图1中的PCF。并且，图2所示网元之间的连接关系可以参见图1中相应网元之间的连接关系。这里不再赘述。
如下以本申请实施例应用于图1所示系统，即应用功能网元为图1所示AF、接口网元为图1所示NEF、数据网元为图1所示UDM、策略网元为图1所示PCF、管理网元为图1所示OAM为例来说明本申请实施例的技术方案。
首先，介绍AF向OAM申请LAN服务的流程，该流程是本申请实施例的群组管理方法的基础。也就是说，在得到OAM的授权之后，AF才可以获得使用LAN服务的权限，比如，AF可以获得动态创建群组的权限。具体的，参见图3，AF向OAM申请LAN服务的流程包括如下步骤：
S301、AF向OAM发送签约请求(比如可以是5G-LAN service request)。
相应的，OAM从AF网元接收签约请求。
其中，签约请求用于请求签约LAN服务。
签约请求包括AF支持的应用标识(APP ID)。比如，若AF为微信应用服务器，签约请求包括微信应用服务器支持的微信应用的标识。
S302、OAM基于AF支持的应用，确定AF对应的第一配置信息(LAN configuration data)。
作为一种可能的实现方式，第一配置信息用于指示群组的签约配置。
其中，OAM可以为AF配置一个或多个群组的第一配置信息。第一配置信息包括一个或多个群组分别对应的数据网络标识。网络数据标识比如可以为DNN，或者其他用于标识数据网络的信息。不同群组对应不同的数据网络标识。如此，数据网络标识可以唯一标识一个群组。后续，终端有数据到达时，可向网络设备(比如AMF)发送PDU会话建立请求，该PDU会话建立请求携带该终端所在群组的DNN，以便于网络设备(比如AMF)识别出该终端在哪一群组中。
可选的，第一配置信息还包括如下至少一项信息：一个或多个群组分别对应的切片信息、一个或多个群组分别对应的会话类型。
群组的切片信息比如可以为单个群组管理辅助信息(single network slice selection assistance information，S-NSSAI)。在本申请实施例中，群组通常基于业务类型创建，即同一群组中终端的业务类型通常相同。基于此，同一群组中每一终端的S-NSSAI的业务类型(比如SST)通常均相同。比如，在某一游戏APP中，用户通过终端上的APP创建群组1，该群组1中终端业务要求是高可靠、低时延，该群组1中每一终端对应的S-NSSAI的SST可以均为uRLLC。在该游戏APP中，用户创建群组2，该群组2中终端执行业务需要较大带宽，群组2中每一终端对应的S-NSSAI的SST可以均为eMBB。
每个PDU会话(session)支持一个会话类型，会话类型包括但不限于IPv4、IPv6、IPv4v6、Ethenet、Unstructured中的一种。通常，群组是基于APP类型、业务类型创建的，对于通过相同类型APP(比如微信)所建群组中的终端，当终端执行相同类型业务时，这些终端的会话类型可以相同。比如，通过微信应用创建的微信群，当微信群内终端进行相同类型业务时，比如均收发微信文字消息时，这些终端的会话类型可以相同。由上文描述，同一群组中终端的业务类型通常相同，所以，同一群组中终端的会话类型通常也相同。
示例性的，针对AF下的微信群1和微信群2，OAM分配的第一配置信息为：{微信群1：使用DNN1标识该微信群1、微信群1内终端切片的业务类型为eMBB、微信群1内的终端的会话类型为以太网类型；微信群2：使用DNN2标识该微信群2、微信群2内终端切片的业务类型为uRLLC、微信群2内的终端的会话类型为以太网类型}。
OAM为AF具体配置多少个群组的第一配置信息，与AF的签约条件有关。签约条件比如可以但不限于是签约资费，AF的签约资费较高时，OAM可以为AF配置更多群组的第一配置信息。比如，OAM可以在AF请求签约LAN服务的情况下，为AF配置1000个群组的第一配置信息。如此，AF仅请求一次LAN服务，就可以获取1000个群组分别对应的第一配置信息，进而AF具有创建1000个群组的能力。当AF的签约资费较低，OAM为AF配置较少(比如10个)群组的第一配置信息。如此，AF一次请求LAN服务，可以具有创建10个群组的能力。若用户需在应用层创建第11个群组，AF可以向OAM发送签约请求，以请求新的第一配置信息。这种情况下，OAM可以仅配置第11个群组的第一配置信息，也可以配置多个群组(比如配置第11～第100个群组)的第一配置信息。
S303、OAM向AF发送签约响应。
相应的，AF从OAM接收签约响应。
签约响应包括一个或多个群组分别对应的第一配置信息。
图3所示签约方法中，外部AF能够根据自己的需求动态向运营商的OAM签约LAN服务，进而从OAM获得DNN、S-NSSAI等第一配置信息，以便于后续AF可以基于获得的第一配置信息动态创建LAN群组。也就是说，AF能够动态为新建群组分配外部群组标识，且核心网侧能够动态为新建群组分配内部群组标识。
在一些实施例中，参见图4，AF向OAM申请LAN服务，具体还可以实现为如下 步骤：
S401、AF向OAM发送签约请求。
相应的，OAM从AF网元接收签约请求。
签约请求用于请求签约注册LAN服务，即请求核心网分配第二配置信息。第二配置信息的详细描述可参见下文。
签约请求包括AF支持的应用标识、AF分配的一个或多个群组的外部群组标识。
以AF为微信应用服务器为例，微信应用服务器预期签约100个群组的LAN服务，换句话说，AF预期具有创建100个群组的能力，则微信应用服务器可以向OAM发送签约请求，该签约请求携带微信应用的标识和微信应用服务器动态预分配的100个外部群组标识(比如微信应用服务器为群组1～100分别预先分配的外部群组标识)。
作为一种可能的实现方式，签约请求比如可以是5G-LAN service request。
S402、OAM根据一个或多个群组的外部群组标识，获取一个或多个群组的第二配置信息。
第二配置信息用于指示群组的签约配置。
对于某一群组来说，该群组的第二配置信息包括：该群组的内部群组标识、单个群组的数据网络标识。
可选的，单个群组的第二配置信息还包括如下至少一种信息：单个群组的切片信息、单个群组对应的会话类型。
其中，OAM可以自己根据预设策略为AF分配一个或多个群组分别对应的第二配置信息，OAM也可以将上述一个或多个外部群组标识和APP ID发送给其他网元，从而借助其他网元的算力计算一个或多个群组分别对应的第二配置信息，即由其他网元为一个或多个群组分配相应的第二配置信息。本申请实施例对此不进行限制。
S403、OAM对每一群组的外部群组标识和第二配置信息进行关联，得到每一群组的外部群组标识和第二配置信息的对应关系。
作为一种可能的实现方式，OAM还可以对外部群组标识、第二配置信息、群组对应的APP ID进行关联。
也就是说，针对每一群组，OAM将群组的外部群组标识，以及该群组的第二配置信息(可选的，还可以对群组的APP ID)进行关联。
S404、OAM向UDM发送外部群组标识和对应的第二配置信息(可选的，还发送群组对应的APP ID)。
S405、UDM存储外部群组标识和第二配置信息的对应关系。
作为一种可能的实现方式，UDM将上述对应关系存储至统一数据存储(Unified Data Repository，UDR)。
可选的，UDM存储每一群组的外部群组标识、第二配置信息、APP ID之间的对应关系。
如此，后续当AF向网络侧触发5G LAN业务(比如创建某一5G LAN群组)时，AF向UDM提供外部群组标识，UDM可以根据UDR中储存的对应关系查找该外部群组标识对应的内部群组标识，以便于网络侧利用该内部群组标识执行群组管理等。
S406、OAM向AF发送签约响应。
签约响应包括上述第二配置信息，用以指示一个或多个群组的签约配置。
本申请实施例中，对S406的执行时机不进行限制。除图4所示执行时机之外，还可以在S402获取第二配置信息之后，直接执行S406。或者，可以在S403之后，执行S406。或者在其他时机执行S406。
图4所示签约方法，OAM能根据AF提供的外部群组标识为AF动态分配第二配置信息，并对外部群组标识和第二配置信息进行关联，将该关联存储至UDM。这样，后续，当AF向网络侧触发LAN业务时，AF向UDM发送外部群组标识，UDM根据储存的对应关系查找内部群组标识，若能够查找到相应内部群组标识，则直接利用该内部群组标识执行群组管理等，若未能查找到群组对应的内部群组标识，则生成相应内部群组标识，以供核心网后续进行LAN业务使用。相比于现有技术中不支持AF动态组建群组，即外部群组标识和网络侧标识均提前配置在核心网和AF，本申请实施例提供的方法，使得AF能动态分配外部群组标识，核心网侧也能动态分配网络侧层群组标识。即支持AF动态创建群组。
本申请实施例还提供一种群组管理方法，在图3或图4所示签约流程的基础上，参见图5，动态管理群组的方法包括如下步骤：
S501、AF向NEF发送第一群组请求。
相应的，NEF从AF接收第一群组请求。
其中，第一群组请求包括指示信息(indication)和外部群组标识(External Group ID)。外部群组标识为核心网内部网元不能够识别的群组标识。指示信息用于指示群组业务类型。群组业务类型包括但不限于创建群组、更新群组参数、删除群组成员、添加群组成员、群组成员的权限管理。
可选的，第一群组请求还包括第一群组信息，第一群组信息还包括如下至少一项信息：群组的数据网络标识、群组的切片信息、群组对应的会话类型、群组包括的一个或多个群组成员的第一标识、群组对应的应用标识。
第一标识包括但不限于通用公共用户标识(general public subscriber identity，GPSI)。每一终端均对应一个GPSI。
S502、NEF向UDM发送鉴权请求。
相应的，UDM从NEF接收鉴权请求。
鉴权请求用于查询AF是否已签约LAN服务，也就是对AF进行鉴权。
其中，S502为可选步骤。
S503、UDM向NEF发送鉴权响应。
相应的，NEF从UDM接收鉴权响应。
鉴权响应用于指示AF是否已签约LAN服务。作为一种可能的实现方式，UDM判断AF是否签约LAN服务，并向NEF反馈鉴权响应，该鉴权响应指示AF已签约LAN服务，或者，AF未签约LAN服务。作为另一种可能的实现方式，UDM并不直接指示AF是否已签约LAN服务，而是向NEF反馈鉴权响应，该鉴权响应包括AF的签约信息。如此，NEF根据AF的签约信息可以判断AF是否已签约LAN服务。
其中，S503为可选步骤。
S504、NEF向UDM发送第一群组请求。
相应的，UDM从NEF接收第一群组请求。
作为一种可能的实现方式，NEF调用UDM的Nudm_Parameter Provision_xxx request服务向UDM发送第二群组请求。示例性的，当群组业务类型为创建群组，NEF调用UDM的Nudm_Parameter Provision_update request服务向UDM发送第二群组请求。示例性的，当群组业务类型为删除群组成员，NEF调用UDM的Nudm_Parameter Provision_delete request服务向UDM发送第二群组请求。
S505、若群组业务类型为创建群组，则UDM获取外部群组标识对应的内部群组标识。
容易理解的是，当群组业务类型为创建群组，说明AF已检测到用户在应用层新建群组的操作，此时，UDM需为AF动态分配新建群组的内部群组标识，以便后续核心网网元使用内部群组标识执行群组管理。
作为一种可能的实现方式，UDM中预配置有生成策略。UDM基于生成策略生成内部群组标识。可选的，该生成策略可以为预设算法，如此，UDM基于预设算法计算内部群组标识。作为另一种可能的实现方式，UDM还可以在接收到第一群组请求之后，从其他网元获取内部群组标识。即由其他网元计算内部群组标识，并向UDM反馈计算结果。也就是说，UDM可以自己计算内部群组标识，也可以从其他网元直接获取计算好的内部群组标识。本申请实施例对UDM获取内部群组标识的方式不做限定。
在一个示例中，UDM自身计算新建微信群组对应的内部群组标识。
S506、UDM根据一个或多个群组成员的第一标识确定一个或多个群组成员的第二标识。
S507、UDM向NEF发送一个或多个群组成员的第二标识。
其中，S507为可选步骤。
S508、UDM将内部群组标识、外部群组标识，以及第一群组信息进行关联。
作为一种示例，本申请实施例可以采用如下格式关联内部群组标识、外部群组标识和第一群组信息：{群组1的内部群组标识1、群组1的外部群组标识A、群组1的DNN1、群组1的S-NSSAI1、群组1对应的会话类型1、群组1包括终端1(第一标识为xx)和终端2(第一标识为yy)}。又比如，{群组1的内部群组标识1、群组1的外部群组标识A、群组1的DNN1、群组1的S-NSSAI1、群组1包括终端1(第一标识为xx)和终端2(第一标识为yy)}。当然，还可以采用其他格式表示上述各信息之间的关联，比如采用表格格式表示。本申请实施例对此不进行限制。
S509、UDM向AF发送群组响应。
相应的，AF从UDM接收群组响应。
群组响应用于指示群组创建成功，这就意味着，UDM已关联内部群组标识、外部群组标识和第一群组信息。
作为一种可能的实现方式，UDM先向NEF发送群组响应，该群组响应携带UDM新分配的内部群组标识，再由NEF向AF发送群组响应。如此，NEF能够获取外部群组标识对应的内部群组标识。
S510、UDM向PCF发送通知消息。
相应的，PCF从UDM接收通知消息。
通知消息携带如下至少一项信息：内部群组标识，群组的应用标识(APP ID)、群组成员的第二标识、数据网络标识、切片信息、会话类型。
S511、PCF根据通知消息生成URSP。
其中，URSP包括如下至少一项信息：内部群组标识，群组的应用标识、数据网络标识、切片信息、会话类型。
S512、PCF分别向一个或多个群组成员发送URSP。
本申请实施例提供的群组管理方法，可以从应用功能网元接收第一群组请求。第一群组创建请求携带用于指示群组业务类型的指示信息、第一群组信息，以及外部群组标识。如此，当应用功能网元请求创建群组时，数据网元能够基于第一群组请求，获取外部群组标识对应的内部群组标识，并将内部群组标识、外部群组标识和第一群组信息进行关联。一方面，用户在应用层创建群组的操作具有随机性，通过本申请实施例提供的群组管理方法，可以针对创建群组的动态需求，动态关联第一群组信息、外部群组标识和内部群组标识，这就意味着，能够使得AF具有动态创建群组的能力。另一方面，由于可以将用户在应用层创建的群组用3GPP网元能够识别的内部群组标识表示，所以，后续，3GPP网元能够基于内部群组标识区分不同群组，从而能够针对不同群组进行相应管理。
进一步的，图5所示群组管理方法中，当UDM接收到来自AF的第一群组请求之后，若该第一群组请求的群组业务类型为创建群组，说明AF需要新建群组，则UDM直接获取该新建群组对应的内部群组标识，以确保后续核心网网元能够基于内部群组标识识别不同群组。该实现方式中，UDM无需执行判断等逻辑，UDM的逻辑实现复杂度有所降低。
本申请实施例还提供一种群组管理方法，参见图6，动态管理群组的方法包括如下步骤：
S601、AF向NEF发送第三群组请求。
相应的，NEF从AF接收第三群组请求。
第三群组请求携带外部群组标识和第一群组信息。第一群组信息包括如下至少一项信息：群组的数据网络标识、群组的切片信息、群组对应的会话类型、群组包括的一个或多个群组成员的第一标识、群组的APP ID。
作为一种可能的实现方式，AF调用NEF的Nnef_ParameterProvision_Update request服务向NEF发送第三群组请求。
S502、NEF向UDM发送鉴权请求。
相应的，UDM从NEF接收鉴权请求。
S503、UDM向NEF发送鉴权响应。
相应的，NEF从UDM接收鉴权响应。
其中，S503为可选步骤。
S604、NEF向UDM发送第二群组请求。
相应的，UDM从NEF接收第二群组请求。
第二群组请求包括外部群组标识和一个或多个群组成员的第一标识。
可选的，第二群组请求还包括如下至少一项信息：DNN、S-NSSAI、会话类型、应用标识。
S605、UDM判断是否已存储外部群组标识对应的内部群组标识的条目。
S606、若确定未存储外部群组标识对应的内部群组标识的条目，则UDM获取外部群组标识对应的内部群组标识。
作为一种可能的实现方式，UDR中存储有一个或多个外部群组标识和一个或多个内部群组标识，若UDM在UDR中查询不到外部群组标识对应的内部群组标识，则UDM获取外部群组标识对应的内部群组标识。
其中，UDM可以使用自身的算力，或借助其他网元的算力来计算外部群组标识对应的内部群组标识。
可选的，UDM向AF发送外部群组标识对应的内部群组标识。
S506、UDM根据一个或多个群组成员的第一标识确定一个或多个群组成员的第二标识。
第一标识包括GPSI，第二标识包括SUPI。如此，3GPP网元能够基于SUPI识别群组包括的终端。
S507、UDM向NEF发送一个或多个群组成员的第二标识。
相应的，NEF从UDM接收一个或多个群组成员的第二标识。
可选的，若S604中，NEF向UDM发送的第二群组请求不包含群组的数据网络标识、群组的网络切片信息、群组对应的会话类型、应用标识中的一项或多项，则NEF还可以执行如下步骤S608：
S608、NEF向UDM发送第四群组请求。
相应的，UDM从NEF接收第四群组请求。
其中，第四群组请求包括群组的内部群组标识、一个或多个群组成员的第二标识、数据网络标识、群组的网络切片信息、群组对应的会话类型、APP ID中的一项或多项。
作为一种可能的实现方式，NEF调用UDM的Nudm_ParameterProvision_Update request服务向UDM发送第三群组请求。
作为一种可能的实现方式，若S604中，NEF已向UDM发送群组的数据网络标识，则此步骤S608中，NEF不再向UDM发送数据网络标识，而是向UDM发送内部群组标识、至少一个第二标识、群组的网络切片信息，群组对应的会话类型、APP ID中的一项或多项。如此，NEF能够将UDM所需的一个或多个信息通过一个或多个消息(比如仅通过第二群组请求，或者通过第二群组请求和第四群组请求等多个消息)发送给UDM。
S508、UDM将内部群组标识、外部群组标识和第一群组信息进行关联，得到内部群组标识、外部群组标识和第一群组信息的对应关系。
S609、UDM存储外部群组标识、内部群组标识和第一群组信息。
比如，将新建群组的外部群组标识、内部群组标识和第一群组信息的对应关系存储至UDR。
S509、UDM向AF发送群组响应。
作为一种可能的实现方式，UDM先向NEF发送群组响应，该群组响应携带UDM分配的内部群组标识，NEF再向AF发送群组响应。
S510、UDM向PCF发送通知消息。
相应的，PCF从UDM接收通知消息。
S511、PCF根据通知消息生成URSP。
S512、PCF分别向一个或多个群组成员发送URSP。
相应的，一个或多个群组成员从PCF接收URSP。
如此，群组中的终端能够更新URSP，以便于后续进行LAN业务时能够根据不同群组确定不同的路由。
需要说明的是，本申请实施例并不限制上述各个步骤之间的执行顺序，各个附图中所列举的执行顺序仅为可能的一种实现方式。比如，UDM还可以先执行S506、507，再执行S605。再比如，可以先执行S510，再执行S509。
图6所示群组管理方法中，当接收到来自AF的某一群组的外部群组标识之后，UDM能判断是否已存储该外部群组标识对应的内部群组标识，进而确定用哪一标识标识该群组，以确保后续核心网网元能够识别不同群组。
本申请实施例还提供一种群组管理方法，结合图3或图4所示签约流程，参见图7，动态创建某一群组的方法包括如下步骤：
S701、NEF向UDM发送订阅消息。
相应的，UDM从NEF接收订阅消息，订阅消息用于请求订阅外部群组标识、内部群组标识和第一群组信息的对应关系。该订阅指的是UDM可主动向NEF发送该对应关系。示例性的，当UDM更新该对应关系后，比如当存在新的外部群组标识、内部群组标识和第一群组信息，UDM可主动向NEF发送更新的对应关系。以便于NEF存储该对应关系。
其中，该S701为可选步骤。也就是说，NEF也可以不向UDM订阅新的内部群组标识、外部群组标识和第一群组信息的对应关系。在NEF不向UDM订阅上述对应关系的情况下，由于NEF可触发UDM生成新的内部群组标识，UDM在生成新的内部群组标识之后，也可以主动向触发生成新内部群组标识的NEF发送新的内部群组标识、外部群组标识和第一群组信息。
S601、AF向NEF发送第三群组请求。
相应的，NEF从AF接收第三群组请求。
S502、NEF向UDM发送鉴权请求。
相应的，UDM从NEF接收鉴权请求。
其中，S502为可选步骤。
S503、UDM向NEF发送鉴权响应。
相应的，NEF从UDM接收鉴权响应。
其中，S503为可选步骤。
S704、NEF判断是否存储有外部群组标识对应的内部群组标识。
S705、若NEF确定不存在外部群组标识对应的内部群组标识，则向UDM发送第二群组请求。
相应的，UDM从NEF接收第二群组请求。第二群组请求用于请求UDM分配内部群组标识。关于第二群组请求的详细介绍，可参见上文，这里不再赘述。
S706、UDM获取外部群组标识对应的内部群组标识。
S506、UDM根据一个或多个群组成员的第一标识确定一个或多个群组成员的第二标识。
S507、UDM向NEF发送一个或多个群组成员的第二标识。
S608、NEF向UDM发送第四群组请求。
相应的，UDM从NEF接收第四群组请求。
S508、UDM将内部群组标识、外部群组标识和第一群组信息进行关联，得到内部群组标识、外部群组标识和第一群组信息的对应关系。
S509、UDM向AF发送群组响应。
作为一种可能的实现方式，UDM先向NEF发送群组响应，该群组响应携带UDM新分配的内部群组标识，NEF再向AF发送群组响应。
S510、UDM向PCF发送通知消息。
相应的，PCF从UDM接收通知消息。
S511、PCF根据通知消息生成URSP。
S512、PCF分别向一个或多个群组成员发送URSP。
图7所示群组管理方法中，NEF可以向UDM订阅对应关系，如此，当UDM中的对应关系更新后，UDM向NEF通知外部群组标识、外部群组标识所转换成的新内部群组标识和外部群组标识对应的第一群组信息。后续，当NEF接收到来自AF的某一群组的外部群组标识之后，NEF可以判断是否已存储该外部群组标识对应的内部群组标识。
本申请实施例还提供一种群组管理方法，结合图3或图4所示签约流程，参见图8，动态创建某一群组的方法包括如下步骤：
S601、AF向NEF发送第三群组请求。
相应的，NEF从AF接收第三群组请求。
S502、NEF向UDM发送鉴权请求。
相应的，UDM从NEF接收鉴权请求。
其中，S502为可选步骤。
S503、UDM向NEF发送鉴权响应。
相应的，NEF从UDM接收鉴权响应。
其中，S503为可选步骤。
S804、NEF获取一个或多个群组的内部群组标识、外部群组标识和第一群组信息。
作为一种可能的实现方式，S804可以具体实现为：
S8041、NEF向UDM发送获取请求。
相应的，UDM从NEF接收获取请求。
其中，获取请求用于NEF在接收到来自AF的第三群组请求后，获取一个或多个群组的内部群组标识、外部群组标识和第一群组信息。
S8042、UDM向NEF发送一个或多个群组的内部群组标识、外部群组标识和第一群组信息。
作为一种可能的实现方式，UDM将存储的全部群组的内部群组标识、外部群组标识和第一群组信息发送给NEF。比如，UDM存储有群组1～10各自对应的内部群组标识、外部群组标识和第一群组信息，则UDM将这10个群组的内部群组标识、外部群组标识和 第一群组信息下发给NEF。
S704、NEF判断是否存在外部群组标识对应的内部群组标识。
作为一种可能的实现方式，NEF根据从UDM获取的一个或多个群组的内部群组标识、外部群组标识和第一群组信息，查询是否存在外部群组标识对应的内部群组标识。
S705、若NEF确定不存在外部群组标识对应的内部群组标识，则向UDM发送第二群组请求。
相应的，UDM从NEF接收第二群组请求。第二群组请求用于请求UDM分配内部群组标识。
S706、UDM获取外部群组标识对应的内部群组标识。
S506、UDM根据一个或多个群组成员的第一标识确定一个或多个群组成员的第二标识。
S507、UDM向NEF发送一个或多个群组成员的第二标识。
S608、NEF向UDM发送第四群组请求。
其中，S608为可选步骤。
S508、UDM将内部群组标识、外部群组标识和第一群组信息进行关联。
S609、UDM存储外部群组标识、内部群组标识和第一群组信息。
也就是说，UDM将新生成的内部群组标识、该内部群组标识对应的外部群组标识、该内部群组标识对应的第一群组信息进行存储。
S509、UDM向AF发送群组响应。
S510、UDM向PCF发送通知消息。
相应的，PCF从UDM接收通知消息。
S511、PCF根据通知消息生成URSP。
S512、PCF分别向一个或多个群组成员发送URSP。
图8所示群组管理方法中，NEF接收到来自AF的某一群组的外部群组标识之后，可以实时向UDM申请一个或多个群组的内部群组标识、外部群组标识和第一群组信息的对应关系，并基于该对应关系判断是否已存储该外部群组标识对应的内部群组标识，能够确保后续核心网网元能够基于内部群组标识识别不同群组。
本申请实施例还提供一种群组管理方法，参见图9，动态创建某一群组的方法包括如下步骤：
S1001、AF向NEF发送第三群组请求。
相应的，NEF从AF接收第三群组请求。
作为一种可能的实现方式，该第三群组请求可以为5G LAN Internal Group ID Allocation Request。
第三群组请求携带如下至少一项：群组的数据网络标识、群组的网络切片信息、群组对应的会话类型、一个或多个群组成员的第一标识、APP ID。
作为一种可能的实现方式，第三群组请求还携带指示信息。用于指示群组业务类型。
S502、NEF向UDM发送鉴权请求。
相应的，UDM从NEF接收鉴权请求。
其中，S502为可选步骤。
S503、UDM向NEF发送鉴权响应。
相应的，NEF从UDM接收鉴权响应。
其中，S503为可选步骤。
S1004、NEF向UDM发送第二群组请求。
相应的，UDM从NEF接收第二群组请求。
第二群组请求用于请求创建群组，第二群组请求携带如下至少一项：群组的数据网络标识、群组的网络切片信息、群组对应的会话类型、至少一个第一标识、APP ID。
第二创建请求的相关描述可参见上文，这里不再赘述。可选的，第二群组请求还携带指示信息，用于指示群组业务类型。
S1005、UDM根据如下至少一项信息，获取内部群组标识：数据网络标识、切片信息、会话类型、至少一个终端的标识、APP ID。
其中，UDM可以自身计算内部群组标识，也可以从其他网元获取内部群组标识。比如，UDM根据群组的数据网络标识和切片信息为该群组分配内部群组标识。
S506、UDM根据一个或多个群组成员的第一标识确定一个或多个群组成员的一个第二标识。
S507、UDM向NEF发送一个或多个群组成员的第二标识。
S508、UDM将内部群组标识、外部群组标识和第一群组信息进行关联。
可选的，UDM存储新生成的内部群组标识、该内部群组标识对应的外部群组标识和该内部群组标识对应的第一群组信息。
S1009、UDM向AF发送内部群组标识、外部群组标识和第一群组信息。
UDM将新生成的内部群组标识、该内部群组标识对应的外部群组标识和该内部群组标识对应的第一群组信息下发给NEF。
相应的，AF从UDM接收内部群组标识、外部群组标识和第一群组信息。
S509、UDM向AF发送群组响应。
作为一种可能的实现方式，群组响应可以为5G LAN Internal Group ID Allocation response。群组响应用于指示已关联内部群组标识、外部群组标识和第一群组信息。
作为一种可能的实现方式，S1009和S509可以通过一个步骤实现。即UDM可以通过群组响应向AF发送内部群组标识、外部群组标识和第一群组信息。
S510、UDM向PCF发送通知消息。
相应的，PCF从UDM接收通知消息。
S511、PCF根据通知消息更新URSP。
S512、PCF分别向至少一个终端发送URSP。
图9所示群组管理方法中，当UDM接收到来自NEF的某一群组的第二群组请求之后，UDM可以不执行判断逻辑，而是直接生成该外部群组标识对应的内部群组标识，UDM的逻辑实现复杂度有所降低。
可以理解的是，上述各个方法实施例中由各个设备实现的方法和功能也可以通过可用于设备的芯片实现。
上述主要从不同网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本申请中所公开的实施例描述的各示例的单元及算法步骤，本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本申请实施例的技术方案的范围。
本申请实施例可以根据上述方法示例对数据网元、接口网元、应用功能网元、终端、策略网元、管理网元等进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
[根据细则91更正 22.05.2020]　
图10示出了本申请实施例中提供的群组管理装置的一种示意性框图。该群组管理装置1200可以以软件的形式存在，也可以为硬件，比如可以为可用于硬件设备中的芯片。群组管理装置1200包括：处理单元1202和通信单元1203。
[根据细则91更正 22.05.2020]　
若群组管理装置1200为数据网元，处理单元1202可以用于支持群组管理装置1200执行图5所示S505、S506，和/或用于本文所描述的方案的其它过程。通信单元1203用于支持群组管理装置1200和其他网元(例如接口网元)之间的通信，比如，执行图4所示的S404、S406，和/或，本文所描述方案的其他步骤。
[根据细则91更正 22.05.2020]　
若群组管理装置1200为接口网元，处理单元1202可以用于支持群组管理装置1200执行图7所示S704，和/或用于本文所描述的方案的其它过程。通信单元1203用于支持群组管理装置1200和其他网元(例如数据网元)之间的通信，比如，执行图7所示的S701、S502、S503，和/或，本文所描述方案的其他步骤。
[根据细则91更正 22.05.2020]　
若群组管理装置1200为应用功能网元，处理单元1202可以用于支持群组管理装置1200为新建群组分配新的外部群组标识，和/或用于本文所描述的方案的其它过程。通信单元1203用于支持群组管理装置1200和其他网元(例如接口网元)之间的通信，比如，执行图5所示的S501、S509，和/或，本文所描述方案的其他步骤。
[根据细则91更正 22.05.2020]　
若群组管理装置1200为策略网元，处理单元1202可以用于支持群组管理装置1200执行图5所示S511，和/或用于本文所描述的方案的其它过程。通信单元1203用于支持群组管理装置1200和其他网元之间的通信，比如，执行图5所示的S510、S512，和/或，本文所描述方案的其他步骤。
[根据细则91更正 22.05.2020]　
若群组管理装置1200为管理网元，处理单元1202可以用于支持群组管理装置1200执行图4所示S402、S403，和/或用于本文所描述的方案的其它过程。通信单元1203用于支持群组管理装置1200和其他网元之间的通信，比如，执行图4所示的S401、S404，和/或，本文所描述方案的其他步骤。
[根据细则91更正 22.05.2020]　
若群组管理装置1200为终端，处理单元1202可以用于支持群组管理装置1200执行根据URSP获知自己所在群组，和/或用于本文所描述的方案的其它过程。通信单元1203用于支持群组管理装置1200和其他网元之间的通信，比如，执行图5所示的S512，和/或，本文所描述方案的其他步骤。
[根据细则91更正 22.05.2020]　
可选的,群组管理装置1200还可以包括存储单元1201，用于存储群组管理装置1200的程序代码和数据，数据可以包括不限于原始数据或者中间数据等。
一种可能的方式中，处理单元1202可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理(Digital Signal Processing，DSP)，应用专用集成电路(Application Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field－Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元1203可以是收发器、收发电路或通信接口等。存储单元1201可以是存储器。
一种可能的方式中，当处理单元1202为处理器，通信单元1203为通信接口，存储单元1201为存储器时，本申请实施例所涉及的群组管理装置的结构可以为图11所示。
图11示出了本申请实施例中所涉及的群组管理装置的一种可能的设计结构的简化示意图。群组管理装置1500包括：处理器1502、通信接口1503、存储器1501。可选的，群组管理装置1500还可以包括总线1504。其中，通信接口1503、处理器1502以及存储器1501可以通过总线1504相互连接。总线1504可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。总线1504可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条线表示，但并不表示仅有一根总线或一种类型的总线。
本领域普通技术人员可以理解：在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(Digital Video Disc，DVD))、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件 可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络设备(例如终端)上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个功能单元独立存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘，硬盘或光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (34)

  1. 一种群组管理方法，其特征在于，包括：
    从应用功能网元接收第一群组请求，所述第一群组请求包括指示信息、外部群组标识和第一群组信息，所述指示信息用于指示群组业务类型，所述外部群组标识为核心网内部网元不能够识别的群组标识；
    若群组业务类型为创建群组，则获取所述外部群组标识对应的内部群组标识，所述内部群组标识为核心网内部能够识别的群组标识；
    对所述内部群组标识、所述外部群组标识，以及所述第一群组信息进行关联。
  2. 根据权利要求1所述的群组管理方法，其特征在于，所述第一群组信息包括如下至少一项信息：所述群组的数据网络标识、所述群组的切片信息、所述群组对应的会话类型、所述群组包括的一个或多个群组成员的第一标识。
  3. 根据权利要求1或2所述的群组管理方法，其特征在于，所述方法还包括：向接口网元发送所述内部群组标识。
  4. 根据权利要求2或3所述的群组管理方法，其特征在于，向一个或多个群组成员发送所述内部群组标识和所述第一群组信息。
  5. 一种群组管理方法，其特征在于，包括：
    从接口网元接收第二群组请求，所述第二群组请求包括外部群组标识和第一群组信息，所述外部群组标识为核心网内部不能够识别的群组标识；
    获取所述外部群组标识对应的内部群组标识，所述内部群组标识为核心网内部能够识别的群组标识；
    将所述内部群组标识、所述外部群组标识，以及所述第一群组信息进行关联。
  6. 根据权利要求5所述的群组管理方法，其特征在于，所述第一群组信息包括如下至少一项信息：所述群组的数据网络标识、所述群组的切片信息、所述群组对应的会话类型、所述群组包括的一个或多个群组成员的第一标识。
  7. 根据权利要求5或6所述的群组管理方法，其特征在于，获取所述外部群组标识对应的内部群组标识，包括：
    判断是否已存储所述外部群组标识对应的内部群组标识的条目；
    若确定未存储所述外部群组标识对应的所述内部群组标识的条目，则获取所述外部群组标识对应的所述内部群组标识。
  8. 根据权利要求5至7中任一项所述的群组管理方法，其特征在于，向接口网元发送所述内部群组标识，以指示所述接口网元存储所述内部群组标识。
  9. 根据权利要求5至8中任一项所述的群组管理方法，其特征在于，向一个或多个群组成员发送所述内部群组标识和所述第一群组信息。
  10. 一种群组管理方法，其特征在于，包括：
    从应用功能网元接收第三群组请求，所述第三群组请求包括外部群组标识和第一群组信息，所述外部群组标识为核心网内部不能够识别的群组标识；
    判断是否已存储所述外部群组标识对应的内部群组标识的条目，所述内部群组标识为核心网内部能够识别的群组标识；
    若未存储所述外部群组标识对应的内部群组标识的条目，则向数据网元发送第二 群组请求，所述第二群组请求包括所述外部群组标识和一个或多个群组成员的第一标识。
  11. 根据权利要求10所述的群组管理方法，其特征在于，所述第一群组信息包括如下至少一项信息：所述群组的数据网络标识、所述群组的切片信息、所述群组对应的会话类型、所述群组包括的一个或多个群组成员的第一标识。
  12. 一种群组管理装置，其特征在于，包括：
    通信接口，用于从应用功能网元接收第一群组请求，所述第一群组请求包括指示信息、外部群组标识和第一群组信息，所述指示信息用于指示群组业务类型，所述外部群组标识为核心网内部网元不能够识别的群组标识；
    处理器，用于若群组业务类型为创建群组，则获取所述外部群组标识对应的内部群组标识，所述内部群组标识为核心网内部能够识别的群组标识；对所述内部群组标识、所述外部群组标识，以及所述第一群组信息进行关联。
  13. 根据权利要求12所述的群组管理装置，其特征在于，所述第一群组信息包括如下至少一项信息：所述群组的数据网络标识、所述群组的切片信息、所述群组对应的会话类型、所述群组包括的一个或多个群组成员的第一标识。
  14. 根据权利要求12或13所述的群组管理装置，其特征在于，所述通信接口，还用于向接口网元发送所述内部群组标识。
  15. 根据权利要求12至14中任一项所述的群组管理装置，其特征在于，
    所述通信接口，还用于向一个或多个群组成员发送所述内部群组标识和所述第一群组信息。
  16. 一种群组管理装置，其特征在于，包括：
    通信接口，用于从接口网元接收第二群组请求，所述第二群组请求包括外部群组标识和第一群组信息，所述外部群组标识为核心网内部不能够识别的群组标识；
    处理器，用于获取所述外部群组标识对应的内部群组标识，所述内部群组标识为核心网内部能够识别的群组标识；将所述内部群组标识、所述外部群组标识，以及所述第一群组信息进行关联。
  17. 根据权利要求16所述的群组管理装置，其特征在于，所述第一群组信息包括如下至少一项信息：所述群组的数据网络标识、所述群组的切片信息、所述群组对应的会话类型、所述群组包括的一个或多个群组成员的第一标识。
  18. 根据权利要求16或17所述的群组管理装置，其特征在于，所述处理器，用于获取所述外部群组标识对应的内部群组标识，包括：用于判断是否已存储所述外部群组标识对应的内部群组标识的条目；若确定未存储所述外部群组标识对应的所述内部群组标识的条目，则获取所述外部群组标识对应的所述内部群组标识。
  19. 根据权利要求16至18中任一项所述的群组管理装置，其特征在于，所述通信接口，还用于向接口网元发送所述内部群组标识，以指示所述接口网元存储所述内部群组标识。
  20. 根据权利要求16至19中任一项所述的群组管理装置，其特征在于，所述通信接口，还用于向一个或多个群组成员发送所述内部群组标识和所述第一群组信息。
  21. 一种群组管理装置，其特征在于，包括：
    通信接口，用于从应用功能网元接收第三群组请求，所述第三群组请求包括外部群组标识和第一群组信息，所述外部群组标识为核心网内部不能够识别的群组标识；
    处理器，用于判断是否已存储所述外部群组标识对应的内部群组标识的条目，所述内部群组标识为核心网内部能够识别的群组标识；
    所述通信接口，还用于若未存储所述外部群组标识对应的内部群组标识的条目，则向数据网元发送第二群组请求，所述第二群组请求包括所述外部群组标识和一个或多个群组成员的第一标识。
  22. 根据权利要求21所述的群组管理装置，其特征在于，所述第一群组信息包括如下至少一项信息：所述群组的数据网络标识、所述群组的切片信息、所述群组对应的会话类型、所述群组包括的一个或多个群组成员的第一标识。
  23. 一种群组管理装置，其特征在于，包括：用于执行权利要求1至4任一项所述的群组管理方法中各个步骤的单元。
  24. 一种群组管理装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求1至4任一项所述的群组管理方法。
  25. 一种群组管理装置，其特征在于，包括：处理器和接口电路，所述接口电路用于与其它装置通信，所述处理器用于执行权利要求1至4任一项所述的群组管理方法。
  26. 一种群组管理装置，其特征在于，包括：用于执行权利要求5至9任一项所述的群组管理方法中各个步骤的单元。
  27. 一种群组管理装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求5至9任一项所述的群组管理方法。
  28. 一种群组管理装置，其特征在于，包括：处理器和接口电路，所述接口电路用于与其它装置通信，所述处理器用于执行权利要求5至9任一项所述的群组管理方法。
  29. 一种群组管理装置，其特征在于，包括：用于执行权利要求10或11所述的群组管理方法中各个步骤的单元。
  30. 一种群组管理装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求10或11所述的群组管理方法。
  31. 一种群组管理装置，其特征在于，包括：处理器和接口电路，所述接口电路用于与其它装置通信，所述处理器用于执行权利要求10或11所述的群组管理方法。
  32. 一种可读存储介质，其特征在于，包括程序或指令，当所述程序或指令被执行时，如权利要求1-4中任一项所述的群组管理方法被实现，或者，如权利要求5-9中任一项所述的群组管理方法被实现，或者，如权利要求10或11所述的群组管理方法被实现。
  33. 一种计算机程序产品，其特征在于，包括指令，当所述指令被执行时，如权利要求1-4中任一项所述的群组管理方法被实现，或者，如权利要求5-9中任一项所述的群组管理方法被实现，或者，如权利要求10或11所述的群组管理方法被实现。
  34. 一种群组管理系统，其特征在于，包括如权利要求12-15中任一项所述的群组管理装置，以及权利要求21-22中任一项所述的群组管理装置，或者，所述群组管理系统包括如权利要求16-20中任一项所述的群组管理装置，以及权利要求21-22中任一项所述的群组管理装置。
PCT/CN2020/088519 2019-05-06 2020-04-30 群组管理方法、装置及系统 WO2020224559A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20802287.1A EP3955521A4 (en) 2019-05-06 2020-04-30 GROUP MANAGEMENT METHOD, DEVICE AND SYSTEM
US17/519,741 US12063709B2 (en) 2019-05-06 2021-11-05 Group management method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910372920.9A CN111901132B (zh) 2019-05-06 2019-05-06 群组管理方法、装置及系统
CN201910372920.9 2019-05-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/519,741 Continuation US12063709B2 (en) 2019-05-06 2021-11-05 Group management method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2020224559A1 true WO2020224559A1 (zh) 2020-11-12

Family

ID=73050715

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/088519 WO2020224559A1 (zh) 2019-05-06 2020-04-30 群组管理方法、装置及系统

Country Status (4)

Country Link
US (1) US12063709B2 (zh)
EP (1) EP3955521A4 (zh)
CN (1) CN111901132B (zh)
WO (1) WO2020224559A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112533178A (zh) * 2020-11-24 2021-03-19 中移（杭州）信息技术有限公司 网络能力开放的实现方法、平台、服务器、存储介质
WO2022143983A1 (zh) * 2020-12-31 2022-07-07 华为技术有限公司 Lan群组计费的方法、及相关装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200038808A (ko) * 2018-10-04 2020-04-14 삼성전자주식회사 무선 통신 시스템에서 그룹 통신을 제공하는 방법 및 장치
CN114521004A (zh) * 2020-11-19 2022-05-20 中国移动通信集团有限公司 数据发送方法、装置、设备及存储介质
CN115776665B (zh) * 2021-09-06 2024-04-19 中国联合网络通信集团有限公司 Vn组配置方法、装置、设备及存储介质
CN113794627A (zh) * 2021-09-29 2021-12-14 北京字跳网络技术有限公司 即时通信群组的处理方法、处理装置、设备和存储介质
WO2023186341A1 (en) * 2022-03-29 2023-10-05 Telefonaktiebolaget Lm Ericsson (Publ) Handling of groups of user equipment in a core network

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108206986A (zh) * 2016-12-08 2018-06-26 诺基亚技术有限公司 一种发送组消息的方法和设备
US20180270778A1 (en) * 2017-03-17 2018-09-20 Samsung Electronics Co., Ltd. Af influenced pdu session management and subscription procedures
US20180352050A1 (en) * 2017-06-02 2018-12-06 Huawei Technologies Co., Ltd. Method and system for supporting edge computing
CN109640275A (zh) * 2018-12-24 2019-04-16 新华三技术有限公司成都分公司 小区重选方法、装置及宽带集群系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8527347B2 (en) * 2009-11-12 2013-09-03 Oracle International Corporation Integration architecture for mobile advertisement campaign management, marketplace and service provider interface
US8713076B2 (en) * 2012-01-20 2014-04-29 Cross Commerce Media, Inc. Providing a multi-tenant knowledge network
US9432820B2 (en) * 2013-05-29 2016-08-30 Qualcomm Incorporated Method for efficiently supporting multiple simultaneous group PTT calls requiring low call setup latency
KR102167870B1 (ko) * 2014-07-07 2020-10-20 콘비다 와이어리스, 엘엘씨 머신 타입 통신 그룹 기반 서비스를 위한 조정된 그룹화
CN104618349B (zh) * 2015-01-13 2018-09-11 上海华为技术有限公司 一种集群通信系统、服务器及通信方法
CN111885508B (zh) * 2015-12-15 2022-04-12 华为云计算技术有限公司 一种群组多播和群组创建的方法以及移动网络平台

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108206986A (zh) * 2016-12-08 2018-06-26 诺基亚技术有限公司 一种发送组消息的方法和设备
US20180270778A1 (en) * 2017-03-17 2018-09-20 Samsung Electronics Co., Ltd. Af influenced pdu session management and subscription procedures
US20180352050A1 (en) * 2017-06-02 2018-12-06 Huawei Technologies Co., Ltd. Method and system for supporting edge computing
CN109640275A (zh) * 2018-12-24 2019-04-16 新华三技术有限公司成都分公司 小区重选方法、装置及宽带集群系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON ET AL.: "Group Identifier Translation", 3GPP TSG-CT WG4 MEETING #90 C4-191362, 21 March 2019 (2019-03-21), XP051706638, DOI: 20200716192250X *
See also references of EP3955521A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112533178A (zh) * 2020-11-24 2021-03-19 中移（杭州）信息技术有限公司 网络能力开放的实现方法、平台、服务器、存储介质
CN112533178B (zh) * 2020-11-24 2022-04-08 中移（杭州）信息技术有限公司 网络能力开放的实现方法、平台、服务器、存储介质
WO2022143983A1 (zh) * 2020-12-31 2022-07-07 华为技术有限公司 Lan群组计费的方法、及相关装置

Also Published As

Publication number Publication date
EP3955521A1 (en) 2022-02-16
US20220060881A1 (en) 2022-02-24
CN111901132B (zh) 2022-04-05
EP3955521A4 (en) 2022-06-08
CN111901132A (zh) 2020-11-06
US12063709B2 (en) 2024-08-13

Similar Documents

Publication Publication Date Title
WO2020224559A1 (zh) 群组管理方法、装置及系统
CN109842906B (zh) 一种通信的方法、装置及系统
US11812496B2 (en) User group session management method and apparatus
WO2018205150A1 (zh) 网络切片选择策略更新方法、及装置
WO2019029525A1 (zh) 网络功能信息的管理方法及相关设备
WO2018232570A1 (zh) 一种注册及会话建立的方法、终端和amf实体
EP3577952B1 (en) Method and system for selection of an access and mobility management function in an access network environment
WO2019196811A1 (zh) 通信方法和相关装置
EP4142218A1 (en) Slice access method, device and system
WO2019033269A1 (zh) 一种会话建立的方法及设备
WO2022033345A1 (zh) 一种pdu会话建立方法、终端设备和芯片系统
WO2019095837A1 (zh) 数据处理方法、装置及设备
WO2018090386A1 (zh) 一种nf组件异常的处理方法、设备及系统
WO2018024121A1 (zh) 一种网络功能nf管理方法及nf管理设备
WO2021197155A1 (zh) 一种通信方法及装置
WO2019076308A1 (zh) 终端设备的状态的确定方法、装置及设备
WO2020052463A1 (zh) 通信方法和网元
WO2021227600A1 (zh) 一种网络切片控制方法及通信装置
WO2021163901A1 (zh) 一种会话处理方法及其装置
WO2023051288A1 (zh) 一种隧道管理方法、装置及系统
WO2022237857A1 (zh) 确定安全保护开启方式的方法、通信方法及通信装置
WO2022099484A1 (zh) 标识发送方法和通信装置
WO2021115447A1 (zh) 会话管理网元发现的方法、设备及系统
WO2020259058A1 (zh) 一种策略和计费控制的实现方法及装置
WO2020156277A1 (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: 20802287

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

Country of ref document: EP

Effective date: 20211110