CN114222284A

CN114222284A - Terminal equipment identification method and device and readable storage medium

Info

Publication number: CN114222284A
Application number: CN202111376155.1A
Authority: CN
Inventors: 鲍丽娜; 秦晓东; 由文琬
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2021-11-19
Filing date: 2021-11-19
Publication date: 2022-03-22
Anticipated expiration: 2041-11-19
Also published as: CN114222284B

Abstract

The application provides a terminal equipment identification method, a terminal equipment identification device and a readable storage medium. The method comprises the following steps: the method comprises the steps of obtaining a first message set detected at a target communication interface, wherein the target communication interface is an interface for communication between core network equipment and access network equipment, the first messages in the first message set are messages in a first network, each first message comprises equipment type information of first terminal equipment, the equipment identification information is used for representing that the first terminal equipment is connected with the first network, and the first network is a target network of independent networking. And acquiring a first user identification information set associated with at least one piece of equipment type information based on the equipment type information contained in the first message set, wherein the terminal equipment associated with the user identification information in the first user identification information set supports connection with the first network. The method can identify whether the terminal equipment supports the target network of independent networking or not, and provide proper network service for the terminal equipment.

Description

Terminal equipment identification method and device and readable storage medium

Technical Field

The present application relates to information processing technologies, and in particular, to a method and an apparatus for identifying a terminal device, and a readable storage medium.

Background

Fifth generation (the 5)^thGeneration, 5G) mobile communication technology provided 5G communication services for terminal devices in early applications in a Non-independent (NSA) networking manner, and the NSA 5G network is a technology for implementing the fourth Generation (the 4) by using a Dual-Connected (DC) technology^thGeneration, 4G) communication technology and 5G communication technology realize joint networking, and 5G base stations are converged to a 4G core network through a 4G network.

With the gradual improvement of network construction, the 5G network of the current independent (NSA) networking has started to provide services, and compared with the NSA 5G network, the network can provide a larger data transmission rate and a smaller transmission delay for the terminal device.

However, the 5G terminal devices include both some terminal devices that are shipped from early stages and can only connect to the NSA 5G network and terminal devices that can connect to the SA5G network. At present, an effective technical scheme for identifying whether the terminal device supports connection with the SA5G network is still lacking, so that a suitable 5G network service cannot be accurately provided for the terminal device, and a barrier exists for improving the user activity of the SA5G network.

Disclosure of Invention

The application provides a terminal device identification method, a terminal device identification device and a readable storage medium, which are used for identifying whether the terminal device supports a target network connected with an independent networking and providing a suitable network service for the terminal device.

In a first aspect, a method for identifying a terminal device is provided, including: acquiring a first message set detected at a target communication interface, wherein the target communication interface is an interface for communication between core network equipment and access network equipment, first messages in the first message set are messages in a first network, each first message comprises equipment type information of first terminal equipment, the equipment identification information is used for representing that the first terminal equipment is connected with the first network, and the first network is a target network of independent networking; and acquiring a first user identification information set associated with at least one piece of equipment type information based on the equipment type information contained in the first message set, wherein terminal equipment associated with the user identification information in the first user identification information set supports connection with the first network.

According to the method, whether the terminal equipment supports the target network connected with the independent networking or not can be identified, and the appropriate network service is provided for the terminal equipment.

Optionally, the obtaining, based on the device type information, a first set of subscriber identity information associated with at least one piece of the device type information includes: and querying a first user database to obtain a first user identification information set associated with at least one piece of equipment type information in the first user database, wherein the first user database is a user database supporting terminal equipment connected with a second network, and the second network is the target network of a non-independent networking.

Optionally, the method further comprises: and generating a target incidence relation, wherein the target incidence relation comprises that the user identification information in a second user identification information set is associated with a first label, the first label is used for representing that the terminal equipment associated with the user identification information supports connection with the first network, and the second user identification information set comprises the first user identification information set and the user identification information which is contained in the first message set and is associated with each first terminal equipment.

Optionally, the user identification information in the first user database except for the first user identification information set is a third user identification information set, the target association relationship further includes that the user identification information in the third user identification information set is associated with a second tag, and the second tag is used for representing that the terminal device associated with the user identification information does not support connection with the first network.

Optionally, the method further comprises: and sending first information to terminal equipment associated with the user identification information in the first user identification information set, wherein the first information is used for recommending connection to the first network.

Optionally, the method further comprises: obtaining software identification information associated with at least one piece of first user identification information based on the first user identification information of the first terminal equipment contained in the first message set, wherein the software identification information comprises application program identification information and/or operating system identification information; and acquiring a fourth user identification information set based on each piece of software identification information, determining that the user identification information in the fourth user identification information set is associated with at least one piece of software identification information, and the terminal equipment associated with the user identification information in the fourth user identification information set supports connection with the second network.

Optionally, the obtaining software identification information associated with at least one piece of first user identification information based on the first user identification information of the first terminal device included in the first message set includes: querying a software database based on first user identification information of the first terminal device contained in the first message set to obtain software identification information associated with at least one piece of the first user identification information; and, said obtaining a fourth set of subscriber identity information based on each of said software identity information comprises: and acquiring the fourth user identification information set based on each piece of software identification information, the software database and the first user database, wherein the fourth user identification information set is a set of user identification information which is associated with the software identification information in the software database and is contained in the first user database.

