CN113573336A

CN113573336A - Communication management and control method and device

Info

Publication number: CN113573336A
Application number: CN202110786128.5A
Authority: CN
Inventors: 李延斌; 马瑞涛
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2021-07-12
Filing date: 2021-07-12
Publication date: 2021-10-29
Anticipated expiration: 2041-07-12
Also published as: CN113573336B

Abstract

The invention discloses a communication management and control method and equipment, relates to the technical field of communication, and aims to improve the effectiveness of communication management and control. The specific scheme is as follows: after network management and control are started, network equipment sends a first logout message to terminal equipment, the terminal equipment receives the first logout message sent by the network equipment, the first logout message is used for indicating the reason for executing logout of the terminal equipment, and the first logout message comprises a management and control parameter used for indicating a management and control object; determining whether the terminal equipment accepts control or not according to the control parameters in the first logout message and the characteristic information (equipment type or user category and the like) of the terminal equipment; if the terminal equipment receives control, logging out the network and then re-initiating registration to the network equipment; and if the terminal equipment does not accept the control, sending a rejection message to the network equipment.

Description

Communication management and control method and device

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for managing and controlling communications.

Background

The network security act stipulates that temporary measures such as management and control can be taken for a communication network in a specific area due to the requirements of maintaining national security and social public order and handling major sudden social security events. When communication management and control are usually implemented, a special government organization issues management and control requirements to an operator through a communication management bureau, and provides information such as areas, services, management and control users, guarantee users and the like which need to be managed and controlled.

At present, after receiving a control command, an operator issues the control command to an access network element in the area, the access network element notifies all users under its coverage of logout of the network through a logout flow, and then a terminal initiates a registration flow again, so that the access network element accurately controls the users according to the control command.

However, the access network element notifies all users under its coverage to log off the network through the log-off process, so that all types of users can execute the log-off and log-on processes. The user (such as the car networking device) who does not need to perform management and control executes the process completely meaningless, which may cause network resource waste, low validity of communication management and control, and bad social influence, even safety problems.

Disclosure of Invention

The invention provides a communication management and control method and equipment, which are used for improving the effectiveness of communication management and control.

In order to achieve the purpose, the invention adopts the following technical scheme:

in a first aspect, the present invention provides a communication management and control method, which may include:

the terminal device receives a first logout message sent by the network device, where the first logout message is used to execute a reason for logout, the first logout message includes a control parameter for indicating a control object, and the control parameter may include a control type, or the control parameter may include a control type and a control strength; the terminal equipment determines whether the terminal equipment receives management and control according to the management and control type and the characteristic information of the terminal equipment; wherein the characteristic information is used for indicating the type of the equipment or the category of the user; if the terminal equipment receives control, the terminal equipment logs out of the network and then initiates registration to the network equipment again; and if the terminal equipment does not accept the control, the terminal equipment sends a rejection message to the network equipment.

In a second aspect, the present invention provides a communication management method, which may include:

the network device sends a first logout message to the terminal device, where the first logout message is used to indicate a reason for performing logout, the first logout message includes a control parameter used to indicate a control object, and the control parameter may include a control type, or the control parameter may include a control type and a control strength; the network equipment receives the registration initiated after the managed and controlled terminal equipment logs off the network; or the network equipment receives a rejection message sent by the terminal equipment which does not accept the control.

In a third aspect, the present invention provides a terminal device, which may include:

a receiving unit, configured to receive a first logout message sent by a network device, where the first logout message is used to indicate a reason for performing logout, and the first logout message includes a control parameter used to indicate a control object, where the control parameter includes a control type, or the control parameter includes a control type and a control strength.

And the determining unit is used for determining whether the terminal equipment accepts the management and control according to the management and control type and the characteristic information of the terminal equipment. Wherein the characteristic information is used to indicate a device type or a user category.

And the processing unit is used for initiating registration to the network equipment again after logging off the network if the determining unit determines that the terminal equipment receives management and control.

And the sending unit is used for sending a rejection message to the network equipment if the determining unit determines that the terminal equipment does not accept the management and control.

In a fourth aspect, the present invention provides a network device, which may include:

a sending unit, configured to send a first logout message to a terminal device, where the first logout message is used to indicate a reason for performing logout, and the first logout message includes a control parameter used to indicate a control object, where the control parameter includes a control type, or the control parameter includes a control type and a control strength.

The receiving unit is used for receiving registration initiated after the terminal equipment which receives management and control logs off the network; or receiving a rejection message sent by the terminal device which does not accept the control.

In a fifth aspect, the present invention provides a communication device, comprising: the communication management and control system comprises a memory and a processor, wherein the memory is used for storing a computer program, and the processor is used for calling the computer program to execute the communication management and control method.

In a sixth aspect, the present invention provides a computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, and when the computer program runs on a computer, the computer is caused to execute the above communication management method.

In a seventh aspect, the present invention provides a computer program product, wherein the computer program product comprises computer instructions, which when run on a computer, cause the computer to execute the above communication management method.

According to the communication management and control method and device, the management and control parameter is carried in the first logout message, the terminal device determines whether to accept the management and control according to the management and control type in the management and control parameter, the network is logged out to initiate the registration again under the condition that the management and control are determined to be accepted, the management and control can be refused when the management and control are determined not to be accepted, and compared with the situation that the network is logged out by all users under the coverage of the current network device, the terminal device autonomously determines whether to accept the management and control, so that the users without the management and control are prevented from being managed and controlled, and the effectiveness of communication management and control is improved.

