CN117858084A - Management method and device for group control charging pile of group management - Google Patents

Abstract

In the method, an AMF network element can trigger a main authentication flow of a head charging pile only when the charging pile is the head charging pile in a charging pile cluster under the condition that the charging pile in the charging pile cluster is requested to be registered to a network, and if the charging pile is a non-head charging pile managed by the head charging pile, the AMF network element can directly register the non-head charging pile to the network under the condition that the main authentication flow of the non-head charging pile is not triggered. That is, the network performs the main authentication procedure only for the head charging stake, thereby reducing the number of times of performing the main authentication procedure in the group registration scenario, thereby being capable of improving the registration efficiency and reducing the overhead of the network.

Description

Management method and device for group control charging pile of group management

Technical Field

The present disclosure relates to the field of communications, and in particular, to a method and an apparatus for managing a group control charging pile.

Background

Currently, the third generation partnership project (non-3rd generation partnership project,non-3 GPP) defines a primary authentication flow for fifth generation (5th generation,5G) mobile communications. Specifically, after the terminal initiates registration with the network, the access and mobility management function (access and mobility management function, AMF) network element triggers a main authentication procedure of the terminal, where the terminal can authenticate the network, and the network also authenticates the terminal. If both authenticate each other, the AMF network element registers the terminal to the network.

However, for a group scenario, for example, a plurality of charging piles are respectively used as terminals to form a group, how to realize the main authentication of the group is a hot problem of current research.

Disclosure of Invention

The embodiment of the application provides a management method and device for a group control charging pile, so as to realize main authentication of a group.

In order to achieve the above purpose, the present application adopts the following technical scheme:

in a first aspect, a management method of a group management and group control charging pile is provided, and the method is applied to an AMF network element, and includes: under the condition that the first charging pile requests to register to a network where the AMF network element is located, the AMF network element determines that the first charging pile is a head charging pile in the charging pile cluster; the AMF network element triggers a main authentication flow of the first charging pile, wherein if the non-head charging pile in the charging pile cluster requests to register to the network, the AMF network element registers the non-head charging pile in the charging pile cluster to the network under the condition that the main authentication flow of the non-head charging pile in the charging pile cluster is not triggered, and the head charging pile in the charging pile cluster can authenticate the non-head charging pile in the charging pile cluster; and under the condition that the primary authentication of the first charging pile passes, the AMF network element registers the first charging pile to the network.

In one possible design, the AMF network element determines that the first charging pile is a head charging pile in the charging pile cluster, including: the AMF network element receives a first registration request from a first charging pile, wherein the first registration request is used for indicating the first charging pile to request to register to a network; the AMF network element acquires the subscription data of the first charging pile from the UDM network element according to the first registration request; and the AMF network element determines that the first charging pile is the head charging pile in the charging pile cluster according to the information in the subscription data of the first charging pile, which is used for indicating that the first charging pile is the head charging pile in the charging pile cluster.

Optionally, the AMF network element triggers a primary authentication procedure of the first charging stake, including: the AMF network element sends a first authentication request to the AUSF network element, wherein the first authentication request is used for requesting the AUSF network element to perform main authentication on the first charging pile, and the main authentication of the first charging pile comprises a first charging pile authentication network and a network authentication first charging pile; the AMF network element receives a first authentication response of the AUSF network element, wherein the first authentication response is used for indicating whether the primary authentication of the first charging pile passes or not.

Further, the AMF network element registers the first charging pile to the network, including: the AMF network element sends a first registration acceptance to the first charging pile, wherein the first registration acceptance is used for indicating that the first charging pile is successfully registered to the network.

In one possible design, after the AMF network element registers the first charging stake to the network, the method further includes: under the condition that the second charging pile requests to register to the network, the AMF network element determines that the second charging pile is a non-head charging pile in the charging pile cluster; the AMF network element registers the second charging pile to the network under the condition that the main authentication flow of the second charging pile is not triggered.

Optionally, the AMF network element determines that the second charging pile is a non-head charging pile in the charging pile cluster, including: the AMF network element receives a second registration request from a second charging pile, wherein the second registration request is used for indicating the second charging pile to request to register to the network; the AMF network element acquires the subscription data of the second charging pile from the UDM network element according to the second registration request; and the AMF network element determines that the second charging pile is the non-head charging pile in the charging pile cluster according to the information in the subscription data of the second charging pile, which is used for indicating that the first charging pile is the non-head charging pile in the charging pile cluster.

Further, the AMF network element registers the second charging stake to the network without triggering a primary authentication procedure of the second charging stake, including: if the subscription data of the second charging pile comprises information for indicating that the second charging pile is controlled by the first charging pile, the AMF network element determines whether the first charging pile is registered to the network; and under the condition that the first charging pile is registered to the network, the AMF network element determines that an authentication request for the second charging pile is not sent to the AUSF network element, and the AMF network element sends a second registration acceptance to the second charging pile, wherein the second registration acceptance is used for indicating that the second charging pile is successfully registered to the network.

Further, the AMF network element registers the second charging stake to the network without triggering a primary authentication procedure of the second charging stake, including: if the subscription data of the second charging pile comprises information for indicating that the second charging pile is controlled by the third charging pile, the AMF network element determines whether the third charging pile is registered to the network; under the condition that the third charging pile is not registered to the network, the AMF network element determines to send a second authentication request to the AUSF network element, wherein the second authentication request is used for requesting the AUSF network element to initiate authentication of the second charging pile to the network, and the authentication of the network to the second charging pile is not initiated; the AMF network element receives a second authentication response of the AUSF network element, wherein the second authentication response is used for indicating whether a second charging pile authentication network passes or not; and under the condition that the second charging pile authentication network passes, the AMF network element sends a second registration acceptance to the second charging pile, wherein the second registration acceptance is used for indicating that the second charging pile is successfully registered in the network.

