CN106304062B

CN106304062B - Method and equipment for managing terminal

Info

Publication number: CN106304062B
Application number: CN201510275195.5A
Authority: CN
Inventors: 焦斌; 谌丽; 秦飞
Original assignee: China Academy of Telecommunications Technology CATT
Current assignee: China Academy of Telecommunications Technology CATT; Datang Mobile Communications Equipment Co Ltd
Priority date: 2015-05-26
Filing date: 2015-05-26
Publication date: 2019-12-13
Anticipated expiration: 2035-05-26
Also published as: CN106304062A; WO2016188345A1

Abstract

The embodiment of the invention relates to the technical field of wireless communication, in particular to a method and equipment for managing terminals, which are used for solving the problems that the load of a core network is increased and a signaling storm is easily caused as the number of machine type terminals is increased in the prior art. In the embodiment of the invention, after determining that the core network authorization is obtained, the DSC functional entity manages the EP in the cluster, wherein the DSC functional entity is connected with each EP in the corresponding cluster. Since the DSC functional entity manages the EP in the cluster, the burden on the core network is not increased after the number of machine type terminals is increased, thereby avoiding the signaling storm caused by the overlarge burden of the core network.

Description

Method and equipment for managing terminal

Technical Field

The present invention relates to the field of wireless communication technologies, and in particular, to a method and a device for managing a terminal.

background

Bluetooth technology is currently widely used in near field communications (e.g., sensor networks).

As shown in fig. 1A, in a bluetooth system of a MESH (ad hoc or non-fixed infrastructure) network model, a cluster head and a series of end nodes (EndPoint) form a cluster, and EndPoint communication in the cluster is controlled by a cluster head device. The intra-cluster communication adopts a 2.4GHz public frequency band, and interference is avoided in a frequency hopping mode. And statically configured channels and security parameters are adopted between the cluster head and EndPoint. The clusters are independent from each other, and EndPoint members in different clusters cannot communicate with each other.

As shown in fig. 1B, in the existing cellular system, a terminal determines a service base station according to the downlink pilot signal strength, and the service base station is responsible for providing a data transmission service for an access terminal. The service base station forwards the uplink data received from the terminal to the core network, and the core network is responsible for providing the access terminal with a connection service to an external network.

in the prior art, the terminal completes the registration process with the network through an Attach (Attach) process. In the process of registering the terminal to the network, the core network MME entity is responsible for storing the state information of the terminal, wherein the state information comprises security context information, activation session information, position area information and the like. The state information of the terminal is stored in the core network, and thus there are two problems if the access terminal is a machine type terminal. First, since the number of machine types of future terminals will far exceed that of existing terminals (which is predicted to be on the order of 500 to 1000 billion), if a context is to be established for each machine type terminal in the core network, this will cause a problem of overwhelming the storage of the core network. In addition, the connection management function of the existing terminal also relates to a core network, which means that a large amount of signaling to the core network is generated each time the terminal enters a connection state, and signaling storm is easily caused after a large amount of machine type terminals are accessed into the network.

In summary, as the number of terminals of machine type increases, the load of the core network increases and a signaling storm is easily caused.

Disclosure of Invention

the invention provides a method and equipment for managing terminals, which are used for solving the problems that the load of a core network is increased and a signaling storm is easily caused along with the increase of the number of machine type terminals in the prior art.

The embodiment of the invention provides a method for managing a terminal, which comprises the following steps:

The DSC functional entity determines to obtain the authorization of the core network;

The DSC functional entity manages EPs in a cluster, wherein a DSC functional entity is connected to each EP in the corresponding cluster.

Optionally, the DSC functional entity manages EPs in the cluster, including:

And the DSC functional entity performs identity authentication on the EP when the EP performs an attachment process, and establishes context information of the EP after the authentication is passed.

Optionally, after the DSC functional entity passes the verification, the method further includes:

And the DSC functional entity informs the core network of updating the corresponding cluster information.

optionally, before the attaching process of the EP, the DSC functional entity further includes:

and the DSC functional entity broadcasts the access configuration information through an air interface.

Optionally, the DSC functional entity manages EPs in the cluster, including:

The DSC functional entity deletes the context information of the EP in the EP detachment process.

optionally, the method further includes:

and the DSC functional entity informs the core network of updating the corresponding cluster information after the EP is removed.

Optionally, the DSC functional entity manages EPs in the cluster, including:

And after receiving the state updating request of the EP, the DSC functional entity updates the context information of the EP and informs the core network of updating the corresponding cluster information.

Optionally, the DSC functional entity manages EPs in the cluster, including:

The DSC functional entity determines the service activated by the EP request according to the received service identification or terminal type information from the EP;

And the DSC functional entity stores the EP activation service information into the context information of the EP after the EP request activated service is authorized.

Optionally, the DSC functional entity determines, according to the received service identifier or terminal type information from the EP, the service that the EP requests to activate, and further includes:

the DSC functional entity initiates a service authorization request process to a core network after the EP request activated service is not activated;

And the DSC functional entity stores the EP activation service information into the context information of the EP after determining that the service requested to be activated by the EP is authorized according to the indication of the core network.

Optionally, the DSC functional entity manages EPs in the cluster, including:

and after the EP requests to deactivate the service, the DSC functional entity updates the activated service information stored in the context information of the EP.

Optionally, after the EP requests to deactivate the service, the DSC functional entity further includes:

and after determining that the authorization service needs to be updated, the DSC functional entity informs the core network of updating the authorization service.

optionally, the DSC functional entity manages EPs in the cluster, including:

And the DSC functional entity updates the corresponding cluster authorization service after the core network informs that the authorization service needs to be updated.

Optionally, after updating the authorization service of the corresponding cluster, the DSC functional entity further includes:

and the DSC functional entity informs the EP needing to be deactivated to perform deactivation operation after determining that the EP needs to be deactivated according to the updated authorization service, and updates the activation service information in the context information of the EP needing to be deactivated.

Optionally, the DSC functional entity is a mobile terminal or base station type device or server type device or distributed service center; and/or

The EP is a mobile terminal or wearable or machine-like device.

another method for managing a terminal provided in an embodiment of the present invention includes:

the core network equipment determines a DSC functional entity needing authorization;

And the core network equipment authorizes the determined DSC functional entity so that the DSC functional entity manages the EP in the cluster, wherein the DSC functional entity is connected with each EP in the corresponding cluster.

Optionally, after the core network device authorizes the determined DSC functional entity, the method further includes:

And the core network equipment updates the cluster information corresponding to the DSC functional entity according to the received cluster information notified by the DSC functional entity.

The embodiment of the invention provides a DSC functional entity for managing a terminal, which comprises:

A first determining module, configured to determine to obtain core network authorization;

And the management module is used for managing the EP in the cluster, wherein the DSC functional entity is connected with each EP in the corresponding cluster.

optionally, the management module is specifically configured to

When the EP is subjected to an attachment process, the EP is subjected to identity authentication, and the context information of the EP is established after the authentication is passed.

optionally, the management module is further configured to:

And after the verification is passed, the core network is informed to update the corresponding cluster information.

optionally, the management module is further configured to:

and before the attachment process of the EP, broadcasting the access configuration information through an air interface.

optionally, the management module is specifically configured to:

Deleting context information of the EP in the EP detach process.

optionally, the management module is further configured to:

optionally, the management module is specifically configured to:

After receiving the state updating request of the EP, updating the context information of the EP and informing the core network to update the corresponding cluster information.

optionally, the management module is specifically configured to:

determining a service activated by the EP request according to the received service identification or terminal type information from the EP; and after the EP requests the activated service to be authorized, storing the EP activation service information into the context information of the EP.

Optionally, the management module is further configured to:

After the EP requests the activated service to be not activated, a service authorization request process is initiated to a core network; and according to the indication of the core network, after determining that the service requested to be activated by the EP is authorized, storing the EP activation service information into the context information of the EP.

optionally, the management module is specifically configured to:

And after the EP requests to deactivate the service, updating the activated service information stored in the context information of the EP.

Optionally, the management module is further configured to:

And after determining that the authorization service needs to be updated, informing the core network of updating the authorization service.

optionally, the management module is specifically configured to:

And after the core network informs that the authorization service needs to be updated, updating the authorization service of the corresponding cluster.

Optionally, the management module is further configured to:

After the authorization service of the corresponding cluster is updated, according to the updated authorization service, after the EP needs to be deactivated, the EP needing to be deactivated is informed to perform deactivation operation, and the activation service information in the context information of the EP which is deactivated is updated.

the EP is a mobile terminal or wearable or machine-like device.

the core network device for managing a terminal provided by the embodiment of the present invention includes:

The second determining module is used for determining the DSC functional entity needing to be authorized;

And the processing module is used for authorizing the determined DSC functional entity so that the DSC functional entity manages the EP in the cluster, wherein the DSC functional entity is connected with each EP in the corresponding cluster.

Optionally, the processing module is further configured to:

And after the determined DSC functional entity is authorized, updating cluster information corresponding to the DSC functional entity according to the received cluster information notified by the DSC functional entity.

in the embodiment of the invention, after determining that the core network authorization is obtained, the DSC functional entity manages the EP in the cluster, wherein the DSC functional entity is connected with each EP in the corresponding cluster. Since the DSC functional entity manages the EP in the cluster, the burden on the core network is not increased after the number of machine type terminals is increased, thereby avoiding the signaling storm caused by the overlarge burden of the core network.

drawings

FIG. 1A is a diagram of a MESH network structure in the background art;

FIG. 1B is a schematic diagram of a cellular network in the background art;

FIG. 2 is a schematic diagram of a distributed network according to an embodiment of the present invention;

Fig. 3 is a schematic structural diagram of a system for managing a terminal according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a first DSC functional entity in accordance with an embodiment of the present invention;

Fig. 5 is a schematic structural diagram of a first core network device according to an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a second DSC functional entity in accordance with an embodiment of the present invention;

Fig. 7 is a schematic structural diagram of a second core network device according to an embodiment of the present invention;

Fig. 8 is a flowchart illustrating a first method for managing a terminal according to an embodiment of the present invention;

Fig. 9 is a flowchart illustrating a second method for managing a terminal according to a second embodiment of the present invention;

fig. 10 is a flowchart illustrating a method for attaching a terminal according to an embodiment of the present invention;

Fig. 11 is a flowchart illustrating a method for triggering detachment by a terminal according to an embodiment of the present invention;

Fig. 12 is a flowchart illustrating a method for updating a trigger state of a terminal according to an embodiment of the present invention;

Fig. 13 is a flowchart illustrating a method for activating a terminal trigger service according to an embodiment of the present invention;

Fig. 14 is a flowchart illustrating a method for terminal triggering service deactivation according to an embodiment of the present invention;

Fig. 15 is a flowchart illustrating a method for triggering service deactivation by a core network according to an embodiment of the present invention.

Detailed Description

the clusters of the embodiments of the present invention may also be referred to as groups.

the following describes a scenario in which the embodiments of the present invention are applied. As shown in fig. 2, the distributed network system according to the embodiment of the present invention includes: MESH access network, cellular access network, backhaul network and core network.

The MESH access network is connected with the core network through the backhaul network; the cellular access network is connected to the core network via the backhaul network.

The backhaul networks include wired backhaul networks, wireless backhaul networks, and mobile cellular backhaul networks.

The core network is composed of various special and general service devices, a data center, a router and other devices, and is responsible for signing and managing various access devices, user identity verification, authentication, policy control, charging management and service management.

the MESH access network mainly provides services for machine type access devices (MTC), wherein a Sensor device (e.g., a temperature Sensor, a pressure Sensor, a camera, etc.) may be bound to an EndPoint (end node), an actuator device (e.g., an accelerator, a brake, a steering gear, a mechanical arm, etc.) may be bound to the EndPoint, and a physical entity (e.g., an automobile, a bicycle, a helmet, glasses, a smart watch, an unmanned aerial vehicle, etc.) may be bound to the EndPoint.

the cellular access network mainly provides access service for a conventional handheld or vehicle-mounted access Device (Device) or a Modem (Modem), and in addition, the cellular access network can also provide signaling and data return service to a core network for a MESH access network.

Before the specific system architecture is introduced, the interfaces in the following figure are introduced:

Me1 interface: an interface established between the DSC functional entity and the NSC.

me2 interface: and the DSC functional entity.

Me3 interface: DSC functional entity and EP (EndPoint).

Me4 interface: an interface established between the EP and the EP.

C1 interface: an interface established between the LSC and the NSC.

C2 interface: an interface established between the LSC and the base station.

c3 interface: the interface established between the LSC and the access point AP.

C4 interface: several ports are established between the base station and the Device.

c5 interface: the access point AP and the Device.

c6 interface: interface between Device and Device.

in 1: an interface established between the DSC functional entity and the LSC.

