Information processing method, first function, first terminal, storage medium and product

Abstract

The invention discloses an information processing method, a first function, a first terminal, a computer readable storage medium and a computer program product, and the method comprises the steps: the first function receives a first message sent by a first application function, determines a target identifier, and / or determines an indication parameter; the first terminal receives a second message including a target identifier and / or an indication parameter sent by the first function, determines or matches or obtains a device of the first terminal based on the target identifier, and / or determines the content of a message reported, fed back or sent by the first terminal to the first function based on the indication parameter, and / or determines the content of the message reported, fed back or sent by the first terminal to the first function based on the first indication parameter. Generating and / or updating a temporary identifier; the first function receives a third message sent by the first terminal, and determines an equipment identifier of the first terminal based on the second identifier; the first application function receives one or more of the following items: first information; and a device identifier of the first terminal.

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of communications, and particularly to an information processing method, a first function, a first terminal, a computer-readable storage medium, and a computer program product. Background Technology

[0002] Currently, the 3rd Generation Partnership Project (3GPP) research report references a temporary identifier (ID) technology proposed by relevant companies. This temporary ID technology is similar to the globally unique temporary UE identity (GUTI) of the 5th generation mobile communication technology core network (5GC) user equipment (UE) to protect subscription permanent identifier (SUPI) information. This requires an additional registration process and frequent reallocation of temporary IDs through the core network. Furthermore, each reallocation of the temporary ID requires a write process to be written to the passive IoT device for synchronization. Clearly, this solution suffers from significant process complexity. Therefore, there is an urgent need for a simpler technical solution to protect the device identifier privacy of passive IoT devices. Summary of the Invention

[0003] This application provides an information processing method, a first function, a first terminal, a computer-readable storage medium, and a computer program product, and provides a technical solution for protecting the privacy of tag information in passive Internet of Things.

[0004] In a first aspect, embodiments of this application provide an information processing method applied to a first function, including:

[0005] Receive a first message sent by a first application function; wherein the first message includes part or all of a first identifier representing the device identifier of the first terminal;

[0006] Determine a target identifier; wherein the target identifier is used to identify the first terminal; the target identifier includes one of the following: a temporary identifier; a device identifier;

[0007] Send a second message to the first terminal; wherein the second message includes a target identifier.

[0008] Secondly, embodiments of this application provide an information processing method applied to a first function, including:

[0009] Receive a first message sent by a first application function; wherein the first message includes part or all of a first identifier representing the device identifier of the first terminal;

[0010] Determine a first indication parameter; wherein the first indication parameter is used to indicate the content of a message sent by the first terminal to the first function;

[0011] Send a second message to the first terminal; wherein the second message includes the first indication parameter.

[0012] Thirdly, embodiments of this application provide an information processing method applied to a first terminal, comprising:

[0013] Receive a second message sent by a first function; wherein the second message includes one or more of the following: a target identifier; a first indication parameter; the first indication parameter is used to indicate the content of the message sent by the first terminal to the first function; the target identifier is used to identify the first terminal; the target identifier includes one of the following: a temporary identifier; a device identifier;

[0014] Based on the target identifier, determine or match or obtain the device of the first terminal, and / or based on the first indication parameter, determine the content of the message reported or fed back or sent by the first terminal to the first function, and / or based on the first indication parameter, generate and / or update the temporary identifier.

[0015] Fourthly, embodiments of this application provide an information processing method applied to a first function, including:

[0016] Receive a first message sent by a first application function; wherein the first message includes part or all of a first identifier representing the device identifier of the first terminal;

[0017] Determine a target identifier; wherein the target identifier is used to identify the first terminal; the target identifier includes one of the following: a tag identifier; a device identifier;

[0018] Send a second message to the first terminal; wherein the second message includes a target identifier.

[0019] Fifthly, embodiments of this application provide an information processing method applied to a first terminal, comprising:

[0020] Receive a second message sent by the first function; wherein the second message includes one or more of the following: target identifier; second indication parameter; the target identifier is used to identify the first terminal; the target identifier includes one of the following: tag identifier; device identifier;

[0021] Based on the target identifier, determine or match or obtain the device of the first terminal, and / or based on the second indication parameter, determine the content of the message reported or fed back or sent by the first terminal to the first function.

[0022] Sixthly, embodiments of this application provide a first function, the first function including:

[0023] The first receiving module is configured to receive a first message sent by a first application function; wherein the first message includes part or all of a first identifier representing the device identifier of the first terminal;

[0024] A first processing module is configured to determine a target identifier; wherein the target identifier is used to identify the first terminal; the target identifier includes one of the following: a temporary identifier; a device identifier;

[0025] The first sending module is used to send a second message to the first terminal; wherein the second message includes a target identifier.

[0026] Seventhly, embodiments of this application provide a first function, the first function including:

[0027] The second receiving module is configured to receive a first message sent by the first application function; wherein the first message includes part or all of a first identifier representing the device identifier of the first terminal;

[0028] The second processing module is used to determine the first indication parameter; wherein the first indication parameter is used to indicate the content of the message sent by the first terminal to the first function;

[0029] A first sending module is configured to send a second message to the first terminal; wherein the second message includes a first indication parameter.

[0030] Eighthly, embodiments of this application provide a first terminal, the first terminal comprising:

[0031] The third receiving module is configured to receive a second message sent by the first function; wherein the second message includes one or more of the following: a target identifier; a first indication parameter; the first indication parameter is used to indicate the content of a message sent by the first terminal to the first function; the target identifier is used to identify the first terminal; the target identifier includes one of the following: a temporary identifier; a device identifier;

[0032] The third processing module is used to determine, match, or obtain the device of the first terminal based on the target identifier, and / or determine the content of the message reported, fed back, or sent by the first terminal to the first function based on the first indication parameter, and / or generate and / or update the temporary identifier based on the first indication parameter.

[0033] Ninthly, embodiments of this application provide a first function, the first function including:

[0034] The fourth receiving module is used to receive a first message sent by the first application function; wherein the first message includes part or all of a first identifier that represents the device identifier of the first terminal;

[0035] The fourth processing module is used to determine a target identifier; wherein the target identifier is used to identify the first terminal; the target identifier includes one of the following: a tag identifier; a device identifier;

[0036] The fourth sending module is used to send a second message to the first terminal; wherein the second message includes a target identifier.

[0037] In a tenth aspect, embodiments of this application provide a first terminal, the first terminal comprising:

[0038] The fifth receiving module is used to receive a second message sent by the first function; wherein the second message includes one or more of the following: a target identifier; a second indication parameter; the second indication parameter is used to indicate the content of the message sent by the first terminal to the first function; the target identifier is used to identify the first terminal; the target identifier includes one of the following: a tag identifier; a device identifier;

[0039] The fifth processing module is used to determine, match, or obtain the device of the first terminal based on the target identifier, and / or determine the content of the message reported, fed back, or sent by the first terminal to the first function based on the second indication parameter.

[0040] In one aspect, embodiments of this application provide a first function, the first function including:

[0041] The first memory is used to store executable instructions;

[0042] The first processor, when executing executable instructions stored in the first memory, implements the above-described information processing method.

[0043] In a twelfth aspect, embodiments of this application provide a first terminal, the first terminal comprising:

[0044] The second memory is used to store executable instructions;

[0045] The second processor, when executing executable instructions stored in the second memory, implements the above-described information processing method.

[0046] In a thirteenth aspect, embodiments of this application provide a computer-readable storage medium storing one or more programs that can be executed by one or more processors to implement the information processing method described above.

[0047] In a fourteenth aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the information processing method described above.

[0048] This application primarily aims to achieve privacy protection by utilizing the Tag ID of passive IoT tags or generating temporary IDs from passive IoT tag devices to replace existing network-generated temporary ID schemes. This approach leverages existing Tag IDs of passive IoT tags or generates temporary IDs from passive IoT tag devices, eliminating the need for frequent write operations to protect the privacy of passive IoT device identifiers over the air interface. Furthermore, it avoids introducing new registration processes and requires no write operations; instead, it can be implemented through command message flows that slightly extend existing application functions to initiate business operations (such as inventory checks, read / write, and deactivation). Attached Figure Description

[0049] Figure 1 This is a schematic diagram of a communication system according to an embodiment of this application;

[0050] Figure 2 Flowchart of the information processing method provided in the embodiments of this application Figure 1 ;

[0051] Figure 3 A schematic diagram of a first function provided in an embodiment of this application. Figure 1 ;

[0052] Figure 4 A schematic diagram of a first function provided in an embodiment of this application. Figure 2 ;

[0053] Figure 5 A schematic diagram of a first terminal provided in an embodiment of this application. Figure 1 ;

[0054] Figure 6 A schematic diagram of a first function provided in an embodiment of this application. Figure 3 ;

[0055] Figure 7 A schematic diagram of a first terminal provided in an embodiment of this application. Figure 2 ;

[0056] Figure 8 This is a schematic structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0057] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0058] The embodiments of this application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), next-generation communication systems, or other communication systems, etc.

[0059] Figure 1 This is a schematic diagram of a communication system according to an embodiment of this application.

[0060] like Figure 1As shown, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.

[0061] exist Figure 1 In the communication system 100 shown, network device 120 can be an access network device that communicates with terminal device 110. The access network device can provide communication coverage for a specific geographical area and can communicate with terminal device 110 located within that coverage area.

[0062] Network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB or gNodeB) in an NR system, or a radio controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, or network equipment in a future evolved Public Land Mobile Network (PLMN), etc.

[0063] Terminal equipment 110 can also be referred to as UE, tag, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc. Terminal equipment can be a station (STAION, ST) in a WLAN, a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle equipment, wearable device, and next-generation communication systems, such as terminal equipment in NR networks or terminal equipment in future evolved Public Land Mobile Network (PLMN) networks, etc.

[0064] Terminal device 110 can be used for device-to-device (D2D) communication.

[0065] The communication system 100 may further include a core network device 130 that communicates with the base station. This core network device 130 may be a 5GC device, such as an Access and Mobility Management Function (AMF) device, an Authentication Server Function (AUSF) device, a User Plane Function (UPF) device, or a Session Management Function (SMF) device. Optionally, the core network device 130 may also be an Evolved Packet Core (EPC) device for an LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions of both SMF and PGW-C. During network evolution, the names of the aforementioned core network devices may change, or new network entities may be formed by dividing the core network functions; this embodiment does not limit this.

[0066] Figure 1 An exemplary embodiment shows a base station, a core network device, and two UEs. Optionally, the communication system 100 may include multiple base stations, and the coverage area of ​​each base station may include other numbers of UEs. This application embodiment does not limit this.

[0067] It should be noted that, Figure 1This application merely illustrates the system to which this application applies; of course, the methods shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as LTE protocol, NR protocol, and related protocols applied to future communication systems, and this application does not limit this.

[0068] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0069] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0070] Before explaining this application, the following section describes the schemes for allocating temporary IDs in related technologies:

[0071] Currently, 3GPP RAN1 has explicitly informed SA2 of the limitations of the write process: the write process for passive IoT devices cannot be guaranteed to succeed; the power consumption of the write process for passive IoT devices is higher than that of the read process; RAN1 recommends that frequent write operations should be avoided.

[0072] The temporary ID scheme referenced in the 3GPP research report requires frequent additional registration procedures to reallocate temporary IDs and then synchronously write them to passive IoT devices. This process is complex and costly. Furthermore, the system needs to support additional registration procedures for temporary ID allocation and frequent write procedures to synchronize temporary IDs with passive IoT devices. This places high demands on passive IoT tags, significantly impacting their power consumption, cost, and lifespan, making practical industrial implementation unlikely. Therefore, protecting the privacy of the unique device identifier of passive IoT devices is a crucial issue, especially since low-end passive IoT tags (such as Type 1 tags) do not support encryption, and there are no relevant low-cost solutions for protecting the privacy of the unique device identifier. Moreover, if SA3 must protect privacy, SA2 needs to provide a corresponding solution.

[0073] Figure 2 This is a flowchart illustrating an information processing method provided in an embodiment of this application, such as... Figure 2 As shown, this method is applied to Figure 1 In the communication system 100 shown, the method includes:

[0074] Step 201: The first function receives the first message sent by the first application function.

[0075] The first message includes part or all of the first identifier that represents the device identifier of the first terminal.

[0076] In this embodiment of the application, the first application function includes, but is not limited to, Figure 1 The core network equipment 130 includes the application functions (AFs).

[0077] In this embodiment of the application, the first function includes, but is not limited to, Figure 1 The core network equipment 130 includes network functions (NFs), such as passive Internet of Things (AIoT) NFs.

[0078] In this embodiment, the first terminal includes, but is not limited to, Figure 1 The terminal device 110 in the middle, for example, an AIoT device or an AIoT tag.