Further, after the AMF network element sends the second registration acceptance to the second charging stake, the method further includes the AMF network element determining that the second charging stake is in a service limited state before the third charging stake is registered with the network.

In a second aspect, a management system of a group management and group control charging pile is provided, the system including an AMF network element, the system being configured to: under the condition that the first charging pile requests to register to a network where the AMF network element is located, the AMF network element determines that the first charging pile is a head charging pile in the charging pile cluster; the AMF network element triggers a main authentication flow of the first charging pile, wherein if the non-head charging pile in the charging pile cluster requests to register to the network, the AMF network element registers the non-head charging pile in the charging pile cluster to the network under the condition that the main authentication flow of the non-head charging pile in the charging pile cluster is not triggered, and the head charging pile in the charging pile cluster can authenticate the non-head charging pile in the charging pile cluster; and under the condition that the primary authentication of the first charging pile passes, the AMF network element registers the first charging pile to the network.

In one possible design, the system is configured to: the AMF network element receives a first registration request from a first charging pile, wherein the first registration request is used for indicating the first charging pile to request to register to a network; the AMF network element acquires the subscription data of the first charging pile from the UDM network element according to the first registration request; and the AMF network element determines that the first charging pile is the head charging pile in the charging pile cluster according to the information in the subscription data of the first charging pile, which is used for indicating that the first charging pile is the head charging pile in the charging pile cluster.

Optionally, the system is configured to: the AMF network element sends a first authentication request to the AUSF network element, wherein the first authentication request is used for requesting the AUSF network element to perform main authentication on the first charging pile, and the main authentication of the first charging pile comprises a first charging pile authentication network and a network authentication first charging pile; the AMF network element receives a first authentication response of the AUSF network element, wherein the first authentication response is used for indicating whether the primary authentication of the first charging pile passes or not.

Further, the system is configured to: the AMF network element sends a first registration acceptance to the first charging pile, wherein the first registration acceptance is used for indicating that the first charging pile is successfully registered to the network.

In one possible design, the system is configured to: after the AMF network element registers the first charging pile to the network, under the condition that the second charging pile requests to register to the network, the AMF network element determines that the second charging pile is a non-head charging pile in the charging pile cluster; the AMF network element registers the second charging pile to the network under the condition that the main authentication flow of the second charging pile is not triggered.

Optionally, the system is configured to: the AMF network element receives a second registration request from a second charging pile, wherein the second registration request is used for indicating the second charging pile to request to register to the network; the AMF network element acquires the subscription data of the second charging pile from the UDM network element according to the second registration request; and the AMF network element determines that the second charging pile is the non-head charging pile in the charging pile cluster according to the information in the subscription data of the second charging pile, which is used for indicating that the first charging pile is the non-head charging pile in the charging pile cluster.

Further, the system is configured to: if the subscription data of the second charging pile comprises information for indicating that the second charging pile is controlled by the first charging pile, the AMF network element determines whether the first charging pile is registered to the network; and under the condition that the first charging pile is registered to the network, the AMF network element determines that an authentication request for the second charging pile is not sent to the AUSF network element, and the AMF network element sends a second registration acceptance to the second charging pile, wherein the second registration acceptance is used for indicating that the second charging pile is successfully registered to the network.

Further, the system is configured to: if the subscription data of the second charging pile comprises information for indicating that the second charging pile is controlled by the third charging pile, the AMF network element determines whether the third charging pile is registered to the network; under the condition that the third charging pile is not registered to the network, the AMF network element determines to send a second authentication request to the AUSF network element, wherein the second authentication request is used for requesting the AUSF network element to initiate authentication of the second charging pile to the network, and the authentication of the network to the second charging pile is not initiated; the AMF network element receives a second authentication response of the AUSF network element, wherein the second authentication response is used for indicating whether a second charging pile authentication network passes or not; and under the condition that the second charging pile authentication network passes, the AMF network element sends a second registration acceptance to the second charging pile, wherein the second registration acceptance is used for indicating that the second charging pile is successfully registered in the network.

Further, the system is configured to: after the AMF network element sends the second registration acceptance to the second charging stake, the AMF network element determines that the second charging stake is in a service limited state before the third charging stake is registered with the network.

In a third aspect, there is provided a communication apparatus comprising: a processor and a memory; the memory is for storing a computer program which, when executed by the processor, causes the communication device to perform the method of the first aspect.

In one possible design, the communication device according to the third aspect may further comprise a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be for use in a communication device according to the third aspect to communicate with other communication devices.

In an embodiment of the present application, the communication apparatus according to the third aspect may be the terminal or the network device according to the first aspect, or a chip (system) or other parts or components that may be disposed in the terminal or the network device, or an apparatus including the terminal or the network device.

In a fourth aspect, there is provided a computer-readable storage medium comprising: computer programs or instructions; the computer program or instructions, when run on a computer, cause the computer to perform the method of the first aspect.

In summary, the method and the system have the following technical effects:

when the charging pile is a head charging pile in the charging pile cluster, the AMF network element may trigger a main authentication procedure of the head charging pile, and if the charging pile is a non-head charging pile managed by the head charging pile, the AMF network element may directly register the non-head charging pile to the network without triggering the main authentication procedure of the non-head charging pile. That is, the network performs the main authentication procedure only for the head charging stake, thereby reducing the number of times of performing the main authentication procedure in the group registration scenario, thereby being capable of improving the registration efficiency and reducing the overhead of the network.

Drawings

FIG. 1 is a schematic diagram of a 5GS architecture;

fig. 2 is a schematic architecture diagram of a communication system according to an embodiment of the present application;

fig. 3 is a flow chart of a management method of a group management and group control charging pile according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

It is convenient to understand that technical terms related to the embodiments of the present application are first described below.

1. A 5G mobile communication system (5G system,5 gs) for short:

Fig. 1 is a schematic diagram of a 5GS architecture. As shown in fig. 1, 5GS includes: AN Access Network (AN) and a CN may further include: and (5) a terminal.

The terminals may be one or more, such as a first terminal, a second terminal, a third terminal, etc. The terminal may be a terminal having a transmitting/receiving function, or may be a chip or a chip system provided in the terminal. The terminal may also be referred to as a UE, an access terminal, a subscriber unit (subscriber unit), a subscriber station, a Mobile Station (MS), a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminals in embodiments of the present application may be mobile phones (mobile phones), cellular phones (cellular phones), smart phones (smart phones), tablet computers (Pad), wireless data cards, personal digital assistants (personal digital assistant, PDA), wireless modems (modem), handheld devices (handset), laptop computers (laptop computers), machine type communication (machine type communication, MTC) terminals, computers with wireless transceiving functions, virtual Reality (VR) terminals, augmented reality (augmented reality, AR) terminals, smart home devices (e.g., refrigerator, television, air conditioner, electric meter, etc.), smart robots, robotic arms, wireless terminals in workshop devices, industrial control (industrial control), wireless terminals in unmanned aerial vehicle (self driving), wireless terminals in smart media, wireless terminals in smart grid (smart grid), wireless terminals in transportation safety (transportation safety), wireless terminals in smart city (smart city), wireless terminals in the road side, mobile terminals in the air, mobile station, etc. The terminal of the present application may also be an in-vehicle module, an in-vehicle component, an in-vehicle chip, or an in-vehicle unit built into a vehicle as one or more components or units. The terminal device may also be other devices with terminal functions, for example, the terminal device may also be a device functioning as a terminal function in D2D communication.

The embodiment of the application does not limit the device form of the terminal, and the device for realizing the function of the terminal device can be the terminal device; or a device, such as a chip system, capable of supporting the terminal device to implement the function. The device can be installed in or matched with the terminal equipment. In the embodiment of the application, the chip system may be formed by a chip, and may also include a chip and other discrete devices.

The AN is used for realizing the function related to access, providing the network access function for authorized users in a specific area, and determining transmission links with different qualities according to the level of the users, the service requirements and the like so as to transmit user data. The AN forwards control signals and user data between the terminal and the CN. The AN may include: an access network device, which may also be referred to as a radio access network device (radio access network, RAN) device. The CN is mainly responsible for maintaining subscription data of the mobile network and providing session management, mobility management, policy management, security authentication and other functions for the terminal. The CN mainly comprises the following network elements: user plane function (user plane function, UPF) network elements, authentication service function (authentication server function, AUSF) network elements, access and mobility management function (access and mobility management function, AMF) network elements, session management function (session management function, SMF) network elements, network slice selection function (network slice selection function, NSSF) network elements, network opening function (network exposure function, NEF) network elements, network function warehousing function (NF repository function, NRF) network elements, policy control function (policy control function, PCF) network elements, unified data management (unified data management, UDM) network elements, unified data storage (unified data repository, UDR), and application function (application function, AF).

The RAN equipment, i.e. the access network means, may be one or more. The access network device may be a device with a wireless transceiver function, or may be a chip or a chip system provided in the device, and be located in AN Access Network (AN) of a communication system, so as to provide AN access service for a terminal. For example, the access network device may be referred to as a radio access network equipment (radio access network, RAN) device, and may specifically be a next generation mobile communication system, for example, a 6G access network device, for example, a 6G base station, or in a next generation mobile communication system, an access network device may also have other naming manners, which are covered by the protection scope of the embodiments of the present application, which is not limited in any way. Alternatively, the access network device may also include a 5G, such as a gNB in a New Radio (NR) system, or one or a group (including multiple antenna panels) of base stations in the 5G, or may also be a network node forming a gNB, a transmission point (transmission and reception point, TRP or transmission point, TP), or a transmission measurement function (transmission measurement function, TMF), such as a Central Unit (CU), a Distributed Unit (DU), a CU-Control Plane (CP), a CU-User Plane (UP), or a Radio Unit (RU), an RSU with a base station function, or a wired access gateway, or a core network element of the 5G, etc. Alternatively, the access network apparatus may further include: access Points (APs) in wireless fidelity (wireless fidelity, wiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also referred to as small stations), relay stations, access points, wearable devices, vehicle devices, and the like.

Wherein the CU and the DU may be provided separately or may be included in the same network element, e.g. in a baseband unit (BBU). The RU may be included in a radio frequency device or unit, such as in a remote radio unit (remote radio unit, RRU), an active antenna processing unit (active antenna unit, AAU), or a remote radio head (remote radio head, RRH). It is understood that the network device may be a CU node, or a DU node, or a device comprising a CU node and a DU node. In addition, the CU may be divided into network devices in the access network RAN, or may be divided into network devices in the core network CN, which is not limited herein.