In 2: an interface established between the LSC and the LSC.

The MESH access network comprises at least one DSC functional entity and at least one EP, the cellular access network comprises at least one LSC, at least one base station and/or at least one AP, and the core network comprises at least one NSC.

each entity is described separately below.

1. end node EndPoint (EP):

The EP is an MTC type access device having a communication function, obtains a data transmission service by accessing a "cluster", and can be bound to a specific physical device, such as various sensors, actuators, accelerators, braking devices, mechanical arms, aircrafts, automobiles, bicycles, safety helmets, smart glasses, smart watches, and the like. Depending on the particular physical device to which it is bound, an EP having a different communication function may be selected. A general EP is a communication scenario oriented to short range (e.g., less than 100m), low data rates (e.g., less than 1000 bits/s). Embodiments of the present invention are equally applicable to long-range high-rate EP's.

2. distributed Service Center (DSC) function:

the DSC functional entity is used for transmitting information related to EP in a corresponding cluster with the core network through the backhaul network; wherein a DSC functional entity is connected to each EP in the corresponding cluster.

In practice, the DSC functional entity forms a Cluster (Cluster) with the surrounding EndPoints to which the DSC functional entity is attached.

optionally, the DSC functional entity is also responsible for managing and maintaining the clusters.

Specifically, the DSC functional entity manages EPs in the corresponding cluster, and coordinates communication with other adjacent clusters, as well as performs interference management.

if the MESH access network shares radio resources with other wireless networks, the DSC functional entity may also coordinate interference with neighboring or co-covering inter-system radio resource control entities and perform cross-system communication with the inter-system.

For example, the DSC functional entity may notify the surrounding DSC functional entities or LSCs of time or frequency information of radio resources allocated for "intra-cluster communication";

Accordingly, the surrounding DSC functional entities, LSCs, avoid using the same time or frequency for communication.

The DSC functional entity can also inform the interference information obtained by the self or the EP in the cluster to the surrounding DSC functional entities or the LSC;

correspondingly, surrounding DSC functional entities or LSCs determine that they interfere with other clusters or "local access network" communications, and then the interference may be weakened by reducing the transmission power.

In terms of business layer and cluster member management: and the DSC functional entity is responsible for participating in maintenance of a member list, verifying the identity of the cluster members and maintaining the equipment type and service requirements associated with EndPoint.

MESH access network layer: the DSC functional entity is also responsible for coordinating communication with other adjacent clusters, as well as interference management, as a control point of the Cluster.

In terms of cross-system collaboration: for the case that the MESH access network shares radio resources with other wireless networks (e.g. cellular), the DSC functional entity is also responsible for coordinating interference with neighboring or co-covering inter-system radio resource control entities and cross-system communication (e.g. the DSC functional entity is responsible for coordinating base stations for interference coordination).

the DSC functional entity supports software and hardware decoupling and software configurable functionality. The DSC functional entity is responsible for controlling access to an EP-type terminal, and the DSC functional entity needs to verify the identity of the terminal in the terminal access process. The core network adopts a management strategy based on the cluster, so the DSC functional entity is responsible for reporting cluster information managed by the DSC functional entity to the core network, wherein the cluster information comprises the information of the number of members in the cluster managed by the DSC functional entity, the information of services activated in the cluster managed by the DSC functional entity and the like.

3. Local Service Center (LSC):

the LSC is configured to transmit information related to a specific access device to the core network through the backhaul network; wherein the specific access device is an access device accessing to a base station or an AP connected with the LSC.

Optionally, the LSC further performs connection management and transmission management on the specific access device.

specifically, the transmission management includes part or all of the following management:

performing cross-base station and/or cross-AP interference management;

Performing interference coordination or wireless resource coordination with adjacent or overlapped cellular local access networks;

Performing wireless resource configuration and/or transmission parameter configuration in a multi-base station and/or multi-AP transmission mode;

and coordinating the wireless resources with the adjacent or overlapped MESH access networks.

for example: the LSC may inform surrounding DSC functional entities or LSCs of the radio resources allocated for the "local access network" communication;

accordingly, surrounding DSC functional entities or LSCs avoid communicating using the same time or frequency resources.

The LSC can also inform surrounding DSC functional entities or LSCs according to interference information measured by the AP, the BS and the access Device in the local access network;

In practice, the cellular access network of the embodiment of the present invention is formed by a plurality of cellular local access networks which may overlap with each other. The base stations in the cellular local access network may be various types of base stations.

the LSC and the base station or the access point AP jointly form a cellular local access network, wherein if the cellular local access network is formed by the LSC and the base station, the cellular local access network is responsible for providing wide area coverage for a specific geographic area; and if the cellular local access network is formed by the LSC and the AP together, the cellular local access network is responsible for enhancing the service for the hot spot capacity. The cellular access network is formed by a plurality of cellular local access networks which may overlap each other.

4. Base Station (BS):

The base station BS and the LSC together form a cellular local access network (macro network layer) responsible for providing wide area coverage services for a specific geographical area. And the seamless connection experience of the access equipment is ensured in the moving process.

Specifically, the base station may perform some or all of the following functions:

the wireless access control system is responsible for controlling a wireless access process;

The base band processing function related to the wireless transmission of the physical layer is responsible;

Performing wireless resource scheduling and transmission parameter configuration for single cell transmission;

And broadcasting the multicast transmission service for the equipment system under the wide area coverage through a broadcast channel.

5. An Access Point (AP):

The access point AP and the LSC together form a cellular local access network (hotspot network layer) and are responsible for providing capacity services for hotspot areas, thereby providing higher data transmission rate for access devices. The AP itself can be seen as a low cost base station tailored in terms of functionality and hardware capabilities.

Specifically, the AP may perform some or all of the following functions:

and is responsible for controlling the wireless access process.

Is responsible for the baseband processing functions associated with the physical layer radio transmission.

and carrying out wireless resource scheduling and transmission parameter configuration for single-cell transmission.

Under the condition of no equipment access, a silent mode can be entered, so that the power consumption is reduced.

6. the Device:

The Device can be a terminal, a Modem Device or other devices capable of accessing the network through the cellular access network.

Optionally, the Device itself may also provide relay services to the core network or external network for MESH access network members.

Optionally, the Device according to the embodiment of the present invention may support access to the cellular network (e.g. a linear distance from the base station antenna exceeds 1500m) in a high speed situation (e.g. a moving speed exceeds 500km/h), and support a very high data transmission rate (e.g. a data transmission rate greater than 1 Gbps).