[0079] In some embodiments, the first message may be a command initiated by the AF to perform a business operation (such as inventory, read, write, or deactivate).

[0080] In this embodiment of the application, the device identifier of the first terminal can be assigned by the operator or by a third-party application; here, the device ID can be an Electronic Product Code (EPC); it should be noted that the EPC can be a single complete EPC, and / or a complete list of EPCs, and / or a non-complete EPC that can represent a group of passive IoT devices.

[0081] In this embodiment of the application, the first message also includes a first application function identifier, such as AF ID.

[0082] Step 202: First function: Determine the target identifier.

[0083] The target identifier is used to identify the first terminal; the target identifier includes the following: temporary identifier; device identifier.

[0084] In some embodiments, a target identifier is determined based on the type of a first identifier and / or a first mapping relationship; wherein the first mapping relationship is a mapping relationship between a device identifier and a temporary identifier.

[0085] In some embodiments, based on a first application function identifier and / or service level agreement, it is determined whether to enable privacy protection for the device identifier; if privacy protection for the device identifier is enabled, the target identifier is determined. If privacy protection for the device identifier is not enabled, it is determined that the second message sent to the first terminal includes the device identifier of the first terminal.

[0086] In some embodiments, if privacy protection for the device identifier is enabled, the target identifier is determined based on the type of the first identifier and / or the first mapping relationship.

[0087] Here, if the first identifier represents at least one specific passive IoT device, and there is a temporary identifier that has a mapping relationship with the first identifier, the target identifier is determined to be a temporary identifier. If the first identifier represents at least one specific passive IoT device, and there is no temporary identifier that has a mapping relationship with the first identifier, the target identifier is determined to be a device identifier. If the first identifier represents a group of passive IoT devices, the target identifier is determined to be a device identifier. If the first identifier represents a group of passive IoT devices, and there is a temporary identifier that has a mapping relationship with the first identifier, and the temporary identifier represents a group of passive IoT devices, the target identifier is determined to be either a temporary identifier or a device identifier.

[0088] In some embodiments, the target identifier includes one of the following: a tag identifier; a device identifier.

[0089] In some embodiments, based on a first application function identifier and / or a service level agreement, it is determined whether to enable privacy protection for the device identifier; if privacy protection for the device identifier is enabled, a target identifier is determined based on the type of the first identifier and / or a second mapping relationship; wherein, the second mapping relationship is a mapping relationship between the device identifier and a temporary identifier.

[0090] Here, if the first identifier represents at least one specific passive IoT device and there is no tag identifier that has a mapping relationship with the first identifier, the target identifier is determined to be a device identifier; if the first identifier represents a group of passive IoT devices, the target identifier is determined to be a device identifier; if the first identifier represents at least one specific passive IoT device and there is a tag identifier that has a mapping relationship with the first identifier, the target identifier is determined to be a tag identifier.

[0091] Step 203: Determine the first function indicator parameters.

[0092] The indication parameters include a first indication parameter and / or a second indication parameter. The first indication parameter is used to indicate the content of the message sent by the first terminal to the first function; the second indication parameter is used to indicate the content of the message sent by the first terminal to the first function.

[0093] In some embodiments, if privacy protection for the device identifier is enabled, the indication content of the first indication parameter is determined based on the first identifier and / or the first mapping relationship; wherein, the first mapping relationship is the mapping relationship between the device identifier and the temporary identifier.

[0094] In some embodiments, based on the first application function identifier and / or service level agreement, it is determined whether to enable privacy protection for the device identifier; if privacy protection for the device identifier is enabled, the instruction content of the first instruction parameter is determined based on whether it is necessary to update the temporary identifier and / or the first identifier and / or the first mapping relationship.

[0095] Here, if there is a temporary identifier that is mapped to the first identifier, the instruction content is determined to be used to instruct the reporting of the temporary identifier. If there is no temporary identifier that is mapped to the first identifier, the instruction content is determined to be used to instruct the reporting of both the device identifier and the temporary identifier. If the temporary identifier needs to be updated, the instruction content is determined to be used to instruct the reporting of both the updated temporary identifier and the device identifier, or the instruction content is used to instruct the reporting of both the updated temporary identifier and the original temporary identifier.

[0096] In some embodiments, if privacy protection for the device identifier is enabled, the indication content of the second indication parameter is determined based on the first identifier and / or the second mapping relationship.

[0097] Here, if there is no tag identifier that is mapped to the first identifier, the instruction content is determined to be used to indicate that both the tag identifier and the device identifier are reported simultaneously; if there is no tag identifier that is mapped to the first identifier, the instruction content is determined to be used to indicate that the tag identifier is reported.

[0098] It should be noted that the execution order of steps 202 and 203 can be interchanged, or they can be executed simultaneously.

[0099] Step 204: The first function sends a second message to the first terminal.

[0100] The second message includes one or more of the following: target identifier; indication parameters.

[0101] In this embodiment of the application, the second message is a business operation command (such as inventory, read, write, deactivate, etc.).

[0102] In this embodiment of the application, if privacy protection for device identification is enabled, the second message includes one or more of the following: indication parameters; target identifier.

[0103] Step 205: The first terminal receives the second message.

[0104] Step 206: The first terminal determines or matches or obtains the device of the first terminal based on the target identifier; and / or determines the content of the message reported or fed back or sent by the first terminal to the first function based on the indication parameter; and / or generates and / or updates the temporary identifier based on the first indication parameter.

[0105] In some embodiments, the content of the message reported, fed back, or sent by the first terminal to the first function is determined based on the first indication parameter.

[0106] In some embodiments, the content of the message reported, fed back, or sent by the first terminal to the first function is determined based on the second indication parameter.

[0107] Step 207: The first terminal sends a third message to the first function.

[0108] The third message includes one or more of the following: first information; second identifier.

[0109] Here, the second identifier includes the following: device identifier and temporary identifier; temporary identifier; temporary identifier before update and temporary identifier after update; device identifier and temporary identifier after update.

[0110] In this embodiment of the application, the first information includes, but is not limited to, inventory information, read information, write result information, and deactivation result information. That is, the first information is business information obtained by responding to the business operation command of the second message, such as tag temperature or environmental parameters.

[0111] If the second message includes a first indication parameter, and the first indication parameter is used to indicate that the device identifier and the temporary identifier are reported simultaneously, the first device identifier and the first temporary identifier are sent to the first function.

[0112] If the second message includes a first indication parameter, and the first indication parameter is used to indicate that the device identifier and the temporary identifier are reported simultaneously, and the first terminal does not have a temporary identifier locally, a temporary identifier is generated and stored locally; the first device identifier and the first temporary identifier are sent to the first function; wherein, the first temporary identifier is a newly generated temporary identifier.

[0113] If the second message includes a first indication parameter, and the first indication parameter is used to indicate the reporting of the updated temporary identifier and the previous temporary identifier, a new temporary identifier is generated locally to obtain the updated temporary identifier; the updated temporary identifier is stored; furthermore, the updated temporary identifier and the previous temporary identifier are sent to the first function, and / or the previous temporary identifier is deleted locally.

[0114] If the second message includes a first indication parameter, and the first indication parameter is used to indicate the reporting device identifier and the updated temporary identifier, a new temporary identifier is generated locally to obtain the updated temporary identifier; the updated temporary identifier is stored; furthermore, the first device identifier and the second temporary identifier are sent to the first function, and / or the temporary identifier before the update is deleted locally; wherein, the second temporary identifier is the updated temporary identifier.

[0115] If the second message includes a first indication parameter, and the first indication parameter is used to indicate the reporting of a temporary identifier, then the first temporary identifier is sent to the first function.

[0116] If the second message does not include the first indication parameter, send the device identifier of the first terminal to the first function.

[0117] In some embodiments, the second identifier includes one of the following: a device identifier and a tag identifier; the tag identifier.

[0118] It should be noted that the first terminal has a first parameter pre-stored locally; the first parameter, by default, represents the identifier of the unreported device.

[0119] If the second message includes a second indication parameter, and the second indication parameter is used to indicate that the tag identifier and the device identifier are reported simultaneously, the first device identifier and the first tag identifier are sent to the first function.

[0120] If the second message includes a second indication parameter, and the second indication parameter is used to indicate that the tag identifier and the device identifier are reported simultaneously, the first terminal sends the first device identifier and the first tag identifier to the first function; and updates the first parameter to indicate that the device identifier has been reported.

[0121] If the second message includes a second indication parameter, and the second indication parameter is used to indicate the reporting tag identifier, then the first tag identifier is sent to the first function.

[0122] If the second message does not include the second indication parameter, send the device identifier of the first terminal to the first function.

[0123] If the second message does not include the second indication parameter, and the first parameter indicates that the device identifier has not been reported, send the first tag identifier and the first device identifier to the first function; update the first parameter to indicate that the device identifier has been reported.

[0124] If the second message does not include the second indication parameter, and the first parameter represents the reported device identifier, send the first tag identifier to the first function.

[0125] Step 208: The first function receives the third message and determines the device identifier of the first terminal based on the second identifier, i.e., queries, and / or updates, and / or establishes, and / or saves the mapping relationship related to the second identifier, and determines the device identifier of the first terminal based on the mapping relationship and the second identifier.

[0126] The mapping relationship is obtained by learning the information in the third message reported by the first terminal from the first function.

[0127] In some embodiments, if the second identifier includes a first device identifier and a first temporary identifier, a mapping relationship between the first device identifier and the first temporary identifier is established and saved; the first device identifier is determined to be the device identifier of the first terminal.

[0128] It should be noted that if the second identifier includes the first device identifier and the first temporary identifier, and there is a second device identifier that has a mapping relationship with the first temporary identifier, the mapping relationship between the first temporary identifier and the second device identifier is deleted; wherein the first device identifier and the second device identifier are different; the mapping relationship between the first device identifier and the first temporary identifier is established and saved.

[0129] In some embodiments, if the second identifier includes a first temporary identifier, a first device identifier matching the first temporary identifier is determined as the device identifier of the first terminal based on a first mapping relationship; wherein, the first mapping relationship is a mapping relationship between the device identifier and the temporary identifier.

[0130] It should be noted that if the second identifier includes the first temporary identifier, and the first device identifier corresponding to the first temporary identifier cannot be obtained based on the first mapping relationship, the first function resends the second message to the first terminal; wherein, the resent second message includes a first indication parameter for instructing simultaneous reporting of the temporary identifier and the device identifier; the first terminal receives the resent second message from the first function and resends a third message to the first function; wherein, the resent third message includes the first temporary identifier and the first device identifier; the first function receives the resent third message from the first terminal. If there is a second temporary identifier that has a mapping relationship with the first device identifier, the mapping relationship between the second temporary identifier and the first device identifier is deleted; wherein, the second temporary identifier and the first temporary identifier are different; a mapping relationship between the first device identifier and the first temporary identifier is established and saved.

[0131] In some embodiments, if the second identifier includes a temporary identifier before the update and a temporary identifier after the update, based on the first mapping relationship, a third device identifier that has a mapping relationship with the temporary identifier before the update is determined as the device identifier of the first terminal; a mapping relationship between the third device identifier and the temporary identifier after the update is established and saved; and the mapping relationship between the third device identifier and the temporary identifier before the update is deleted.

[0132] In some embodiments, if the second identifier includes a first device identifier and a second temporary identifier, and the second temporary identifier is an updated temporary identifier, the first device identifier is determined to be the device identifier of the first terminal; the mapping relationship between the temporary identifier before the update and the first device identifier is deleted; and the mapping relationship between the first device identifier and the second temporary identifier is established and saved.

[0133] In some embodiments, if the second identifier includes a first device identifier and a first tag identifier, a mapping relationship between the first device identifier and the first tag identifier is established and saved; the first device identifier is determined to be the device identifier of the first terminal.

[0134] Here, if the second identifier includes the first device identifier and the first tag identifier, and there is a second device identifier that has a mapping relationship with the first tag identifier, the mapping relationship between the first tag identifier and the second device identifier is deleted; wherein, the first device identifier and the second device identifier are different; the mapping relationship between the first device identifier and the first tag identifier is established and saved.

[0135] In some embodiments, if the second identifier includes the first tag identifier, the first device identifier that matches the first tag identifier is determined as the device identifier of the first terminal based on the second mapping relationship.

[0136] Here, if the second identifier includes the first tag identifier, and the first device identifier corresponding to the first tag identifier cannot be obtained based on the second mapping relationship, the first function resends the second message to the first terminal; wherein, the resend of the second message includes a second indication parameter for indicating that both the tag identifier and the device identifier should be reported simultaneously; the first terminal receives the resend of the second message from the first function and resends a third message to the first function; wherein, the resend of the third message includes the first device identifier and the first tag identifier; the first function receives the resend of the third message from the first terminal. If there is a second tag identifier that has a mapping relationship with the first device identifier, the mapping relationship between the second tag identifier and the first device identifier is deleted; wherein, the second tag identifier and the first tag identifier are different; a mapping relationship between the first device identifier and the first tag identifier is established and saved.