In different systems, CUs (or CU-CP and CU-UP), DUs or RUs may also have different names, but the meaning will be understood by those skilled in the art. For example, in an ORAN system, a CU may also be referred to as an O-CU (open CU), a DU may also be referred to as an O-DU, a CU-CP may also be referred to as an O-CU-CP, a CU-UP may also be referred to as an O-CU-UP, and a RU may also be referred to as an O-RU. For convenience of description, the present application will be described with reference to CU, CU-CP, CU-UP, DU and RU. Any unit of CU (or CU-CP, CU-UP), DU and RU in the present application may be implemented by a software module, a hardware module, or a combination of software and hardware modules.

The UPF network element is mainly responsible for user data processing (forwarding, receiving, charging, etc.). For example, the UPF network element may receive user data from a Data Network (DN), which is forwarded to the terminal through the access network device. The UPF network element may also receive user data from the terminal through the access network device and forward the user data to the DN. DN network elements refer to the operator network that provides data transmission services for subscribers. Such as the internet protocol (internet protocol, IP) Multimedia Services (IMS), the internet, etc. The DN may be an external network of the operator or a network controlled by the operator, and is configured to provide service to the terminal device.

The AUSF network element is mainly used for executing security authentication of the terminal.

The AMF network element is mainly used for mobility management in a mobile network. Such as user location updates, user registration networks, user handoffs, etc.

The SMF network element is mainly used for session management in a mobile network. Such as session establishment, modification, release. Specific functions are for example assigning internet protocol (internet protocol, IP) addresses to users, selecting UPF network elements providing packet forwarding functions, etc.

The PCF network element mainly supports providing a unified policy framework to control network behavior, provides policy rules for a control layer network function, and is responsible for acquiring user subscription information related to policy decision. The PCF network element may provide policies, such as quality of service (quality of service, qoS) policies, slice selection policies, etc., to the AMF network element, SMF network element.

The NSSF network element is mainly used to select network slices for the terminal.

The NEF network element is mainly used for supporting the opening of capabilities and events.

The UDM network element is mainly used for storing subscriber data, such as subscription data, authentication/authorization data, etc.

The UDR network element is mainly used for storing structured data, and the stored content includes subscription data and policy data, externally exposed structured data and application related data.

AF mainly supports interactions with CN to provide services, such as influencing data routing decisions, policy control functions or providing some services of third parties to the network side. Optionally, the AF may provide a personal identification number (personal identification number, PIN) service, which may also be referred to as PIN-AF.

When the 5GC (5G core network) supports non-trusted non-3GPP (abbreviated as N3G) access, the architecture of the 5GS is shown in fig. 2, where the N3IWF is also called a non-trusted non-3GPP access gateway, such as an untrusted WLAN access gateway, for supporting an untrusted WLAN access technology.

In addition, the 5GC may also support trusted non-3 GPP access or/and wired network access. The trusted non-3 GPP network includes a trusted WALN network, and the wired network includes a fixed home network access. The network side architecture is similar to the non-trusted non-3 GPP access architecture, e.g., the N3IWF may be replaced with a trusted WLAN access gateway (trusted non-3GPP gateway function,TNGF), or with a wired network access gateway (wireline access gateway function, W-AGF). Access network devices between the UE and the access gateway (e.g., TNGF or W-AGF) include WLAN APs, wired network access network devices (fixed access network, FAN), switches, routers, etc.

In summary, the N3G access technologies include WLAN access technologies and wired access technologies. The WLAN access technology corresponds to WLAN AP deployed in a park or WLAN AP hot spots deployed in public places, and the wired access technology corresponds to wired access deployed in a home network. Furthermore, WLAN access technologies may be further classified into trusted WLANs and untrusted WLANs. In summary, the non-3 GPP access technologies include access technologies such as trusted non-3 GPP access, untrusted non-3 GPP access, trusted WLAN access, untrusted WLAN access, wired access, or referred to as fixed network access. Whether trusted non-3 GPP access or untrusted non-3 GPP access, the core network side can support a point-to-point interface protocol as shown in FIG. 2, or a servitized interface consistent with the 3GPP access core network architecture as shown in FIG. 1.

The technical solutions in the present application will be described below with reference to the accompanying drawings.

The technical solution of the embodiments of the present application may be applied to various communication systems, such as a wireless network (Wi-Fi) system, a vehicle-to-arbitrary object (vehicle to everything, V2X) communication system, an inter-device (D2D) communication system, a car networking communication system, a fourth generation (4th generation,4G) mobile communication system, such as a long term evolution (long term evolution, LTE) system, a worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) communication system, a 5G, such as an NR system, and future communication systems.

In the embodiment of the application, the "indication" may include a direct indication and an indirect indication, and may also include an explicit indication and an implicit indication. The information indicated by a certain information (such as the first indication information, the second indication information, or the third indication information) is referred to as information to be indicated, and in a specific implementation process, there are various ways of indicating the information to be indicated, for example, but not limited to, the information to be indicated may be directly indicated, such as the information to be indicated itself or an index of the information to be indicated. The information to be indicated can also be indicated indirectly by indicating other information, wherein the other information and the information to be indicated have an association relation. It is also possible to indicate only a part of the information to be indicated, while other parts of the information to be indicated are known or agreed in advance. For example, the indication of the specific information may also be achieved by means of a pre-agreed (e.g., protocol-specified) arrangement sequence of the respective information, thereby reducing the indication overhead to some extent. And meanwhile, the universal part of each information can be identified and indicated uniformly, so that the indication cost caused by independently indicating the same information is reduced.