Optionally, the Device according to the embodiment of the present invention may receive the broadcast service information through a system broadcast channel.

Optionally, the Device according to the embodiment of the present invention may obtain the data transmission service by accessing the cellular network.

Optionally, the Device according to the embodiment of the present invention may implement direct communication between devices.

7. Network service center NetworkServiceCenter (NSC):

The NSC is responsible for terminating the access network to core network control plane interface. The NSC supports software and hardware decoupling and software configurable functions.

And the NSC is used for transmitting the received information of the DSC functional entity and/or the LSC to the core network through the backhaul network.

That is, in terms of connection management, the NSC is responsible for terminating the control plane connection of the MESH access network, the cellular access network, to the core network.

Optionally, in terms of network layer security, the NSC is responsible for performing identity authentication on the DSC functional entity and the LSC and establishing a secure tunnel.

Specifically, the NSC may perform identity authentication on the DSC functional entity and/or the LSC, and establish a secure tunnel for transmitting data through the backhaul network between the DSC functional entity and/or the LSC after the authentication is passed.

For example, the NSC, the DSC functional entity and the LSC realize identity authentication through a certificate mechanism, and establish an IPsec security channel to ensure the security of Me1 and C1 interfaces.

optionally, the NSC may further manage the EP and the specific access device connected to the DSC functional entity at a Service layer (Service) and an identity layer (identity).

Optionally, the Device is responsible for processing control plane signaling received from the MESH access network and the cellular access network, including authentication of the EP and the Device, authentication and activation procedures of a Device type and a service type associated with the EP, and activation of a session to a specific external network for the Device.

For example, the NSC is responsible for managing the state information of the EP, including trace management (information about "clusters" currently accessed by the EP), session management (e.g., currently activated service of the EP), and identity management (e.g., device type and service type subscribed to by the EP).

in implementation, the NSCs belong to a central control unit, while the LSCs and DSC functional entities both belong to distributed control units.

Optionally, in the management aspect, the LSC and DSC functional entity are responsible for controlling local functions with high latency requirements. And the NSC is responsible for controlling functions which are global, have low requirements on time delay and have high requirements on safety.

For example, the LSC is responsible for "cluster member" management, and stores information of the current cluster member. The method comprises the steps of distributing temporary identifications for cluster members, being responsible for distributing wireless resources for cluster communication, and managing the frame format and basic parameters of an air interface in a cluster.

The DSC functional entity is responsible for managing the local access network, including maintaining the AP and BS lists of the local access network, establishing reliable connection between the maintenance and AP and the BS, performing wireless resource allocation and coordination for intra-AP communication or intra-BS communication, and responsible for link management of devices accessed from the AP and the BS. The DSC functional entity may also control the selection of the AP and BS user plane data forwarding paths, and may also configure the frame structures and frame configuration parameters of the AP and the BS on the air interface, the transmission schemes used by the AP and the BS on the MAC layer, and the high-level protocol stack architecture.

in implementation, the core network itself may deploy one or more NSCs, and the different NSCs are equal to each other. On the access network side, due to the distributed characteristic of the access network, the LSCs are deployed according to the geographical area and the type of the coverage or capacity improvement area, each LSC area is controlled by one LSC, different LSCs are also in an equal relationship with each other, and no hierarchical relationship exists (no matter the LSCs control macro base stations or the LSCs control access points).

The clusters in the MESH access network can be mutually overlapped;

The local access networks in the cellular access network can be mutually overlapped;

the local access networks and clusters can overlap.

Optionally, the MESH access network and the cellular access network use a dedicated frequency of a conventional cell or other common public frequency. For example, the conventional cellular system uses dedicated frequency, and the primary frequency is allocated to different operators for specific cellular systems, such as frequency used by CDMA (Code Division Multiple Access), WCDMA (Wide-band Code Division Multiple Access), LTE (Long Term Evolution), TD-LTE (TD-SCDMA Long Term Evolution, time Division synchronous Code Division Multiple Access); frequency resources shared by multiple wireless communication systems of the same or different standards, in addition to dedicated frequencies employed by conventional cellular systems.

The embodiments of the present invention will be described in further detail with reference to the drawings attached hereto.

As shown in fig. 3, the system for managing a terminal according to the embodiment of the present invention includes: a DSC functional entity 10 and a core network device 20.

And the DSC functional entity 10 is configured to determine to obtain core network authorization, and manage the EPs in the cluster, where the DSC functional entity is connected to each EP in the corresponding cluster.

A core network device 20, configured to determine a DSC functional entity that needs to be authorized; authorizing the determined DSC functional entity.

in practice, the clusters of embodiments of the present invention may also be referred to as groups.

The DSC functional entity of the embodiments of the present invention may be a mobile terminal, such as a handheld terminal (e.g., a smart phone), or a base station type device (e.g., a femto base station) or a server type device or a distributed service center.

the EP of embodiments of the present invention may be a mobile-capable terminal, such as a handheld type terminal (e.g., a smartphone), or a wearable device (e.g., a smart band), or a machine type device (e.g., a sensor).

The EP of the embodiments of the present invention may not be visible to the core network. The core network equipment can perform hosted management on the MTC type access terminal through the authorized DSC functional entity. An authorized DSC functional entity may sign up with the operator. In implementation, the operator may configure the management functions of the DSC functional entity in a software manner. The DSC functional entity configured with the management function and the EP form a dynamic network in a self-organizing way, and the DSC functional entity is responsible for management. The DSC functional entity reports the group information or cluster information of the dynamic network managed by the DSC functional entity to the core network equipment as a whole, and the core network equipment can perform charging, policy control and other functions according to the group information or the cluster information.

When the DSC functional entity 10 manages the EPs in the cluster in the embodiment of the present invention, the security mechanism used between the EPs and the DSC functional entity can be customized according to the user needs, and does not need to sign a contract with an operator in advance (for example, different security mechanisms may be used for a factory or for an in-vehicle system). Furthermore, the EP is not visible to the operator core network, and therefore the core network employs a cluster-based charging policy (i.e. the cluster is treated as a basic user, e.g. a contracted factory is a user) instead of the conventional terminal-based charging policy.

The DSC functional entity 10 manages EPs in a cluster including, but not limited to, some or all of the following:

an EP attachment process, an EP detachment process, an EP state updating process, a service activation process and a service deactivation process.

the following are described separately.

first, an EP attachment process.

In implementation, the DSC functional entity broadcasts the access configuration information over the air interface. The access configuration information includes, but is not limited to, some or all of the following information:

Network identification, DSC functional entity identification and service identification list information.

after receiving the access configuration information, the EP may initiate an attach request to the DSC functional entity according to the received configuration information, where the attach request may include a fixed identifier and authentication information of the EP.

After receiving the attachment request, the DSC functional entity determines a corresponding EP according to the fixed identification of the EP, performs identity authentication on the EP according to the identity authentication information of the EP, and establishes the context information of the EP after the authentication is passed.

In practice, there are many ways to perform authentication, such as authentication via a secure certificate mechanism.

optionally, after the verification passes, the DSC functional entity may return an attach response message to the EP, where the attach response message may include a temporary identifier of the EP, a fixed identifier of the EP, and authentication information of the DSC functional entity;

Correspondingly, after receiving the attach response, the EP verifies the network validity, and sends an attach complete message to the DSC functional entity after the verification is passed, wherein the attach complete message may include a temporary identifier of the EP;

And after receiving the attachment completion message, the DSC functional entity establishes the context information of the EP.

currently, there are many techniques for mutual authentication of terminal and network identities (e.g. certificate based, AAA or AKA, etc.). The embodiment of the invention is suitable for the current mutual authentication technology of the terminal and the network identity, and the embodiment of the invention can also customize the safety scheme adopted between the terminal EP and the DSC functional entity according to the user requirements, for example, for an intelligent factory or an in-vehicle system, the user (factory, car factory) can require to adopt the safety scheme of the self-customized telephone.

optionally, after the DSC functional entity passes the verification, the core network may also be notified to update the corresponding cluster information.

The cluster information includes, but is not limited to, part or all of the following information:

the number of EP's in a cluster, the activation service information in a cluster, the used bandwidth of the MESH system, and the used carrier frequency information of the MESH system.

correspondingly, the core network equipment updates the cluster information corresponding to the DSC functional entity according to the received cluster information notified by the DSC functional entity.

And II, an EP (EP) detaching process.

In implementation, before the EP is removed or powered off, a detach request message is sent to the DSC functional entity, which may include a temporary identifier of the EP.

And after receiving the detach request message, the DSC functional entity deletes the context information of the corresponding EP.

Optionally, after deleting the context information of the corresponding EP, the EP may further send a detach response to the EP, where the detach response may include a temporary identifier of the EP.

optionally, after deleting the context information of the corresponding EP, the EP may further notify the core network to update the corresponding cluster information.

the number of EP's in a cluster, the activation service information in a cluster, the bandwidth used by the MESH system, and the carrier frequency used by the MESH system.

And thirdly, triggering a state updating process by the EP.

after the EP attaches to the network, the EP and DSC functional entities start a status update timer.

The EP sends a status update request to the DSC functional entity after the status update timer expires, where the status update request may include a temporary identification of the EP.

And after receiving the state updating request, the DSC functional entity determines the corresponding EP according to the temporary identification of the EP and updates the context information corresponding to the EP.

the DSC functional entity, after updating the context information of the EP, may send a status update response to the EP, which may include a temporary identification of the EP.

optionally, after updating the context information of the EP, the EP may further notify the core network to update the corresponding cluster information.

Optionally, the DSC functional entity may maintain two state update timers T1 and T2 for the corresponding EP, and if a state update request of the corresponding EP is not received after the state update timer T1 times out, the DSC functional entity may consider that the EP is in an attachment abnormal state, and release the terminal context after the state update timer T2 times out.

In implementation, if after T1 times out, T2 receives a status update request for time out, the embodiment of the present invention provides a processing method:

since the T1 timeout DSC functional entity sets the state of the terminal to "abnormal" state (in abnormal state, the DSC functional entity may suspend providing data transfer service to the terminal), after the T1 timeout, when T2 receives a state update request for timeout, the DSC functional entity resets the state information of the terminal to "normal" state.

Alternatively, the state update timer T2 may be started after the state update timer T1 times out. The state update timer T2 may also be started along with the state update timer T1 if the duration of the state update timer T2 is greater than the duration of the state update timer T1.

And fourthly, triggering the service activation by the EP.

The EP sends a service activation request to the DSC functional entity when a new service needs to be activated, wherein the request can comprise service identification and/or terminal type information;

correspondingly, the DSC functional entity determines the service activated by the EP request according to the received service identification or terminal type information from the EP;

And if the EP requests that the activated service is authorized, storing the EP activation service information into the context information of the EP.

If the service activated by the EP request is not authorized, the DSC functional entity may make a service authorization request to the core network, if the core network authorizes the service, the EP activation service information is stored in the context information of the EP, and if the core network does not authorize the service, the DSC functional entity will not start the related function.

For example, factory a user has signed up for service using the MESH network to connect robots within the factory, but in practice factory a has used this subscription in cars to connect sensors, in which case the service will not be authorized for use by the core network.

optionally, if the EP requests the activated service authorization, the DSC functional entity may send a service activation response to the EP;

Correspondingly, the EP returns a service activation completion message to the terminal after receiving the message.

and fifthly, triggering service deactivation by the EP.

The EP sends a service deactivation request to the DSC functional entity when the service needs to be deactivated, wherein the request can comprise service identification and/or terminal type information;

And after receiving the service deactivation request, the DSC functional entity updates the activated service information stored in the context information of the EP.

optionally, after receiving the service deactivation request, the DSC functional entity may further determine whether the authorization service needs to be updated, and if so, notify the core network to update the authorization service.

For example, if the DSC functional entity authorization list includes (video real-time backhaul service), and there is no terminal that activates the service in the cluster that the DSC functional entity is responsible for managing, the DSC functional entity may initiate a cluster (group) service authorization update process to the core network to update the DSC functional entity authorization service list.

optionally, after updating the activated service information stored in the context information of the EP, the DSC functional entity may further send a service deactivation command to the EP;

accordingly, the EP may return a service deactivation complete message to the DSC functional entity.

and sixthly, triggering service deactivation by the core network.

After the authorization of part or all of services authorized by some DSC functional entities is overtime or invalid, the core network equipment initiates a cluster service authorization updating process to the DSC functional entities.

Correspondingly, after the core network informs that the authorization service needs to be updated, the DSC functional entity updates the authorization service of the corresponding cluster.

Optionally, if the failed service is an activated service, the activated service needs to be deactivated.

Specifically, after the core network notifies that an authorization service needs to be updated, the DSC functional entity determines whether a service activated by an EP in a cluster needs to be deactivated, and if so, sends a service deactivation command to the EP;