Optionally, the method further comprises: and associating the user identification information which belongs to the second user identification information set and the fourth user identification information set in the target association relation with a third label, wherein the third label is used for representing the software support of the user identification information association to connect with the first network.

Optionally, the method further comprises: and associating the user identification information which does not belong to the second user identification information set and/or does not belong to the fourth user identification information set in the target association relation with a fourth label, wherein the fourth label is used for representing that software associated with the user identification information does not support connection with the first network.

Optionally, the method further comprises: acquiring a second message set in the second network, wherein each second message in the second message set is associated with a second terminal device and a user identification information, and each second message comprises a second message used for indicating whether a target switch unit of the second terminal device is in an on state or not, and the target switch unit is a switch unit of the terminal device connected with the first network; and determining a fifth user identification information set in the second message set based on each piece of the second information, wherein the target switch unit of the second terminal equipment associated with the user identification information in the fifth user identification information set is in an on state.

Optionally, the method further comprises:

and associating the user identification information which belongs to the second user identification information set and the fifth user identification information set in the target association relation with a fifth label, wherein the fifth label is used for representing that a target switch unit of the terminal equipment associated with the user identification information is in an on state.

Optionally, the method further comprises: and associating each piece of user identification information which does not belong to the second user identification information set and/or does not belong to the fifth user identification information set in the target association relation with a sixth label, wherein the sixth label is used for representing that a target switch unit of the terminal equipment associated with the user identification information is not in an on state.

Optionally, the method further comprises: and outputting the target association relation to a network platform.

In a second aspect, a terminal device identification apparatus is provided, which includes means for implementing the terminal device identification method described in any one of the first aspect and the first aspect. Illustratively, the terminal device identification apparatus includes an acquisition unit and a processing unit.

The acquiring unit is configured to acquire a first message set detected at a target communication interface, where the target communication interface is an interface between a core network device and an access network device, a first message in the first message set is a message in a first network, each first message includes device type information of a first terminal device, the device identification information is used to represent that the first terminal device is connected to the first network, and the first network is a target network of an independent network;

the processing unit is configured to obtain, based on the device type information included in the first message set, a first subscriber identity information set associated with at least one piece of the device type information, where a terminal device associated with subscriber identity information in the first subscriber identity information set supports connection to the first network.

In a third aspect, a terminal device identification apparatus is provided, which includes a processor configured to execute the terminal device identification method provided in any one of the first aspect and the first aspect.

The apparatus may also include a memory to store instructions and data. The memory is coupled to the processor, and the processor, when executing the instructions stored in the memory, may implement the method described in the first aspect above. The apparatus may also include a communication interface for the apparatus to communicate with other devices, which may be, for example, a transceiver, circuit, bus, module, or other type of communication interface.

In a fourth aspect, there is provided a computer-readable storage medium comprising instructions which, when run on a computer, cause the computer to carry out the method provided in any one of the first aspect and the first aspect.

In a fifth aspect, there is provided a computer program product comprising: a computer program (which may also be referred to as code, or instructions), which when executed, causes a computer to perform the method provided in any of the first aspect and the first aspect.

Drawings

Fig. 1 is a network architecture suitable for the terminal device identification method provided in the present application;

fig. 2 is a schematic flowchart of a terminal device identification method provided in an embodiment of the present application;

fig. 3 is a flowchart of whether a terminal device supports connection to a first network according to an embodiment of the present application;

fig. 4 is another schematic flow chart of a method for determining terminal device identification provided in an embodiment of the present application;

FIG. 5 is a schematic flow chart diagram for determining whether software supports connection to a first network according to an embodiment of the present application;

fig. 6 is a schematic flowchart for determining whether a target network switch unit is in an on state according to an embodiment of the present application;

FIG. 7 is a schematic flowchart for acquiring a full-volume 5G end user database according to an embodiment of the present application

Fig. 8 is a schematic block diagram of a terminal device identification apparatus provided in an embodiment of the present application;

fig. 9 is another schematic block diagram of a terminal device identification apparatus according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

In order to meet the requirement of accurate construction of an SA5G network, a user is guided to use 5G terminal equipment, data support is provided for the construction of the SA5G network, the capacity of terminal SA capacity identification is expanded, the capacity of the terminal equipment for connecting the SA5G network is improved, and guidance on the accurate construction of the 5G network, popularization of the 5G terminal equipment, maintenance of a user who replaces the equipment and the like are facilitated.

In the embodiment of the application, based on the same type of terminal equipment, hardware functions are the same, and as a network system which can be supported by a mobile phone of the same type, if one terminal equipment logs in an SA5G network, other terminal equipment of the same type as the terminal equipment can also log in the SA5G network. Therefore, the embodiment of the present application proposes to identify the device type of the terminal device connected to the SA5G network, and determine that the terminal device of the type can support the SA5G network, so that based on the device type, the user who determines the type of terminal device can use the SA5G network through the type of terminal device.

It should be understood that the technical solution provided by the present application can solve the problem that the network service cannot be provided accurately in the 5G network at present, but the application scenario of the present application is not limited thereto, and the technical solution provided by the present application can also be used in the case of using other communication technologies (such as the sixth generation (the 6 th generation)^thGeneration, 6G) mobile communication technology and future communication technology).