[0137] In some embodiments, when the first function updates the device identifier corresponding to an existing tag identifier, if privacy protection for the device identifier is activated and there is no mapping relationship corresponding to the first tag identifier, the first function resends a second message to the first terminal; wherein, the resend of the second message includes a second indication parameter for instructing the simultaneous reporting of the tag identifier and the device identifier; the first terminal receives the resend of the second message from the first function and resends a third message to the first function; wherein, the resend of the third message includes the first device identifier and the first tag identifier; the first function receives the resend of the third message from the first terminal; wherein, the resend of the third message includes the first device identifier and the first tag identifier; if there is a second tag identifier that has a mapping relationship with the first device identifier, the mapping relationship between the second tag identifier and the first device identifier is deleted; wherein, the second tag identifier and the first tag identifier are different; a mapping relationship between the first device identifier and the first tag identifier is established and saved.

[0138] Step 209: The first function sends one or more of the following to the first application function: first information; device identifier of the first terminal.

[0139] Furthermore, the first application function receives one or more of the following: first information; device identifier of the first terminal.

[0140] This application provides an information processing method, comprising: a first application function sending a first message to a first function, wherein the first message includes part or all of a first identifier representing a device identifier of a first terminal; the first function receiving the first message and determining a target identifier, and / or determining an indication parameter, wherein the target identifier is used to identify the first terminal, and the indication parameter is used to indicate the content of a message sent by the first terminal to the first function, the target identifier including one of the following: a temporary identifier; a device identifier; a tag identifier; the first function sending a second message to the first terminal; wherein the second message includes one or more of the following: a target identifier; an indication parameter; the first terminal receiving the second message and, based on the target identifier, determining or matching or obtaining the device of the first terminal, and / or, based on the indication parameter, determining a first The terminal reports, provides feedback on, or sends messages to the first function, and / or generates a temporary identifier based on the first indication parameter; the first terminal sends a third message to the first function, wherein the third message includes one or more of the following: first information; a second identifier; the second identifier includes one of the following: a device identifier and a temporary identifier; a temporary identifier; a temporary identifier before and after the update; a device identifier and the updated temporary identifier; a tag identifier; the first function receives the third message and determines the device identifier of the first terminal based on the second identifier; the first function sends one or more of the following: first information; the device identifier of the first terminal; the first application function receives one or more of the following: first information; the device identifier of the first terminal; that is, this application mainly achieves privacy protection by using the Tag ID of a passive IoT tag or generating a temporary ID from a passive IoT tag device to replace the relevant schemes for generating temporary IDs in the network. This approach leverages existing Tag IDs from passive IoT tags or generates temporary IDs from passive IoT tag devices, eliminating the need for frequent write processes to protect the privacy of passive IoT device identifiers over the air interface. Furthermore, it avoids introducing new registration processes and requires no write operations. Instead, it can be achieved through command message processes that slightly extend existing application functions to initiate business operations (such as inventory checks, read / write, and deactivation).

[0141] The following will describe an exemplary application of the embodiments of this application in a real-world application scenario.

[0142] This application enhances the 5GC architecture and related processes in the relevant technologies; it achieves device ID protection through the interaction between AIoT NF, AF and device tag; it enables the binding between Tag ID and Device ID, and / or the transmission of Tag ID, and / or the transmission of Device ID by AIoT NF, and obtains Device ID based on Tag ID; at the same time, it adds information reporting instructions or tag local marking.

[0143] It should be noted that this application includes schemes that use AIoT NF as the center (Centric) and replace the temporary ID generated by the relevant network with Tag ID, and schemes that use device tags as the center and replace the temporary ID generated by the relevant network with Tag ID.

[0144] For solutions using AIoT NF as the centric, the following steps are included:

[0145] Step A1: AF sends an Inventory message.

[0146] The Inventory message carries parameters such as Device ID 1 and AF ID.

[0147] For example, Device ID 1 is an EPC; an EPC can be a single complete EPC, a list of complete EPCs, or a non-complete EPC representing a group of passive IoT devices.

[0148] Step A2: The AIoT NF receives the Inventory message sent by the AF via the NEF and determines whether to enable Privacy protection based on the AF ID and SLA protocol. If privacy protection is enabled, the AIoT NF adds an information reporting indication parameter to the Inventory command sent to the device tag; simultaneously, the core network system determines the value of the information reporting indication parameter based on whether there is a related binding relationship between the Device ID and Tag ID; furthermore, it sends the Inventory command to the Reader.

[0149] If privacy protection is not enabled (by default), AIoT NF will not add information reporting indication parameters to the Inventory command and will not use Tag ID to replace Device ID.

[0150] Here, the privacy protection function in AIoT NF is optional, meaning that operators can flexibly enable or disable the privacy protection function in AIoT NF according to the AF SLA agreement.

[0151] In some embodiments, the AIoT NF queries whether the binding relationship between the relevant Device ID and Tag ID has been stored in the 5GC system based on the Device ID1 issued by the AF to determine the value of the information reporting parameters (uplink privacy protection):

[0152] If no mapping exists between Device IDs and Tag IDs, add a reporting indication parameter to the Inventory command, specifying that the device tag must report both the Device ID and Tag ID. If a mapping exists between Device IDs and Tag IDs, add a reporting indication parameter to the Inventory command, instructing the device tag to report only the Tag ID to achieve privacy protection.

[0153] It should be noted that AIoT NF learns and implements the binding relationship between Device ID and Tag ID by the response of passive IoT devices in the Inventory process and stores it in 5GC.

[0154] In some embodiments, the AIoT NF determines whether to use the Device ID or Tag ID to match the passive IoT device based on the type of Device ID1 and whether there is a related binding relationship between Device ID and Tag ID in the 5GC (downlink privacy protection):

[0155] If Device ID1 represents one or more specific passive IoT devices, and there is a binding relationship between Device ID and Tag ID in the 5GC system, then Tag ID is used instead of Device ID to identify the passive IoT device, thereby protecting the Device ID in the downlink message.

[0156] If the 5GC system does not have a corresponding binding relationship between Device ID and Tag ID, it will continue to use Device ID to identify passive IoT devices.

[0157] If Device ID1 represents a group of passive IoT devices, regardless of whether there is a binding relationship between Device ID and Tag ID in the 5GC system, the Device ID will continue to be used to identify a group of passive IoT devices. This is because the Device ID only contains incomplete passive IoT tag information, which can protect the passive IoT tag information in downlink messages, and at the same time can efficiently identify a group of passive IoT devices.

[0158] Step A3: The device tag receives the Inventory command from the Reader and matches it with the Device ID or Tag ID in the Inventory command. The response content is determined according to the information reporting indication parameters. For example, the device tag may report both the complete Device ID and Tag ID to the AIoT NF at the same time, or report only the Tag ID to the AIoT NF. If the device tag receives an Inventory command without information reporting indication parameters, it may report only the complete Device ID to the AIoT NF.

[0159] Step A4: The AIoT NF receives the response sent by the device tag.

[0160] In this embodiment of the application, if the device tag reports both Device ID and Tag ID according to the information reporting instruction parameters, the AIoT NF stores the Device ID and Tag ID, establishes a mapping relationship between Device ID and Tag ID, and stores it in the 5GC system.

[0161] If the device tag only reports the tag ID according to the information reporting instruction parameters, the AIoT NF needs to find the device ID within 5GC by using the reported tag ID based on the existing mapping relationship between device ID and tag ID.

[0162] If the device tag only reports the Tag ID, but the AIoT NF cannot find the Device ID within the 5GC, it needs to resend a storage command with information reporting indication parameters to the device tag. These parameters should be set to require both the Device ID and Tag ID to be reported simultaneously. If the device tag successfully reports both the Device ID and Tag ID, the AIoT NF will store the reported Device ID and Tag ID in the 5GC, re-establishing the binding relationship between the Device ID and Tag ID.

[0163] If the AF updates an existing tag with a new Device ID, and privacy protection is enabled during the initial inventory, and AIoTNF cannot find the binding relationship between the Device ID and Tag ID in the 5GC system based on the Device ID, the AIoT NF reissues an inventory command carrying information reporting indication parameters to the device tag. These information reporting indication parameters are set to require simultaneous reporting of both the Device ID and Tag ID. The tag device will report both the Device ID and Tag ID according to the information reporting indication parameters. The AIoT NF stores the reported Device ID and Tag ID in the 5GC, re-establishes and saves the binding relationship between the Device ID and Tag ID, and deletes any existing old binding relationships.

[0164] Step A5: The AIoT NF sends inventory information carrying Device ID information to the AF.

[0165] For the solution using device tags as centrics, a reporting flag parameter is added to the device tag. The factory default value of this flag parameter is "No Device ID reported". This solution includes the following steps:

[0166] Step B1: AF sends an Inventory message.

[0167] The Inventory message carries parameters such as Device ID1 and AF ID.

[0168] For example, Device ID1 is EPC; EPC can be a single complete EPC, a list of complete EPCs, or a non-complete EPC representing a group of passive IoT devices.

[0169] Step B2: The AIoT NF receives the Inventory message sent by the AF via the NEF. Based on the AF ID and SLA protocol, it determines whether to enable Privacy protection. If Privacy protection is enabled, the AIoT NF determines whether to use the Device ID or Tag ID to identify the passive IoT device based on the type of Device ID1 and whether there is a related binding relationship between Device ID and Tag ID in 5GC, and sends an Inventory command to the Reader.

[0170] It should be noted that if privacy protection is not enabled, AIoT NF will not add information reporting indication parameters to the Inventory command and will not use Tag ID to replace Device ID; if privacy protection is enabled, AIoT NF will determine whether to use Device ID or Tag ID to identify passive IoT devices based on the type of Device ID1 and whether there is a related binding relationship between Device ID and Tag ID in 5GC, in order to match passive IoT devices (downlink privacy protection):

[0171] If Device ID1 issued by AF represents one or more specific passive IoT devices, and the 5GC system has a related binding relationship between Device ID and Tag ID, then Tag ID is used instead of Device ID to identify the passive IoT device, thereby achieving protection of Device ID in downlink messages.

[0172] If the 5GC system does not have a binding relationship between Device ID and Tag ID, the Device ID is used to identify the passive IoT device.

[0173] If Device ID1 issued by AF represents a group of passive IoT devices, regardless of whether there is a binding relationship between Device ID and Tag ID in the 5GC system, this Device ID is used to identify a group of passive IoT devices. This is because Device ID1 only contains incomplete passive IoT tag information, which can protect the passive IoT tag information in downlink messages, and at the same time can efficiently identify a group of passive IoT devices.

[0174] Step B3: The device tag receives the Inventory command from the Reader, matches the device tag with the DeviceID or Tag ID in the Inventory command, and determines the response content based on the reported tag parameters (uplink privacy protection).

[0175] If the Inventory command does not carry an information reporting instruction parameter and the tag local reporting flag parameter is "No Device ID reported", then both the Device ID and Tag ID will be reported to the AIoT NF at the same time; and the device tag local flag will be updated to "Device ID reported".

[0176] If the Inventory command does not carry an information reporting indication parameter and the local reporting tag parameter is "Device ID reported", then only the Tag ID will be reported to the AIoT NF.

[0177] If the Inventory command includes an information reporting instruction parameter, this parameter requires both the Device ID and Tag ID to be reported. For matching device tags, the local reporting flag parameter is ignored, and both the Device ID and Tag ID are reported. The reporting flag parameter is also set to "Reported Device".

[0178] Step B4: The AIoT NF receives the response sent by the device tag.

[0179] In this embodiment, if the device tag reports both Device ID and Tag ID, the AIoT NF stores the Device ID and Tag ID, establishes a binding relationship between the Device ID and Tag ID, and stores the 5GC system. If the AIoT NF discovers that another binding relationship already exists between the Device ID and the Tag ID in the 5GC system, it needs to delete the existing binding relationship and save the new binding relationship.

[0180] If the device tag only reports the Tag ID, the AIoT NF will query the Device ID in the 5GC system based on the binding relationship between the Device ID and the Tag ID. If the corresponding Device ID cannot be found based on the reported Tag ID, the AIoT NF will resend the Inventory command to the device tag, carrying the Device ID and additional information reporting parameters, requiring both the Device ID and the Tag ID to be reported.

[0181] Step B5: The AIoT NF sends inventory information to the AF, carrying the Device ID.