These and other aspects of the present application will be more readily apparent from the following description.

Drawings

FIG. 1 is a flow chart diagram of a communication management;

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

fig. 3 is a schematic diagram illustrating a network device according to an embodiment of the present application;

fig. 4 is a schematic composition diagram of a terminal device according to an embodiment of the present application;

fig. 5 is a flowchart of a communication management and control method according to an embodiment of the present application;

fig. 6 is a flowchart of another communication management and control method according to an embodiment of the present application;

fig. 7 is a schematic diagram of a communication management and control flow according to an embodiment of the present application;

fig. 8 is a block diagram of a terminal device according to an embodiment of the present disclosure;

fig. 9 is a block diagram of another terminal device according to an embodiment of the present disclosure;

fig. 10 is a block diagram of a network device according to an embodiment of the present application;

fig. 11 is a block diagram of another network device according to an embodiment of the present disclosure;

fig. 12 is a block diagram of another network device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present invention, "a plurality" means two or more unless otherwise specified.

For ease of understanding, examples are given in part to illustrate concepts related to embodiments of the present application.

The method provided in the embodiment of the present application may be applied to a communication system of any standard, where the communication system may be a 3rd generation partnership project (3 GPP) communication system, for example, a Long Term Evolution (LTE) system, a 5G mobile communication system, a New Radio (NR) system, or a non-3 GPP communication system, and is not limited.

Fig. 1 shows a simplified schematic diagram of a communication system architecture to which embodiments of the present invention may be applied. As shown in fig. 1, the communication system may include: a (radio) access network (R) AN device, a terminal, a core network, a Data Network (DN), etc.

In the communication system shown in fig. 1, (R) AN access network equipment is used to implement radio access related functions, providing AN access network within its coverage area. The terminal can access the core network through the access network provided by the (R) AN access network equipment, and then access the DN to complete the interaction of the service data.

The (R) AN device may be a base station, a broadband network service gateway (BNG), a convergence switch, a non-3 GPP access device, or the like. The base stations may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, etc. The embodiment of the present application is not particularly limited to this. For example, the access network device may be an evolved universal terrestrial radio access network (E-UTRAN) device in a fourth generation mobile communication technology (4th generation, 4G) network, a next generation radio access network (NG-RAN) device in a 5G network, an evolved Node B (eNodeB), a WIFI access Node (AP), a global interoperability for microwave access (max) Base Station (BS), and the like.

A terminal equipment (terminal equipment), which may be referred to as a User Equipment (UE) or a terminal (terminal) equipment. Obviously, the terminal of each area shown in fig. 1 may include, but is not limited to, a vehicle-mounted terminal, a mobile phone (mobile phone), a tablet computer or a computer with wireless transceiving function, an intelligent gas station, an intelligent signal lamp, and the like.

At present, when communication management and control are implemented, a special government organization issues management and control requirements to an operator through a communication management bureau, and provides information such as areas, services, management and control users and guarantee users which need to be managed and controlled. The operator manually or automatically implements communication management according to the above information.

In connection with the communication system shown in fig. 1, the current communication management and control flow may be as shown in fig. 2. As shown in fig. 2, AN operator network management platform receives a management and control command, where the management and control command requires to limit a specific service of a specific user in a specific area, and the network management platform issues the management and control command to (R) AN equipment in the area through a command or manually, and the (R) AN equipment notifies a UE in a coverage area to register through a Deregistration (Deregistration) procedure and then re-initiates a registration procedure. After UE deregisters, initiating a new Registration request (Registration request), (R) AN equipment forwarding the Registration request (Registration request) to a core network element, and in the interaction process of the (R) AN equipment and the core network equipment, accurately managing and controlling a user according to a management and control scheme.

The core network element illustrated in fig. 2 may include an access and mobility management function (AMF), a Session Management Function (SMF), and a User Plane Function (UPF)

As can be easily found from the management and control flow illustrated in fig. 2, the (R) AN apparatus notifies all types of users (a type users and B type users) through the registration flow, and then both the a type users and the B type users initiate the registration flow again, that is, all types are managed and controlled in communication. However, managing and controlling users who do not need to be managed and controlled (for example, a-type users) leads to waste of social resources, adverse social effects, and even security problems.

In order to solve the above problems, the present application provides a communication management and control method and device, where a first logout message carries a management and control type, a terminal device determines whether to accept management and control according to the management and control type, and logs out a network to reinitiate registration if it is determined that management and control are accepted, and may refuse management and control if it is determined that management and control are not accepted. Therefore, whether management and control are required to be accepted or not is confirmed by the terminal equipment, so that management and control of users who do not need management and control are avoided, and effectiveness of communication management and control is improved.

Fig. 3 is a schematic composition diagram of a network device according to an embodiment of the present application. As shown in fig. 3, the network device 30 may include at least one processor 31, a memory 32, a communication interface 33, and a communication bus 34.

The following describes each component of the network device 30 in detail with reference to fig. 3:

the processor 31 is a control center of the communication device, and may be a single processor or a collective term for a plurality of processing elements. For example, the processor 31 is a Central Processing Unit (CPU), or may be an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as: one or more microprocessors (digital signal processors, DSPs), or one or more Field Programmable Gate Arrays (FPGAs).

The processor 31 may perform various functions of the communication device as a network controller or a network device by running or executing software programs stored in the memory 32 and calling data stored in the memory 32.