For facilitating understanding of the embodiments of the present application, first, a network architecture suitable for the identification method of the terminal device provided in the present application is described in detail with reference to fig. 1. As shown in fig. 1, the network architecture 100 may include a terminal device 110, an access network device 120, and a core network device 130. Where terminal device 110 may communicate with core network device 130 through access network device 120. For example, the terminal 110 may send an attach request (attach request) message or a tracking area update request (TAU request) message to the core network device 130 through the access network device 120.

The access network device may forward the message to the core network device through an interface with the core network device. Illustratively, the core network device 130 may be a Mobility Management Entity (MME) in the 4G network, and the connection interface of the access network device 120 and the core network device 130 may be an S1-MME interface in the 4G network.

It should be understood that the illustration in the drawings is merely an example, and the application does not limit the number of access network devices connected to the core network device in the network architecture, nor the number of terminals within the coverage area of the access network device. In addition, the core network device may be an MME in a 4G network, or may be a device that can be used to implement a mobility management function in a5G network, such as an access and mobility management element (AMF), and an interface between an access network device and the core network device corresponding to the core network device may also be an N2 interface in the 5G network. The embodiments of the present application are not limited thereto.

For ease of understanding, the method provided by embodiments of the present application is described below in conjunction with the architecture shown in fig. 1. Fig. 2 is a schematic flowchart of an identification method of a terminal device according to an embodiment of the present application. The following description will be given by taking the core network device as an example to execute the method, and it should be understood that the present application is not limited thereto. The method shown in fig. 2 may be executed by a core network device or an apparatus (e.g., a chip) configured in the core network device, or may be executed by other devices and apparatuses. The identification method of the terminal device shown in fig. 2 includes, but is not limited to, the following steps:

s201, a core network device obtains a first message set detected at a target communication interface, where first messages in the first message set are messages in a first network, each first message includes device identification information of a first terminal device, the device identification information is used to represent that the first terminal device is connected to the first network, and the first network is a target network of an independent network.

Optionally, the core network device may perform Deep Packet Inspection (DPI) on traffic of the communication interface between the access network device and the core network device, search for the message flow record, and obtain the first message based on the message flow record of each first terminal device.

For example, the message flow record may be a Call Detail Record (CDR) including network type indication information indicating a network type to which the terminal device is connected. The network type indicated by the network type indication information in the first message is the first network (i.e., the target network that is not independently networked). The core network device may obtain the first message set according to the network type indication information. Each first message contains equipment identification information of the first terminal equipment, and the first terminal equipment is characterized in being connected with the first network.

The first message may include an International Mobile Equipment Identity (IMEI) or an International Mobile Equipment Software Version (IMEI Software Version, IMEISV) of the first terminal device, where the first 8 bits of the IMEI and the first 8 bits of the IMEISV are Type Allocation Codes (TAC), and the TAC may identify a device brand and a device model of the terminal device. The core network device may obtain the TAC (i.e., an example of the device type information) in each first message, and determine, based on the device model identified by each TAC, that the first terminal device of the device model is capable of supporting connection with the first network.

S202, the core network device obtains, based on the device type information of the first terminal device, a first subscriber identity information set associated with at least one piece of the device type information, where the terminal device associated with the subscriber identity information in the first subscriber identity information set supports connection to the first network.

The core network device obtains a first user identification information set associated with the device type information based on the device type information of a first terminal device connected to a first network, so as to determine a user identified by the user identification information in the first user identification information set, and the terminal device used by the core network device can support connection to the first network.

By way of example and not limitation, the Subscriber identification information may be Subscriber unique identification information, such as a Mobile Subscriber Integrated Service Digital Network identification Number (MSISDN).

Optionally, the core network device queries a first user database to obtain a first user identification information set associated with the device identification information of at least one first terminal device in the first user database, where the first user database is a user database supporting terminal devices connected to the second network. The second network is a target network that is not independently networked.

The first user database may be obtained by the core network device from the network data platform, for example, the core network device may subscribe to the first user database from a data server, and the data server provides the first user database for the core network device. Or the core network device may be obtained by the core network device collecting data recorded when the user connects to the network from network devices in other mobile communication networks, which is not limited in this application.

For example, the target network is a5G network, and the first user database includes a first user database supporting 5G terminal devices connected to the 5G network that is not independently networked. The user using the 5G terminal device may be referred to as a5G user, the first user database may include user identification information of the 5G user and device type information of the terminal device used by each 5G user, and optionally, the first user database may further include device brand information, a record of a connection network, and the like. After the core network device obtains the first user database, it may be determined that the terminal device in the first user database may support a5G network connected to a non-independent networking, but it may not be determined whether the terminal device in the first user database supports an independent networking terminal device. The core network device may query the first user database for the device type information obtained in S201, and obtain all user identification information associated with the device type information of the at least one first terminal device in the first user database, to obtain a first user identification information set. The terminal device associated with the subscriber identity information in the first subscriber identity information set supports connection with the first target network.

According to the method, the core network equipment can identify whether the terminal equipment supports the target network connected with the independent networking or not, and provide proper network service for the terminal equipment.

Optionally, the core network device may send first information to a terminal device associated with the user identification information in the first user identification information set, where the first information is used to recommend connection to the first network.