The specific indication means may be any of various existing indication means, such as, but not limited to, the above indication means, various combinations thereof, and the like. Specific details of various indications may be referred to the prior art and are not described herein. As can be seen from the above, for example, when multiple pieces of information of the same type need to be indicated, different manners of indication of different pieces of information may occur. In a specific implementation process, a required indication mode can be selected according to specific needs, and in this embodiment of the present application, the selected indication mode is not limited, so that the indication mode according to the embodiment of the present application should be understood to cover various methods that can enable a party to be indicated to learn information to be indicated.

It should be understood that the information to be indicated may be sent together as a whole or may be sent separately in a plurality of sub-information, and the sending periods and/or sending timings of these sub-information may be the same or different. The specific transmission method is not limited in this embodiment. The transmission period and/or the transmission timing of the sub-information may be predefined, for example, predefined according to a protocol, or may be configured by the transmitting end device by transmitting configuration information to the receiving end device.

The "pre-defining" or "pre-configuring" may be implemented by pre-storing corresponding codes, tables, or other manners that may be used to indicate relevant information in the device, and the embodiments of the present application are not limited to specific implementation manners thereof. Where "save" may refer to saving in one or more memories. The one or more memories may be provided separately or may be integrated in an encoder or decoder, processor, or communication device. The one or more memories may also be provided separately as part of a decoder, processor, or communication device. The type of memory may be any form of storage medium, and embodiments of the present application are not limited in this regard.

The "protocol" referred to in the embodiments of the present application may refer to a protocol family in the communication field, a standard protocol similar to a frame structure of the protocol family, or a related protocol applied to a future communication system, which is not specifically limited in the embodiments of the present application.

In the embodiments of the present application, the descriptions of "when … …", "in the case of … …", "if" and "if" all refer to that the device will perform the corresponding processing under some objective condition, and are not limited in time, nor do the descriptions require that the device must have a judging action when implemented, nor do they mean that there are other limitations.

In the description of the embodiments of the present application, unless otherwise indicated, "/" means that the associated object is an "or" relationship, for example, a/B may represent a or B; in the embodiment of the present application, "and/or" is merely an association relationship describing an association object, and indicates that three relationships may exist, for example, a and/or B may indicate: a alone, a and B together, and B alone, wherein A, B may be singular or plural. Also, in the description of the embodiments of the present application, unless otherwise indicated, "a plurality" means two or more than two. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", and the like are used to distinguish the same item or similar items having substantially the same function and effect. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ. Meanwhile, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion that may be readily understood.

The network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided in the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

To facilitate understanding of the embodiments of the present application, a communication system suitable for the embodiments of the present application will be described in detail first with reference to the communication system shown in fig. 2 as an example. Fig. 2 is a schematic diagram of a communication system to which the management method of a group management and group control charging pile according to an embodiment of the present application is applicable.

As shown in fig. 2, the communication system may be applied to the above 5GS, and mainly includes: charging pile clusters and AMF network elements. Each charging pile in the charging pile cluster can be understood as the terminal described above.

The following describes the interaction flow between each network element/device in the communication system in detail through the method embodiment. The management method of the group management and group control charging pile provided by the embodiment of the application can be applied to the communication system, and is specifically applied to various scenes mentioned in the communication system, and is specifically described below.

Fig. 3 is a flow chart of a management method of a group management and group control charging pile according to an embodiment of the present application. The management method of the group management and group control charging pile is applicable to the communication system and mainly relates to interaction between the charging pile group and an AMF network element and the like.

The method comprises the following steps:

s301, under the condition that the first charging pile requests to register to a network where the AMF network element is located, the AMF network element determines that the first charging pile is a head charging pile in the charging pile cluster.

Wherein the AMF network element may receive a first registration request from a first charging stake. The first registration request is used for indicating that the first charging pile requests to register to the network. The AMF network element obtains subscription data of the first charging stake from the UDM network element according to the first registration request (e.g., an identification of the first charging stake therein). The AMF network element may determine that the first charging pile is a head charging pile in the charging pile cluster according to information (e.g. 1 bit, with a value of 0) in the subscription data of the first charging pile, where the information is used to indicate that the first charging pile is the head charging pile in the charging pile cluster.

S302, the AMF network element triggers a main authentication flow of the first charging pile.

If the non-head charging pile in the charging pile cluster requests to register to the network, the AMF network element registers the non-head charging pile in the charging pile cluster to the network under the condition that the main authentication flow of the non-head charging pile in the charging pile cluster is not triggered, and the head charging pile in the charging pile cluster can authenticate the non-head charging pile in the charging pile cluster.

For example, the AMF network element may send a first authentication request to the AUSF network element. The first authentication request (e.g., an identifier of the first charging pile) is used to request the AUSF network element to perform primary authentication on the first charging pile, where the primary authentication of the first charging pile includes a first charging pile authentication network and a network authentication first charging pile, and specifically may be EAP-AKA or 5G-AKA, which is not described herein. The AMF network element receives a first authentication response of the AUSF network element. Wherein the first authentication response is used to indicate whether the primary authentication of the first charging stake is passed.

S303, the AMF network element registers the first charging pile to the network when the primary authentication of the first charging pile passes.

For example, the AMF network element may send a first registration accept to the first charging stake. Wherein the first registration acceptance is used to indicate that the first charging stake is successfully registered with the network.

