Communication resource management method, device, system, and storage medium

Abstract

The present application provides a communication resource management method, apparatus, and related device. A session management function entity acquires a quality of service (QoS) parameter set from a first network element, where the QoS parameter set includes at least one QoS parameter to be applied to a terminal device group, the terminal device group including multiple terminal devices; acquires a corresponding policy control rule set based on the QoS parameter set, where the policy control rule set includes at least one policy control rule; and applies the policy control rule set to a data connection session of the terminal device, where the data connection session of the terminal device is for intra-group communication of the terminal device group. Thus, management resources can be efficiently configured for PDU sessions corresponding to the terminal devices in the terminal device group.

Description

[Technical Field]

[0001] The present application relates to the field of communications, and more particularly to a resource management method and a communications device. [Background technology]

[0002] Fifth generation (5G) local area network (5G LAN) services are services provided by current 5G networks and are mainly applied to home communications, corporate offices, factory manufacturing, Internet of Vehicles, power grid reconstruction, public security organizations, and the like. The services can provide private communications of Internet Protocol type or non-IP type (e.g., Ethernet type) for two or more terminals in a group of terminals. For example, devices in a factory can form a group, and the devices in the group can transmit Ethernet data packets to each other. Alternatively, the office devices (such as mobile phones, computers, or notebook computers) of employees in a department of an enterprise can form a group and transmit IP data packets to each other.

[0003] QoS (Quality of Service) is a security mechanism that ensures the quality of service of a network. In a practical network environment, QoS configuration usually needs to be performed on a user equipment to ensure the quality of service of the network. In the existing QoS configuration, the application management function network element (AF) separately sends corresponding configuration requests to the network function publishing network element (NFE) to separately perform the QoS configuration on the PDU sessions of a single user equipment. Therefore, the efficiency is low. Summary of the Invention

[0004] SUMMARY OF THE INVENTION The present application provides a communication resource management method, an apparatus, and a related device, according to which a data connection session can be configured for at least one terminal device in a terminal device group.

[0005] According to a first aspect, an embodiment of the present application provides a communication resource management method applied to a session management function entity, the method comprising: receiving a group identifier of a terminal device group to which a first terminal device belongs, and a data network identity and network slicing support information of a data connection session of the first terminal device; receiving, from a data management network element, a data network identity and network slicing support information corresponding to the group identifier, and first indication information, wherein the first indication information indicates obtaining, from an authentication server, a quality of service QoS parameter set to be applied to the terminal device group, the QoS parameter set including at least one QoS parameter to be applied to the terminal device group; and receiving, from a data management network element, a data network identity and network slicing support information of the data connection session of the first terminal device, respectively, the data network identity and network slicing support information corresponding to the group identifier and first indication information, wherein the first indication information indicates obtaining, from an authentication server, a quality of service QoS parameter set to be applied to the terminal device group, the QoS parameter set including at least one QoS parameter to be applied to the terminal device group. The method includes determining that the data network identity and the network slice assistance information are the same; sending a first authentication request message to the authentication server based on the first indication information, where the first authentication request message includes the data network identity and the network slice assistance information of the terminal device group; obtaining a first authentication response message from the authentication server, where the first authentication response message includes the QoS parameter set of the terminal device group; obtaining a policy control rule set based on the QoS parameter set, where the policy control rule set includes at least one policy control rule; and binding the policy control rule set to a QoS flow of the data connection session of the first terminal device. It can be recognized that a corresponding policy control rule is obtained based on the QoS parameter set, and the policy rule is applied to the data connection session, thereby allowing the first network element to obtain at least one Quality of Service QoS flow used for the terminal device group at a certain time. This reduces signaling exchanges and saves network resources.

[0006] In a possible design, the first indication information further includes an address of the authentication server. It can be appreciated that the QoS parameter set can be obtained from an authentication server.

[0007] In a possible design, the data network identity and the network slice support information of the data connection session of the first terminal device are received from the first terminal device; and the group identifier of the terminal device group is received from the data management network element.

[0008] In a possible design, the step of obtaining a policy control rule set based on the QoS parameter set includes: sending a second request message to a policy control function entity, where the second request message includes the QoS parameter set; and receiving a second response message sent by the policy control function entity, where the second response message includes the policy control rule set.

[0009] In a possible design, the QoS parameter is at least one of the following parameters: priority of session transmission packets, packet size, delay, maximum rate, guaranteed rate, packet error rate, periodicity, clock domain, packet arrival time, remaining time, or silence time.

[0010] According to a second aspect, an embodiment of the present application provides a second communication resource management method applied to a data management network element entity, the method comprising: receiving a configuration request message sent by an application function network element, where the configuration request message includes a group identifier of a terminal device group to which a first terminal device belongs, a data network identity and network slice support information of the terminal device group, and first indication information, the first indication information indicating to obtain a quality of service QoS parameter set applicable to the terminal device group from an authentication server, the QoS parameter set including at least one QoS parameter applied to the terminal device group; receiving the group identifier sent by a session management network element; and indexing the data network identity and the network slice support information of the terminal device group based on the group identifier, and transmitting the data network identity and the network slice support information of the terminal device group and the first indication information to the session management network element. It can be appreciated that the data management network element entity obtains information related to the QoS parameter set and transmits this information related to the QoS parameter set to the session management network element, thereby allowing the session management network element to obtain the information related to the QoS parameter set by using one message in order to reduce signaling exchanges.

[0011] In a possible design, the first indication information further includes an address of the authentication server. In a possible design, the QoS parameter is at least one of the following parameters: a priority of a session transmission packet, a packet size, a delay, a maximum rate, a guaranteed rate, a packet error rate, a periodicity, a clock domain, a packet arrival time, a time remaining, or a quiet time.

[0012] According to a third aspect, an embodiment of the present application provides a communication resource management method, including: a data management function entity receives a configuration request message sent by an application function network element, where the configuration request message includes a group identifier of a terminal device group to which a first terminal device belongs, a data network identity and network slice support information of the terminal device group, and first indication information, where the first indication information indicates obtaining a quality of service (QoS) parameter set to be applied to the terminal device group from an authentication server, the QoS parameter set including at least one QoS parameter to be applied to the terminal device group. The data management function entity receives the group identifier sent by a session management network element. The data management function entity indexes the data network identity and the network slice support information of the terminal device group based on the group identifier, and sends the data network identity and the network slice support information of the terminal device group, and the first indication information to a session management function entity. The session management function entity receives the data network identity and the network slice support information of the terminal device group, and the first indication information from the data management function entity. The session management function entity determines that the data network identity and network slice support information of the data connection session of the first terminal device are the same as the data network identity and the network slice support information of the terminal device group, respectively, and sends a first authentication request message to the authentication server based on the first indication information, wherein the first authentication request message includes the data network identity and the network slice support information of the terminal device group.The session management function entity receives a first authentication response message from the authentication server, where the first authentication response message includes the QoS parameter set for the terminal device group. The session management function entity receives a policy control rule set based on the QoS parameter set, where the policy control rule set includes at least one policy control rule. The session management function entity binds the policy control rule set to a QoS flow of the data connection session of the first terminal device. In a possible design, the first indication information further includes an address of the authentication server.

[0013] In a possible design, the session management function entity receives from the first terminal device the data network identity and the network slice support information of the data connection session of the first terminal device.

[0014] In a possible design, the step of the session management function entity obtaining a policy control rule set based on the QoS parameter set includes: sending a second request message to a policy control function entity, where the second request message includes the QoS parameter set; and receiving a second response message sent by the policy control function entity, where the second response message includes the policy control rule set.

[0015] In a possible design, the QoS parameter is at least one of the following parameters: priority of session transmission packets, packet size, delay, maximum rate, guaranteed rate, packet error rate, periodicity, clock domain, packet arrival time, remaining time, or silence time.

[0016] According to a fourth aspect, an embodiment of the present application provides a communications apparatus, which may be a device, or a chip or circuit disposed within the device, comprising a module configured to perform a communications resource management method as provided in any one of the possible designs of the first aspect.

[0017] According to a fifth aspect, an embodiment of the present application provides a communications apparatus, which may be a device, or a chip or circuit disposed within the device, comprising a module configured to perform a communications resource management method as provided in any one of the possible designs of the second aspect.

[0018] According to a sixth aspect, an embodiment of the present application provides a communications device, comprising: a processor configured to execute instructions stored in a memory that enable the communications device to perform a communications resource management method as provided in any one of the possible designs of the first aspect or the second aspect.

[0019] According to a seventh aspect, an embodiment of the present application provides a computer program or computer program product comprising code or instructions, which when executed on a computer, enable the computer to perform the method in any one of the possible implementations of the first and second aspects. [Brief explanation of the drawings]