When the core network device determines that the terminal device connected with the target network (namely, the second network) of the non-independent networking supports the target network (namely, the first network) of the independent networking. The core network device may send the first information to the terminal device associated with the subscriber identity information in the first subscriber identity information set, so as to prompt the user that the terminal device used by the user may use the target network of the independent networking, and thus, the user can enjoy higher-speed data services. The first information may further include information instructing to turn on a switch connected to the first network. The situation that the user uses the terminal equipment supporting connection with the first network but does not notice that the first network can be connected or does not know how to turn on a switch for connecting the first network and the like can be avoided. The network access rate of the user of the first network can be improved, and therefore the network construction of the first network is enhanced.

Optionally, the core network device generates a target association relationship, where the target association relationship includes that the user identification information in the second user identification information set is associated with a first tag, and the first tag is used to represent that the terminal device associated with the user identification information supports connection with the first target network. Wherein the second set of subscriber identity information comprises the subscriber identity information (i.e. the subscriber identity information associated with each first terminal device) included in the first set of messages and the first set of subscriber identity information.

The core network device may determine, through S201 and S202, that the first terminal device connected to the first target network in the first message supports connection to the first target network, and that the terminal device associated with the user identification information in the first user identification information set supports connection to the first target network, and the core network device establishes association between the user identification information associated with the terminal device supporting connection to the first target network and the first tag.

Optionally, the first user database includes, in addition to the user identification information in the first user identification information set, a third user identification information set, and the target association relationship further includes that the user identification information in the third user identification information set is associated with a second tag, where the second tag is used to represent that the terminal device associated with the user identification information does not support connection to the first target network.

For example, the core network device associates the user identification information belonging to the first user identification information set in the first user database with the first tag, and associates the user identification information not belonging to the first user identification information set with the second tag, based on whether the user identification information in the first user database belongs to the first user identification information set. And the core network equipment associates the user identification information associated with the first terminal equipment in the first message set with the first label. The core network device may determine a second set of user databases of the target network, the second set of user databases including a union of the first user database with user data and device data associated with the user identification information included in the first set of messages. The second database set comprises the above-mentioned target association relationship, i.e. each user identification information is associated with the first tag or with the second tag.

Optionally, the core network device may supplement the terminal data associated with the user identification information in the second user database based on the terminal database. For example, the core network device may associate the second user database with the terminal database, and may supplement the terminal device data associated with the user identification information in the second user database.

For example, the terminal database may include TAC values and brand name information of the terminal device, type name information of the terminal device, and the like. For the user identification information contained in the first message set and not contained in the first user database, the first user database may lack terminal device data associated with the user identification information, the core network device may search the terminal database based on the device type information to obtain the terminal data associated with the device type information, and supplement the searched terminal data to the second user database to associate the terminal data with the corresponding device type information. Thereby obtaining a more complete second user database of the target network.

For another example, in the example shown in fig. 3, the core network device may first obtain the second terminal database based on that the user data and the terminal data in the first message set are fully associated with the terminal database, that is, a union of the user data, the terminal data and the first terminal database in the first message set is taken. The first terminal database comprises a TAC value, brand information of terminal equipment corresponding to the TAC value, equipment type information of the terminal equipment and the like. I.e. the second terminal database comprises only device-related information of the terminal device. The core network device associates the second terminal device library with the first user database to obtain a second user database, wherein the first user database is a5G terminal user database, and the second user database includes user data and terminal device data associated with the user data (such as user identification information, home location, and the like). The user identification information associated with the device type information of at least one first terminal device in the second user database is associated with a first tag, the first tag is used for representing that the terminal device supports an SA5G network, the associated user identification information of the device type information which does not belong to the device type information contained in the first message set is associated with a second tag, and the second tag is used for representing that the terminal device does not support the SA5G network, namely, the second user database contains the target association relationship. Thus, the user identification information of the hardware supporting connection with the first network and the data of the relevant terminal device can be known based on the second user database.

According to the scheme, the second user database of the target network can be obtained, and the method and the device are favorable for guiding accurate network construction of the first network, maintenance of new users of the machine changing and the like.

In the above, the method for the core network device to determine whether the terminal device (i.e. hardware) used by the user supports connection with the first network is introduced, and the present application also provides a method for determining whether the software used by the user supports connection with the first network. The method and the method for determining whether the hardware of the user supports connection with the first network may be implemented separately or in combination, and the present application does not limit this.

Fig. 4 is another schematic flowchart of a terminal device identification method provided in an embodiment of the present application.

S401, the core network device obtains software identification information associated with at least one piece of first user identification information based on the first user identification information of the first terminal device included in the first message set, where the software identification information includes application identification information and/or operating system identification information.

The core network device may acquire software identification information of software used by a user connected to the first network. Thereby determining that the software identified by the software identification information associated with the first terminal device contained in the first set of messages supports connection to the first network.

The core network device may determine whether the software supports connecting to the first network based on identification information of some operating systems. Since it cannot be determined whether the software supports connection to the first network based on identification information of some operating systems, the core network device may determine whether the software supports connection to the first network based on the application identification information. But the application is not limited thereto.

S402, the core network device determines a fourth user identification information set based on the software identification information of each first terminal device, wherein the user identification information in the fourth user identification information set is associated with the software identification information of at least one first terminal device, and the terminal device associated with the user identification information in the fourth user identification information supports connection with the second network.