Correspondingly, after receiving the service deactivation command, the EP returns a service deactivation completion message.

And after receiving the service deactivation completion message, the DSC functional entity updates the activated service information stored in the context information of the EP.

As shown in fig. 4, the first DSC functional entity of the embodiment of the present invention includes: a first determination module 400 and a management module 401.

A first determining module 400, configured to determine to obtain core network authorization;

a management module 401, configured to manage EPs in a cluster, where a DSC function entity is connected to each EP in a corresponding cluster.

Optionally, the management module 401 is specifically configured to

optionally, the management module 401 is further configured to:

Optionally, the management module 401 is further configured to:

Optionally, the management module 401 is specifically configured to:

deleting context information of the EP in the EP detach process.

optionally, the management module 401 is further configured to:

optionally, the management module 401 is specifically configured to:

optionally, the management module 401 is further configured to:

optionally, the management module 401 is specifically configured to:

Optionally, the management module 401 is further configured to:

Optionally, the management module 401 is specifically configured to:

optionally, the management module 401 is further configured to:

The EP is a mobile terminal or wearable or machine-like device.

As shown in fig. 5, a first core network device according to an embodiment of the present invention includes: a second determination module 500 and a processing module 501.

a second determining module 500, configured to determine a DSC functional entity that needs to be authorized;

a processing module 501, configured to authorize the determined DSC functional entity to enable the DSC functional entity to manage the EPs in the cluster, where the DSC functional entity is connected to each EP in the corresponding cluster.

Optionally, the processing module 501 is further configured to:

as shown in fig. 6, the second DSC functional entity in the embodiment of the present invention includes:

The processor 601, configured to read the program in the memory 604, executes the following processes:

Determining to obtain core network authorization; managing the EPs in the cluster, wherein a DSC functional entity is connected to each EP in the corresponding cluster.

a transceiver 602 for receiving and transmitting data under the control of the processor 601.

optionally, the processor 601 is specifically configured to

Optionally, the processor 601 is further configured to:

optionally, the processor 601 is specifically configured to:

Deleting context information of the EP in the EP detach process.

Optionally, the processor 601 is further configured to:

Optionally, the management module 401 is specifically configured to:

Optionally, the processor 601 is specifically configured to:

Optionally, the processor 601 is further configured to:

Optionally, the processor 601 is specifically configured to:

Optionally, the processor 601 is further configured to:

Optionally, the processor 601 is specifically configured to:

Optionally, the processor 601 is further configured to:

The EP is a mobile terminal or wearable or machine-like device.

in fig. 6, a bus architecture (represented by bus 600), bus 600 may include any number of interconnected buses and bridges, and bus 600 links together various circuits including one or more processors, represented by processor 601, and memory, represented by memory 604. The bus 600 may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface 603 provides an interface between the bus 600 and the transceiver 602. The transceiver 602 may be one element or may be multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 601 is transmitted over a wireless medium via the antenna 605, and further, the antenna 605 receives the data and transmits the data to the processor 601.

The processor 601 is responsible for managing the bus 600 and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 604 may be used to store data used by processor 601 in performing operations.

alternatively, the processor 601 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).

As shown in fig. 7, a second core network device according to the embodiment of the present invention includes:

A processor 701, configured to read the program in the memory 704, and execute the following processes:

Determining a DSC functional entity needing authorization; the determined DSC functional entity is authorized by the transceiver 702 to manage the EPs in the cluster, wherein the DSC functional entity is connected with each EP in the corresponding cluster.

A transceiver 702 for receiving and transmitting data under the control of the processor 701.

Optionally, the processor 701 is further configured to:

in fig. 7, a bus architecture (represented by bus 700), bus 700 may include any number of interconnected buses and bridges, bus 700 linking together various circuits including one or more processors, represented by processor 701, and memory, represented by memory 704. The bus 700 may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface 703 provides an interface between the bus 700 and the transceiver 702. The transceiver 702 may be one element or multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. Data processed by processor 701 is transmitted over a wireless medium via antenna 705, which antenna 705 receives data and transmits data to processor 701.

The processor 701 is responsible for managing the bus 700 and general processing, and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 704 may be used to store data used by processor 701 in performing operations.

Alternatively, the processor 701 may be a CPU, ASIC, FPGA or CPLD.

Based on the same inventive concept, the embodiment of the present invention further provides a method for managing a terminal, and since the device corresponding to the method is a device in the system for managing a terminal in the embodiment of the present invention, and the principle of the method for solving the problem is similar to that of the system, the implementation of the method can refer to the implementation of the system, and repeated details are not repeated.

As shown in fig. 8, a first method for managing a terminal according to an embodiment of the present invention includes:

Step 801, a DSC functional entity determines to obtain core network authorization;

step 802, the DSC functional entity manages the EPs in the cluster, wherein the DSC functional entity is connected to each EP in the corresponding cluster.

optionally, the DSC functional entity manages EPs in the cluster, including:

Optionally, the DSC functional entity manages EPs in the cluster, including:

optionally, the method further includes:

optionally, the DSC functional entity manages EPs in the cluster, including:

Optionally, the DSC functional entity manages EPs in the cluster, including:

optionally, the DSC functional entity manages EPs in the cluster, including:

Optionally, the DSC functional entity manages EPs in the cluster, including:

The EP is a mobile terminal or wearable or machine-like device.

As shown in fig. 9, a second method for managing a terminal according to the embodiment of the present invention includes:

Step 901, the core network device determines a DSC functional entity that needs to be authorized;

step 902, the core network device authorizes the determined DSC functional entity, so that the DSC functional entity manages the EPs in the cluster, where the DSC functional entity is connected to each EP in the corresponding cluster.

The following describes in detail the management of an EP in a cluster by a DSC functional entity according to the present invention, taking an EP as a terminal, by way of a few examples.

First, as shown in fig. 10, an Attach (Attach) network procedure of a terminal according to an embodiment of the present invention is described.

For the attachment process, because the terminal is invisible to the core network, the core network does not store the subscription information of the terminal in advance, so the access control and authentication functions of the terminal are managed by the DSC functional entity, for example, a factory manager manually configures the authentication information of the sensor type terminal to the DSC functional entity, and the DSC functional entity controls the access of the terminal (including performing authentication in the terminal access process), and a security scheme adopted between the sensor type terminal and the DSC functional entity can be customized by a factory user (so the security mechanism adopted by the terminal and the DSC functional entity can not be controlled by an operator).