[0020] [Figure 1] FIG. 1 is a diagram of an architecture of a network system according to an embodiment of the present application. [Figure 2] A diagram of the user plane architecture for 5G LAN services. [Figure 3] FIG. 1 illustrates a communication resource configuration method according to an embodiment of the present application. [Figure 4] FIG. 1 illustrates another communication resource configuration method according to an embodiment of the present application. [Figure 5A] FIG. 1 illustrates another communication resource configuration method according to an embodiment of the present application. [Figure 5B] FIG. 1 illustrates another communication resource configuration method according to an embodiment of the present application. [Figure 6] FIG. 1 illustrates another communication resource configuration method according to an embodiment of the present application. [Figure 7] FIG. 1 illustrates another communication resource configuration method according to an embodiment of the present application. [Figure 8] 1 is a diagram of the structure of a communication device according to an embodiment of the present application; [Figure 9] FIG. 2 is a diagram of the structure of another communication device according to an embodiment of the present application; [Figure 10] FIG. 2 is a diagram of the structure of another communication device according to an embodiment of the present application; [Figure 11] FIG. 2 is a diagram of the structure of another communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0021] For ease of understanding, the following will first explain technical terms in the embodiments of the present application. 1. 5th generation (5G) mobile communication system (abbreviated as 5G system (5GS)) Figure 1 is a diagram of a non-roaming architecture of 5GS. As shown in Figure 1, 5GS includes an access network (AN) and a core network (CN), and may further include a terminal.

[0022] A terminal may be a terminal having receiving and transmitting capabilities, or may be a chip or chip system that may be located within a terminal. A terminal may also be called user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station (MS), remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communication device, user agent, or user equipment. The terminal in the embodiments of the present application may be a mobile phone, a cellular phone, a smartphone, a tablet computer (Pad), a wireless data card, a personal digital assistant (PDA) computer, a wireless modem, a handheld device (handset), a laptop computer, a machine type communication (MTC) terminal, a computer with wireless transceiver functionality, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, an in-vehicle terminal, a road side unit (RSU) with terminal functionality, or the like. Alternatively, the terminal in this application may be an on-board module, on-board assembly, on-board part, on-board chip, or on-board unit that is constructed in a vehicle as one or more parts or units.