In particular implementations, processor 31 may include one or more CPUs such as CPU0 and CPU1 shown in fig. 3 as one example.

In a specific implementation, the communication device may include a plurality of processors, and each of the processors may be a single-Core Processor (CPU) or a multi-Core Processor (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 32 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) 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 32 may be self-contained and coupled to the processor 31 via a communication bus 34. The memory 32 may also be integrated with the processor 31.

The memory 32 is used for storing software programs for executing the scheme of the application, and is controlled by the processor 31 to execute.

The communication interface 33 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc. The communication interface 33 may include a receiving unit implementing a receiving function and a transmitting unit implementing a transmitting function.

The communication bus 34 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 3, but this does not mean only one bus or one type of bus.

The device architecture shown in fig. 3 does not constitute a limitation of the network controller and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

Fig. 4 is a schematic diagram of a terminal device 40 according to an embodiment of the present disclosure, and as shown in fig. 4, the terminal device 40 may include at least one processor 41, a memory 42, a display 43, and a transceiver 44.

The following specifically describes each constituent component of the terminal device 40 with reference to fig. 4:

the processor 41 is a control center of the terminal device 40, and may be a single processor or a collective term for a plurality of processing elements. For example, the processor 31 is a CPU, an ASIC, or one or more integrated circuits configured to implement embodiments of the present application, such as: one or more DSPs, or one or more FPGAs. The processor 41 may perform various functions of the terminal by running or executing software programs stored in the memory 42, and calling data stored in the memory 42, among others.

In particular implementations, processor 41 may include one or more CPUs such as CPU0 and CPU1 shown in fig. 4 as one example.

In one embodiment, the mobile terminal may include a plurality of processors, and each of the processors may be a single-CPU processor or a multi-CPU processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

Memory 42 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, 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 42 may be self-contained and coupled to the processor 41 via a communication bus 44. The memory 42 may also be integrated with the processor 41. The memory 42 is used for storing software programs for executing the scheme of the application, and is controlled by the processor 41 to execute.

The display 43 may be used to display information input by or provided to the user as well as various menus for the terminal device 40. The display 43 may include a display panel, and may be configured in the form of a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), or the like.

The transceiver 44, using any transceiver or like device, is used to communicate with other devices or communication networks, such as ethernet, RAN, WLAN, etc. The transceiver 44 may include a receiving unit to implement the receiving function and a transmitting unit to implement the transmitting function.

The mobile terminal structure shown in fig. 4 does not constitute a limitation of the mobile terminal and may include more or fewer components than those shown, or some of the components may be combined, or a different arrangement of components. Although not shown, the mobile terminal may further include a battery, a camera, a bluetooth module, a Global Positioning System (GPS) module, and the like, which are not described in detail herein.

As shown in fig. 5, an embodiment of the present application provides a communication management and control method, which may include:

s501, after the network management and control is started, the network equipment sends a first logout message to the terminal equipment.

The network device may be an access network device or a core network device of a communication system, and an implementation subject of the embodiment of the present application is not limited. When the network device executing the present application is a core network device, it should be understood that the core network device may communicate with the terminal device through the access network device, and details of the process of communicating with the terminal device through the access network device are omitted in this embodiment of the present application.

Wherein the first de-registration message is used to indicate a reason for performing de-registration. The first deregistration message may include a regulating parameter indicating a regulating object. The embodiment of the present application does not limit the content of the control parameter.

Optionally, the management parameter may include a management type.

The management and control type is used for indicating the type of the target equipment managed and controlled by the network this time.

Optionally, the management parameters may include a management type and a management intensity.

The management and control strength is used for indicating the strength of the network management and control, the management and control strength can indicate that all terminal devices need to be managed and controlled, or the management and control strength can indicate that whether the network management and control is accepted or not by the terminal devices according to the self-help judgment of the management and control types.

For example, the light control intensity may be represented in a number or other forms, which is not limited in the embodiments of the present application.

For example, different strength of regulation may be indicated by assigning different values to the "lev" field. For example, lev-0 represents mandatory acceptance of regulation, and lev-1 represents determination of whether or not to accept regulation by the terminal device.

Specifically, the first logout message is sent after determining that network security management and control are required. For example, the registration message illustrated in fig. 2 may be a registration message, and the management and control type may be a mobile device, a vehicle-mounted device, an internet of things, and the like, which is not specifically limited in the embodiment of the present invention.

It should be noted that, before the network device sends the first logout message to the terminal device, the method may further include: the communication management bureau firstly issues a communication management and control requirement to an operator network management platform, wherein the communication management and control requirement comprises information of a management and control area, a management and control service, a management and control type, a guarantee user and the like, and then the operator network management platform triggers the network equipment to execute S501 according to the management and control type in the communication management and control requirement, so that the network equipment in the area sends a first logout message to the terminal equipment in the coverage area range of the network equipment.

S502, the terminal equipment receives a first logout message sent by the network equipment.

It should be noted that if the first logout message indicates that the terminal device determines whether to accept the management control, S503 is executed after S502. For example, the first logout message does not include the strength of management and control, or the first logout message includes the strength of management and control indicating that the terminal device determines whether to accept management and control, then S503 is executed after S502.

If the first logout message indicates to enforce acceptance of management and control, after S502, S504 is executed, and the process is ended. For example, the first logout message includes a control strength indicating that the control is forcibly accepted, and then the process ends after executing S504 after S502.