The core network equipment searches user identification information which is associated with the software identification information and supports the association of the terminal equipment connected with the second network based on the software identification information of the first terminal equipment. For example, the target network is a5G network, the core network device searches for 5G terminal devices that support a5G network connected to a non-independent networking based on the software identification information of the first terminal device, and determines that software associated with these 5G terminal devices supports the 5G network connected to the independent networking.

By way of example and not limitation, the software identification information may be firmware version information.

Optionally, the core network device may obtain the fourth user identification information set based on the software identification information, the software database, and the first user database associated with each first terminal device. Wherein the fourth set of user identification information is a set of user identification information associated with the software identification information in the software database and contained in the first user database.

The software database includes a plurality of user identification information and one or more software identification information associated with each user identification information. The core network device may determine, based on the software database and the first user database, user identification information associated with the at least one piece of software identification information and supporting association with a terminal device connected to the second network.

By way of example and not limitation, the software database may be obtained by the core network device from a network data platform, for example, the core network device may subscribe to the software database from a data server that provides the software database for the core network device. Or the core network device may be obtained by the core network device collecting data recorded when the user accesses the network from network devices in other mobile communication networks, which is not limited in this application.

Optionally, the core network device may associate the subscriber identity information in the fourth set of subscriber identity information with a third tag, where the third tag is used to characterize that the software associated with the subscriber identity information supports connection with the first network.

This approach may be implemented in conjunction with a method in which the core network device determines whether the hardware supports the first network.

In one embodiment, the core network device may associate, in the target association relationship, the user identification information belonging to both the second user identification information set and the fourth user identification information set with the third tag.

That is, if a terminal device associated with one piece of subscriber identity information supports connection with the first network (i.e., the subscriber identity information belongs to the second subscriber identity information set), and the subscriber identity information also belongs to the fourth subscriber identity information set, the core network device determines that the terminal device associated with the subscriber identity information supports connection with the first network (i.e., hardware supports connection with the first network), and associated software also supports connection with the first network.

When the terminal device does not support connection with the first network, even if the software supports connection with the first network, the user cannot connect with the first network through the terminal device, so that if one terminal device associated with the user identification information does not support the first network, but the user identification information belongs to the fourth user identification information set, the core network device associates the user identification information with the third tag.

Optionally, the core network device associates the user identification information that does not belong to the second user identification information set and/or does not belong to the fourth user identification information set in the target association relationship with a fourth tag, where the fourth tag is used to represent that software associated with the user identification information does not support connection with the first network.

In another embodiment, the core network device associates the user identification information in the second user database, which belongs to both the second user identification information set and the fourth user identification information set, with the third tag, and associates the user identification information in the second user database, which does not belong to the second user identification information set and/or does not belong to the fourth user identification information set, with the fourth tag, so as to obtain a third user database. The third user database comprises the second user database and a third label or a fourth label associated with each identification information in the second user database, and the third user database also comprises identification information which does not belong to the second user database in the fourth user identification information and the associated third label or fourth label.

Optionally, the core network device may supplement the terminal data associated with the user identification information in the third user database based on the terminal database. For example, the core network device may associate the third user database with the terminal database, and may supplement the terminal device data associated with the user identification information in the third user database.

In another embodiment, as shown in fig. 5, the core network device may first associate the user data and the terminal data in the first message set with the software database, that is, obtain an intersection of the user data and the terminal data in the first message set and the software database based on the first user identification information, to obtain a TAC library supporting a SA5G (that is, an example of the first network) connection network, where each user identification information in the TAC library is associated with a third tag for characterizing that the associated software supports the SA5G connection network. The core network device also associates the first user database (i.e. the 5G end user database) with the software database to obtain the 5G end user database with the firmware version information (i.e. the firmware version information is an example of the software identification information). The core network device associates and supports a TAC database connected with an SA5G network on the left side of a5G terminal user database with firmware version information, namely if the 5G terminal user database with firmware version information contains a TAC value in the TAC database, the data associated with the TAC value in the TAC database is associated with the TAC value in the 5G terminal user database with firmware version information. Optionally, the core network device may further associate, in the fourth user database, the user identification information that is not associated with the third tag with a fourth tag, where the fourth tag is used to characterize that the associated software does not support connection to the first network.

According to the scheme, the core network device can obtain a user database related to the target network, such as a third user database or a fourth user database, and obtain whether the terminal device associated with the user identification information and software support the related data connected with the first network, so that guidance on accurate network construction of the first network, maintenance of a new machine user and the like is facilitated.

Optionally, the core network device obtains a second message set in the second network, where each second message in the second message set is associated with a second terminal device and a piece of user identification information, and each second message includes a piece of second information, where the second information is used to indicate whether a target switch unit of the second terminal device is in an on state, and the target switch unit is a switch unit of the terminal connected to the first network. The core network device determines a fifth user identification information set in the second message set based on each piece of second information, and a target switch unit of the second terminal device associated with the user identification information in the fifth user identification information set is in an on state.

For example, the core network device may acquire a tracking area update request (TAU request) message from the S1-MME interface (i.e., the TAU update message is an example of the second message). Each tracking area update request message includes a User Equipment Network Capability (UENC) field including N1 interface MODE (N1_ MODE) information (i.e., one example of second information), and the N1 interface MODE information is used to indicate whether an SA switch unit (i.e., a target switch unit) of the terminal device is turned on. If the field indicates 1, the SA switch unit is turned on. The core network device determines whether a target switch unit of the terminal device is in an on state based on the second information of each second message in the second message set.