In summary, when a charging pile request is registered to the network in the charging pile cluster, the AMF network element may trigger the primary authentication flow of the first charging pile only when the charging pile is the first charging pile in the charging pile cluster, and if the charging pile is a non-first charging pile managed by the first charging pile, the AMF network element may directly register the non-first charging pile to the network without triggering the primary authentication flow of the non-first charging pile. That is, the network performs the main authentication procedure only for the head charging stake, thereby reducing the number of times of performing the main authentication procedure in the group registration scenario, thereby being capable of improving the registration efficiency and reducing the overhead of the network.

In one possible design, after the AMF network element registers the first charging stake to the network, the method further includes:

and step 1, under the condition that the second charging pile requests to register to the network, the AMF network element determines that the second charging pile is a non-head charging pile in the charging pile cluster.

The AMF network element may also receive a second registration request from a second charging stake. The second registration request is used for indicating that the second charging pile requests to register to the network. And the AMF network element acquires the subscription data of the second charging pile from the UDM network element according to the second registration request (such as the identification of the second charging pile carried in the second registration request). The AMF network element may determine that the second charging pile is a non-head charging pile in the charging pile cluster according to information (e.g. 1 bit, and a value of 1) in the subscription data of the second charging pile, where the information is used to indicate that the first charging pile is a non-head charging pile in the charging pile cluster.

And 2, the AMF network element registers the second charging pile to the network under the condition that the main authentication flow of the second charging pile is not triggered.

For example, if the subscription data of the second charging pile includes information for indicating that the second charging pile is controlled by the first charging pile, the AMF network element determines whether the first charging pile is registered to the network. And under the condition that the first charging pile is registered to the network, the AMF network element determines that an authentication request for the second charging pile is not sent to the AUSF network element, and the AMF network element sends a second registration acceptance to the second charging pile, wherein the second registration acceptance is used for indicating that the second charging pile is successfully registered to the network.

At this time, because the second fills electric pile and is controlled by first electric pile, when first electric pile initiates control to second electric pile through the network that both registered together, first electric pile can be by oneself to whether second electric pile is reliable to carry out authentication. For example, the first charging stake may verify that the second charging stake is one of the trusted charging stakes that the first charging stake is preconfigured with. In other words, the purpose of the second charging pile to register with the network is mainly to communicate with the first charging pile.

For another example, if the subscription data of the second charging stake includes information indicating that the second charging stake is controlled by the third charging stake, the AMF network element determines whether the third charging stake is registered with the network. And under the condition that the third charging pile is not registered in the network, the AMF network element determines to send a second authentication request to the AUSF network element. The second authentication request is used for requesting the AUSF network element to initiate authentication of the second charging pile to the network, and does not initiate authentication of the second charging pile by the network. The AMF network element receives a second authentication response of the AUSF network element, wherein the second authentication response is used for indicating whether a second charging pile authentication network passes or not; and under the condition that the second charging pile authentication network passes, the AMF network element sends a second registration acceptance to the second charging pile, wherein the second registration acceptance is used for indicating that the second charging pile is successfully registered in the network. In other words, since it is not determined whether the third charging pile is authenticated, it is meaningless to network authenticate the second charging pile.

Optionally, after the AMF network element sends the second registration accept to the second charging pile, the AMF network element determines that the second charging pile is in a service limited state before the third charging pile registers to the network, that is, the network may send data to the second charging pile, but the network does not accept the data sent by the second charging pile to the network, so as to ensure network security.

The management method of the group management and group control charging pile provided in the embodiment of the application is described in detail above with reference to fig. 3. The following describes in detail a management system of a group management and group control charging pile for executing the management method of a group management and group control charging pile provided in the embodiment of the present application.

The system is configured to: under the condition that the first charging pile requests to register to a network where the AMF network element is located, the AMF network element determines that the first charging pile is a head charging pile in the charging pile cluster; the AMF network element triggers a main authentication flow of the first charging pile, wherein if the non-head charging pile in the charging pile cluster requests to register to the network, the AMF network element registers the non-head charging pile in the charging pile cluster to the network under the condition that the main authentication flow of the non-head charging pile in the charging pile cluster is not triggered, and the head charging pile in the charging pile cluster can authenticate the non-head charging pile in the charging pile cluster; and under the condition that the primary authentication of the first charging pile passes, the AMF network element registers the first charging pile to the network.

In one possible design, the system is configured to: the AMF network element receives a first registration request from a first charging pile, wherein the first registration request is used for indicating the first charging pile to request to register to a network; the AMF network element acquires the subscription data of the first charging pile from the UDM network element according to the first registration request; and the AMF network element determines that the first charging pile is the head charging pile in the charging pile cluster according to the information in the subscription data of the first charging pile, which is used for indicating that the first charging pile is the head charging pile in the charging pile cluster.

Optionally, the system is configured to: the AMF network element sends a first authentication request to the AUSF network element, wherein the first authentication request is used for requesting the AUSF network element to perform main authentication on the first charging pile, and the main authentication of the first charging pile comprises a first charging pile authentication network and a network authentication first charging pile; the AMF network element receives a first authentication response of the AUSF network element, wherein the first authentication response is used for indicating whether the primary authentication of the first charging pile passes or not.

Further, the system is configured to: the AMF network element sends a first registration acceptance to the first charging pile, wherein the first registration acceptance is used for indicating that the first charging pile is successfully registered to the network.

In one possible design, the system is configured to: after the AMF network element registers the first charging pile to the network, under the condition that the second charging pile requests to register to the network, the AMF network element determines that the second charging pile is a non-head charging pile in the charging pile cluster; the AMF network element registers the second charging pile to the network under the condition that the main authentication flow of the second charging pile is not triggered.