S503, the terminal equipment determines whether the terminal equipment accepts management and control according to the management and control parameters and the characteristic information of the terminal equipment.

Wherein the characteristic information is used for indicating the device type of the terminal device or the user category using the terminal device.

Illustratively, the terminal device may determine the device type by obtaining a Unique Device Identifier (UDID). The device type of the terminal device may specifically be a mobile device, a vehicle network device, an internet of things device, and the like, and the embodiment of the present application is not particularly limited.

For example, the terminal device may determine the user type by obtaining a Subscriber Identity Module (SIM) of a user using the terminal device, or by querying subscription data of the user. The user type of the terminal device may be a common user, a vehicle network user, an internet of things user, and the like, and the embodiment of the present application is not particularly limited.

In an optional embodiment, determining whether the terminal device accepts management and control according to the management and control parameter and the feature information of the terminal device includes: if the characteristic information of the terminal equipment indicates the control type, determining that the terminal equipment receives control; and if the characteristic information of the terminal equipment does not indicate the control type, determining that the terminal equipment does not accept control.

It should be understood that the feature information indicates a management and control type, and may be that the feature information is a management and control type, or that the feature information is a management and control type.

For example, if the control type is a mobile phone capable of calling, after the terminal device receives the first logout message, if the terminal device is the mobile phone capable of calling, it is determined that the terminal device accepts control; and if the terminal equipment is vehicle network equipment or Internet of things equipment, determining that the terminal equipment is not subjected to management and control.

In another optional embodiment, determining whether the terminal device accepts management and control according to the management and control parameter and the feature information of the terminal device includes: if the characteristic information of the terminal equipment indicates the control type and the control white list comprises the user identification of the terminal equipment, determining that the terminal equipment does not accept control; and if the characteristic information of the terminal equipment indicates the control type and the control white list does not include the user identification of the terminal equipment, determining that the terminal equipment receives control. And the control white list comprises user identifications which do not participate in control.

The user identifier may be used to uniquely identify the identity of the user, and the user identifier may specifically be a mobile phone number, a license plate number, a vehicle engine number, or the like.

For example, if the control type is the car networking device, the terminal device determines whether the device type of the terminal device is the car networking device after receiving the first logout message, and if the terminal device is the car networking device and the license plate number of the terminal device is the license plate number in the control white list, the terminal device is determined not to be controlled; and if the terminal equipment is the Internet of vehicles equipment and the license plate number of the terminal equipment is not the license plate number in the control white list, determining that the terminal equipment receives control.

In yet another optional embodiment, determining whether the terminal device accepts management and control according to the management and control parameter and the feature information of the terminal device includes: if the characteristic information of the terminal equipment does not indicate the control type and the control blacklist comprises the user identification of the terminal equipment, determining that the terminal equipment receives control; and if the characteristic information of the terminal equipment does not indicate the control type and the control blacklist does not include the user identification of the terminal equipment, determining that the terminal equipment is not controlled. And the control blacklist comprises user identification for forced control.

For example, if the control type is a mobile device, the terminal device determines whether the device type of the terminal device is the mobile device after receiving the first logout message, and if the device type of the terminal device is not the mobile device and the control blacklist includes the mobile phone number of the terminal device, determines that the terminal device accepts control; and if the equipment type of the terminal equipment is not the control type and the mobile equipment of the terminal equipment is not included in the control blacklist, determining that the terminal equipment is not controlled.

It should be noted that the control white list and the control black list may be configured in advance, may be configured and issued by a communication management office, or configured and issued by an operator, or configured in other manners, which is not limited in this embodiment of the present invention.

Optionally, in S503, if it is determined that the terminal device accepts management, S504 is executed, and if it is determined that the terminal device does not accept management control, S505 is executed.

S504, the terminal device logs off the network and initiates registration to the network device again.

It should be noted that the terminal device may execute S504 according to a communication protocol of a communication system used by the terminal device, and details of the process are not described in this embodiment of the present application.

And S505, the terminal equipment sends a rejection message to the network equipment.

And the refusing message is used for indicating that the terminal equipment does not accept the management and control.

S506, the network equipment receives the rejection message sent by the terminal equipment.

Specifically, after receiving the rejection message, the network device may end the management and control flow of the terminal device.

According to the communication management and control method provided by the embodiment, the management and control type is carried in the first logout message, the terminal device determines whether to accept management and control according to the management and control type, the network is logged out to initiate registration again under the condition that management and control are determined to be accepted, network management and control can be refused when management and control are determined not to be accepted, and compared with the situation that the current network device notifies all users under the coverage of the network to log out the network, the terminal device autonomously determines whether to accept management and control, so that management and control of users without management and control are avoided, and the effectiveness of communication management and control is improved.

In practical applications, there may be malicious evasion of control by the user of the terminal device, and therefore, further optionally, the reject message may include reason information, where the reason information is used to indicate a reason why the terminal device does not accept control. And after receiving the rejection message, the network equipment further determines whether the terminal equipment accepts management and control according to the carried reason information.

Specifically, the reason information may be different management and control types, a management and control type of the terminal device, a user corresponding to the terminal device is a management and control white list user, and the like, which is not specifically limited in this embodiment.

Optionally, as shown in fig. 6, after the network device receives the rejection message sent by the terminal device, the method provided in the embodiment of the present application may further include S507 to S509.

And S507, the network equipment determines whether the terminal equipment which is allowed to send the rejection message is not controlled according to the reason information.