[0182] It should be noted that the technical solutions centered on AIoT NF and those based on device tags do not require the introduction of an additional registration process network to allocate temporary IDs. The network does not need to write a process to allocate temporary IDs and synchronize with passive IoT devices. Only additional instruction parameters are needed to guide passive IoT devices to report Device ID and Tag ID, making full use of existing Tag IDs to achieve privacy protection for Device IDs.

[0183] This application enhances the 5GC architecture and related processes in the relevant technologies, using AIoT NF to achieve the binding between temporary ID and Device ID, and / or the transmission of temporary ID, and / or the transmission of Device ID, obtaining Device ID based on the generation of temporary ID by passive IoT tag devices, the generation of temporary ID by passive IoT devices, and adding ID reporting indication parameters.

[0184] For a solution that uses the device tag as the centric, i.e., a temporary ID generated based on a passive IoT tag, the following steps are included:

[0185] Step C1: AF sends an Inventory message.

[0186] The Inventory message carries parameters such as Device ID1 and AF ID.

[0187] For example, Device ID1 is EPC; EPC can be a single complete EPC, a list of complete EPCs, or a non-complete EPC representing a group of passive IoT devices.

[0188] Step C2: The AIoT NF receives the Inventory message sent by the AF through the NEF and decides whether to enable Privacy protection in the AIoT NF according to the SLA agreement signed with the customer (AF ID). If Privacy protection is enabled, the Inventory command sent by the AIoT NF to the Reader needs to add the ID reporting indication parameter.

[0189] If privacy protection is not enabled, AIoT NF will not add an ID reporting indicator parameter to the Inventory command, and will not use a temporary ID to replace the Device ID in messages such as Inventory'.

[0190] It should be noted that AIoT NF needs to decide whether to use Device ID or temporary ID to identify passive IoT devices (for downlink privacy protection).

[0191] Here, you can decide whether to use a Device ID or a temporary ID to identify a passive IoT device based on the Device ID type, the binding relationship between the Device ID and the temporary ID, and whether the temporary ID needs to be updated.

[0192] Specifically, if Device ID1 represents one or more specific passive IoT devices, and the 5GC system has a binding relationship between Device ID and Temporary ID for all tagged devices, then the Temporary ID is used to replace the Device ID to identify the passive IoT device, while carrying the ID reporting indication parameter "Report Temporary ID".

[0193] If Device ID1 represents one or more specific passive IoT devices, and the 5GC system has a binding relationship between Device IDs and temporary IDs for all tagged devices, and the temporary ID needs to be updated according to the system settings, then the temporary ID is used to replace the Device ID to identify the passive IoT device, while carrying the ID reporting indication parameter, which is set to "report the new temporary ID and Device ID" or "report the existing temporary ID and the new temporary ID".

[0194] If Device ID1 represents one or more specific passive IoT devices, and there is no binding relationship between Device ID and temporary ID in the system, continue to use Device ID to identify the passive IoT device, and carry the ID reporting instruction parameter, set to "report temporary ID and Device ID" (this is generally the case for the first inventory).

[0195] If Device ID1 represents a group of passive IoT devices, regardless of whether there is a binding relationship between Device ID and temporary ID in the system, this Device ID will continue to be used to identify the group of passive IoT devices. Because this Device ID only contains incomplete passive IoT tag information, it can protect the passive IoT tag information in downlink messages, while efficiently identifying a group of passive IoT devices;

[0196] If Device ID1 represents a group of passive IoT devices, and the tags of this group of passive IoT devices in the 5GC system all have a binding relationship between Device ID and temporary ID, and the temporary ID (e.g., an incomplete temporary ID that identifies a group of passive IoT devices) can efficiently identify a group of passive IoT devices (the temporary ID needs to be able to efficiently identify a group of passive IoT devices similar to the Device ID), then the temporary ID can be used to replace the Device ID to achieve complete downlink protection of Device ID information.

[0197] It should be noted that AIoT NF determines the value of the ID reporting indicator parameter based on the Device ID type, the binding relationship between the Device ID and the temporary ID, and whether the temporary ID needs to be updated. The specific logic is as follows:

[0198] If the 5GC system has a binding relationship between the Device ID and the Temporary ID, set the ID reporting indicator parameter to "report Temporary ID";

[0199] If the 5GC system does not have a binding relationship between the tag device Device ID and the temporary ID, set the ID reporting indicator parameter to "report temporary ID and device ID".

[0200] If the 5GC system needs to update the temporary ID, set the ID reporting indicator parameter to "report the new temporary ID and Device ID" or "report the existing temporary ID and the new temporary ID".

[0201] Step C3: The device tag receives the Inventory command from the Reader, matches the device tag with the Device ID or temporary ID, and determines the content to be responded to by the AIoT NF based on the ID reporting indication parameters. The logic is as follows (uplink privacy protection):

[0202] If the Inventory command includes an ID reporting instruction parameter, and the parameter is set to "report temporary ID and Device ID", the tag handles the temporary ID as follows: If the tag does not have a local temporary ID, the tag generates a new temporary ID and stores it locally. If a local temporary ID already exists, that temporary ID is used. Then, both the Device ID and the temporary ID are reported to the AIoT NF simultaneously.

[0203] If the Inventory command carries an ID reporting instruction parameter, and the parameter is set to "report temporary ID", then only the temporary ID stored in the tag will be reported to AIoTNF to achieve privacy protection.

[0204] If the Inventory command includes an ID reporting instruction parameter set to "report new temporary ID and Device ID", the tag will generate a new temporary ID and then report both the Device ID and the new temporary ID to the AIoT NF. Afterwards, the existing temporary ID must be deleted, and the new temporary ID saved.

[0205] If the Inventory command includes an ID reporting instruction parameter, and the parameter is set to "report existing temporary ID and new temporary ID", then the tag will regenerate a temporary ID and then report both the existing temporary ID and the new temporary ID to the AIoT NF. Afterwards, the existing temporary ID needs to be deleted, and the new temporary ID saved.

[0206] Step C4: The AIoT NF receives the response sent by the device tag.

[0207] In this embodiment of the application, the AIoT NF receives the response to the device tag Inventory command, and the processing logic is as follows:

[0208] If the device tag reports both Device ID and Temporary ID, AIoT NF stores the Device ID and Temporary ID and establishes a mapping relationship between the Device ID and Temporary ID.

[0209] If the device tag only reports a temporary ID, AIoT NF can query the Device ID in 5GC based on the mapping relationship between the Device ID and the temporary ID.

[0210] Here, if the corresponding Device ID cannot be found based on the reported temporary ID, the AIoT NF resends commands such as inventory to the device tag, carrying the Device ID and ID reporting instruction parameters set to "report temporary ID and Device ID", requiring the simultaneous reporting of both Device ID and temporary ID.

[0211] If the AIoT NF triggers the temporary ID update process in step C2: If the ID reporting indication parameter is set to "report new temporary ID and Device ID", the AIoT NF receives the new temporary ID and Device ID reported by the device tag. The AIoT NF needs to store the new temporary ID and Device ID, and look up the binding record between the Device ID and the old temporary ID based on the Device ID. Then, it deletes the old binding record in 5GC to achieve the temporary ID update. If the ID reporting indication parameter is set to "report existing temporary ID and new temporary ID", the AIoT NF receives the new temporary ID and existing temporary ID reported by the passive IoT device. AIoTNF looks up the Device ID and existing temporary ID binding record based on the existing temporary ID, and updates the binding record with the Device ID and the new temporary ID in 5GC to achieve the temporary ID update.

[0212] Step C5: The AIoT NF sends inventory information to the AF, carrying the Device ID.

[0213] In this application's temporary ID solution based on passive IoT tags, there is no need to introduce an additional registration process network to allocate temporary IDs, nor is there a need for the network to implement the allocation of temporary IDs and the synchronization of passive IoT devices through writing processes. Only an additional ID reporting instruction parameter is added to guide the passive IoT devices to report Device IDs and / or temporary IDs, and the privacy protection of Device IDs is achieved by using the passive IoT devices to generate temporary IDs themselves.

[0214] Embodiments of this application provide a first function, which can be used to implement Figure 2 A corresponding embodiment provides an information processing method, referring to... Figure 3 As shown, the first function 300 includes:

[0215] The first receiving module 301 is configured to receive a first message sent by a first application function; wherein the first message includes part or all of a first identifier representing the device identifier of the first terminal;

[0216] The first processing module 302 is used to determine the target identifier; wherein, the target identifier is used to identify the first terminal; the target identifier includes the following: a temporary identifier; a device identifier;

[0217] The first sending module 303 is used to send a second message to the first terminal; wherein the second message includes a target identifier.

[0218] In other embodiments of this application, the first processing module 302 is used to determine the target identifier based on the type of the first identifier and / or the first mapping relationship; wherein the first mapping relationship is a mapping relationship between the device identifier and the temporary identifier.

[0219] In other embodiments of this application, the first receiving module 301 is used to receive a third message sent by the first terminal; wherein the third message includes one or more of the following: first information; second identifier; the second identifier includes one of the following: device identifier and temporary identifier; temporary identifier; temporary identifier before update and temporary identifier after update; device identifier and temporary identifier after update.

[0220] In other embodiments of this application, the first processing module 302 is used to determine the device identifier of the first terminal based on the second identifier.

[0221] In other embodiments of this application, the first sending module 303 is used to send one or more of the following to the first application function: first information; device identifier of the first terminal.

[0222] In other embodiments of this application, the first processing module 302 is used to determine whether to enable privacy protection for the device identifier based on the first application function identifier and / or service level agreement; if enabled, the target identifier is determined based on the type of the first identifier and / or the first mapping relationship and / or the type of the temporary identifier.

[0223] In other embodiments of this application, if started, the inventory message also includes a first indication parameter. The first processing module 302 is used to determine the indication content of the first indication parameter based on whether it is necessary to update the temporary identifier, and / or the first identifier, and / or the first mapping relationship; wherein, the first indication parameter is used to indicate the content of the message sent by the first terminal to the first function.

[0224] In other embodiments of this application, the first processing module 302 is used to determine the target identifier as a temporary identifier if the first identifier represents at least one specific passive IoT device and there is a temporary identifier that has a mapping relationship with the first identifier.

[0225] In other embodiments of this application, the first processing module 302 is used to determine the target identifier as a device identifier if the first identifier represents at least one specific passive IoT device and there is no temporary identifier that has a mapping relationship with the first identifier.

[0226] In other embodiments of this application, the first processing module 302 is used to determine the target identifier as a device identifier if the first identifier represents a group of passive IoT devices.

[0227] In other embodiments of this application, the first processing module 302 is used to determine the target identifier as a temporary identifier or a device identifier if the first identifier represents a group of passive IoT devices and there is a temporary identifier that has a mapping relationship with the first identifier and the temporary identifier represents a group of passive IoT devices.

[0228] In other embodiments of this application, the first processing module 302 is used to determine the instruction content to instruct the reporting of the temporary identifier if there is a temporary identifier that has a mapping relationship with the first identifier.

[0229] In other embodiments of this application, the first processing module 302 is used to determine the indication content to indicate the reporting device identifier and the temporary identifier if there is no temporary identifier that has a mapping relationship with the first identifier.

[0230] In other embodiments of this application, the first processing module 302 is used to determine, if the temporary identifier needs to be updated, that the instruction content is used to indicate the reporting of the updated temporary identifier and the device identifier, or that the instruction content is used to indicate the reporting of the updated temporary identifier and the temporary identifier before the update.

[0231] In other embodiments of this application, the first processing module 302 is used to query, and / or update, and / or establish, and / or save a mapping relationship related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier; wherein the mapping relationship is obtained by the first function learning the information in the third message reported by the first terminal.

[0232] In other embodiments of this application, the first processing module 302 is used to establish and save the mapping relationship between the first device identifier and the first temporary identifier if the second identifier includes the first device identifier and the first temporary identifier; and to determine the first device identifier as the device identifier of the first terminal.

[0233] In other embodiments of this application, the first processing module 302 is configured to determine, based on the first mapping relationship, a first device identifier that matches the first temporary identifier as the device identifier of the first terminal if the second identifier includes the first temporary identifier.

[0234] In other embodiments of this application, the first processing module 302 is used to delete the mapping relationship between the first temporary identifier and the second device identifier if the second identifier includes a first device identifier and a first temporary identifier, and there is a second device identifier that has a mapping relationship with the first temporary identifier; wherein the first device identifier and the second device identifier are different; and to establish and save the mapping relationship between the first device identifier and the first temporary identifier.

[0235] In other embodiments of this application, the first sending module 303 is configured to resend a second message to the first terminal if the second identifier includes a first temporary identifier and the first device identifier corresponding to the first temporary identifier cannot be obtained based on the first mapping relationship; wherein the resent second message includes a first indication parameter for instructing the simultaneous reporting of the temporary identifier and the device identifier;