[0023] The AN is for implementing access-related functions and may provide network access functions for authorized users in a specific area, and may determine transmission links with different qualities based on user levels, service requirements, and the like to transmit user data. The AN transfers control signals and user data between terminals and CNs. The AN may include an access network device or may be referred to as a radio access network (RAN) device. The CN is mainly responsible for maintaining subscription data of the mobile network and provides functions such as session management, mobility management, policy management, and security authentication for terminals. The CN mainly includes the following network elements: a user plane function (UPF) network element, an authentication server function (AUSF) network element, an access and mobility management function (AMF) network element, a session management function (SMF) network element, a network slice selection function (NSSF) network element, a network exposure function (NEF) network element, a network function repository function (NRF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, a unified data repository (UDR), and an application function (AF).

[0024] As shown in Figure 1, a UE accesses a 5G network through a RAN device, and the UE communicates with an AMF network element through an N1 interface (abbreviated as N1). The RAN network element communicates with an AMF network element through an N2 interface (abbreviated as N2). The RAN network element communicates with a UPF network element through an N3 interface (abbreviated as N3). The SMF communicates with a UPF network element through an N4 interface (abbreviated as N4), and the UPF network element accesses a data network (DN) through an N6 interface (abbreviated as N6). In addition, control plane functions, such as the AUSF network element, AMF network element, SMF network element, NSSF network element, NEF network element, NRF network element, PCF network element, UDM network element, UDR network element, or AF shown in Figure 1, interact with each other through service-based interfaces. For example, a service-based interface presented by an AUSF network element is Nausf, a service-based interface presented by an AMF network element is Namf, a service-based interface presented by an SMF network element is Nsmf, a service-based interface presented by an NSSF is Nnssf, a service-based interface presented by an NEF network element is Nnef, a service-based interface presented by an NRF network element is Nnrf, a service-based interface presented by a PCF network element is Npcf, a service-based interface presented by a UDM network element is Nudm, a service-based interface presented by a UDR network element is Nudr, and a service-based interface presented by an AF is Naf.

[0025] The RAN device may be a device that provides access for a terminal. For example, the RAN device may include a next-generation mobile communication system (e.g., 6G access network device such as a 6G base station). Alternatively, in a next-generation mobile communication system, the network device may be named in another manner, which falls within the scope of protection of the embodiments of the present application. This is not limited in the present application. Alternatively, the RAN device may include a 5G, e.g., a gNB in ​​a new radio (NR) system, or one or a group of antenna panels (including multiple antenna panels) of a base station in 5G, or may be a gNB, a transmission and reception point (TRP or transmission point, TP), or a transmission measurement function (TMF), e.g., a baseband unit (BBU), a central unit (CU) or a distributed unit (DU), an RSU with base station functionality, a wired access gateway, or a network node forming a 5G core network element. Alternatively, a RAN device may include an access point (AP) in a wireless fidelity (Wi-Fi®) system, a wireless relay node, a wireless backhaul node, various forms of macro base stations, micro base stations (also referred to as small cells), relay stations, access points, wearable devices, in-vehicle devices, or the like.

[0026] The UPF network element is mainly responsible for user data processing (forwarding, reception, charging, and the like). For example, the UPF network element may receive user data from a data network (DN) and forward the user data to a terminal via an access network device. Alternatively, the UPF network element may receive user data from a terminal via an access network device and forward the user data to the DN. The DN network element is an operator network that provides data transmission services for users, such as Internet Protocol (IP) multimedia services (IMS) and the Internet. The DN may be an operator's external network or a network controlled by the operator, and is configured to provide services for terminal devices.

[0027] The AUSF network element is primarily configured to perform security authentication on the terminal.

[0028] The AMF network element is mainly for mobility management in a mobile network, such as user location update, user registration to the network, and user handover.

[0029] The SMF network element is mainly responsible for session management in a mobile network, such as session establishment, modification, and release. Specific functions include assigning an Internet Protocol (IP) address to a user or selecting a UPF network element that provides data packet forwarding functionality.

[0030] The PCF network element is mainly responsible for providing a unified policy framework to control network behavior, supporting provision of policy rules for control layer network functions, and obtaining users' policy-related subscription information. The PCF network element may provide policies, such as quality of service (QoS) policies or slice selection policies, to the AMF network element and the SMF network element.

[0031] The NSSF network element is primarily configured to select a network slice for a terminal.

[0032] The NEF network element is primarily for function support and event publishing.

[0033] The UDM network element is primarily configured to store user data, such as subscription data and authentication / authorization data.

[0034] The UDR network element is primarily configured to store structured data, including subscription data, policy data, publicly visible structured data, and application-related data.

[0035] The AF mainly supports interaction with the CN to provide services, such as influencing data routing decision-making and policy control functions, or providing some third-party services for the network side.

[0036] As shown in Figure 1, the 5G network may further include an access device, a user plane function (UPF) network element, an authentication server function (AUSF) network element, a network slice selection function (NSSF) network element, a network exposure function (NEF) network element, a network function repository function (NRF) network element, a unified data management (UDM) network element, an application function (AF) network element, and the like, which is not specifically limited in this embodiment of the present application. (2)QoS A UE may establish a data connection session (e.g., a protocol data unit (PDU) session) with a UPF network element. A PDU session is used as an example in the following description to explain the method. For a PDU session, a QoS flow is the smallest granularity for QoS differentiation. A QoS flow may be a QoS flow that supports guaranteed bit rate (GBR) QoS, i.e., a GBR QoS flow, or a QoS flow that supports non-guaranteed bit rate (non-GBR) QoS, i.e., a non-GBR QoS flow. One PDU session may include multiple QoS flows. For example, up to 64 QoS flows are supported. Each QoS flow has a corresponding QoS flow identifier (QFI) to distinguish between different QoS flows. User plane service flows with the same QFI may be mapped to the same QoS flow, so that the same service transport processing mode (e.g., scheduling) can be used to process the user plane service flows. One PDU session may correspond to multiple radio bearers (RBs) on the air interface, and one radio bearer may contain one or multiple QoS flows, in other words, carry one or multiple QoS flows.

[0037] QoS configuration is at the QoS flow level, i.e., the configuration is performed at the granularity of a QoS flow. The characteristics of a QoS flow may be represented by several parameters. The SMF network element pre-configures, establishes, or modifies the corresponding QoS flow by configuring these parameters. For example, for a QoS flow, these parameters include a QoS profile on the RAN device side, a QoS rule on the UE side, and an uplink packet detection rule (PDR) and a downlink PDR on the UPF network side. 3.5G LAN service 5G LAN service is a service provided by a 5G network. The service can provide IP or non-IP (Ethernet type) private communication for two or more UEs in a certain group of UEs. 5G LAN service is mainly for home communication, enterprise offices, factory manufacturing, Internet of Vehicles, power grid reconstruction, public security organizations, and the like. A UE in a certain group of UEs joins the group due to service requirements or dedicated attributes. UEs in a group may communicate with each other by using the 5G LAN service. For example, devices in a factory form a group, and the devices in the group may send Ethernet data packets to each other. Office devices (mobile phones, computers, or notebook computers) of employees in a certain department of an enterprise form a group and send IP data packets to each other. If two UEs are not in the same group, the two UEs cannot communicate with each other.

[0038] 2 is a diagram of a user plane architecture of an existing 5G LAN service. A terminal establishes a session with a UPF network element providing a 5G LAN service to access the UPF network element providing the 5G LAN service. As described above, the UPF network element providing the 5G LAN service may interconnect with an existing LAN in a data network through N6, for example, to communicate with a personal computer (PC) in the LAN. Alternatively, the UPF network element providing the 5G LAN service may associate sessions of different terminals through an internal connection between the UPF network elements to implement private communication. This is not specifically limited in this embodiment of the present application.

[0039] To complete communication in a 5G LAN, specific user equipment needs to be grouped into a VN group based on requirements, and members in the VN group can perform intra-group communication in the 5G LAN. In the VN configuration mode, a third party can flexibly perform dynamic VN group subscription management through a function publishing platform. In the prior art, when a QoS flow is configured for a PDU session corresponding to each terminal device in a VN group, the AF needs to separately send parameter configuration messages to configure the PDU session of each terminal device one by one. This resource configuration management method has low efficiency and high signaling overhead. Therefore, how to efficiently configure management resources for PDU sessions corresponding to terminal devices in a terminal device group becomes a problem that needs to be solved.

[0040] The following describes the technical solution of the present application with reference to the accompanying drawings.

[0041] The technical solutions in the embodiments of the present application may be applied to various communication systems, such as wireless fidelity (Wi-Fi®) systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, Internet of Vehicles communication systems, fourth generation (4G) mobile communication systems, such as long term evolution (LTE) systems and worldwide interoperability for microwave access (WiMAX®) communication systems, fifth generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems, such as sixth generation (6G) mobile communication systems.

[0042] All aspects, embodiments, or features are presented herein by describing a system that may include multiple devices, components, modules, and the like. It is to be appreciated and understood that each system may include other devices, components, modules, and the like and / or may not include all of the devices, components, modules, and the like discussed with reference to the accompanying drawings. Additionally, combinations of these solutions may be used.

[0043] Additionally, in the embodiments of the present application, terms such as "example" or "for example" are intended to provide an example, illustration, or explanation. Any embodiment or design scheme described herein as an "example" should not be described as preferred or having more advantages than another embodiment or design scheme. Strictly speaking, the term "example" is intended to present a concept in a particular way.

[0044] In the embodiments of the present application, "information", "signal", "message", "channel", and "signaling" may sometimes be used interchangeably. It should be noted that the meanings represented by these terms are equivalent when the difference between the terms is not emphasized. The terms "of", "corresponding, relevant", and "corresponding" may sometimes be used interchangeably. It should be noted that the meanings represented by these terms are equivalent when the difference between the terms is not emphasized. In addition, " / " referred to in the present application may indicate an "or" relationship.

[0045] The network architectures and service scenarios described in the embodiments of the present application are intended to more clearly explain the technical solutions in the embodiments of the present application, and do not constitute limitations on the technical solutions provided in the embodiments of the present application. Those skilled in the art may recognize that with the evolution of network architectures and the emergence of new service scenarios, the technical solutions provided in the embodiments of the present application can also be applied to similar technical problems.

[0046] The following describes important terms in the embodiments of the present application.

[0047] A terminal device group includes multiple terminal devices. For example, the terminal device group may be a group of terminal devices that can enjoy consistent services provided by an application network element, or may be a group of all terminal devices located within a specified area. The terminal device group may be a 5G VN or another type of terminal device group, for example, a temporary terminal device group or a dynamic terminal device group (a terminal device group whose members need to be dynamically managed). This is not specifically limited.

[0048] A QoS parameter set includes at least one QoS parameter that applies to a terminal device group. Note that the QoS parameter sets in this specification are at a group granularity, that is, each terminal device group corresponds to one QoS parameter set.

[0049] A policy control rule set includes at least one policy control rule, also referred to as a PCC rule, and multiple PCC rules are associated with one QoS flow.

[0050] A data connection session is an association between a user equipment and a user plane data gateway, for providing a connection service for communication between the user equipment and an accessed network or between the user equipment and another user equipment. The creation process of a data connection session may be initiated by the user equipment, and the deletion process of a data connection session may be initiated by the user equipment or another network device. In the embodiments of the present application, a data connection session is sometimes referred to as a "data session" or simply as a "session." The data connection session may be an IP-CAN (IP-connectivity access network) session or a protocol data unit session (PDU session) defined in the 3GPP (registered trademark) standard specifications, or may be another type of session. This is not limited in the embodiments of the present application.

[0051] The data connection session may be a protocol data unit session applicable to a 5G network, or may be another session applicable to another network, which is not limited in the embodiments of the present application.

[0052] 3 is a schematic flowchart of a communication resource management method according to an embodiment of the present application, which is applied to a scenario in which session management resources are configured for terminal devices belonging to the same terminal device group.

[0053] S301: The SMF obtains a quality of service QoS parameter set from a first network element, where the QoS parameter set includes at least one QoS parameter applied to a terminal device group.

[0054] In one implementation, the first network element is an AF, and the QoS parameter set is obtained from the AF.

[0055] In one implementation, the first network element is a UDM, and the QoS parameter set is obtained from the UDM.

[0056] In this way, the SMF obtains the QoS parameter set from the first network element; when terminal devices in the terminal device group establish PDU sessions separately, the SMF does not need to obtain the QoS parameters corresponding to the terminal devices in multiple batches from the AF or another network element, thereby reducing signaling exchanges.

[0057] S302: The SMF obtains a corresponding policy control rule set based on the QoS parameter set, where the policy control rule set includes at least one policy control rule.

[0058] The SMF sends a second request message to the PCF, where the second request message includes the QoS parameter set. The SMF receives the first response message sent by the PCF, where the first response message includes the policy control rule set.

[0059] S303: The SMF applies policy control rules to a data connection session of the terminal device, where the data connection session of the terminal device is for intra-group communication of the terminal device group.

[0060] The SMF binds policy control rules to the QoS flows of the data connection sessions of the terminal device.

[0061] The SMF determines that the data connection session is for internal communication of the terminal device group based on the acquired group DNN and slice identifier and the DNN and slice identifier corresponding to the data connection session of the terminal device. The group slice identifier is for identifying a slice instance corresponding to the terminal device group. If it is determined that the DNN and slice identifier corresponding to the data connection session are the same as the group DNN and group slice identifier, it is determined that the data connection session is for internal communication of the terminal device group to which the terminal device belongs.

[0062] In this way, after it is determined that the data connection session of the terminal device is for internal communication of the terminal device group to which the terminal device belongs, the SMF obtains the QoS parameter set corresponding to the terminal device group, and the QoS parameters corresponding to a single terminal device do not need to be obtained separately, which helps to simplify signaling exchanges and reduce network resource consumption.

[0063] The above steps are merely examples for ease of explanation and do not constitute limitations on the sequence of steps.

[0064] The following describes in detail two implementations of the embodiment of FIG. 3 separately.

[0065] FIG. 4 is a schematic flowchart of a resource configuration management method according to an embodiment of the present application.

[0066] S311: The UDM receives a configuration request message sent by an application function network element AF, where the configuration request message includes a group identifier (group identifier #1) of a terminal device group to which a first terminal device (terminal device #1) belongs, a data network identity (group DNN #1) and network slice support information (group S-NSSAI #1) corresponding to the group identifier, and first indication information.

[0067] The first indication information indicates obtaining, from an authentication server, a quality of service QoS parameter set to be applied to the terminal device group, where the QoS parameter set includes at least one QoS parameter to be applied to the terminal device group.

[0068] S312: The SMF receives data network identity and network slice support information from the data connection session of the terminal device.

[0069] The UE establishes a PDU session request, where the PDU session request carries the data network identity DNN and network slice support information S-NSSAI of the UE's PDU session.

[0070] The SMF may obtain the terminal device identifier from the AMF.

[0071] S313: The SMF obtains the group identifier #1 of the terminal device group to which the first terminal device belongs.

[0072] The UDM stores a subscription data packet of the UE, where the subscription data packet includes a group identifier of a terminal device group to which the first terminal device belongs.

[0073] The SMF acquires, from the UDM based on the terminal device identifier, the group identifier (group identifier #1) of the terminal device group to which the first terminal device belongs.

[0074] S314: The SMF sends the group identifier #1 of the terminal device group to which the first terminal device belongs to the UDM.

[0075] S315: Based on the group identifier, the UDM indexes the data network identity (group DNN) and network slice support information (group S-NSSAI) corresponding to the group identifier.

[0076] S316: The UDM sends a data network identity (group DNN) and a network slice support identifier (group S-NSSAI) corresponding to the group identifier, and the first indication information to the SMF.

[0077] In response, the SMF receives the group DNN, group S-NSSAI, and first indication information from the UDM.

[0078] S317: The SMF determines that the data network identity of the data connection session of the terminal device is the same as the data network identity corresponding to the group identifier, and that the network slice support information of the data connection session of the terminal device is the same as the network slice support information corresponding to the group identifier.

[0079] The SMF determines that the DNN#1 of the terminal device is the same as the group DNN#1 of the terminal device group, and the S-NSSAI#1 of the terminal device is the same as the group S-NSSAI#1 of the terminal device group. Therefore, it is determined that the terminal device belongs to the terminal device group, and the data connection session of the terminal device is for internal communication of the terminal device group to which the terminal device belongs.

[0080] S318: The SMF sends a first authentication request message to the authentication server based on the first indication information.

[0081] The first authentication request message includes a data network identity corresponding to the group identifier and network slice support information.

[0082] S319: The authentication server sends a first authentication response message to the SMF, where the first authentication response message includes a QoS parameter set of the terminal device group.

[0083] A mapping relationship between the QoS parameter set and the data network identity (group DNN#1) and network slice support information (group S-NSSAI#1) corresponding to the group identifier is configured on the authentication server. The authentication server indexes the corresponding QoS parameter set based on the received group DNN#1 and group S-NSSAI#1. In this way, the QoS parameter set corresponding to the terminal device group is obtained.

[0084] The QoS parameter set includes QoS parameters that apply to a terminal device group, specifically, the QoS parameter set includes at least one of the following parameters: priority of session transmission packets, packet size, delay, maximum rate, guaranteed rate, packet error rate, periodicity, clock domain, packet arrival time, remaining time, or silence time.

[0085] S320: The SMF obtains a policy control rule set based on the QoS parameter set. The policy control rule set includes at least one policy control rule.

[0086] The SMF sends the QoS parameter set to the PCF, and the PCF obtains a corresponding policy control rule set based on the QoS parameter set, and then sends the policy control rule set to the SMF.

[0087] S321: The SMF binds a policy control rule set to a QoS flow of a data connection session of a first terminal device.

[0088] In this way, after it is determined that the data connection session of the terminal device is for internal communication of the terminal device group to which the terminal device belongs, the SMF obtains the QoS parameter set corresponding to the terminal device group, and the QoS parameters corresponding to a single terminal device do not need to be obtained separately, which helps to simplify signaling exchanges and reduce network resource consumption.

[0089] 5A and 5B are schematic flowcharts of a resource configuration management method according to an embodiment of the present application.

[0090] S401: An application function network element AF sends a first configuration request message to a network function publishing network element NEF.

[0091] An AF is configured to provide a specific service. An AF may be a service server. For example, an AF may be a game server or a video server.

[0092] The first configuration request message is for sending a configuration message related to a service requirement. The first configuration request message is for requesting to create / update / delete a terminal device group. For example, the first configuration request message is a Nnef_ParameterProvision_Create / Update / Delete request.

[0093] In one implementation, if the service requirement is for a terminal device group to create or update a PDU session for the terminal device group, the first configuration request message is for transmitting relevant parameters required to create or update a PDU session for the terminal device group.

[0094] The first parameter configuration request message includes a group identifier (Group ID) of a terminal device group to which the first terminal device belongs, a data network identity (Group DNN) and network slice support information (Group S-NSSAI) corresponding to the group identifier, and first indication information.

[0095] The group identifier (Group ID) is used to identify terminal device groups, and each terminal device group corresponds to a respective group identifier. For example, Group ID #1 is used to identify the first terminal device group #1, and the first terminal device #1 belongs to the first terminal device group #1. Group ID #2 is used to identify the second terminal device group.

[0096] Group network slice assistance information (Group S-NSSAI) is for identifying a slice corresponding to a terminal device group. For ease of explanation, the group network slice assistance information is also referred to as a group slice identifier. Network slices corresponding to at least one terminal device in a terminal device group are associated by using the group slice identifier. For example, Group S-NSSAI#1 is for identifying a slice identifier corresponding to a first terminal device group. In other words, Group S-NSSAI#1 identifies a slice in the first terminal device group.

[0097] The first indication information indicates that the terminal device group has a corresponding QoS parameter set. Optionally, the first indication information further includes address information of a DN-AAA server, and the first indication information indicates obtaining, from an authentication server (e.g., the DN-AAA server), a quality of service QoS parameter set to be applied to the terminal device group.

[0098] The QoS parameter set is a QoS parameter set corresponding to a terminal device group and includes at least one QoS parameter that is applied to the terminal device group. The QoS parameter set is a QoS parameter at a group granularity.

[0099] For example, if the QoS parameter set corresponding to a terminal device group includes QoS parameter #1, then QoS parameter #1 is applied to the PDU session corresponding to one of the terminal devices in the terminal device group.

[0100] In another example, the QoS parameter set corresponding to the terminal device group includes QoS parameter #2, where both terminal device #1 and terminal device #2 belong to the terminal device group, and QoS parameter #2 is applied to terminal device #1 and terminal device #2.

[0101] The first parameter configuration request message further includes a group data network name (Group DNN), also referred to as a group data network identity or group DNN. The group DNN is for identifying the group data network name of a data network corresponding to a terminal device group, and PDU sessions corresponding to at least one terminal device in the terminal device group are associated by using the group DNN. For example, group DNN#1 is for identifying a data network corresponding to group ID#1 of a first terminal device group, and each terminal device in the first terminal device group belongs to the data network.

[0102] In a possible implementation, there is a correspondence between the group identifier, group data network identity, and group slice identifier of a terminal device group, for example, group identifier #1 corresponds to group data network identity #1 and group slice identifier #1.

[0103] S402: The NEF receives the first configuration request message and sends a second configuration request message to the UDM, which in turn receives the second configuration request message.

[0104] The second configuration request message is for transmitting the parameters carried in the first configuration request message, e.g., the parameters carried in the first configuration request message in step S401. For example, the second configuration request message is a Nnef_ParameterProvision_Create / Update / Delete request.

[0105] S403: The UDM determines whether to update a group identifier (Group ID) and group subscription data based on the received second configuration request message, where the group subscription data includes a group network slicing assistance information (group S-NSSAI) and first indication information. The first indication information is the first indication information carried in the second configuration request message, i.e., indicates that the terminal device group has a corresponding QoS parameter set. Optionally, the first indication information further includes address information of a DN-AAA server.

[0106] In one implementation, the UDM compares the information carried in the received second configuration request message with the locally stored information to determine whether the information stored in the UDM is updated. For example, the information carried in the second configuration request message includes at least one of the following data: a group identifier, a group slice identifier, and the first indication information.

[0107] When it is determined that the group identifier and group subscription data are updated, the UDM sends a first notification message to the SMF, in other words, executes step S407.

[0108] S404: The UDM sends a second configuration response message to the NEF in response to the second parameter configuration request message, where the second configuration response message is for feeding back the parameter configuration result of the second parameter configuration request message, i.e., parameter configuration success or failure, to the NEF. In this embodiment, the parameter configuration result is success.

[0109] S405: The NEF sends a first configuration response message to the AF in response to the first parameter configuration request message, where the first configuration response message is for feeding back the execution result of the first configuration request message to the AF.

[0110] S406: The UE establishes a PDU session.

[0111] The UE may access the network and initiate a session request, and the SMF may establish a corresponding data connection session, e.g., a PDU session, for the UE to ensure normal communication of user plane data.

[0112] To establish a PDU session, the UE generates a PDU session identifier, and initiates the PDU session establishment procedure requested by the UE by sending an NAS message containing a PDU session establishment request in an N1 SM container. The UE sends the PDU session identifier (PDU session ID), PDU session DNN, PDU session slice S-NSSAI, and PDU session request type corresponding to the PDU session establishment request. If the PDU session establishment request is a request to establish a new PDU session, the PDU session request type indicates "initial request." If an existing PDU session to be switched between 3GPP access and non-3GPP access, or a PDU session to be switched from an existing PDN connection in the EPC, is requested, the PDU session request type indicates "existing PDU session."

[0113] S407: The SMF receives a first notification message from the UDM.

[0114] The SMF receives a first notification message from the UDM, where the first notification message includes first indication information, and the first indication information indicates obtaining a quality of service QoS parameter set to be applied to the terminal device group from the authentication server.

[0115] The first notification message further includes a group DNN and a group S-NSSAI.

[0116] In one implementation, the SMF obtains the terminal device identifier from the AMF and sends the terminal device identifier to the UDM.

[0117] The UDM stores a subscription data packet of the terminal device and a group subscription data packet of the terminal device. The UDM determines a group identifier of a terminal device group to which the terminal device belongs based on the terminal device identifier, and then indexes a group DNN and a group S-NSSAI corresponding to the group identifier based on the group identifier.

[0118] When the UE establishes a PDU session, the SMF sends a get message to the UDM to acquire data information stored in the UDM. The UDM sends the indication information acquired in step S403 to the SMF in response to the message. In this way, the SMF acquires the indication information, which indicates that the QoS parameter set has been acquired. Specifically, the UDM sends a first notification message to the SMF, where the first notification message carries a group identifier and group subscription data. The group subscription data includes a group DNN, a group S-NSSAI, and the first indication information. For example, the first notification message is Nudm_SDM_get. It can be understood that when the UE establishes a PDU session, the SMF sends a subscribe message to the UDM, where the subscribe message is for subscribing to update information of the UDM.

[0119] When the UE establishes a corresponding PDU session, in the process of establishing the corresponding PDU session for the UE, the SMF sends a subscription message to the UDM. After the data information stored in the UDM is updated, the UDM sends the updated data information to the SMF in response to the subscription message. For example, the UDM sends a first notification message to the SMF, where the first notification message carries first indication information, a group slice identifier, and a group data network identity, and the first indication information indicates obtaining a QoS parameter set. Optionally, the indication information includes the address of the DN-AAA server. Specifically, the UDM sends a first notification message to the SMF, where the first notification message carries the group DNN, the group S-NSSAI, and the first indication information.

[0120] S408: The SMF determines that the data connection session of the terminal device is for internal communication of the terminal device group to which the terminal device belongs.

[0121] Based on the received group DNN and group S-NSSAI, the SMF determines that the slice identifier corresponding to the data connection session of the terminal device is the same as the group S-NSSAI, and the data network identity of the data connection session of the terminal device is the same as the group DNN of the terminal device. If the slice identifier corresponding to the data connection session of the terminal device is the same as the group slice identifier, it is determined that the PDU session of the UE is for internal communication of the terminal device group to which the terminal device belongs, and subsequent steps are triggered. If the slice identifier corresponding to the data connection session of the terminal device is different from the group slice identifier, it indicates that the PDU session of the terminal device is not for internal communication of the terminal device group to which the terminal device belongs.

[0122] In one implementation, the SMF determines that the PDU session of the UE is for internal communication of the terminal device group to which the UE belongs based on a first notification message from the UDM. The first notification message carries a group slice identifier and a group DNN. The SMF determines that the DNN and slice identifier (S-NSSAI) corresponding to the PDU session of the terminal device are the same as the group DNN and group slice identifier, respectively, and triggers step S409.

[0123] The first notification message further includes first indication information and a group identifier of the terminal device group, where the first indication information indicates obtaining the QoS parameter set. The first indication information further includes an address of the DN-AAA server. For example, the first notification message is an SDM_Notification. The SMF sends a first request message to the DN-AAA server based on the first indication information.

[0124] The DNN and slice identifier corresponding to the PDU session of the terminal device are obtained when the SMF establishes a PDU session for the UE, which is not limited in this specification of the present invention.

[0125] S409: The SMF sends a first request message to the authentication server. In response, the authentication server receives the first request message from the SMF. For example, the authentication server is a DN-AAA server.

[0126] The SMF sends a first request message to the DN-AAA server based on the indication information, where the first request message is to request to obtain a QoS parameter set.

[0127] The first request message includes at least one or a combination of the following group granularity parameters: a group identifier, a group slice identifier, and a group DNN. The first request message further includes second indication information, where the second indication information indicates obtaining a QoS parameter set. The first request message is a first authentication request message.

[0128] S410: The DN-AAA server sends a first response message to the SMF in response to the first request message. In response, the SMF receives the first response message from the DN-AAA server.

[0129] A mapping relationship between one of the following group granularity parameters and a QoS parameter set is preconfigured on the DN-AAA server, where the group granularity parameter includes a group identifier, a group slice identifier, or a group DNN. The DN-AAA server indexes a QoS parameter set corresponding to the group granularity parameter based on the group granularity parameter carried in the first request message to obtain a QoS parameter set corresponding to the terminal device group. The DN-AAA server sends a first response message to the SMF, where the first response message carries the QoS parameter set. In response, the SMF obtains a QoS parameter set corresponding to the terminal device group. In one implementation, the mapping relationship between the group DNN, the group slice identifier, and the QoS parameter set is preconfigured on the DN-AAA server. The DN-AAA server obtains the corresponding QoS parameter set based on the group slice identifier. For example, the group DNN and the group slice identifier are group DNN#1 and S-NSSAI#1, and the corresponding QoS parameter set is QoS parameter#1. The first request message carries the group DNN, the group slice identifier, and indication information. The DN-AAA server obtains a QoS parameter set corresponding to the group DNN and the group slice identifier based on the group DNN and the group slice identifier, and sends a first response message to the SMF in response to the first request message, where the first response message carries the QoS parameter set corresponding to the group DNN and the group slice identifier.

[0130] In another implementation, the mapping relationship between the group identifier and the QoS parameter set is pre-configured on the DN-AAA server. The DN-AAA server obtains the corresponding QoS parameter set based on the group identifier. For example, the group identifier is Group ID #1, and the corresponding QoS parameter set is QoS Parameter #1. The first request message carries the group identifier and indication information. The DN-AAA server obtains the QoS parameter set corresponding to the group identifier based on the group identifier, and sends a first response message to the SMF in response to the first request message, where the first response message carries the QoS parameter set corresponding to the group identifier.

[0131] The QoS parameter set includes QoS parameters that apply to a terminal device group, specifically, the QoS parameter set includes at least one of the following parameters: priority of session transmission packets, packet size, delay, maximum rate, guaranteed rate, packet error rate, periodicity, clock domain, packet arrival time, remaining time, or silence time.

[0132] The DN-AAA server configures corresponding QoS parameter sets for terminal device groups based on different service requirements. For example, in a factory workshop, the DN-AAA server configures the same bandwidth, the same packet loss rate, and the same packet transmission delay for all production devices in the workshop. In this scenario, all production devices in the workshop may be considered as a terminal device group, and the corresponding QoS parameter sets include bandwidth, packet loss rate, and packet transmission delay.

[0133] The DN-AAA server indexes a QoS parameter set corresponding to the group DNN and the group slice identifier based on the group DNN and the group slice identifier, and sends a first response message to the SMF in response to the first request message, where the first response message carries the QoS parameter set.

[0134] The first response message is a first authentication response message, for example, a response message for secondary authentication.

[0135] When a first terminal device in a terminal device group establishes a PDU session, the SMF performs steps S409 and S410 to obtain a group DNN, a group slice identifier, and a QoS parameter set. The SMF stores the group DNN, the group slice identifier, and the QoS parameter set. In this way, when another terminal device in the terminal device group establishes a PDU session, the other terminal device may locally obtain the QoS parameter set from the SMF without requesting to obtain the QoS parameter set from the DN-AAA server, in order to further reduce signaling exchanges.

[0136] S411: The SMF sends a second request message to the PCF, where the second request message includes a QoS parameter set.

[0137] In response, the PCF receives a second request message from the SMF, thus obtaining the QoS parameter set.

[0138] In a possible implementation, the second request message is a message for invoking an SM policy association service.

[0139] S412: The PCF obtains a corresponding policy control rule set based on the QoS parameter set, where the policy control rule set includes at least one policy control rule.

[0140] The PCF stores a table of mapping relationships between QoS parameter sets and policy control rule sets. The PCF queries the table of mapping relationships by using the QoS parameter sets to obtain corresponding control policy rules, also referred to as PCC rules. Table 1 is a table of mapping relationships between QoS parameter sets and policy control rule sets according to this embodiment of the present application. Table 1: Mapping relationship between QoS parameter sets and policy control rule sets [Table 1] It can be understood that Table 1 only provides an example table of mapping relationships.

[0141] In one example, the PCC rule includes one or a combination of the following parameters: 5G quality identity (5QI), assign and retain priorities (ARP), guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), maximum packet loss rate (MPLR), and reflective QoS attribute (RQA).

[0142] S413: The PCF sends a second response message to the SMF in response to the second request message, where the second response message includes a policy control rule set.

[0143] In response, the SMF receives a second response message including the policy control rule set from the PCF and obtains the policy control rule set.

[0144] S414: The SMF applies the policy control rule set to the data connection session of the terminal device.

[0145] In one implementation, the SMF binds a policy control rule set to at least one QoS flow in a data connection session, in other words, a PCC rule is associated with a QoS flow in a PDU session.

[0146] Specifically, the SMF binds the PCC rules to the QoS flows in the aforementioned PDU session.

[0147] It can be understood that one PDU session can correspond to multiple QoS flows and multiple PCC rules can be associated with one QoS flow.

[0148] When the PCF provides a PCC rule, the SMF determines whether the QoS parameters of the QoS flow are the same as the QoS parameters in the PCC rule. If no such QoS flow exists, the SMF determines the QoS parameters of the new QoS flow by using the parameters in the PCC rule and establishes a new QoS flow based on the QoS parameters. In this case, the PCC rule is bound to the new QoS flow. If a QoS flow with the same QoS parameters exists, the SMF maps the PCC rule to the existing QoS flow based on the QoS parameters and service requirements.

[0149] The SMF binds PCC rules to QoS flows in data connection sessions based on QoS and service requirements. For each PCC rule bound to a QoS flow, if the PCC rule is used, the SMF generates a QoS rule based on the PCC rule and provides the QoS rule along with additional operations of the terminal device.

[0150] The QoS rule includes a QFI, a data packet filter set, and a priority associated with the QoS flow. The QoS rule also includes a QoS rule identifier, which is unique within a PDU session and is generated by the SMF.

[0151] It should be noted that "binding" is merely an example description and can be replaced with any other possible description, such as "mapping" or "corresponding", which is not specifically limited herein.

[0152] 6 is a schematic flowchart of another resource configuration management method according to an embodiment of the present application. The difference from the resource configuration management method shown in FIG. 5A and FIG. 5B is that in the method according to this embodiment, the first configuration request message includes a QoS parameter set.

[0153] S501: An application function network element AF sends a first configuration request message to a network function publishing network element NEF. The difference from the embodiment shown in Figure 4 is that the first configuration request message includes the following related parameters: a group identifier (Group ID), a group DNN, a group network slice assistance information (Group S-NSSAI), and a QoS parameter set.

[0154] The QoS parameter set is a QoS parameter set corresponding to the group identifier or group DNN and group network slice support information. For the function of the first configuration request message, please refer to the description of step S401. The details will not be described again in this specification.

[0155] S502: The NEF receives the first configuration request message and sends a second configuration request message to the UDM, and in response, the UDM receives the second configuration request message.

[0156] The difference between this step and S402 is that the second configuration request message includes a QoS parameter set.

[0157] S503: The UDM determines whether to update the group identifier, group DNN, group network slice support information, and QoS parameter set based on the received second configuration request message.

[0158] For details of this step, please refer to the description of S403. To avoid repetition, the details will not be described again here.

[0159] S504: The UDM sends a second configuration response message to the NEF in response to the second parameter configuration request message, where the second configuration response message is for feeding back the parameter configuration result of the second parameter configuration request message to the NEF.

[0160] S505: The NEF sends a first configuration response message to the AF in response to the first parameter configuration request message, where the first configuration response message is for feeding back the execution result of the first configuration request message to the AF.

[0161] S506: The UE establishes a PDU session.

[0162] For a specific implementation of this step, please refer to step S406, and the details will not be described again here.

[0163] S507: The SMF receives a QoS parameter set from the UDM.

[0164] The SMF receives a first notification message from the UDM, where the first notification message includes a group DNN, a group S-NSSAI, and a QoS parameter set.

[0165] When the UE establishes a PDU session, the SMF sends a get message to the UDM to get the data information stored in the UDM. The UDM sends the QoS parameter set obtained in step S503 to the SMF in response to the message, so that the SMF obtains the QoS parameter set. Specifically, the UDM sends a first notification message to the SMF, where the first notification message carries the group DNN, group S-NSSAI, and the QoS parameter set. For example, the first notification message is SMD_get.

[0166] The UE establishes a corresponding PDU session. In the process of establishing a corresponding PDU session for the UE, the SMF sends a subscribe message to the UDM. After the UDM determines to update the group identifier and the QoS parameter set, the UDM sends the updated group identifier and the updated QoS parameter set to the SMF in response to the subscribe message. Specifically, the UDM sends a first notification message to the SMF, where the first notification message carries the group DNN, the group S-NSSAI, and the QoS parameter set.

[0167] S508: The SMF determines that the data connection session of the terminal device is for internal communication of the terminal device group to which the terminal device belongs.

[0168] The SMF determines, based on the received group slice identifier, that the DNN and slice identifier corresponding to the data connection session of the terminal device are the same as the group DNN and group slice identifier. If the DNN and slice identifier corresponding to the data connection session of the terminal device are the same as the group DNN and group slice identifier, it is determined that the PDU session of the UE is for internal communication of the terminal device group of the UE, and subsequent steps are triggered. If the DNN and slice identifier corresponding to the data connection session of the terminal device are different from the DNN and group slice identifier, it indicates that the PDU session of the UE is not for internal communication of the terminal device group of the UE.

[0169] In one implementation, the SMF determines that the PDU session of the terminal device is for internal communication of the terminal device group to which the terminal device belongs based on a first notification message from the UDM. The first notification message carries a group DNN. The SMF determines that the DNN and slice identifier (S-NSSAI) corresponding to the PDU session of the terminal device are the same as the group DNN and group S-NSSAI, and triggers step S509.

[0170] S509: The SMF sends a request message #1 to the PCF, where the request message #1 includes a QoS parameter set. In response, the PCF receives the request message #1 from the SMF.

[0171] For the specific implementation of this step, please refer to S411, and the details will not be described again here.

[0172] S510: The PCF obtains a corresponding policy control rule set based on the QoS parameter set.

[0173] For the specific implementation of this step, please refer to S412, and the details will not be described again here.

[0174] S511: The PCF sends a response message #1 to the SMF in response to the request message #1, where the response message #1 includes a policy control rule set. In response, the SMF receives the response message #1 from the PCF.

[0175] For the specific implementation of this step, please refer to S413, and the details will not be described again here.

[0176] S512: The SMF applies the policy control rule set to the data connection session.

[0177] For the specific implementation of this step, please refer to S414, and the details will not be described again here.

[0178] FIG. 7 is a schematic flowchart of another resource configuration management method according to an embodiment of the present application.

[0179] Step S601: The application function network element AF sends a first configuration request message to the network function publishing network element NEF, where the first configuration request message includes a group identifier (Group ID), a group DNN, a slice identifier (Group S-NSSAI), and a QoS policy parameter set.

[0180] For the specific implementation of this step, please refer to S501, and the details will not be described again in this specification.

[0181] Step S602: The NEF sends a second configuration request message to the UDM. In response, the UDM receives the second configuration request message. The second configuration request message includes an identifier (Group ID), a group DNN, a group slice identifier (Group S-NSSAI), and a QoS policy parameter set.

[0182] For the specific implementation of this step, please refer to S502, and the details will not be described again in this specification.

[0183] S603: The UDM sends a DM_Query message to the UDR, which responds by returning a message to the UDM.

[0184] In a specific implementation, the UDM receives the second configuration request message and sends a DM_Query message to the UDR. For example, the DM_Query message includes a group identifier and group subscription data, and the group subscription data includes a group identifier, a group slice identifier, and / or a group DNN. In one implementation, the UDR stores subscription data of each terminal device in a terminal device group and / or subscription data of a terminal device group. The UDR receives the DM_Query message and returns the queried subscription data corresponding to each terminal device and / or the subscription data of the terminal device group to the UDM based on the identifier of the terminal device. Thus, the UDM obtains the group subscription data corresponding to the terminal device group. Specifically, the UDR queries the group subscription data corresponding to the group identifier based on the group identifier (Group ID).

[0185] For example, when a new 5G VN group is created, the UDM must assign a unique group ID to the 5G VN group and include the newly assigned group ID in the Nudr_DM_creation request message (first configuration request message). If the 5G VN group member list or 5G VN group data changes, the UDM updates the group subscription data based on the request of the AF / NEF. The group subscription data includes one or a combination of the following parameters: group identifier, group slice identifier, or group DNN.

[0186] S604: The UDM updates the subscription data and the subscription data of the terminal device group.

[0187] S605: The UDM sends a DM_Update message to the UDR, which responds by returning a message to the UDM.

[0188] In one implementation, the DM_Update message carries a group identifier, a group DNN, a group slice identifier, and a QoS parameter set.

[0189] The DM_Update service is invoked to update the group identifier, group DNN / group S-NSSAI, and QoS parameter set of a terminal device group in the UDR.

[0190] S606: The UDM sends a second configuration response message to the NEF in response to the second parameter configuration request message, where the second configuration response message is for feeding back the parameter configuration result of the second parameter configuration request message to the NEF.

[0191] S607: The NEF sends a first configuration response message to the AF in response to the first parameter configuration request message, where the first configuration response message is for feeding back the execution result of the first configuration request message to the AF.

[0192] S608: The UDR sends a first message to the PCF, where the first message includes a QoS parameter set and a group slice identifier.

[0193] In one implementation, in step 605, the UDR obtains the updated group slice identifier and QoS parameter set and sends the group slice identifier and QoS parameter set to the PCF by using a first message. Optionally, the PCF stores the received QoS parameter set. It can be seen that in response to the first message, the PCF sends a response message #2 to the UDR to notify the UDR of the request result.

[0194] S609: The PCF sends a second message to the SMF, where the second message includes a group slice identifier or a group DNN. In response, the SMF receives a second message, where the second message includes a group slice identifier or a group DNN.

[0195] For example, the second message is an SM policy association.

[0196] S610: The SMF determines that the data connection session of the terminal device is for internal communication of the terminal device group to which the terminal device belongs.

[0197] For a specific implementation in which the SMF determines that the data connection session of the terminal device is for internal communication of the terminal device group to which the terminal device belongs, see step S408. Details will not be described again in this specification.

[0198] S611: The SMF sends a third message to the PCF, where the third message includes a group slice identifier. In response, the PCF receives the third message and obtains the group slice identifier.

[0199] Optionally, the third message further includes a QoS parameter set.

[0200] S612: The PCF obtains a corresponding policy control rule set based on the QoS parameter set.

[0201] For a specific implementation of step S612, please refer to step S412, and the details will not be described again in this specification.

[0202] S613: The PCF sends a response message #1 to the SMF, where the response message #1 includes a policy control rule set.

[0203] S614: The SMF applies the policy control rule set to the data connection session.

[0204] For the implementation of S611 and S612, please refer to steps 413 and 414. The details will not be described again in this specification.

[0205] The above describes in detail the communication resource management method in the embodiment of the present application with reference to Figures 3 to 6. The following describes in detail the communication apparatus and related devices in the embodiment of the present application with reference to Figures 7 to 10. It should be understood that the communication apparatus and related devices shown in Figures 7 to 10 can implement one or more steps in the method procedures shown in Figures 3 to 6. To avoid repetition, the details will not be described again in this specification.

[0206] Figure 8 illustrates an embodiment of a communications device configured to implement the method performed by the SMF in the embodiments illustrated in Figures 3 to 7. The communications device 700 includes a transceiver unit 710 and a processing unit 720. The transceiver unit 710 is configured to obtain a quality of service (QoS) parameter set from a first network element. The processing unit 720 is configured to: determine that a data connection session of the terminal device is for internal communication of a terminal device group to which the terminal device belongs; obtain a corresponding policy control rule set based on the QoS parameter set, where the policy control rule set includes at least one policy control rule; and apply the policy control rule to the data connection session.

[0207] In one implementation, the relevant functions implemented by the units in FIG. 8 may be implemented by using a transceiver, a processor, and a memory.

[0208] 9 is a diagram of a session management function network element according to an embodiment of the present application. The session management function network element may be a device (e.g., a chip) capable of performing the communication resource management method provided in the embodiment of the present application. The session management function network element may include a transceiver 801, at least one processor 802, and a memory 803. The transceiver 801, the processor 802, and the memory 803 may be connected to each other through one or more communication buses, or may be connected to each other in another manner.

[0209] The transceiver 801 may be configured to transmit data or receive data. It may be understood that the transceiver 801 is generic and may include a receiver and a transmitter.

[0210] The processor 802 may be configured to process data for the session management function network element. The processor 802 may include one or more processors. For example, the processor 802 may be one or more central processing units (CPUs), one or more network processors (NPs), one or more hardware chips, or any combination thereof. If the processor 802 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0211] The memory 803 is configured to store program code and the like. The memory 803 may include volatile memory, such as random access memory (RAM). The memory 803 may further include non-volatile memory, such as read-only memory (ROM), flash memory, a hard disk drive (HDD), or a solid-state drive (SSD). The memory 803 may also include a combination of the aforementioned types of memory.

[0212] The processor 802 and the memory 803 may be coupled through an interface or may be integrated together, which is not limited in this embodiment.

[0213] The transceiver 801 and the processor 802 may be configured to perform the communication resource management method provided in the embodiments of the present application. A specific implementation is as follows.

[0214] The transceiver 801 is configured to obtain a quality of service QoS parameter set from a first network element, where the QoS parameter set includes at least one QoS parameter to be applied to a terminal device group.

[0215] The processor 802 is configured to determine that a data connection session of the terminal device is for internal communication of a terminal device group to which the terminal device belongs; obtain a corresponding policy control rule set based on the QoS parameter set, where the policy control rule set includes at least one policy control rule; and apply the policy control rule to the data connection session.

[0216] 10 is a diagram of another communication device according to an embodiment of the present application. The communication device shown in FIG. 10 is configured to implement the method performed by the UDM in the aforementioned embodiment. The communication device 900 includes a transceiver unit 910 and a processing unit 920. The processing unit 920 obtains information related to a QoS parameter set by using the transceiver unit 910, where the QoS parameter set includes at least one QoS parameter shared by a group of terminal devices. The processing unit 920 transmits the information related to the QoS parameter set to a session management network element by using the transceiver unit 910, where the information related to the QoS parameter set is the QoS parameter set or indication information indicating the QoS parameter set.

[0217] In one implementation, the relevant functionality implemented by the units in FIG. 10 may be implemented using a transceiver, a processor, and a memory.

[0218] 11 is a diagram of a UDM network element according to an embodiment of the present application. The session management function network element may be a device (e.g., a chip) capable of executing the communication resource management method provided in the embodiment of the present application. The session management function network element may include a transceiver 1001, at least one processor 1002, and a memory 1003. The transceiver 1001, the processor 1002, and the memory 1003 may be connected to each other through one or more communication buses, or may be connected to each other in another manner.

[0219] The transceiver 1001 may be configured to transmit data or receive data. It may be understood that the transceiver 1001 is generic and may include a receiver and a transmitter.

[0220] The processor 1002 may be configured to process data for the UDM network element. The processor 1002 may include one or more processors. For example, the processor 1002 may be one or more central processing units (CPUs), one or more network processors (NPs), one or more hardware chips, or any combination thereof. If the processor 1002 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0221] The memory 1003 is configured to store program code and the like. The memory 1003 may include volatile memory, such as random access memory (RAM). The memory 1003 may further include non-volatile memory, such as read-only memory (ROM), flash memory, a hard disk drive (HDD), or a solid-state drive (SSD). The memory 1003 may also include a combination of the aforementioned types of memory.

[0222] The processor 1002 and the memory 1003 may be coupled through an interface or may be integrated together, which is not limited in this embodiment.

[0223] The transceiver 1001 and the processor 1002 may be configured to perform the communication resource management method provided in the embodiments of the present application. A specific implementation is as follows.

[0224] The transceiver 1001 is configured to obtain information related to a QoS parameter set, where the QoS parameter set includes at least one QoS parameter shared by a group of terminal devices; and transmit the information related to the QoS parameter set to a session management network element, where the information related to the QoS parameter set is the QoS parameter set or indication information indicating the QoS parameter set.

[0225] The processor 1002 may execute program code stored in the memory 1003 to perform the following operations: when the information related to the QoS parameter set is updated, the processor 1002 is configured to trigger transmission of the information related to the QoS parameter set to the session management network element.

[0226] It should be noted that the structure of the communications device 900 shown in Figure 10 does not constitute a limitation on the communications device. An actual communications device may include more or fewer components than those shown in the figure, combine some components, or have a different component arrangement.

[0227] In addition, for the technical effects of the communication device 900, please refer to the technical effects of the communication method in the above method embodiments, and the details will not be described again in this specification.

[0228] An embodiment of the present application provides a communication system, which includes the access and mobility management network element, the radio access network device, and the session management network element in the above-mentioned embodiment.

[0229] It should be understood that the processor in embodiments of the present application may be a central processing unit (CPU), or the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or the like. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like.

[0230] It will be understood that the memory in the embodiments of the present application may be volatile memory or nonvolatile memory, or may include volatile memory and nonvolatile memory. Nonvolatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) may be used, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM).