Specifically, after receiving the rejection message sent by the terminal device, the network device first acquires the reason information in the rejection message, if the reason information is of different control types, the network device needs to acquire the feature information of the terminal device, and then compares the feature information of the terminal device with the control types to determine whether the terminal device that is allowed to send the rejection message is not controlled, that is, the network device confirms again whether the terminal device that is sending the rejection message can be controlled, thereby avoiding the behavior of the user of the terminal device that escapes communication control.

In a possible implementation manner, the reject message may carry the feature information of the terminal device, and the network device may obtain the feature information of the terminal device from the reject message.

In a possible implementation manner, the network device may obtain the feature information of the terminal device from the network element that records the user context information. For example, the network element recording the user context information may be a unified data management function (UDM) network element or a unified data repository function (UDR) network element in 5G.

In an optional embodiment, if the reason information is of a different management and control type, determining whether the terminal device is allowed to be not managed and controlled according to the reason information includes: if the characteristic information of the terminal equipment indicates the control type, determining that the terminal equipment is not allowed to be controlled; and if the characteristic information of the terminal equipment does not indicate the control type, determining that the terminal equipment is allowed not to accept control.

In another optional embodiment, if the reason information is of a different management and control type, determining whether the terminal device is allowed to be not managed and controlled according to the reason information includes: if the characteristic information of the terminal equipment does not indicate the control type and the control blacklist includes the user identification of the terminal equipment, determining that the terminal equipment is not allowed to be controlled; and if the characteristic information of the terminal equipment does not indicate the control type and the control blacklist does not include the user identification of the terminal equipment, determining that the terminal equipment is allowed not to be controlled. And the control blacklist comprises user identification for forced control.

In another optional embodiment, if the reason information is a non-management-control user or a white-list user, determining whether to allow the terminal device to be not managed according to the reason information includes: if the control white list comprises the user identification of the terminal equipment, determining that the terminal equipment is allowed not to be controlled; and if the control white list does not include the user identification of the terminal equipment, determining that the terminal equipment is not allowed to be controlled. The control white list comprises user identifications which do not accept control.

It should be noted that the control white list and the control black list may be determined according to a communication control requirement issued by a communication authority, that is, the control white list is determined according to the guaranteed user information in the communication control requirement, and the control black list is determined according to the control user information in the communication control requirement; the user identifiers in the control white list and the control black list may also be manually entered (that is, the user identifiers in the control black list and the control white list are confirmed in advance), and this embodiment is not particularly limited.

It should be noted that the control white list and the control black list described in S507 may be configured in advance, may be configured and issued by a communication management office, or configured and issued by an operator, or configured in other manners, which is not limited in this embodiment of the present application.

It should be further noted that the control white list and the control black list described in S507 may be the same as or different from the control white list and the control black list described in S503, and this is not limited in this embodiment of the present application.

Optionally, in S507, if it is determined that the terminal device that is not allowed to send the rejection message is not managed, then S508, S509, and S510 are executed, and in S507, if it is determined that the terminal device that is allowed to send the rejection message is not managed, the management and control flow of the terminal device is ended.

S508, the network device sends a second logout message to the terminal device.

And the second logout message is used for indicating to forcibly accept the network security control.

S509, the terminal device receives the second logout message sent by the network device.

After receiving the second logout message, the terminal device executes S504 to logout the network and re-initiate registration with the network device.

It should be noted that, if the network device is an access network device, S507 to S509 may be executed by the access network device, or may be executed by forwarding the network device to a core network device, which is not limited in this embodiment of the present invention.

After the network device receives the rejection message sent by the terminal device, whether the terminal device accepts management and control is determined according to the reason information in the rejection message, that is, whether the terminal device needs to accept management and control is determined again by the network device, so that the behavior that a user of the terminal device escapes communication management and control is avoided.

Fig. 7 is a specific implementation manner of a communication management and control flow provided in this embodiment. Assume that end user a is a user using a mobile terminal and end user B is a user using a car networking device. And the operator receives the communication management and control command and requires to manage and control the user using the mobile terminal. And (R) after receiving the communication management and control command, the AN equipment sends a logout message (De registration message) to all users covered by the AN equipment, wherein the De registration message comprises management and control parameters (a management and control type GZ is 1 which indicates that the management and control type is a user of the mobile terminal; and a management and control strength lev is 1 which represents whether the terminal determines to accept management and control).

After the terminal user A receives the Registration, because the device type of the terminal user A is the same as the management and control type, the terminal user A is normally offline and initiates a Registration application (Registration request) to attempt Registration again, (R) the AN device forwards the Registration application (Registration request) to the AMF network element and manages and controls the A according to the latest management and control requirement.

After receiving the registration, the end user B sends a rejection message (Error message) to the network device and carries the car networking user identifier because the device type is different from the management and control type. And the network equipment agrees to the rejection control of the terminal user B of the terminal according to the Error message and the terminal type of the terminal user B, and ends the control flow of the terminal user B.

Or after receiving the registration, the end user B sends a rejection message (Error message) to the network device to avoid management and control, and carries reason information with different management and control types. The network device determines that the terminal user B needs to accept control according to the Error message and the terminal type of the terminal user B, and then resends a cancellation message (registration message) to the terminal user B, where the registration message includes a control parameter (control type GZ is 1, which indicates that the control type is a user of the mobile terminal, and control strength lev is 0, which represents that the control is accepted forcibly). After receiving Registration, the terminal user B initiates a Registration application (Registration request) again to attempt Registration according to the indication that lev is 0 after registering, and (R) the AN device forwards the Registration application (Registration request) to the AMF network element and manages and controls the B according to the latest management and control requirement.