Optionally, the system is configured to: the AMF network element receives a second registration request from a second charging pile, wherein the second registration request is used for indicating the second charging pile to request to register to the network; the AMF network element acquires the subscription data of the second charging pile from the UDM network element according to the second registration request; and the AMF network element determines that the second charging pile is the non-head charging pile in the charging pile cluster according to the information in the subscription data of the second charging pile, which is used for indicating that the first charging pile is the non-head charging pile in the charging pile cluster.

Further, the system is configured to: if the subscription data of the second charging pile comprises information for indicating that the second charging pile is controlled by the first charging pile, the AMF network element determines whether the first charging pile is registered to the network; and under the condition that the first charging pile is registered to the network, the AMF network element determines that an authentication request for the second charging pile is not sent to the AUSF network element, and the AMF network element sends a second registration acceptance to the second charging pile, wherein the second registration acceptance is used for indicating that the second charging pile is successfully registered to the network.

Further, the system is configured to: if the subscription data of the second charging pile comprises information for indicating that the second charging pile is controlled by the third charging pile, the AMF network element determines whether the third charging pile is registered to the network; under the condition that the third charging pile is not registered to the network, the AMF network element determines to send a second authentication request to the AUSF network element, wherein the second authentication request is used for requesting the AUSF network element to initiate authentication of the second charging pile to the network, and the authentication of the network to the second charging pile is not initiated; the AMF network element receives a second authentication response of the AUSF network element, wherein the second authentication response is used for indicating whether a second charging pile authentication network passes or not; and under the condition that the second charging pile authentication network passes, the AMF network element sends a second registration acceptance to the second charging pile, wherein the second registration acceptance is used for indicating that the second charging pile is successfully registered in the network.

Further, the system is configured to: after the AMF network element sends the second registration acceptance to the second charging stake, the AMF network element determines that the second charging stake is in a service limited state before the third charging stake is registered with the network.

Fig. 4 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device may be a terminal, or may be a chip (system) or other part or component that may be provided in the terminal, for example. As shown in fig. 4, the communication device 400 may include a processor 401. Optionally, the communication device 400 may also include a memory 402 and/or a transceiver 403. Wherein the processor 401 is coupled to the memory 402 and the transceiver 403, e.g. may be connected by a communication bus.

The following describes the respective constituent elements of the communication apparatus 400 in detail with reference to fig. 4:

the processor 401 is a control center of the communication device 400, and may be one processor or a collective term of a plurality of processing elements. For example, processor 401 is one or more central processing units (central processing unit, CPU), but may also be an integrated circuit (application specific integrated circuit, ASIC), or one or more integrated circuits configured to implement embodiments of the present application, such as: one or more microprocessors (digital signal processor, DSPs), or one or more field programmable gate arrays (field programmable gate array, FPGAs).

Alternatively, the processor 401 may perform various functions of the communication device 400, such as performing the above-described management method of the group management and group control charging stake shown in fig. 3, by running or executing a software program stored in the memory 402 and calling data stored in the memory 402.

In a particular implementation, processor 401 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 4, as an embodiment.

In a specific implementation, as an embodiment, the communication apparatus 400 may also include a plurality of processors. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

The memory 402 is configured to store a software program for executing the solution of the present application, and the processor 401 controls the execution of the software program, and the specific implementation may refer to the above method embodiment, which is not described herein again.

Alternatively, memory 402 may be, but is not limited to, read-only memory (ROM) or other type of static storage device that may store static information and instructions, random access memory (random access memory, RAM) or other type of dynamic storage device that may store information and instructions, but may also be electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), compact disc read-only memory (compact disc read-only memory) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 402 may be integrated with the processor 401 or may exist separately and be coupled to the processor 401 through an interface circuit (not shown in fig. 4) of the communication device 400, which is not specifically limited in this embodiment of the present application.

A transceiver 403 for communication with other communication devices. For example, the communication apparatus 400 is a terminal, and the transceiver 403 may be used to communicate with a network device or with another terminal device. As another example, the communication apparatus 400 is a network device, and the transceiver 403 may be used to communicate with a terminal or another network device.

Alternatively, the transceiver 403 may include a receiver and a transmitter (not separately shown in fig. 4). The receiver is used for realizing the receiving function, and the transmitter is used for realizing the transmitting function.

Alternatively, the transceiver 403 may be integrated with the processor 401, or may exist separately, and be coupled to the processor 401 through an interface circuit (not shown in fig. 4) of the communication device 400, which is not specifically limited in the embodiment of the present application.

It will be appreciated that the configuration of the communication device 400 shown in fig. 4 is not limiting of the communication device, and that an actual communication device may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.

In addition, the technical effects of the communication device 400 may refer to the technical effects of the method described in the above method embodiments, which are not described herein.