[0231] All or some of the above-described embodiments may be implemented using software, hardware (e.g., circuits), firmware, or any combination thereof. When software is used to implement an embodiment, the above-described embodiment may be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded and executed on a computer, they generate all or part of the procedures or functions of the embodiments of the present application. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or another programmable device. The computer instructions may be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired (e.g., infrared, radio, microwave, or the like) manner. The computer-readable storage medium may be any available medium accessible by a computer or a data storage device, such as a server or data center, that integrates one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk drive, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium, which may be a solid state drive.

[0232] It should be understood that the term "and / or" in this specification simply describes an association relationship between associated objects and represents that three relationships may exist. For example, A and / or B may represent three cases: a case where only A exists, a case where both A and B exist, and a case where only B exists. A and B may be singular or plural. In addition, the character " / " in this specification usually indicates an "or" relationship between associated objects, but may also indicate an "and / or" relationship. Please refer to the context for further understanding.

[0233] As used herein, "at least one" means one or more, and "multiple" means two or more. "At least one of the following items (moieties)" or similar expressions refers to any combination of these items, including a single item (moiety) or any combination of multiple items (moieties). For example, at least one of a, b, or c can refer to a, b, c, ab, ac, bc, or abc, where a, b, and c can be singular or plural.

[0234] It should be understood that the sequence numbers of the above processes do not mean the execution sequence in various embodiments of the present application, and the execution sequence of the processes should be determined based on the functions and internal logic of the processes, and should not be construed as any limitation on the implementation process of the embodiments of the present application.