In the embodiment of the present application, the network device and the terminal device may be divided into functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

Fig. 8 shows a possible composition diagram of the terminal device in the case of dividing the functional modules according to the respective functions. As shown in fig. 8, the terminal device 80 includes: a receiving unit 801, a determining unit 802, a processing unit 803, and a transmitting unit 804.

A receiving unit 801, configured to receive a first logout message sent by a network device, where the first logout message is used to indicate a reason for performing logout, and the first logout message includes a management and control parameter used to indicate a management and control object, where the management and control parameter may include a management and control type, or the management and control parameter may include a management and control strength.

A determining unit 802, configured to determine whether the terminal device accepts management and control according to the management and control parameter and the feature information of the terminal device. Wherein the characteristic information is used to indicate a device type or a user category.

A processing unit 803, configured to, if the determining unit 802 determines that the terminal device accepts management and control, logout the network, and then initiate a note to the network device again.

A sending unit 804, configured to send a rejection message to the network device if the determining unit 802 determines that the terminal device does not accept management and control.

In an optional embodiment, the determining unit 802 is specifically configured to: if the characteristic information of the terminal equipment indicates the control type, determining that the terminal equipment receives control; and if the characteristic information of the terminal equipment does not indicate the control type, determining that the terminal equipment does not accept control.

In another optional embodiment, the determining unit 802 is specifically configured to: if the characteristic information of the terminal equipment indicates the control type and the control white list comprises the user identification of the terminal equipment, determining that the terminal equipment does not accept control; the control white list comprises user identifications which do not accept control; and if the characteristic information of the terminal equipment indicates the control type and the control white list does not include the user identification of the terminal equipment, determining that the terminal equipment receives control.

In another optional embodiment, the determining unit 802 is specifically configured to: if the characteristic information of the terminal equipment does not indicate the control type and the control blacklist comprises the user identification of the terminal equipment, determining that the terminal equipment receives control; the control blacklist comprises a user identifier for forced control; and if the characteristic information of the terminal equipment does not indicate the control type and the control blacklist does not include the user identification of the terminal equipment, determining that the terminal equipment is not controlled.

Further, the receiving unit 801 may be further configured to receive a second logout message sent by the network device, where the second logout message is used to indicate that network security management and control are forcibly accepted;

the processing unit 803 is further configured to, after the receiving unit 801 receives the second logout message, logout the network and re-initiate registration with the network device.

Fig. 9 shows a schematic diagram of a possible configuration of the terminal device 90 according to the exemplary embodiment described above, in the case of an integrated unit. The terminal device 90 may be the terminal device described in the above method embodiment. The terminal device 90 may include: a processing module 901 and a communication module 902. The processing module 901 is used for controlling and managing the actions of the terminal device 90, and the communication module 902 is used for communicating with other devices. For example, the processing module 901 is configured to execute any one of the processes S503 and S504 in fig. 5. The processing module 901 may execute any one of the processes S502, S505 in fig. 5 through the communication module 902. The terminal device 90 may also include a storage module 903 for storing program codes and data for the terminal device 90.

The processing module 901 may be the processor 41 in the physical structure shown in fig. 4, and may be a processor or a controller. For example, it may be a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processing module 901 can also be a combination that performs computing functions, e.g., including one or more microprocessors, DSPs, and microprocessors, among others. The communication module 902 may be the transceiver 43 in the physical structure shown in fig. 4, and the communication module 902 may be a transceiver, a transceiver circuit, a communication interface, or the like. Alternatively, the communication interface may be configured to communicate with another device through the element having the transmission/reception function. The above-mentioned elements with transceiving functions may be implemented by antennas and/or radio frequency devices. The storage module 903 may be the memory 42 in the physical structure shown in fig. 4.

When the processing module 901 is a processor, the communication module 902 is a transceiver, and the storage module 903 is a memory, the terminal device 90 according to the embodiment of the present application, shown in fig. 9, may be the terminal device 40 shown in fig. 3.

As described above, the terminal device 80 or the terminal device 90 provided in the embodiments of the present application may be used to implement corresponding functions in the methods implemented in the embodiments of the present application, and for convenience of description, only the portions related to the embodiments of the present application are shown, and details of the specific technologies are not disclosed, please refer to the embodiments of the present application.

In the case of dividing each functional module by corresponding functions, fig. 10 shows a possible composition diagram of a network device, and as shown in fig. 10, the network device 100 includes: transmitting section 1001 and receiving section 1002.

A sending unit 1001, configured to send, after network management and control is started, a first logout message to a terminal device, where the first logout message is used to indicate a reason for performing logout, and the first logout message includes a management and control parameter used to indicate a management and control object, where the management and control parameter may include a management and control type, or the management and control parameter may include a management and control type and a management and control strength.

A receiving unit 1002, configured to receive a registration initiated after a terminal device that receives management and control logs off a network; or receiving a rejection message sent by the terminal device which does not accept the control.

Further, as shown in fig. 11, the network device 100 may further include: a determination unit 1003.

A determining unit 1003, configured to determine whether the terminal device that is allowed to send the rejection message is not subject to regulation according to the reason information.

Correspondingly, the sending unit 1001 is further configured to send a second logout message to the terminal device if the terminal device is not allowed to accept the control, where the second logout message is used to indicate that the network security control is forcibly accepted.