step 1: the DSC functional entity sends system broadcast information in a broadcast mode, wherein the system broadcast information can carry a network identifier, a DSC functional entity identifier, DSC functional entity support service list information, configuration information required by a terminal to initiate an access process and the like.

Step 2: the terminal performs a network selection process according to the broadcast message, the type of the device and the type of the network to be accessed, and initiates a network access process according to the access configuration information obtained from the system broadcast message after completing the network selection. In the network access process, the terminal sends an attachment request message to the DSC functional entity, where the attachment request message carries the fixed identification information of the terminal and the terminal identity authentication information.

And step 3: and the DSC functional entity verifies the validity of the terminal identity according to the terminal identity verification information received from the terminal and the fixed identification information of the terminal.

And 4, step 4: after the terminal identity passes the validity verification, the DSC functional entity sends an attachment response message to the terminal, wherein the attachment response message carries a temporary identifier distributed by the DSC functional entity for the terminal and the identity verification information of the DSC functional entity, and can also carry terminal fixed identifier information to assist the terminal in downlink receiving of the message.

And 5: and the terminal verifies the validity of the accessed DSC functional entity according to the received DSC functional entity identity verification information.

Step 6: and after the terminal completes the validity verification of the DSC functional entity, the terminal sends an attachment completion message to the DSC functional entity, and can also simultaneously carry a terminal temporary identifier to help the DSC functional entity to determine the terminal information.

Optionally, the terminal may also start a status update timer.

And 7: and after receiving the attachment completion message, the DSC functional entity indexes the context established locally by the terminal according to the terminal temporary identifier and updates the state of the terminal to be successfully attached. And the DSC functional entity starts a state update timer for the terminal.

And 8: and the DSC functional entity updates the information of the number of the currently accessed terminals and sends the information of the number of the accessed terminals to the core network through the cluster information updating process.

Second, as shown in fig. 11, the terminal triggers a Detach (Detach deregistration) process according to an embodiment of the present invention.

step 1: before the terminal is removed or powered off, a detach (or log-off) procedure is triggered.

step 2: the terminal sends a detach request message to the DSC function entity, where the terminal temporary identity may be carried.

and step 3: the DSC functional entity deletes the context information of the terminal.

And 4, step 4: the DSC functional entity sends an attach response message to the terminal, where the terminal temporary identity can be carried.

And 5: and the DSC functional entity updates the information of the number of the currently accessed terminals and sends the information of the number of the accessed terminals to the core network through the cluster information updating process.

third, as shown in fig. 12, the terminal touch periodic status update process according to the embodiment of the present invention.

after the terminal successfully attaches to the network, the terminal and the DSC functional entity will respectively start a status update timer. The terminal initiates a state updating process to the network after the timer is overtime, if the DSC functional entity does not receive the state updating message of the terminal after the timer T1 is overtime, the DSC functional entity considers that the terminal is in an attachment abnormal state, and implicitly releases the terminal context after the timer T2 is overtime.

Step 1: and after the state updating timer is overtime, the terminal triggers a periodic state updating process.

Step 2: the terminal sends a status update request message to the DSC functional entity, and can simultaneously carry the temporary identifier of the terminal.

and step 3: and the DSC functional entity determines the context of the terminal according to the temporary identifier of the terminal and updates the state information of the terminal in the context of the terminal. For example, the timing T1 is reset, i.e., updated, and the terminal status is set to "abnormal" (in the case where the terminal is in the "abnormal" state, the network may stop providing the communication service to the terminal).

and 4, step 4: and the DSC functional entity sends a state updating response message to the terminal and can simultaneously carry the temporary identifier of the terminal.

And 5: if the terminal does not receive the status update message from the terminal after a period of time T2 after the status update timer T1 expires, the DSC functional entity considers that the terminal implicitly leaves the network.

optionally, after determining that the terminal implicitly leaves the network, the DSC functional entity may locally release the terminal context, and initiate a cluster (group) information update process to the core network, for example, update the information of the number of terminals in the cluster.

example four, as shown in fig. 13, the terminal triggers a service Activation (Activation) process according to the embodiment of the present invention.

Step 1: the terminal initiates a service activation request under the condition that a new service needs to be activated, and carries service identification information or terminal type information through a service request message.

for example, the terminal is a camera device and requests a real-time video return service; for another example, the terminal is a sensor and requests real-time return service for data samples acquired by the sensor.

step 2: the DSC functional entity determines whether it is authorized by the core network to provide corresponding services (e.g. real-time video backhaul) to the members in the cluster. If authorized, directly executing step 4; otherwise, executing step 3.

And step 3: if the DSC functional entity is not authorized by the core network to provide corresponding services (such as real-time video backhaul) for the members in the cluster, the DSC functional entity initiates a cluster service authorization update request process to the core network. The core network will indicate whether the DSC functional entity can provide a new service type within the cluster. The core network records the cluster-activated traffic types managed by the DSC functional entity. The DSC functional entity updates the cluster authorization service list information stored locally. If not, rejecting the service request of the terminal; and if the core network authorization is obtained, executing the step 4.

And 4, step 4: if the DSC functional entity obtains the authorization of the core network to provide the corresponding service type (such as real-time video backhaul), the DSC functional entity sends a service activation response message to the terminal. And may carry the terminal temporary identification information for terminal reception.

And 5: and after the service is activated, the terminal sends a service activation completion message to the DSC functional entity and carries the terminal temporary identifier.

step 6: and the DSC functional entity updates the state information of the terminal activation service in the locally stored terminal context.

in a fifth embodiment, as shown in fig. 14, the MTC terminal initiates a service Deactivation (Deactivation) process in the embodiment of the present invention.

Step 1: after deciding to deactivate the service, the terminal sends a service deactivation request to the DSC functional entity, which can carry service identification information or terminal type information. In addition, the terminal temporary identification information can be carried to help the DSC functional entity to identify the terminal.

step 2: and the DSC functional entity determines the service type which needs to be deactivated by the terminal according to the service identifier or the terminal type, and updates the terminal activation service type information stored in the terminal context.

And step 3: and the DSC functional entity sends a service deactivation command to the terminal, wherein the temporary identification information of the terminal can be carried.

And 4, step 4: the terminal sends a service activation completion message to the DSC functional entity, wherein the terminal temporary identification information can be carried.

and 5: the DSC functional entity judges whether the authorization service list needs to be updated, if so, a cluster (group) service authorization updating process is initiated to the core network, and the DSC functional entity authorization service list is updated.