[0235] Those skilled in the art may recognize that, in combination with the examples described in the embodiments disclosed herein, the units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and the design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but this implementation should not be considered as going beyond the scope of the present application.

[0236] It can be clearly understood by those skilled in the art that for the purpose of convenient and simple description, the detailed operation processes of the aforementioned systems, devices and units should be referred to the corresponding processes in the aforementioned method embodiments, and the details will not be described again in this specification.

[0237] In some embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the described device embodiment is merely an example. For example, the division into multiple units is merely a logical division of functionality, and other divisions may occur in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented. In addition, the shown or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. Indirect couplings or communication connections between devices or units may be implemented in electronic, mechanical, or other forms.

[0238] The units described as separate parts may or may not be physically separate, and the parts shown as units may or may not be physical units, in other words, may be located in one location or distributed over multiple network units. Some or all of the multiple units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.

[0239] Additionally, the functional units in the embodiments of the present application may be integrated into one processing unit, and each of the units may exist physically alone, or two or more units may be integrated into one unit.

[0240] When functions are implemented in the form of software functional units and sold or used as independent products, these functions may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application may essentially be implemented in the form of a software product, or a portion of the technical solutions may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or some of the steps of the methods described in the embodiments of the present application. The storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0241] The above description is merely a specific implementation of the present application and is not intended to limit the scope of protection of the present application. Any modifications or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed in the present application shall be included in the scope of protection of the present application. Therefore, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. 1. A method for managing communications resources, the method comprising: receiving a group identifier of a terminal device group to which a first terminal device belongs, and a data network identity and network slicing support information of a data connection session of the first terminal device; receiving, from a data management network element, a data network identity and network slice support information corresponding to the group identifier, and first indication information, wherein the first indication information indicates obtaining, from an authentication server, a quality of service QoS parameter set to be applied to the terminal device group, the QoS parameter set including at least one QoS parameter to be applied to the terminal device group; determining that the data network identity and the network slice support information of the data connection session of the first terminal device are the same as the data network identity and the network slice support information of the terminal device group, respectively, and sending a first authentication request message to the authentication server based on the first indication information, wherein the first authentication request message includes the data network identity and the network slice support information of the terminal device group; obtaining a first authentication response message from the authentication server, wherein the first authentication response message includes the QoS parameter set for the terminal device group; obtaining a policy control rule set based on the QoS parameter set, wherein the policy control rule set includes at least one policy control rule; and Binding the policy control rule set to a QoS flow of the data connection session of the first terminal device. A method comprising:

2. The method of claim 1 , wherein the first indication further comprises an address of the authentication server.

3. The data network identity and the network slice support information of the data connection session of the first terminal device are received from the first terminal device; The method of claim 1 , wherein the group identifier of the terminal device group is received from the data management network element.

4. The step of obtaining a policy control rule set based on the QoS parameter set includes: sending a second request message to a policy control function entity, wherein the second request message includes the QoS parameter set; and receiving a second response message sent by the policy control function entity, wherein the second response message includes the policy control rule set; The method according to any one of claims 1 to 3, comprising:

5. 5. The method according to claim 1, wherein the QoS parameter is at least one of the following parameters: priority of session transmission packets, packet size, delay, maximum rate, guaranteed rate, packet error rate, periodicity, clock domain, packet arrival time, remaining time, or quiet time.

6. 1. A method for managing communications resources, the method comprising: receiving a configuration request message sent by an application function network element, wherein the configuration request message includes a group identifier of a terminal device group to which a first terminal device belongs, a data network identity and network slicing support information of the terminal device group, and first indication information, the first indication information indicating obtaining a quality of service QoS parameter set to be applied to the terminal device group from an authentication server, the QoS parameter set including at least one QoS parameter to be applied to the terminal device group; receiving the group identifier sent by a session management network element; and indexing the data network identity and the network slice support information of the terminal device group based on the group identifier, and transmitting the data network identity and the network slice support information of the terminal device group and the first indication information to the session management network element. A method comprising:

7. The method of claim 6, wherein the first indication information further includes an address of the authentication server.

8. 8. The method of claim 6 or 7, wherein the QoS parameter is at least one of the following parameters: session transmission packet priority, packet size, delay, maximum rate, guaranteed rate, packet error rate, periodicity, clock domain, packet arrival time, remaining time, or quiet time.

9. 1. A method for managing communications resources, comprising: receiving, by a data management function entity, a configuration request message sent by an application function network element, wherein the configuration request message includes a group identifier of a terminal device group to which a first terminal device belongs, a data network identity and network slicing support information of the terminal device group, and first indication information, the first indication information indicating obtaining, from an authentication server, a quality of service QoS parameter set to be applied to the terminal device group, the QoS parameter set including at least one QoS parameter to be applied to the terminal device group; receiving, by the data management function entity, the group identifier sent by a session management network element; indexing, by the data management function entity, the data network identity and the network slice support information of the terminal device group based on the group identifier, and sending the data network identity and the network slice support information of the terminal device group and the first indication information to a session management function entity; receiving, by the session management function entity, the data network identity and the network slice support information of the terminal device group, and first indication information from the data management function entity; determining, by the session management function entity, that the data network identity and network slice support information of the data connection session of the first terminal device are the same as the data network identity and the network slice support information of the terminal device group, respectively; and sending a first authentication request message to the authentication server based on the first indication information, wherein the first authentication request message includes the data network identity and the network slice support information of the terminal device group; obtaining, by the session management function entity, a first authentication response message from the authentication server, wherein the first authentication response message includes the QoS parameter set of the terminal device group; obtaining, by the session management function entity, a policy control rule set based on the QoS parameter set, wherein the policy control rule set includes at least one policy control rule; and binding, by the session management function entity, the policy control rule set to a QoS flow of the data connection session of the first terminal device. A method comprising:

10. The method of claim 9 , wherein the first indication further comprises an address of the authentication server.

11. The method of claim 9 , wherein the session management function entity receives, from the first terminal device, the data network identity and the network slice support information for the data connection session of the first terminal device.

12. The step of obtaining, by the session management function entity, a policy control rule set based on the QoS parameter set includes: sending a second request message to a policy control function entity, wherein the second request message includes the QoS parameter set; and receiving a second response message sent by the policy control function entity, wherein the second response message includes the policy control rule set; 10. The method of claim 9, comprising:

13. 10. The method of claim 9, wherein the QoS parameter is at least one of the following parameters: session transmission packet priority, packet size, delay, maximum rate, guaranteed rate, packet error rate, periodicity, clock domain, packet arrival time, remaining time, or quiet time.

14. A communication device, said device comprising a module configured to perform the method according to any one of claims 1 to 5.

15. A communication device, said device comprising a module configured to perform the method according to any one of claims 6 to 8.

16. 10. A communication device, the communication device comprising a processor, the processor configured to execute instructions stored in a memory that enable the communication device to perform a communication method according to any one of claims 1 to 5 or claims 6 to 8.

17. A communication system, said system comprising a communication device according to claim 14 or 15.

18. 1. A computer-readable storage medium, the computer-readable storage medium comprising a computer program or instructions; when the computer program or the instructions are executed on a computer, the computer is enabled to perform the communication method according to any one of claims 1 to 5 or claims 6 and 7.

Images