In an optional embodiment, if the reason information indicates that the management and control types are different, the determining unit 1003 is specifically configured to: if the characteristic information of the terminal equipment indicates the control type, determining that the terminal equipment is not allowed to be controlled; and if the characteristic information of the terminal equipment does not indicate the control type, determining that the terminal equipment is allowed not to accept control.

In another optional embodiment, if the reason information indicates that the management and control types are different, the determining unit 1003 is specifically configured to: if the characteristic information of the terminal equipment does not indicate the control type and the control blacklist includes the user identification of the terminal equipment, determining that the terminal equipment is not allowed to be controlled; the control blacklist comprises a user identifier for forced control; and if the characteristic information of the terminal equipment does not indicate the control type and the control blacklist does not include the user identification of the terminal equipment, determining that the terminal equipment is allowed not to be controlled.

In another optional embodiment, if the reason information is an unregulated user or a white list user, the determining unit 1003 is specifically configured to: if the control white list comprises the user identification of the terminal equipment, determining that the terminal equipment is allowed not to be controlled; the control white list comprises user identifications which do not accept control; and if the control white list does not include the user identification of the terminal equipment, determining that the terminal equipment is not allowed to be controlled.

In the case of an integrated unit, fig. 12 shows a schematic diagram of a possible structure of the network device 120 involved in the above-described embodiment. The network device 120 may be the network device described in the above method embodiments. Network device 120 may include: a processing module 1201 and a communication module 1202. The processing module 1201 is used for controlling and managing the operation of the network device 120, and the communication module 1202 is used for communicating with other devices. For example, the processing module 1201 may execute any one of the processes S501, S506 in fig. 5, or S508 in fig. 6 through the communication module 1202. The processing module 1201 may perform the process S507 in fig. 6. Network device 120 may also include a storage module 1203 for storing program codes and data for network device 120.

The processing module 1201 may be the processor 31 in the physical structure shown in fig. 3, and may be a processor or a controller. For example, it may be a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processing module 1201 may also be a combination for performing computing functions, e.g., a combination comprising one or more microprocessors, a combination of a DSP and a microprocessor, or the like. The communication module 1202 may be the communication interface 33 in the physical structure shown in fig. 3, and the communication module 1202 may be a transceiver, a transceiving circuit, a communication interface, or the like. Alternatively, the communication interface may be configured to communicate with another device through the element having the transmission/reception function. The above-mentioned elements with transceiving functions may be implemented by antennas and/or radio frequency devices. The storage module 1203 may be the memory 32 in the physical structure shown in fig. 3.

When the processing module 1201 is a processor, the communication module 1202 is a communication interface, and the storage module 1203 is a memory, the network device 120 in fig. 12 according to the embodiment of the present application may be the network device 30 shown in fig. 3.

As described above, the network device 100 or the network device 120 provided in the embodiments of the present application may be used to implement corresponding functions in the methods implemented in the embodiments of the present application, and for convenience of description, only the portions related to the embodiments of the present application are shown, and details of the specific technologies are not disclosed, please refer to the embodiments of the present application.

As another form of the present embodiment, there is provided a computer-readable storage medium having stored thereon instructions that, when executed, perform the communication management method in the above-described method embodiment.

As another form of the present embodiment, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the communication management method in the above-described method embodiment.

The embodiment of the present invention further provides a chip system, which includes a processor and is used for implementing the technical method of the embodiment of the present invention. In one possible design, the system-on-chip further includes a memory for storing program instructions and/or data necessary for an embodiment of the present invention. In one possible design, the system-on-chip further includes a memory for the processor to call application code stored in the memory. The chip system may be composed of one or more chips, and may also include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.

Through the description of the above embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above functions may be distributed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should 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

1. A communication management and control method is applied to terminal equipment, and is characterized by comprising the following steps:

receiving a first logout message sent by a network device, where the first logout message is used to indicate a reason for performing logout, and the first logout message includes a control parameter used to indicate a control object, where the control parameter includes a control type, or the control parameter includes a control type and a control strength;

determining whether the terminal equipment accepts management and control according to the management and control parameters and the characteristic information of the terminal equipment; wherein the characteristic information is used for indicating the type of equipment or the category of users;

if the terminal equipment accepts control, logging out the network and then re-initiating registration to the network equipment;

and if the terminal equipment does not accept the control, sending a rejection message to the network equipment.

2. The method according to claim 1, wherein determining whether the terminal device accepts management and control according to the management and control parameter and the feature information of the terminal device comprises:

if the characteristic information of the terminal equipment indicates the control type, determining that the terminal equipment receives control;

and if the characteristic information of the terminal equipment does not indicate the control type, determining that the terminal equipment does not accept control.

3. The method according to claim 1, wherein determining whether the terminal device accepts management and control according to the management and control parameter and the feature information of the terminal device comprises:

if the characteristic information of the terminal equipment indicates the control type and a control white list comprises the user identification of the terminal equipment, determining that the terminal equipment does not accept control; the control white list comprises user identifications which do not participate in control;

and if the characteristic information of the terminal equipment indicates the control type and the control white list does not include the user identification of the terminal equipment, determining that the terminal equipment accepts control.

4. The method according to claim 1, wherein determining whether the terminal device accepts management and control according to the management and control parameter and the feature information of the terminal device comprises:

if the characteristic information of the terminal equipment does not indicate the control type and a control blacklist comprises a user identifier of the terminal equipment, determining that the terminal equipment receives control; the control blacklist comprises a user identifier for forced control;

and if the characteristic information of the terminal equipment does not indicate the control type and the control blacklist does not include the user identification of the terminal equipment, determining that the terminal equipment is not controlled.

5. The method according to any of claims 1-4, wherein the reject message comprises reason information indicating a reason why the terminal device does not accept regulation, and after the sending of the reject message to the network device, the method further comprises:

receiving a second logout message sent by the network equipment, wherein the second logout message is used for indicating forced participation in network management and control;

and logging off the network and then re-initiating registration to the network equipment.

6. A communication management and control method is applied to network equipment, and is characterized in that the method comprises the following steps:

after network management and control are started, sending a first logout message to a terminal device, wherein the first logout message is used for indicating a reason for executing logout, the first logout message comprises a management and control parameter used for indicating a management and control object, and the management and control parameter comprises a management and control type, or the management and control parameter comprises a management and control type and a management and control intensity;

receiving registration initiated after the terminal device which receives management and control logs off the network; or receiving a rejection message sent by the terminal device which does not accept the control.

7. The method according to claim 6, wherein the reject message includes reason information indicating a reason why the terminal device does not accept regulation, and after receiving the reject message sent by the terminal device that does not accept regulation, the method further comprises:

determining whether the terminal equipment is allowed to be not subjected to management and control according to the reason information;

and if the terminal equipment is determined not to be allowed to be controlled, sending a second logout message to the terminal equipment, wherein the second logout message is used for indicating to forcibly participate in network control.

8. The method according to claim 7, wherein if the reason information is of a different management and control type, the determining whether the terminal device is allowed to not accept management and control according to the reason information includes:

if the characteristic information of the terminal equipment indicates the control type, determining that the terminal equipment is allowed not to accept control; wherein the characteristic information is used for indicating the type of equipment or the category of users;

and if the characteristic information of the terminal equipment does not indicate the control type, determining that the terminal equipment is not allowed to be not subjected to control.

9. The method according to claim 7, wherein if the reason information is of a different management and control type, the determining whether the terminal device is allowed to not accept management and control according to the reason information includes:

if the characteristic information of the terminal equipment does not indicate the control type and a control blacklist comprises the user identification of the terminal equipment, determining that the terminal equipment is not allowed to be controlled; the control blacklist comprises a user identifier for forced control;

and if the device type of the terminal device does not indicate the control type and the control blacklist does not include the user identifier of the terminal device, determining that the terminal device is allowed not to be controlled.

10. The method according to claim 7, wherein if the reason information is a non-managed user or a white list user, the determining whether the terminal device accepts management and control according to the reason information includes:

if the control white list comprises the user identification of the terminal equipment, determining that the terminal equipment is allowed not to be controlled; the control white list comprises user identifications which do not accept control;

and if the control white list does not include the user identification of the terminal equipment, determining that the terminal equipment is not allowed to be controlled.

11. A terminal device, characterized in that the terminal device comprises:

a receiving unit, configured to receive a first logout message sent by a network device, where the first logout message is used to indicate a reason for performing logout, the first logout message includes a control parameter used to indicate a control object, and the control parameter includes a control type, or the control parameter includes a control type and a control strength;

a determining unit, configured to determine whether the terminal device accepts management and control according to the management and control parameter and the feature information of the terminal device; wherein the characteristic information is used for indicating the type of equipment or the category of users;

the processing unit is used for initiating registration to the network equipment again after logging off the network if the determining unit determines that the terminal equipment receives control;

12. The terminal device according to claim 11, wherein the determining unit is specifically configured to:

13. The terminal device according to claim 11, wherein the determining unit is specifically configured to:

14. The terminal device according to claim 11, wherein the determining unit is specifically configured to:

15. The terminal device according to any of claims 11-14, wherein the reject message comprises reason information indicating a reason why the terminal device does not accept regulation

The receiving unit is further configured to receive a second logout message sent by the network device, where the second logout message is used to indicate to forcibly participate in network management and control;

and the processing unit is also used for logging out the network and then restarting the registration to the network equipment after receiving the second logging-out message.

16. A network device, characterized in that the network device comprises:

a sending unit, configured to send a first logout message to a terminal device after network management and control are started, where the first logout message is used to indicate a cause for performing logout, the first logout message includes a management and control parameter used to indicate a managed object, and the management and control parameter includes a management and control type, or the management and control parameter includes a management and control type and a management and control strength;

the receiving unit is used for receiving the registration initiated after the terminal equipment which receives management and control logs off the network; or receiving a rejection message sent by the terminal device which does not accept the control.

17. The network device according to claim 16, wherein the reject message includes reason information indicating a reason why the terminal device does not accept regulation;

the network device further comprises a determining unit, configured to determine whether to allow the terminal device to not accept management and control according to the reason information;

the sending unit is further configured to send a second logout message to the terminal device if the determining unit determines that the terminal device is not allowed to accept control, where the second logout message is used to indicate to forcibly participate in network control.

18. A communication device, comprising: a memory for storing a computer program and a processor for invoking the computer program to perform the method of any of claims 1-10.

19. A computer-readable storage medium, in which a computer program is stored which, when run on a computer, causes the computer to carry out the method of any one of claims 1 to 10.

20. A computer program product, wherein the computer program product comprises computer instructions which, when run on a computer, cause the computer to perform the method according to any one of claims 1-10.