[0236] The first receiving module 301 is used to receive a third message retransmitted by the first terminal; wherein the retransmitted third message includes a first temporary identifier and a first device identifier;

[0237] The first processing module 302 is used to delete the mapping relationship between the second temporary identifier and the first device identifier if there is a second temporary identifier that has a mapping relationship with the first device identifier; wherein the second temporary identifier and the first temporary identifier are different; and to establish and save the mapping relationship between the first device identifier and the first temporary identifier.

[0238] In other embodiments of this application, the first processing module 302 is configured to, if the second identifier includes a temporary identifier before the update and a temporary identifier after the update, determine a third device identifier that has a mapping relationship with the temporary identifier before the update as the device identifier of the first terminal based on the first mapping relationship; establish and save the mapping relationship between the third device identifier and the temporary identifier after the update; and delete the mapping relationship between the third device identifier and the temporary identifier before the update.

[0239] In other embodiments of this application, the first processing module 302 is configured to: determine the first device identifier as the device identifier of the first terminal if the second identifier includes a first device identifier and a second temporary identifier, and the second temporary identifier is an updated temporary identifier; delete the mapping relationship between the temporary identifier before the update and the first device identifier; and establish and save the mapping relationship between the first device identifier and the second temporary identifier.

[0240] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0241] It should be noted that, in the embodiments of this application, if the above-described information processing method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a terminal device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0242] Embodiments of this application provide a first function, which can be used to implement Figure 2 A corresponding embodiment provides an information processing method, referring to... Figure 4 As shown, the first function 400 includes:

[0243] The second receiving module 401 is used to receive a first message sent by the first application function; wherein the first message includes part or all of a first identifier that represents the device identifier of the first terminal;

[0244] The second processing module 402 is used to determine the first indication parameter; wherein the first indication parameter is used to indicate the content of the message sent by the first terminal to the first function;

[0245] The second sending module 403 is used to send a second message to the first terminal; wherein the second message includes a first indication parameter.

[0246] In other embodiments of this application, the second processing module 402 is used to determine the indication content of the first indication parameter based on the first identifier and / or the first mapping relationship; wherein the first mapping relationship is the mapping relationship between the device identifier and the temporary identifier.

[0247] In other embodiments of this application, the second receiving module 401 is used to receive a third message sent by the first terminal; wherein the third message includes one or more of the following: first information; second identifier; the second identifier includes one of the following: device identifier and temporary identifier; temporary identifier; temporary identifier before update and temporary identifier after update; device identifier and temporary identifier after update.

[0248] In other embodiments of this application, the second processing module 402 is used to determine the device identifier of the first terminal based on the second identifier.

[0249] In other embodiments of this application, the second sending module 403 is used to send one or more of the following to the first application function: first information; device identifier of the first terminal.

[0250] In other embodiments of this application, the first message also includes a first application function identifier and a second processing module 402, which is used to determine whether to activate privacy protection for the device identifier based on the first application function identifier and / or service level agreement; if activated, the instruction content of the first instruction parameter is determined based on whether the temporary identifier and / or the first identifier and / or the first mapping relationship need to be updated.

[0251] In other embodiments of this application, if initiated, the second message further includes a first indication parameter and a second processing module 402, which is used to determine a target identifier based on the type of the first identifier and / or the first mapping relationship and / or the type of the temporary identifier; wherein the target identifier is used to identify the first terminal.

[0252] In other embodiments of this application, the second processing module 402 is used to determine the target identifier as a temporary identifier if the first identifier represents at least one specific passive IoT device and there is a temporary identifier that has a mapping relationship with the first identifier.

[0253] In other embodiments of this application, the second processing module 402 is used to determine the target identifier as a device identifier if the first identifier represents at least one specific passive IoT device and there is no temporary identifier that has a mapping relationship with the first identifier.

[0254] In other embodiments of this application, the second processing module 402 is used to determine the target identifier as a device identifier if the first identifier represents a group of passive IoT devices.

[0255] In other embodiments of this application, the second processing module 402 is used to determine the target identifier as a temporary identifier or a device identifier if the first identifier represents a group of passive IoT devices and there is a temporary identifier that has a mapping relationship with the first identifier and the temporary identifier represents a group of passive IoT devices.

[0256] In other embodiments of this application, the second processing module 402 is used to determine the instruction content to instruct the reporting of the temporary identifier if there is a temporary identifier that has a mapping relationship with the first identifier.

[0257] In other embodiments of this application, the second processing module 402 is used to determine the indication content to indicate the reporting device identifier and the temporary identifier if there is no temporary identifier that has a mapping relationship with the first identifier.

[0258] In other embodiments of this application, the second processing module 402 is used to determine, if the temporary identifier needs to be updated, that the instruction content is used to indicate the reporting of the updated temporary identifier and the device identifier, or that the instruction content is used to indicate the reporting of the updated temporary identifier and the temporary identifier before the update.

[0259] In other embodiments of this application, the second processing module 402 is used to query, and / or update, and / or establish, and / or save a mapping relationship related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier; wherein the mapping relationship is obtained by the first function learning the information in the third message reported by the first terminal.

[0260] In other embodiments of this application, the second processing module 402 is used to establish and save the mapping relationship between the first device identifier and the first temporary identifier if the second identifier includes the first device identifier and the first temporary identifier; and to determine the first device identifier as the device identifier of the first terminal.

[0261] In other embodiments of this application, the second processing module 402 is used to determine, based on the first mapping relationship, a first device identifier that matches the first temporary identifier as the device identifier of the first terminal if the second identifier includes the first temporary identifier; wherein, the first mapping relationship is a mapping relationship between the device identifier and the temporary identifier.

[0262] In other embodiments of this application, the second processing module 402 is used to delete the mapping relationship between the first temporary identifier and the second device identifier if the second identifier includes the first device identifier and the first temporary identifier, and there is a second device identifier that has a mapping relationship with the first temporary identifier; wherein the first device identifier and the second device identifier are different; and to establish and save the mapping relationship between the first device identifier and the first temporary identifier.

[0263] In other embodiments of this application, the second sending module 403 is used to resend a second message to the first terminal if the second identifier includes a first temporary identifier and the first device identifier corresponding to the first temporary identifier cannot be obtained based on the first mapping relationship; wherein the resent second message includes a first indication parameter for instructing the simultaneous reporting of the temporary identifier and the device identifier;

[0264] The second receiving module 401 is used to receive the third message retransmitted by the first terminal; wherein the retransmitted third message includes a first temporary identifier and a first device identifier;

[0265] The second processing module 402 is used to delete the mapping relationship between the second temporary identifier and the first device identifier if there is a second temporary identifier that has a mapping relationship with the first device identifier; wherein the second temporary identifier and the first temporary identifier are different; and to establish and save the mapping relationship between the first device identifier and the first temporary identifier.

[0266] In other embodiments of this application, the second processing module 402 is configured to, if the second identifier includes a temporary identifier before the update and a temporary identifier after the update, determine a third device identifier that has a mapping relationship with the temporary identifier before the update as the device identifier of the first terminal based on the first mapping relationship; establish and save the mapping relationship between the third device identifier and the temporary identifier after the update; and delete the mapping relationship between the third device identifier and the temporary identifier before the update.

[0267] In other embodiments of this application, the second processing module 402 is configured to: determine the first device identifier as the device identifier of the first terminal if the second identifier includes a first device identifier and a second temporary identifier, and the second temporary identifier is an updated temporary identifier; delete the mapping relationship between the temporary identifier before the update and the first device identifier; and establish and save the mapping relationship between the first device identifier and the second temporary identifier.

[0268] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0269] It should be noted that, in the embodiments of this application, if the above-described information processing method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a terminal device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROMs, magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0270] This application provides a first terminal, which can be used to implement... Figures 2 to 3 A corresponding embodiment provides an information processing method, referring to... Figure 5 As shown, the first terminal 500 includes:

[0271] The third receiving module 501 is used to receive a second message sent by the first function; wherein the second message includes one or more of the following: a target identifier; a first indication parameter; the first indication parameter is used to indicate the content of the message sent by the first terminal to the first function; the target identifier is used to identify the first terminal; the target identifier includes one of the following: a temporary identifier; a device identifier;

[0272] The third processing module 502 is used to determine or match or obtain the device of the first terminal based on the target identifier, and / or determine the content of the message reported or fed back or sent by the first terminal to the first function based on the first indication parameter, and / or generate a temporary identifier based on the first indication parameter.

[0273] In other embodiments of this application, the third sending module 503 is used to send a third message to the first function; wherein the third message includes one or more of the following: first information; second identifier; the second identifier includes one of the following: device identifier and temporary identifier; temporary identifier; temporary identifier before update and temporary identifier after update; device identifier and temporary identifier after update.

[0274] In other embodiments of this application, the third sending module 503 is used to send the first device identifier and the first temporary identifier to the first function if the second message includes a first indication parameter and the first indication parameter is used to indicate that the device identifier and the temporary identifier are reported at the same time.

[0275] In other embodiments of this application, the third processing module 502 is used to generate and store a temporary identifier locally if the second message includes a first indication parameter, and the first indication parameter is used to indicate that the device identifier and the temporary identifier are reported at the same time, and the first terminal has no temporary identifier locally.

[0276] The third sending module 503 is used to send a first device identifier and a first temporary identifier to the first function; wherein the first temporary identifier is a newly generated temporary identifier.

[0277] In other embodiments of this application, the third processing module 502 is configured to, if the second message includes a first indication parameter, and the first indication parameter is used to indicate the reported updated temporary identifier and the original temporary identifier, generate a new temporary identifier locally to obtain the updated temporary identifier; and store the updated temporary identifier.

[0278] The third sending module 503 is used to send the updated temporary identifier and the original temporary identifier to the first function.

[0279] The third processing module 502 is used to delete the temporary identifier before the update locally.

[0280] In other embodiments of this application, the third processing module 502 is configured to, if the second message includes a first indication parameter and the first indication parameter is used to indicate the reporting device identifier and the updated temporary identifier, generate a new temporary identifier locally, obtain the updated temporary identifier, and store the updated temporary identifier;

[0281] The third sending module 503 is used to send a first device identifier and a second temporary identifier to the first function; wherein the second temporary identifier is an updated temporary identifier;

[0282] The third processing module 502 is used to delete the temporary identifier before the update locally.

[0283] In other embodiments of this application, the third sending module 503 is used to send a first temporary identifier to the first function if the second message includes a first indication parameter and the first indication parameter is used to indicate the reporting temporary identifier.

[0284] In other embodiments of this application, the third sending module 503 is used to send the device identifier of the first terminal to the first function if the second message does not include the first indication parameter.

[0285] In other embodiments of this application, the third receiving module 501 is used to receive a second message retransmitted by the first function; wherein, the retransmitted second message includes a first indication parameter for instructing the simultaneous reporting of a temporary identifier and a device identifier;

[0286] The third processing module 502 is used to resend a third message to the first function; wherein the resent third message includes a first temporary identifier and a first device identifier.

[0287] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0288] It should be noted that, in the embodiments of this application, if the above-described information processing method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a network device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, ROMs, magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0289] This application provides a first function, which can be used to implement... Figure 4 A corresponding embodiment provides an information processing method, referring to... Figure 6 As shown, the first function 600 includes:

[0290] The fourth receiving module 601 is used to receive a first message sent by the first application function; wherein the first message includes part or all of a first identifier that represents the device identifier of the first terminal;

[0291] The fourth processing module 602 is used to determine the target identifier; wherein, the target identifier is used to identify the first terminal; the target identifier includes the following: tag identifier; device identifier;

[0292] The fourth sending module 603 is used to send a second message to the first terminal; wherein the second message includes a target identifier.

[0293] In other embodiments of this application, the fourth processing module 602 is used to determine the target identifier based on the type of the first identifier and / or the second mapping relationship; wherein the second mapping relationship is a mapping relationship between the device identifier and the tag identifier.

[0294] In other embodiments of this application, the fourth receiving module 601 is used to receive a third message sent by the first terminal; wherein the third message includes one or more of the following: first information and second identifier; the second identifier includes one of the following: device identifier and tag identifier; tag identifier.

[0295] In other embodiments of this application, the fourth processing module 602 is used to determine the device identifier of the first terminal based on the second identifier.

[0296] In other embodiments of this application, the fourth sending module 603 is used to send one or more of the following to the first application function: first information; device identifier of the first terminal.

[0297] In other embodiments of this application, the fourth processing module 602 is used to determine whether to enable privacy protection for the device identifier based on the first application function identifier and / or service level agreement; if enabled, it determines the target identifier based on the type of the first identifier and / or the second mapping relationship.