In one embodiment, the core network device associates the user identification information, which belongs to both the second user identification information set and the fifth user identification information set in the target association relationship, with a fifth tag, where the fifth tag is used to represent that a target switch unit of the terminal device associated with the user identification information is in an on state.

Optionally, the core network device associates each piece of user identification information that does not belong to the second user identification information set and/or does not belong to the fifth user identification information set in the target association relationship with a sixth tag, where the sixth tag is used to represent that a target switch unit of the terminal device associated with the user identification information is not in an on state.

When the terminal device does not support connection to the first network, the terminal device cannot connect to the first network even if it is determined that the target switch unit is in the on state, and therefore the core network device may associate the user identification information belonging to the fifth user identification information set with the sixth tag, but the associated terminal device does not support the first network.

In another embodiment, the core network device associates the user identification information belonging to the second user identification information set and the fourth user identification information set and belonging to the fifth user identification information set in the target association relationship with a fifth tag, where the fifth tag is used to represent that a target switch unit of the terminal device associated with the user identification information is in an on state.

Optionally, the core network device associates each piece of user identification information that does not belong to the second user identification information set, and/or does not belong to the fourth user identification information set, and/or does not belong to the fifth user identification information set in the target association relationship with a sixth tag, where the sixth tag is used to represent that a target switch unit of the terminal device associated with the user identification information is not in an on state.

Since the terminal device does not have a need to use the network service of the first network even if the target switch unit is in the on state if the software of the terminal device does not support the connection to the first network. Therefore, the sixth tag is associated with the user identification information that the software does not support connection to the first network.

Optionally, the core network device outputs the target association relationship to the network platform.

In another embodiment as shown in fig. 6, the core network device performs an internal association between the first user database and the user data and the terminal data in the second message set, that is, a union of the first user data and the terminal data in the second message set is obtained based on the user identification information, so as to obtain a fifth user database. If the second information corresponding to the user identification information contained in the fifth user database indicates that the SA5G switch unit is in the on state, the user identification information is associated with the fifth tag, and if the second information corresponding to the user identification information indicates that the SA5G switch is in the off state, the user identification information is associated with the sixth tag.

The above methods may be implemented in combination, for example, the core network device may associate the second user database, the fourth user database, and the fifth user database, for example, as shown in fig. 7, since the second user database is a user-level full database, the core network device may associate the fourth user database and the fifth user database via IMEI left to obtain a user database with SA capability information, where if one user identification information is associated with one second tag, that is, the associated terminal device does not support connection to the first network, the user identification information is also associated with the fourth tag and the sixth tag (not associated with the third tag and the fifth tag), it is characterized that software associated with the user identification information does not support connection to the first network, and the SA switch is not in an on state. If a piece of user identification information is associated with a fourth tag, i.e. the associated software does not support connection to the first network, the user identification information is also associated with the sixth tag (not associated with the fifth tag), and the SA switch that characterizes the terminal device associated with the user identification information is not in an on state. The core network device associates the first user database with the SA capability information through the IMEI or IMSI to obtain a5G terminal user database with the SA capability information, and associates the 5G terminal user database with the SA capability information with the user data and the terminal data in the first message set to obtain a full SA5G terminal user database. Each terminal device in the full SA5G end-user database may be associated with an SA logoff tag, where the SA logoff tag of the terminal device belonging to the first message set indicates that the SA5G network is connected, and the SA logoff tags of other terminal devices indicate that the SA5G network is not connected. The full SA5G terminal user database also comprises information such as attribution information, visiting place information, a label for whether the NSA network is connected or not, and the like. The core network device can supplement the related terminal data and/or the home information and the like in the full-size SA5G terminal user database in a mode of left-hand association of the 5G terminal user database with the SA login tag and the terminal database and the home database.

Optionally, the core network device outputs the full SA5G end user database to the network platform. So that the network platform can perform data analysis, namely data forwarding or network maintenance and the like, based on the full SA5G terminal user database.

According to the scheme, the core network equipment can respectively judge whether hardware and software of the terminal equipment support a target network connected with the independent networking and whether a switch of the target network connected with the independent networking is in an on state, and data are correlated to obtain a full SA5G terminal user database, wherein the data comprise a label of whether the hardware (namely the terminal equipment) supports the target network connected with the independent networking, a label of whether the software supports the target network connected with the independent networking and a label of whether the target network connected with the independent networking is on, SA login labels and other target network related data of the independent networking, so that accurate network construction, new switch user maintenance and the like can be guided, the target network service and the network can be promoted to cooperatively develop, and the target network user login rate can be improved.

Fig. 8 is a schematic block diagram of a terminal device identification apparatus 800 according to an embodiment of the present application. The terminal device identification apparatus may include an acquisition unit 801 and a processing unit 802. The obtaining unit 801 is configured to obtain a first message set detected at a target communication interface, where the target communication interface is an interface between a core network device and an access network device, a first message in the first message set is a message in a first network, each first message includes device type information of a first terminal device, the device identification information is used to characterize that the first terminal device is connected to the first network, and the first network is a target network of an independent networking. The processing unit 802 is configured to obtain, based on the device type information included in the first message set, a first set of subscriber identity information associated with at least one piece of the device type information, where a terminal device associated with subscriber identity information in the first set of subscriber identity information supports connection to the first network.