For example, if the (video real-time backhaul service) is included in the DSC functional entity authorization list, and there is no terminal activating the service in the cluster managed by the DSC functional entity, the DSC functional entity may initiate a cluster (group) service authorization update process to the core network to update the DSC functional entity authorization service list.

Step 6: and the DSC functional entity initiates a cluster (group) service authorization updating process to the core network after determining to update the authorization service list information.

Sixth, as shown in fig. 15, a service deactivation process triggered by a core network according to an embodiment of the present invention.

Step 1: in a case where a part or all of the service authorization authorized by the core network for a specific DSC functional entity is overtime or invalid (for example, in a case where the time-based service authorization is overtime or a user account corresponding to the DSC functional entity is owed), the core network may initiate a cluster service authorization update procedure.

step 2: and the DSC functional entity locally stores the updated cluster service authorization information.

and step 3: and the DSC functional entity judges whether a cluster terminal activates unauthorized services or not. If the activated service of which the terminal is not authorized is still in the activated state, the DSC functional entity triggers a service deactivation process aiming at the specific terminal.

And 4, step 4: and the DSC functional entity sends a service deactivation command to the terminal.

if the terminal activates a plurality of services at the same time, the terminal can carry the identification information of the deactivated services. In addition, the terminal temporary identifier can be carried to be used for the terminal to judge whether the message is directed to the terminal.

And 5: after the service deactivation is completed, the terminal sends a service deactivation completion message to the DSC functional entity, and can carry the terminal temporary identification information.

Step 6: and after receiving the service deactivation completion message, the DSC functional entity updates the service activation information in the locally stored terminal context.

From the above, it can be seen that: in the embodiment of the invention, after determining that the core network authorization is obtained, the DSC functional entity manages the EP in the cluster, wherein the DSC functional entity is connected with each EP in the corresponding cluster. Since the DSC functional entity manages the EP in the cluster, the burden on the core network is not increased after the number of machine type terminals is increased, thereby avoiding the signaling storm caused by the overlarge burden of the core network.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A method for managing a terminal, the method comprising:

A distributed service center DSC functional entity determines to obtain core network authorization;

the DSC functional entity manages the end node EP in the cluster, coordinates communication with other adjacent clusters and performs interference management, wherein the DSC functional entity is connected with each EP in the corresponding cluster;

Wherein the DSC functional entity manages the EP in the cluster, and comprises the following steps:

The DSC functional entity performs identity authentication on the EP when the EP is attached, and establishes context information of the EP after the authentication is passed; after the DSC functional entity passes the verification, the DSC functional entity also comprises:

the DSC functional entity informs the core network of updating corresponding cluster information through a backhaul network;

The DSC functional entity is one of the following devices positioned at the side of the access network:

a terminal, a base station, a server, or a distributed service center.

2. The method of claim 1, wherein the DSC functional entity further comprises, prior to the EP performing an attachment procedure:

3. the method of claim 1, wherein the DSC functional entity manages EPs in a cluster, comprising:

4. the method of claim 3, further comprising:

5. the method of claim 1, wherein the DSC functional entity manages EPs in a cluster, comprising:

6. The method of claim 1, wherein the DSC functional entity manages EPs in a cluster, comprising:

7. The method according to claim 6, wherein the DSC functional entity determines the service requested to be activated by the EP according to the received service identifier or terminal type information from the EP, further comprising:

8. The method of claim 1, wherein the DSC functional entity manages EPs in a cluster, comprising:

9. the method of claim 8, wherein the DSC functional entity, after the EP requests to deactivate traffic, further comprises:

10. the method of claim 1, wherein the DSC functional entity manages EPs in a cluster, comprising:

11. The method of claim 10, wherein the DSC functional entity, after updating the authorization traffic of the corresponding cluster, further comprises:

12. The method according to any of claims 1 to 11, wherein the DSC functional entity is a mobile terminal or base station type device or server type device or distributed service center; and/or

The EP is a mobile terminal or wearable or machine-like device.

13. A method for managing a terminal, the method comprising:

the core network equipment authorizes the determined DSC functional entity so that the DSC functional entity manages the EP in the cluster, coordinates communication with other adjacent clusters and performs interference management, wherein the DSC functional entity is connected with each EP in the corresponding cluster;

After the core network device authorizes the determined DSC functional entity, the method further includes:

and the core network equipment updates the cluster information corresponding to the DSC functional entity according to the received cluster information notified by the DSC functional entity through the return network.

14. A DSC functional entity that manages a terminal, the DSC functional entity comprising:

A management module, configured to manage EPs in a cluster, coordinate communication with other neighboring clusters, and perform interference management, where a DSC functional entity is connected to each EP in a corresponding cluster;

wherein the management module is specifically configured to:

When the EP is attached, carrying out identity authentication on the EP, and establishing context information of the EP after the authentication is passed;

The management module is further configured to:

after the verification is passed, notifying the core network to update the corresponding cluster information through a return network;

A terminal, a base station, a server, or a distributed service center.

15. The DSC functional entity of claim 14, wherein the management module is further configured to:

16. The DSC functional entity of claim 14, wherein the management module is specifically configured to:

Deleting context information of the EP in the EP detach process.

17. The DSC functional entity of claim 16, wherein the management module is further configured to:

18. The DSC functional entity of claim 14, wherein the management module is specifically configured to:

19. the DSC functional entity of claim 14, wherein the management module is specifically configured to:

20. the DSC functional entity of claim 19, wherein the management module is further configured to:

21. The DSC functional entity of claim 14, wherein the management module is specifically configured to:

22. the DSC functional entity of claim 21, wherein the management module is further configured to:

23. the DSC functional entity of claim 14, wherein the management module is specifically configured to:

24. The DSC functional entity of claim 23, wherein the management module is further configured to:

25. a DSC functional entity according to any of claims 14 to 24, wherein the DSC functional entity is a mobile terminal or base station type device or server type device or distributed service center; and/or

the EP is a mobile terminal or wearable or machine-like device.

26. a core network device for managing a terminal, the core network device comprising:

A processing module, configured to authorize the determined DSC functional entity, so that the DSC functional entity manages EPs in a cluster, coordinates communication with other neighboring clusters, and performs interference management, where the DSC functional entity is connected to each EP in a corresponding cluster;

Wherein the processing module is further configured to:

and after the determined DSC functional entity is authorized, updating cluster information corresponding to the DSC functional entity according to the received cluster information notified by the DSC functional entity through a return network.