[0298] In other embodiments of this application, if started, the inventory message also includes a second indication parameter. The fourth processing module 602 is used to determine the indication content of the second indication parameter based on the first identifier and / or the second mapping relationship.

[0299] In other embodiments of this application, the fourth processing module 602 is used to determine the instruction content to indicate that the tag identifier and the device identifier are reported simultaneously if there is no tag identifier that has a mapping relationship with the first identifier.

[0300] In other embodiments of this application, the fourth processing module 602 is used to determine the indication content to indicate the reporting tag identifier if there is no tag identifier that has a mapping relationship with the first identifier.

[0301] In other embodiments of this application, the fourth processing module 602 is used to determine the target identifier as a tag identifier if the first identifier represents at least one specific passive IoT device and there is a tag identifier that has a mapping relationship with the first identifier.

[0302] In other embodiments of this application, the fourth processing module 602 is used to determine the target identifier as a device identifier if the first identifier represents at least one specific passive IoT device and there is no tag identifier that has a mapping relationship with the first identifier, or the first identifier represents a group of passive IoT devices.

[0303] In other embodiments of this application, the fourth processing module 602 is used to query, and / or update, and / or establish, and / or save the mapping relationship related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier; wherein the mapping relationship is obtained by the first function learning the information in the third message reported by the first terminal.

[0304] In other embodiments of this application, the fourth processing module 602 is used to establish and save the mapping relationship between the first device identifier and the first tag identifier if the second identifier includes the first device identifier and the first tag identifier; and to determine the first device identifier as the device identifier of the first terminal.

[0305] In other embodiments of this application, the fourth processing module 602 is used to determine, based on the second mapping relationship, a first device identifier that matches the first tag identifier as the device identifier of the first terminal if the second identifier includes the first tag identifier.

[0306] In other embodiments of this application, the fourth processing module 602 is used to delete the mapping relationship between the first tag identifier and the second device identifier if the second identifier includes the first device identifier and the first tag identifier, and there is a second device identifier that has a mapping relationship with the first tag identifier; wherein the first device identifier and the second device identifier are different; and to establish and save the mapping relationship between the first device identifier and the first tag identifier.

[0307] In other embodiments of this application, the fourth sending module 603 is used to resend a second message to the first terminal if the second identifier includes the first tag identifier and the first device identifier corresponding to the first tag identifier cannot be obtained based on the second mapping relationship; wherein, the resending of the second message includes a second indication parameter for instructing the simultaneous reporting of the tag identifier and the device identifier;

[0308] The fourth receiving module 601 is used to receive the fourth message retransmitted by the first terminal; wherein the retransmitted fourth message includes the first device identifier and the first tag identifier;

[0309] The fourth processing module 602 is used to delete the mapping relationship between the second tag identifier and the first device identifier if there is a second tag identifier that has a mapping relationship with the first device identifier; wherein the second tag identifier and the first tag identifier are different; and to establish and save the mapping relationship between the first device identifier and the first tag identifier.

[0310] In other embodiments of this application, the fourth sending module 603 is used to resend a second message to the first terminal if privacy protection for the device identifier is activated and there is no mapping relationship corresponding to the first tag identifier when the device identifier corresponding to the existing tag identifier is updated in the first function update; wherein, the resending of the second message includes a second indication parameter for instructing the simultaneous reporting of the tag identifier and the device identifier;

[0311] The fourth receiving module 601 is used to receive the fourth message retransmitted by the first terminal; wherein the retransmitted fourth message includes the first device identifier and the first tag identifier;

[0312] The fourth processing module 602 is used to delete the mapping relationship between the second tag identifier and the first device identifier if there is a second tag identifier that has a mapping relationship with the first device identifier; wherein the second tag identifier and the first tag identifier are different; and to establish and save the mapping relationship between the first device identifier and the first tag identifier.

[0313] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0314] It should be noted that, in the embodiments of this application, if the above-described information processing method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a network device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, ROMs, magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0315] This application provides a first terminal, which can be used to implement... Figure 2 A corresponding embodiment provides an information processing method, referring to... Figure 7 As shown, the first terminal 700 includes:

[0316] The fifth receiving module 701 is used to receive a second message sent by the first function; the second message includes one or more of the following: a target identifier; a second indication parameter; the second indication parameter is used to indicate the content of the message sent by the first terminal to the first function; the target identifier is used to identify the first terminal; the target identifier includes one of the following: a tag identifier; a device identifier;

[0317] The fifth processing module 702 is used to determine, match, or obtain the device of the first terminal based on the target identifier, and / or determine the content of the message reported, fed back, or sent by the first terminal to the first function based on the second indication parameter.

[0318] In other embodiments of this application, the fifth sending module 703 is used to send a third message to the first function; wherein the third message includes one or more of the following: first information; second identifier; the second identifier includes one of the following: device identifier and tag identifier; tag identifier.

[0319] In other embodiments of this application, the fifth sending module 703 is used to send the first device identifier and the first tag identifier to the first function if the second message includes a second indication parameter and the second indication parameter is used to indicate that the tag identifier and the device identifier are reported simultaneously.

[0320] In other embodiments of this application, the fifth processing module 702 is used to send a first tag identifier to the first function if the second message includes a second indication parameter and the second indication parameter is used to indicate the reporting tag identifier.

[0321] In other embodiments of this application, the fifth processing module 702 is used to send the device identifier of the first terminal to the first function if the second message does not include the second indication parameter.

[0322] In other embodiments of this application, the first terminal is locally configured with a first parameter, which by default represents that the device identifier has not been reported. The fifth sending module 703 is used to send the first device identifier and the first tag identifier to the first function if the second message includes a second indication parameter and the second indication parameter is used to indicate that the tag identifier and the device identifier are reported at the same time.

[0323] The fifth processing module 702 is used to update the first parameter to identify the reported device identifier.

[0324] In other embodiments of this application, the fifth sending module 703 is used to send the first tag identifier and the first device identifier to the first function if the second message does not include the second indication parameter and the first parameter represents the unreported device identifier;

[0325] The fifth processing module 702 is used to update the first parameter to identify the reported device identifier.

[0326] In other embodiments of this application, the fifth sending module 703 is used to send a first tag identifier to the first function if the second message does not include a second indication parameter and the first parameter represents the reported device identifier.

[0327] In other embodiments of this application, the fifth receiving module 701 is used to receive a second message retransmitted by the first function; wherein, the retransmitted second message includes a second indication parameter for instructing the simultaneous reporting of the tag identifier and the device identifier;

[0328] The fifth sending module 703 is used to resend the third message to the first function; wherein the resent third message includes the first device identifier and the first tag identifier.

[0329] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0330] It should be noted that, in the embodiments of this application, if the above-described information processing method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a network device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, ROMs, magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0331] Figure 8 This is a schematic structural diagram of a communication device 800 provided in an embodiment of this application. The communication device can be a first terminal or a first function. Figure 8 The communication device 800 shown includes a processor 810, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0332] Optionally, such as Figure 8 As shown, the communication device 800 may further include a memory 820. The processor 810 can retrieve and run computer programs from the memory 820 to implement the methods described in this embodiment.

[0333] The memory 820 can be a separate device independent of the processor 810, or it can be integrated into the processor 810.

[0334] Optionally, such as Figure 8As shown, the communication device 800 may also include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0335] The transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

[0336] Optionally, the communication device 800 may specifically be the first terminal in the embodiments of this application, and the communication device 800 may implement the corresponding processes implemented by the first terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0337] Optionally, the communication device 800 may specifically be the first function of the embodiments of this application, and the communication device 800 may implement the corresponding processes implemented by the first function in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0338] This application also provides a computer program product, including a computer program that can be executed by the processor 810 of the communication device 800 to complete the steps described in any of the foregoing methods.

[0339] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0340] As one embodiment, the processor may include one or more general-purpose central processing units (CPUs). Each of these processors may be a single-core processor or a multi-core processor. Here, "processor" may refer to one or more devices, circuits, and / or processing cores used for processing data (e.g., executing instructions).

[0341] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be ROM, Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), or flash memory. The volatile memory can be Random Access Memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0342] This application also provides a computer-readable storage medium for storing computer programs.

[0343] Optionally, the computer-readable storage medium can be applied to the first terminal in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the first terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0344] Optionally, the computer-readable storage medium can be applied to the first function in the embodiments of this application, and the computer program causes the computer to execute the corresponding process implemented by the first function in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0345] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0346] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0347] The information processing method, first function, first terminal, computer-readable storage medium, and computer program product provided in the embodiments of this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

[0348] It should be understood that the phrases "an embodiment," "an embodiment," "an embodiment of this application," "the foregoing embodiment," "some implementations," or "some embodiments" mentioned throughout the specification mean that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, the phrases "an embodiment," "an embodiment," "an embodiment of this application," "the foregoing embodiment," "some implementations," or "some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0349] Unless otherwise specified, the first device / first function performing any step in the embodiments of this application may be executed by the processor of the first device / first function. Unless otherwise specified, the embodiments of this application do not limit the order in which the first device / first function performs the following steps. Furthermore, the methods used to process data in different embodiments may be the same or different methods.

[0350] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0351] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0352] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0353] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined to obtain new method embodiments without conflict. The features disclosed in the several product embodiments provided in this application can be arbitrarily combined to obtain new product embodiments without conflict. The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined to obtain new method embodiments or device embodiments without conflict.

[0354] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0355] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0356] The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.

[0357] It should be noted that in the various embodiments involved in this application, all steps or some steps may be performed, as long as a complete technical solution can be formed.

[0358] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An information processing method, characterized in that, Applied to the first function, the method includes: Receive a first message sent by a first application function; wherein the first message includes part or all of a first identifier representing the device identifier of the first terminal; Determine a target identifier; wherein the target identifier is used to identify the first terminal; the target identifier includes one of the following: a temporary identifier; a device identifier; Send a second message to the first terminal; wherein the second message includes a target identifier.

2. The method according to claim 1, characterized in that, The determination of the target identifier includes: The target identifier is determined based on the type of the first identifier and / or the first mapping relationship; wherein the first mapping relationship is a mapping relationship between a device identifier and a temporary identifier.

3. The method according to claim 2, characterized in that, The method further includes: Receive a third message sent by the first terminal; wherein the third message includes one or more of the following: first information; second identifier; the second identifier includes one of the following: device identifier and temporary identifier; temporary identifier; temporary identifier before update and temporary identifier after update; device identifier and temporary identifier after update.

4. The method according to claim 3, characterized in that, The method further includes: Based on the second identifier, the device identifier of the first terminal is determined.

5. The method according to claim 3, characterized in that, The method further includes: Send one or more of the following to the first application function: first information; device identifier of the first terminal.

6. The method according to claim 2, characterized in that, The first message also includes a first application function identifier. Determining the target identifier based on the type of the first identifier and / or a first mapping relationship includes: Based on the first application function identifier and / or service level agreement, determine whether to activate privacy protection for the device identifier; If initiated, the target identifier is determined based on the type of the first identifier and / or the first mapping relationship and / or the type of the temporary identifier.

7. The method according to claim 6, characterized in that, If initiated, the second message further includes a first indication parameter, and the method further includes: Based on whether the temporary identifier needs to be updated, and / or the first identifier, and / or the first mapping relationship, the indication content of the first indication parameter is determined; wherein, the first indication parameter is used to indicate the content of the message sent by the first terminal to the first function.

8. The method according to claim 2, characterized in that, Determining the target identifier based on the type of the first identifier and / or the first mapping relationship includes: If the first identifier represents at least one specific passive IoT device, and there is a temporary identifier that has a mapping relationship with the first identifier, then the target identifier is determined to be a temporary identifier.

9. The method according to claim 2, characterized in that, Determining the target identifier based on the type of the first identifier and / or the first mapping relationship includes: If the first identifier represents at least one specific passive IoT device, and there is no temporary identifier that has a mapping relationship with the first identifier, then the target identifier is determined to be a device identifier.

10. The method according to claim 2, characterized in that, Determining the target identifier based on the type of the first identifier and / or the first mapping relationship includes: If the first identifier represents a group of passive IoT devices, then the target identifier is determined to be a device identifier.

11. The method according to claim 6, characterized in that, Determining the target identifier based on the type of the first identifier and / or the first mapping relationship and / or the type of the temporary identifier includes: If the first identifier represents a group of passive IoT devices, and there is a temporary identifier that has a mapping relationship with the first identifier, and the temporary identifier represents a group of passive IoT devices, then the target identifier is determined to be a temporary identifier or a device identifier.

12. The method according to claim 7, characterized in that, The step of determining the indication content of the first indication parameter based on whether the temporary identifier needs to be updated, and / or the first identifier, and / or the first mapping relationship, includes: If there is a temporary identifier that has a mapping relationship with the first identifier, the instruction content is determined to be used to instruct the reporting of the temporary identifier.