Optionally, the processing unit 802 is specifically configured to query a first user database, to obtain a first user identification information set associated with at least one piece of device type information in the first user database, where the first user database is a user database supporting a terminal device connected to a second network, and the second network is the target network of a non-independent networking.

Optionally, the processing unit 802 is further configured to generate a target association relationship, where the target association relationship includes that the user identification information in a second user identification information set is associated with a first tag, and the first tag is used to characterize that a terminal device associated with the user identification information supports connection to the first network, where the second user identification information set includes the first user identification information set and includes the user identification information associated with each first terminal device included in the first message set.

Optionally, the user identification information in the first user database except the first user identification information set is a third user identification information set, the target association relationship further includes that the user identification information in the third user identification information set is associated with a second tag, and the second tag is used for representing that the terminal device associated with the user identification information does not support connection with the first network.

Optionally, the terminal device identifying apparatus 900 further includes a transceiver configured to send first information to a terminal device associated with the user identification information in the first user identification information set, where the first information is used to recommend to connect to the first network.

Optionally, the processing unit 802 is further configured to obtain software identification information associated with at least one piece of first subscriber identification information based on the first subscriber identification information of the first terminal device included in the first message set. The obtaining unit 801 is further configured to obtain a fourth set of user identification information based on each piece of software identification information.

Optionally, the processing unit 802 is specifically configured to query a software database based on the first user identification information of the first terminal device included in the first message set, so as to obtain software identification information associated with at least one piece of the first user identification information. The obtaining unit 801 is specifically configured to obtain the fourth set of user identification information based on each of the software identification information, the software database, and the first user database, where the fourth set of user identification information is a set of user identification information that is associated with the software identification information in the software database and is included in the first user database.

Optionally, the processing unit 802 is further configured to associate, in the target association relationship, the user identification information that belongs to both the second user identification information set and the fourth user identification information set with a third tag, where the third tag is used to represent that software associated with the user identification information supports connection with the first network.

Optionally, the processing unit 802 is further configured to associate the user identification information that does not belong to the second set of user identification information and/or does not belong to the fourth set of user identification information in the target association relationship with a fourth tag, where the fourth tag is used to characterize that software associated with the user identification information does not support connection to the first network.

Optionally, the obtaining unit 801 is further configured to obtain a second message set in the second network, where each second message in the second message set is associated with a second terminal device and a piece of user identification information, and each second message includes a second message, where the second message is used to indicate whether a target switch unit of the second terminal device is in an on state, where the target switch unit is a switch unit of the terminal device connected to the first network, and the target switch unit is a switch unit of the terminal device connected to the first network

Optionally, the processing unit 802 is further configured to determine, based on each piece of the second information, a fifth set of user identification information in the second message set, where a target switch unit of the second terminal device associated with the user identification information in the fifth set of user identification information is in an on state.

Optionally, the processing unit 802 is further configured to associate, in the target association relationship, the user identification information that belongs to both the second user identification information set and the fifth user identification information set with a fifth tag, where the fifth tag is used to represent that a target switch unit of the terminal device associated with the user identification information is in an on state.

Optionally, the processing unit 802 is further configured to associate each piece of user identification information that does not belong to the second set of user identification information and/or does not belong to the fifth set of user identification information in the target association relationship with a sixth tag, where the sixth tag is used to represent that a target switch unit of a terminal device associated with the user identification information is not in an on state.

Optionally, the transceiver unit is further configured to output the target association relationship to a network platform.

Fig. 9 is a schematic block diagram of a terminal device identification apparatus 900 according to an embodiment of the present application. The device can be used for realizing the function of identifying the terminal equipment in the method. Wherein the apparatus may be a system-on-a-chip. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices.

As shown in fig. 9, the apparatus 900 may include at least one processor 901 for implementing the function of terminal device identification in the method provided in the embodiment of the present application. Illustratively, the processor 901 is configured to obtain a first set of subscriber identity information associated with at least one of the device type information based on the device type information contained in the first set of messages.

The apparatus 900 may also include at least one memory 902 for storing program instructions and/or data. The memory 902 is coupled to the processor 901. The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules. The processor 901 may cooperate with the memory 902. The processor 901 may execute program instructions stored in the memory 902. At least one of the at least one memory may be included in the processor.

The apparatus 900 may also include a communication interface 903 for communicating with other devices over a transmission medium such that the apparatus used in the apparatus 900 may communicate with other devices. The communication interface 903 may be, for example, a transceiver, an interface, a bus, a circuit, or a device capable of performing a transceiving function. The processor 901 may send and receive data and/or information using the communication interface 903 and may be used to implement the terminal device identification method in the embodiments corresponding to fig. 2 or fig. 4.

The specific connection medium between the processor 901, the memory 902 and the communication interface 903 is not limited in the embodiments of the present application. In fig. 9, the processor 901, the memory 902, and the communication interface 903 are connected by a bus 904. The bus 904 is shown in fig. 9 by a thick line, and the connection between other components is merely illustrative and not intended to be limiting. 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. 9, but this does not indicate only one bus or one type of bus.

The present application further provides a computer program product comprising: a computer program (also referred to as code, or instructions), which when executed, causes a computer to perform the method of any of the embodiments shown in fig. 2 or 4.