It should be appreciated that the processor in embodiments of the present application may be a central processing unit (central processing unit, CPU), which may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate arrays (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example but not limitation, many forms of random access memory (random access memory, RAM) are available, such as Static RAM (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), synchronous Link DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware (e.g., circuitry), firmware, or any other combination. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the processes or functions described in accordance with the embodiments of the present application are all or partially produced. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center by wired (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more sets of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.

It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: there are three cases, a alone, a and B together, and B alone, wherein a, B may be singular or plural. In addition, the character "/" herein generally indicates that the associated object is an "or" relationship, but may also indicate an "and/or" relationship, and may be understood by referring to the context.

In the present application, "at least one" means one or more, and "a plurality" means two or more. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. The management method of the group management and group control charging pile is characterized by being applied to an AMF network element, and comprises the following steps:

under the condition that a first charging pile requests to register to a network where an AMF network element is located, the AMF network element determines that the first charging pile is a head charging pile in a charging pile cluster;

the AMF network element triggers a main authentication flow of the first charging pile, wherein if a non-head charging pile in the charging pile cluster requests to register to the network, the AMF network element registers the non-head charging pile in the charging pile cluster to the network under the condition that the main authentication flow of the non-head charging pile in the charging pile cluster is not triggered, and the head charging pile in the charging pile cluster can authenticate the non-head charging pile in the charging pile cluster;

And the AMF network element registers the first charging pile to the network under the condition that the primary authentication of the first charging pile passes.

2. The method of claim 1, wherein the AMF network element determining that the first charging stake is a head charging stake in a cluster of charging stakes comprises:

the AMF network element receives a first registration request from the first charging pile, wherein the first registration request is used for indicating the first charging pile to request to register to the network;

the AMF network element acquires the subscription data of the first charging pile from the UDM network element according to the first registration request;

and the AMF network element determines that the first charging pile is the head charging pile in the charging pile cluster according to the information in the subscription data of the first charging pile, which is used for indicating that the first charging pile is the head charging pile in the charging pile cluster.

3. The method of claim 2, wherein the AMF network element triggers a primary authentication procedure of the first charging stake, comprising:

the AMF network element sends a first authentication request to an AUSF network element, wherein the first authentication request is used for requesting the AUSF network element to perform main authentication on the first charging pile, and the main authentication of the first charging pile comprises the authentication of the first charging pile on the network and the authentication of the first charging pile by the network;

The AMF network element receives a first authentication response of the AUSF network element, wherein the first authentication response is used for indicating whether the primary authentication of the first charging pile is passed or not.

4. A method according to claim 3, wherein the AMF network element registering the first charging pile with the network comprises:

and the AMF network element sends a first registration acceptance to the first charging pile, wherein the first registration acceptance is used for indicating that the first charging pile is successfully registered to the network.

5. The method according to any one of claims 1-4, wherein after the AMF network element registers the first charging stake to the network, the method further comprises:

under the condition that a second charging pile requests to be registered in the network, the AMF network element determines that the second charging pile is a non-head charging pile in the charging pile cluster;

and the AMF network element registers the second charging pile to the network under the condition that the main authentication flow of the second charging pile is not triggered.

6. The method of claim 5, wherein the AMF network element determining that the second charging stake is a non-head charging stake of the charging stake set comprises:

The AMF network element receives a second registration request from the second charging pile, wherein the second registration request is used for indicating the second charging pile to request to register to the network;

the AMF network element acquires the subscription data of the second charging pile from the UDM network element according to the second registration request;

and the AMF network element determines that the second charging pile is the non-head charging pile in the charging pile cluster according to the information in the subscription data of the second charging pile, which is used for indicating that the first charging pile is the non-head charging pile in the charging pile cluster.

7. The method of claim 6, wherein the AMF network element registering the second charging stake to the network without triggering a primary authentication procedure of the second charging stake comprises:

if the subscription data of the second charging pile includes information for indicating that the second charging pile is controlled by the first charging pile, the AMF network element determines whether the first charging pile is registered to the network;

and under the condition that the first charging pile is registered to the network, the AMF network element determines that an authentication request for the second charging pile is not sent to the AUSF network element, and the AMF network element sends a second registration acceptance to the second charging pile, wherein the second registration acceptance is used for indicating that the second charging pile is successfully registered to the network.

8. The method of claim 6, wherein the AMF network element registering the second charging stake to the network without triggering a primary authentication procedure of the second charging stake comprises:

if the subscription data of the second charging pile includes information for indicating that the second charging pile is controlled by a third charging pile, the AMF network element determines whether the third charging pile is registered to the network;

under the condition that the third charging pile is not registered to the network, the AMF network element determines to send a second authentication request to the AUSF network element, wherein the second authentication request is used for requesting the AUSF network element to initiate authentication of the second charging pile to the network and not initiate authentication of the network to the second charging pile;

the AMF network element receives a second authentication response of the AUSF network element, wherein the second authentication response is used for indicating whether the second charging pile authenticates the network to pass or not;

and under the condition that the second charging pile authenticates that the network passes, the AMF network element sends a second registration acceptance to the second charging pile, wherein the second registration acceptance is used for indicating that the second charging pile is successfully registered to the network.

9. The method of claim 8, wherein after the AMF network element sends a second registration accept to the second charging stake, the method further comprises:

the AMF network element determines that the second charging pile is in a service limited state before the third charging pile is registered with the network.

10. A management system for a group management and group control charging pile, the system comprising an AMF network element, the system being configured to:

under the condition that a first charging pile requests to register to a network where an AMF network element is located, the AMF network element determines that the first charging pile is a head charging pile in a charging pile cluster;

the AMF network element triggers a main authentication flow of the first charging pile, wherein if a non-head charging pile in the charging pile cluster requests to register to the network, the AMF network element registers the non-head charging pile in the charging pile cluster to the network under the condition that the main authentication flow of the non-head charging pile in the charging pile cluster is not triggered, and the head charging pile in the charging pile cluster can authenticate the non-head charging pile in the charging pile cluster;

and the AMF network element registers the first charging pile to the network under the condition that the primary authentication of the first charging pile passes.