13. The method according to claim 7, characterized in that, The step of determining the indication content of the first indication parameter based on whether the temporary identifier needs to be updated, and / or the first identifier, and / or the first mapping relationship, includes: If there is no temporary identifier that is mapped to the first identifier, the instruction content is determined to be used to indicate the reporting device identifier and the temporary identifier.

14. The method according to claim 7, characterized in that, The step of determining the indication content of the first indication parameter based on whether the temporary identifier needs to be updated, and / or the first identifier, and / or the first mapping relationship, includes: If a temporary identifier needs to be updated, determine whether the instruction content is used to instruct the reporting of the updated temporary identifier and the device identifier, or whether the instruction content is used to instruct the reporting of both the updated temporary identifier and the original temporary identifier.

15. The method according to claim 4, characterized in that, Determining the device identifier of the first terminal based on the second identifier includes: The system queries, and / or updates, and / or establishes, and / or saves a mapping relationship related to the second identifier, and determines the device identifier of the first terminal based on the mapping relationship and the second identifier; wherein the mapping relationship is obtained by the first function learning information from the third message reported by the first terminal.

16. The method according to claim 15, characterized in that, The query, and / or update, and / or establish, and / or save mapping relationships related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier, includes: If the second identifier includes the first device identifier and the first temporary identifier, establish and save the mapping relationship between the first device identifier and the first temporary identifier; The first device identifier is determined to be the device identifier of the first terminal.

17. The method according to claim 15, characterized in that, The query, and / or update, and / or establish, and / or save mapping relationships related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier, includes: If the second identifier includes a first temporary identifier, based on the first mapping relationship, the first device identifier that matches the first temporary identifier is determined as the device identifier of the first terminal.

18. The method according to claim 16, characterized in that, If the second identifier includes a first device identifier and a first temporary identifier, establishing and saving the mapping relationship between the first device identifier and the first temporary identifier includes: If the second identifier includes a first device identifier and a first temporary identifier, and there is a second device identifier that has a mapping relationship with the first temporary identifier, delete the mapping relationship between the first temporary identifier and the second device identifier; wherein the first device identifier and the second device identifier are different; Establish and save the mapping relationship between the first device identifier and the first temporary identifier.

19. The method according to claim 17, characterized in that, The method further includes: If the second identifier includes the first temporary identifier, and the first device identifier corresponding to the first temporary identifier cannot be obtained based on the first mapping relationship, the second message is resent to the first terminal; wherein, the resent second message includes a first indication parameter for instructing that both the temporary identifier and the device identifier be reported simultaneously; Receive a third message retransmitted by the first terminal; wherein the retransmitted third message includes a first temporary identifier and a first device identifier; If there is a second temporary identifier that is mapped to the first device identifier, delete the mapping relationship between the second temporary identifier and the first device identifier; wherein the second temporary identifier and the first temporary identifier are different; Establish and save the mapping relationship between the first device identifier and the first temporary identifier.

20. The method according to claim 15, characterized in that, The query, and / or update, and / or establish, and / or save mapping relationships related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier, includes: If the second identifier includes both the temporary identifier before the update and the temporary identifier after the update, based on the first mapping relationship, the third device identifier that has a mapping relationship with the temporary identifier before the update is determined as the device identifier of the first terminal; Establish and maintain a mapping relationship between the third-party device identifier and the updated temporary identifier; Remove the mapping relationship between the third-party device identifier and the temporary identifier before the update.

21. The method according to claim 15, characterized in that, The query, and / or update, and / or establish, and / or save mapping relationships related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier, includes: If the second identifier includes a first device identifier and a second temporary identifier, and the second temporary identifier is an updated temporary identifier, then the first device identifier is determined to be the device identifier of the first terminal. Delete the mapping relationship between the temporary identifier and the first device identifier before the update; Establish and save the mapping relationship between the first device identifier and the second temporary identifier.

22. An information processing method, characterized in that, Applied to the first function, the method includes: Receive a first message sent by a first application function; wherein the first message includes part or all of a first identifier representing the device identifier of the first terminal; Determine a first indication parameter; wherein the first indication parameter is used to indicate the content of a message sent by the first terminal to the first function; Send a second message to the first terminal; wherein the second message includes the first indication parameter.

23. The method according to claim 22, characterized in that, Determining the first indication parameter includes: Based on the first identifier and / or the first mapping relationship, the indication content of the first indication parameter is determined; wherein, the first mapping relationship is the mapping relationship between the device identifier and the temporary identifier.

24. The method according to claim 23, characterized in that, The method further includes: Receive a third message sent by the first terminal; wherein the third message includes one or more of the following: first information; second identifier; the second identifier includes one of the following: device identifier and temporary identifier; temporary identifier; temporary identifier before update and temporary identifier after update; device identifier and temporary identifier after update.

25. The method according to claim 24, characterized in that, The method further includes: Based on the second identifier, the device identifier of the first terminal is determined.

26. The method according to claim 24, characterized in that, The method further includes: Send one or more of the following to the first application function: first information; device identifier of the first terminal.

27. The method according to claim 23, characterized in that, The first message also includes a first application function identifier, and the step of determining the indication content of the first indication parameter based on the first identifier and / or the first mapping relationship includes: Based on the first application function identifier and / or service level agreement, determine whether to activate privacy protection for the device identifier; If started, the indication content of the first indication parameter is determined based on whether the temporary identifier needs to be updated, and / or the first identifier, and / or the first mapping relationship.

28. The method according to claim 27, characterized in that, If initiated, the second message also includes a target identifier, and the method further includes: The target identifier is determined based on the type of the first identifier, and / or the first mapping relationship, and / or the type of the temporary identifier; wherein the target identifier is used to identify the first terminal.

29. The method according to claim 28, characterized in that, Determining the target identifier based on the type of the first identifier and / or the first mapping relationship and / or the type of the temporary identifier includes: If the first identifier represents at least one specific passive IoT device, and there is a temporary identifier that has a mapping relationship with the first identifier, then the target identifier is determined to be a temporary identifier.

30. The method according to claim 28, characterized in that, Determining the target identifier based on the type of the first identifier and / or the first mapping relationship and / or the type of the temporary identifier includes: If the first identifier represents at least one specific passive IoT device, and there is no temporary identifier that has a mapping relationship with the first identifier, then the target identifier is determined to be a device identifier.

31. The method according to claim 28, characterized in that, Determining the target identifier based on the type of the first identifier and / or the first mapping relationship and / or the type of the temporary identifier includes: If the first identifier represents a group of passive IoT devices, then the target identifier is determined to be a device identifier.

32. The method according to claim 28, characterized in that, Determining the target identifier based on the type of the first identifier and / or the first mapping relationship and / or the type of the temporary identifier includes: If the first identifier represents a group of passive IoT devices, and there is a temporary identifier that has a mapping relationship with the first identifier, and the temporary identifier represents a group of passive IoT devices, then the target identifier is determined to be a temporary identifier or a device identifier.

33. The method according to claim 23, characterized in that, The step of determining the indication content of the first indication parameter based on the type of the first identifier and / or the first mapping relationship includes: If there is a temporary identifier that has a mapping relationship with the first identifier, the instruction content is determined to be used to instruct the reporting of the temporary identifier.

34. The method according to claim 23, characterized in that, The step of determining the indication content of the first indication parameter based on the first identifier and / or the first mapping relationship includes: If there is no temporary identifier that is mapped to the first identifier, the instruction content is determined to be used to indicate the reporting device identifier and the temporary identifier.

35. The method according to claim 27, characterized in that, The step of determining the indication content of the first indication parameter based on whether the temporary identifier and / or the first identifier and / or the first mapping relationship needs to be updated includes: If a temporary identifier needs to be updated, determine whether the instruction content is used to instruct the reporting of the updated temporary identifier and the device identifier, or whether the instruction content is used to instruct the reporting of both the updated temporary identifier and the original temporary identifier.

36. The method according to claim 25, characterized in that, Determining the device identifier of the first terminal based on the second identifier includes: The system queries, and / or updates, and / or establishes, and / or saves a mapping relationship related to the second identifier, and determines the device identifier of the first terminal based on the mapping relationship and the second identifier; wherein the mapping relationship is obtained by the first function learning information from the third message reported by the first terminal.

37. The method according to claim 36, characterized in that, The query, and / or update, and / or establish, and / or save mapping relationships related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier, includes: If the second identifier includes the first device identifier and the first temporary identifier, establish and save the mapping relationship between the first device identifier and the first temporary identifier; The first device identifier is determined to be the device identifier of the first terminal.

38. The method according to claim 36, characterized in that, The query, and / or update, and / or establish, and / or save mapping relationships related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier, includes: If the second identifier includes a first temporary identifier, based on the first mapping relationship, the first device identifier that matches the first temporary identifier is determined as the device identifier of the first terminal.

39. The method according to claim 37, characterized in that, If the second identifier includes a first device identifier and a first temporary identifier, establishing and saving the mapping relationship between the first device identifier and the first temporary identifier includes: If the second identifier includes a first device identifier and a first temporary identifier, and there is a second device identifier that has a mapping relationship with the first temporary identifier, delete the mapping relationship between the first temporary identifier and the second device identifier; wherein the first device identifier and the second device identifier are different; Establish and save the mapping relationship between the first device identifier and the first temporary identifier.

40. The method according to claim 38, characterized in that, The method further includes: If the second identifier includes the first temporary identifier, and the first device identifier corresponding to the first temporary identifier cannot be obtained based on the first mapping relationship, the second message is resent to the first terminal; wherein, the resent second message includes a first indication parameter for instructing that both the temporary identifier and the device identifier be reported simultaneously; Receive a third message retransmitted by the first terminal; wherein the retransmitted third message includes a first temporary identifier and a first device identifier; If there is a second temporary identifier that is mapped to the first device identifier, delete the mapping relationship between the second temporary identifier and the first device identifier; wherein the second temporary identifier and the first temporary identifier are different; Establish and save the mapping relationship between the first device identifier and the first temporary identifier.

41. The method according to claim 36, characterized in that, The query, and / or update, and / or establish, and / or save mapping relationships related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier, includes: If the second identifier includes both the temporary identifier before the update and the temporary identifier after the update, based on the first mapping relationship, the third device identifier that has a mapping relationship with the temporary identifier before the update is determined as the device identifier of the first terminal; Establish and maintain a mapping relationship between the third-party device identifier and the updated temporary identifier; Remove the mapping relationship between the third-party device identifier and the temporary identifier before the update.

42. The method according to claim 36, characterized in that, The query, and / or update, and / or establish, and / or save mapping relationships related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier, includes: If the second identifier includes a first device identifier and a second temporary identifier, and the second temporary identifier is an updated temporary identifier, then the first device identifier is determined to be the device identifier of the first terminal. Delete the mapping relationship between the temporary identifier and the first device identifier before the update; Establish and save the mapping relationship between the first device identifier and the second temporary identifier.

43. An information processing method, characterized in that, Applied to a first terminal, the method includes: Receive a second message sent by a first function; wherein the second message includes one or more of the following: a target identifier; a first indication parameter; the first indication parameter is used to indicate the content of a message sent by the first terminal to the first function; the target identifier is used to identify the first terminal; the target identifier includes one of the following: a temporary identifier; a device identifier; Based on the target identifier, determine or match or obtain the device of the first terminal, and / or based on the first indication parameter, determine the content of the message reported or fed back or sent by the first terminal to the first function, and / or based on the first indication parameter, generate and / or update the temporary identifier.

44. The method according to claim 43, characterized in that, The method further includes: Send a third message to the first function; wherein the third message includes one or more of the following: first information; second identifier; the second identifier includes one of the following: device identifier and temporary identifier; temporary identifier; temporary identifier before update and temporary identifier after update; device identifier and temporary identifier after update.

45. The method according to claim 43, characterized in that, The method further includes: If the second message includes a first indication parameter, and the first indication parameter is used to indicate that the device identifier and the temporary identifier are reported simultaneously, the first device identifier and the first temporary identifier are sent to the first function.

46. ​​The method according to claim 43, characterized in that, The method further includes: If the second message includes a first indication parameter, and the first indication parameter is used to indicate that the device identifier and temporary identifier are reported simultaneously, and the first terminal does not have a temporary identifier locally, a temporary identifier is generated and stored locally; Send a first device identifier and a first temporary identifier to the first function; wherein the first temporary identifier is a newly generated temporary identifier.

47. The method according to claim 43, characterized in that, The method further includes: If the second message includes a first indication parameter, and the first indication parameter is used to indicate the reported updated temporary identifier and the original temporary identifier, a new temporary identifier is generated locally to obtain the updated temporary identifier; Store the updated temporary identifier; Send the updated temporary identifier and the original temporary identifier to the first function, and / or delete the original temporary identifier locally.