The present application also provides a computer-readable storage medium having stored thereon a computer program (also referred to as code, or instructions). The computer program, when executed, causes a computer to perform the method of any of the embodiments shown in fig. 2 or fig. 4.

It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software.

As used in this specification, the terms "unit," "module," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution.

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps (step) described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application. In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the above-described division of units is only one type of division of logical functions, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, 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 or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units 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.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A method for identifying a terminal device, comprising:

acquiring a first message set detected at a target communication interface, wherein the target communication interface is an interface for communication between core network equipment and access network equipment, the first messages in the first message set are messages in a first network, each first message comprises equipment type information of first terminal equipment, the equipment identification information is used for representing that the first terminal equipment is connected with the first network, and the first network is a target network of an independent networking;

and acquiring a first user identification information set associated with at least one piece of equipment type information based on the equipment type information contained in the first message set, wherein terminal equipment associated with the user identification information in the first user identification information set supports connection with the first network.

2. The method of claim 1, wherein obtaining a first set of subscriber identity information associated with at least one of the device type information based on the device type information comprises:

and querying a first user database to obtain a first user identification information set associated with at least one piece of equipment type information in the first user database, wherein the first user database is a user database supporting terminal equipment connected with a second network, and the second network is the target network of a non-independent networking.

3. The method of claim 2, further comprising:

generating a target incidence relation, wherein the target incidence relation comprises that the user identification information in the second user identification information set is associated with a first label, the first label is used for representing that the terminal equipment associated with the user identification information supports to be connected with the first network,

wherein the second set of subscriber identity information comprises the first set of subscriber identity information and subscriber identity information associated with each of the first terminal devices contained in the first set of messages.

4. The method of claim 3, wherein the subscriber identity information in the first subscriber database other than the first set of subscriber identity information is a third set of subscriber identity information,

the target association relationship further includes that the user identification information in the third user identification information set is associated with a second tag, and the second tag is used for representing that the terminal device associated with the user identification information does not support connection with the first network.

5. The method according to any one of claims 1 to 4, further comprising:

and sending first information to terminal equipment associated with the user identification information in the first user identification information set, wherein the first information is used for recommending connection to the first network.

6. The method according to claim 3 or 4, characterized in that the method further comprises:

obtaining software identification information associated with at least one piece of first user identification information based on the first user identification information of the first terminal equipment contained in the first message set, wherein the software identification information comprises application program identification information and/or operating system identification information;

and acquiring a fourth user identification information set based on each piece of software identification information, wherein the user identification information in the fourth user identification information set is associated with at least one piece of software identification information, and the terminal equipment associated with the user identification information in the fourth user identification information set supports connection with the second network.

7. The method of claim 6,

the obtaining software identification information associated with at least one piece of first user identification information based on the first user identification information of the first terminal device included in the first message set includes:

querying a software database based on first user identification information of the first terminal device contained in the first message set to obtain software identification information associated with at least one piece of the first user identification information;

the obtaining a fourth set of user identification information based on each piece of software identification information includes:

and acquiring the fourth user identification information set based on each piece of software identification information, the software database and the first user database, wherein the fourth user identification information set is a set of user identification information which is associated with the software identification information in the software database and is contained in the first user database.

8. The method of claim 6, further comprising:

and associating the user identification information which belongs to the second user identification information set and the fourth user identification information set in the target association relation with a third label, wherein the third label is used for representing the software support of the user identification information association to connect with the first network.

9. The method of claim 8, further comprising:

and associating the user identification information which does not belong to the second user identification information set and/or does not belong to the fourth user identification information set in the target association relation with a fourth label, wherein the fourth label is used for representing that software associated with the user identification information does not support connection with the first network.

10. The method according to any one of claims 3 or 4,

acquiring a second message set in the second network, wherein each second message in the second message set is associated with a second terminal device and a user identification information, and each second message comprises a second message used for indicating whether a target switch unit of the second terminal device is in an on state or not, and the target switch unit is a switch unit of the terminal device connected with the first network;

and determining a fifth user identification information set in the second message set based on each piece of the second information, wherein the target switch unit of the second terminal equipment associated with the user identification information in the fifth user identification information set is in an on state.

11. The method of claim 10, further comprising:

12. The method of claim 11, further comprising:

and associating each piece of user identification information which does not belong to the second user identification information set and/or does not belong to the fifth user identification information set in the target association relation with a sixth label, wherein the sixth label is used for representing that a target switch unit of the terminal equipment associated with the user identification information is not in an on state.

13. The method of claim 2, 4 or 7, further comprising:

and outputting the target association relation to a network platform.

14. A terminal device identification apparatus, comprising:

an obtaining unit, configured to obtain a first message set detected at a target communication interface, where the target communication interface is an interface between a core network device and an access network device, a first message in the first message set is a message in a first network, each first message includes device type information of a first terminal device, the device identification information is used to characterize that the first terminal device is connected to the first network, and the first network is a target network of an independent network;

a processing unit, configured to obtain, based on the device type information included in the first message set, a first subscriber identity information set associated with at least one piece of device type information, where a terminal device associated with subscriber identity information in the first subscriber identity information set supports connection to the first network.

15. A terminal device identification apparatus, comprising: a memory for storing program instructions; a processor for calling and executing program instructions in said memory, performing the method of any of claims 1-13.

16. A computer-readable storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method according to any one of claims 1-13.