48. The method according to claim 43, characterized in that, The method further includes: If the second message includes a first indication parameter, and the first indication parameter is used to indicate the reporting device identifier and the updated temporary identifier, a new temporary identifier is generated locally to obtain the updated temporary identifier; Store the updated temporary identifier; Send a first device identifier and a second temporary identifier to the first function, and / or delete the temporary identifier before the update locally; wherein the second temporary identifier is the updated temporary identifier.

49. The method according to claim 43, characterized in that, The method further includes: If the second message includes a first indication parameter, and the first indication parameter is used to indicate the reporting of a temporary identifier, then the first temporary identifier is sent to the first function.

50. The method according to claim 43, characterized in that, The method further includes: If the second message does not include the first indication parameter, send the device identifier of the first terminal to the first function.

51. The method according to claim 43, characterized in that, The method further includes: Receive a second message resent by the first function; wherein the resent second message includes a first indication parameter for instructing simultaneous reporting of a temporary identifier and a device identifier; Resend the third message to the first function; wherein the resent third message includes the first temporary identifier and the first device identifier.

52. An information processing method, characterized in that, Applied to the first function, the method includes: Receive a first message sent by a first application function; wherein the first message includes part or all of a first identifier representing the device identifier of the first terminal; Determine a target identifier; wherein the target identifier is used to identify the first terminal; the target identifier includes one of the following: a tag identifier; a device identifier; Send a second message to the first terminal; wherein the second message includes a target identifier.

53. The method according to claim 52, characterized in that, The determination of the target identifier includes: The target identifier is determined based on the type of the first identifier and / or the second mapping relationship; wherein the second mapping relationship is a mapping relationship between the device identifier and the tag identifier.

54. The method according to claim 52, characterized in that, The method further includes: Receive a third message sent by the first terminal; wherein the third message includes one or more of the following: first information and second identifier; the second identifier includes one of the following: device identifier and tag identifier; tag identifier.

55. The method according to claim 54, characterized in that, The method further includes: Based on the second identifier, the device identifier of the first terminal is determined.

56. The method according to claim 54, characterized in that, The method further includes: Send one or more of the following to the first application function: first information; device identifier of the first terminal.

57. The method according to claim 53, characterized in that, The first message also includes a first application function identifier. Determining the target identifier based on the type of the first identifier and / or a second mapping relationship includes: Based on the first application function identifier and / or service level agreement, determine whether to activate privacy protection for the device identifier; If initiated, the target identifier is determined based on the type of the first identifier and / or the second mapping relationship.

58. The method according to claim 57, characterized in that, If initiated, the second message further includes a second indication parameter, and the method further includes: Based on the first identifier and / or the second mapping relationship, determine the indication content of the second indication parameter.

59. The method according to claim 58, characterized in that, The step of determining the indication content of the second indication parameter based on the first identifier and / or the second mapping relationship includes: If there is no tag identifier that is mapped to the first identifier, the instruction content is determined to be used to indicate that the tag identifier and the device identifier are reported simultaneously.

60. The method according to claim 58, characterized in that, The step of determining the indication content of the second indication parameter based on the first identifier and / or the second mapping relationship includes: If there is no tag identifier that has a mapping relationship with the first identifier, the instruction content is determined to be used to instruct the reporting tag identifier.

61. The method according to claim 53, characterized in that, Determining the target identifier based on the type of the first identifier and / or the second mapping relationship includes: If the first identifier represents at least one specific passive IoT device, and there is a tag identifier that has a mapping relationship with the first identifier, then the target identifier is determined to be a tag identifier.

62. The method according to claim 53, characterized in that, Determining the target identifier based on the type of the first identifier and / or the second mapping relationship includes: If the first identifier represents at least one specific passive IoT device and there is no tag identifier that has a mapping relationship with the first identifier, then the target identifier is determined to be a device identifier.

63. The method according to claim 53, characterized in that, Determining the target identifier based on the type of the first identifier and / or the second mapping relationship includes: If the first identifier represents a group of passive IoT devices, then the target identifier is determined to be a device identifier.

64. The method according to claim 55, characterized in that, Determining the device identifier of the first terminal based on the second identifier includes: The system queries, and / or updates, and / or establishes, and / or saves a mapping relationship related to the second identifier, and determines the device identifier of the first terminal based on the mapping relationship and the second identifier; wherein the mapping relationship is obtained by the first function learning information from the third message reported by the first terminal.

65. The method according to claim 64, characterized in that, The query, and / or update, and / or establish, and / or save mapping relationships related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier, includes: If the second identifier includes the first device identifier and the first tag identifier, establish and save the mapping relationship between the first device identifier and the first tag identifier; The first device identifier is determined to be the device identifier of the first terminal.

66. The method according to claim 64, characterized in that, The query, and / or update, and / or establish, and / or save mapping relationships related to the second identifier, and determine the device identifier of the first terminal based on the mapping relationship and the second identifier, includes: If the second identifier includes the first tag identifier, based on the second mapping relationship, the first device identifier that matches the first tag identifier is determined as the device identifier of the first terminal.

67. The method according to claim 65, characterized in that, If the second identifier includes a first device identifier and a first tag identifier, establishing and saving the mapping relationship between the first device identifier and the first tag identifier includes: If the second identifier includes a first device identifier and a first tag identifier, and there is a second device identifier that has a mapping relationship with the first tag identifier, delete the mapping relationship between the first tag identifier and the second device identifier; wherein the first device identifier and the second device identifier are different; Establish and save the mapping relationship between the first device identifier and the first tag identifier.

68. The method according to claim 66, characterized in that, The method further includes: If the second identifier includes the first tag identifier, and the first device identifier corresponding to the first tag identifier cannot be obtained based on the second mapping relationship, the second message is resent to the first terminal; wherein, the resentment of the second message includes a second indication parameter for instructing the simultaneous reporting of the tag identifier and the device identifier; Receive a third message retransmitted by the first terminal; wherein the retransmitted third message includes a first device identifier and a first tag identifier; If there is a second tag identifier that is mapped to the first device identifier, delete the mapping relationship between the second tag identifier and the first device identifier; wherein the second tag identifier and the first tag identifier are different; Establish and save the mapping relationship between the first device identifier and the first tag identifier.

69. The method according to claim 57, characterized in that, The method further includes: If the device identifier corresponding to an existing tag identifier is updated in the first function update, and if privacy protection for the device identifier is enabled, and there is no mapping relationship corresponding to the first tag identifier, the second message is resent to the first terminal; wherein, the resentment of the second message includes a second indication parameter for instructing that both the tag identifier and the device identifier be reported simultaneously; Receive a third message retransmitted by the first terminal; wherein the retransmitted third message includes a first device identifier and a first tag identifier; If there is a second tag identifier that is mapped to the first device identifier, delete the mapping relationship between the second tag identifier and the first device identifier; wherein the second tag identifier and the first tag identifier are different; Establish and save the mapping relationship between the first device identifier and the first tag identifier.

70. An information processing method, characterized in that, Applied to a first terminal, the method includes: Receive a second message sent by a first function; wherein the second message includes one or more of the following: a target identifier; a second indication parameter; the second indication parameter is used to indicate the content of a message sent by the first terminal to the first function; the target identifier is used to identify the first terminal; the target identifier includes one of the following: a tag identifier; a device identifier; Based on the target identifier, determine or match or obtain the device of the first terminal, and / or based on the second indication parameter, determine the content of the message reported or fed back or sent by the first terminal to the first function.

71. The method according to claim 70, characterized in that, The method further includes: Send a third message to the first function; wherein the third message includes one or more of the following: first information; second identifier; the second identifier includes one of the following: device identifier and tag identifier; tag identifier.

72. The method according to claim 70, characterized in that, The method further includes: If the second message includes a second indication parameter, and the second indication parameter is used to indicate that the tag identifier and the device identifier are reported simultaneously, the first device identifier and the first tag identifier are sent to the first function.

73. The method according to claim 70, characterized in that, The method further includes: If the second message includes a second indication parameter, and the second indication parameter is used to indicate the reporting tag identifier, then the first tag identifier is sent to the first function.

74. The method according to claim 70, characterized in that, The method further includes: If the second message does not include the second indication parameter, send the device identifier of the first terminal to the first function.

75. The method according to claim 72, characterized in that, The first terminal is locally configured with a first parameter, which by default indicates that the device identifier has not been reported. If the second message includes a second indication parameter, and the second indication parameter is used to indicate that both the tag identifier and the device identifier are reported simultaneously, sending the first device identifier and the first tag identifier to the first function includes: If the second message includes the second indication parameter, and the second indication parameter is used to indicate that the tag identifier and the device identifier are reported simultaneously, the first device identifier and the first tag identifier are sent to the first function; Update the first parameter to identify the reported device identifier.

76. The method according to claim 75, characterized in that, The method further includes: If the second message does not include the second indication parameter, and the first parameter indicates that the device identifier has not been reported, send the first tag identifier and the first device identifier to the first function; Update the first parameter to identify the reported device identifier.

77. The method according to claim 75, characterized in that, The method further includes: If the second message does not include the second indication parameter, and the first parameter represents the reported device identifier, send the first tag identifier to the first function.

78. The method according to claim 71, characterized in that, The method further includes: Receive a second message retransmitted by the first function; wherein the retransmitted second message includes a second indication parameter for instructing simultaneous reporting of tag identifier and device identifier; Resend the third message to the first function; wherein the resent third message includes the first device identifier and the first tag identifier.

79. A first function, characterized in that, The first function includes: The first receiving module is configured to receive a first message sent by a first application function; wherein the first message includes part or all of a first identifier representing the device identifier of the first terminal; A first processing module is configured to determine a target identifier; wherein the target identifier is used to identify the first terminal; the target identifier includes one of the following: a temporary identifier; a device identifier; The first sending module is used to send a second message to the first terminal; wherein the second message includes a target identifier.

80. A first function, characterized in that, The first function includes: The second receiving module is configured to receive a first message sent by the first application function; wherein the first message includes part or all of a first identifier representing the device identifier of the first terminal; The second processing module is used to determine the first indication parameter; wherein the first indication parameter is used to indicate the content of the message sent by the first terminal to the first function; A first sending module is configured to send a second message to the first terminal; wherein the second message includes a first indication parameter.

81. A first terminal, characterized in that, The first terminal includes: The third receiving module is configured to receive a second message sent by the first function; wherein the second message includes one or more of the following: a target identifier; a first indication parameter; the first indication parameter is used to indicate the content of a message sent by the first terminal to the first function; the target identifier is used to identify the first terminal; the target identifier includes one of the following: a temporary identifier; a device identifier; The third processing module is used to determine, match, or obtain the device of the first terminal based on the target identifier, and / or determine the content of the message reported, fed back, or sent by the first terminal to the first function based on the first indication parameter, and / or generate and / or update the temporary identifier based on the first indication parameter.

82. A first function, characterized in that, The first function includes: The fourth receiving module is used to receive a first message sent by the first application function; wherein the first message includes part or all of a first identifier that represents the device identifier of the first terminal; The fourth processing module is used to determine a target identifier; wherein the target identifier is used to identify the first terminal; the target identifier includes one of the following: a tag identifier; a device identifier; The fourth sending module is used to send a second message to the first terminal; wherein the second message includes a target identifier.

83. A first terminal, characterized in that, The first terminal includes: The fifth receiving module is used to receive a second message sent by the first function; wherein the second message includes one or more of the following: a target identifier; a second indication parameter; the second indication parameter is used to indicate the content of the message sent by the first terminal to the first function; the target identifier is used to identify the first terminal; the target identifier includes one of the following: a tag identifier; a device identifier; The fifth processing module is used to determine, match, or obtain the device of the first terminal based on the target identifier, and / or determine the content of the message reported, fed back, or sent by the first terminal to the first function based on the second indication parameter.

84. A communication device, characterized in that, The communication device includes: Memory, used to store executable instructions; A processor, when executing executable instructions stored in the memory, implements the information processing method according to any one of claims 1 to 21, or the information processing method according to any one of claims 22 to 42, or the information processing method according to any one of claims 43 to 51, or the information processing method according to any one of claims 52 to 69, or the information processing method according to any one of claims 70 to 78.

85. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the information processing method of any one of claims 1 to 21, or the information processing method of any one of claims 22 to 42, or the information processing method of any one of claims 43 to 51, or the information processing method of any one of claims 52 to 69, or the information processing method of any one of claims 70 to 78.

86. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the information processing method according to any one of claims 1 to 21, or the information processing method according to any one of claims 22 to 42, or the information processing method according to any one of claims 43 to 51, or the information processing method according to any one of claims 52 to 69, or the information processing method according to any one of claims 70 to 78.

Images