Method, device and storage medium for association between identities

Abstract

The present disclosure discloses an inter-identity association method and device, electronic equipment and storage medium, and relates to the technical field of communication. The specific implementation scheme is: receiving a registration request sent by any application program (APP) on a terminal device, and assigning a first APP identity to any APP according to the registration request, wherein the registration request includes a first Internet Protocol (IP) address of the terminal device; receiving a first RIC message of the terminal device sent by a network device, wherein the first RIC message includes the first IP address and a cell radio network temporary identity (C-RNTI) of the terminal device; constructing an association relationship between the first IP address, the first C-RNTI and the first APP identity, and updating the association relationship to an association relationship list in an application server. Thus, by increasing the storage and updating functions of the association relationship list of the application server, the consistency of the terminal device identification of the application server and the base station is realized, so that the terminal device can be more accurately located and relevant policy adjustment can be performed.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method, apparatus, electronic device, and storage medium for associating identifiers. Background Technology

[0002] Open-Radio Access Network (O-RAN) is currently recognized as one of the wireless access solutions that can enable the widespread adoption of 5G technology.

[0003] In O-RAN network deployment, there is currently no effective method for base stations and application subsystems to identify UEs consistently. The base station transmits user equipment (UE) network information to the application server of the application subsystem through the Near-Real Time RAN Intelligent Controller (nRT RIC). The application server cannot match the terminal APP of the application subsystem with the UE that received the air interface information, so it cannot accurately select the UE for relevant policy adjustments. Summary of the Invention

[0004] This disclosure provides a method, network device, apparatus, electronic device, and storage medium for associating identifiers, to solve the technical problem of consistency in UE identification between base stations and application subsystems.

[0005] According to a first aspect of this disclosure, a method for associating identifiers is provided, the method comprising: receiving a registration request sent by any application (APP) on a terminal device, and assigning a first APP identifier to the APP according to the registration request, wherein the registration request includes a first Internet Protocol (IP) address of the terminal device; receiving a first Radio Interchange Message (RIC) message of the terminal device sent by a network device, wherein the first RIC message includes the first IP address and the Cell Radio Network Temporary Identifier (C-RNTI) of the terminal device; constructing an association relationship between the first IP address, the first C-RNTI, and the first APP identifier, and updating the association relationship list in the application server.

[0006] In one embodiment of this disclosure, after updating the association list in the application server, the method further includes: receiving a re-registration request from the terminal device for any of the apps, and reassigning a second app identifier to any of the apps; updating the first app identifier associated with the first IP address and the first C-RNTI to the second app identifier.

[0007] In one embodiment of this disclosure, after updating the association list in the application server, the method further includes: obtaining a second IP address assigned to the terminal device after it re-registers in the network, wherein the second IP address is associated with the first APP identifier; obtaining a second RIC message sent by the network device, wherein the second RIC message includes the second IP address and the second C-RNTI of the terminal device; obtaining the first C-RNTI and the first IP address that are associated with the first APP identifier, and updating the first C-RNTI to the second C-RNTI and the first IP address to the second IP address.

[0008] In one embodiment of this disclosure, obtaining the second IP address assigned after the terminal device re-registers in the network includes: receiving a link reconstruction request sent by the terminal device, wherein the link reconstruction request includes the second IP address.

[0009] In one embodiment of this disclosure, the method further includes: receiving the first RIC message and the second RIC message sent by the near real-time wireless intelligent controller, wherein the first RIC message and the second RIC message are sent by the network device to the near real-time wireless intelligent controller through an E2 application protocol link with the near real-time wireless intelligent controller.

[0010] In one embodiment of this disclosure, the method further includes: receiving running data sent by the terminal device, wherein the running data includes the C-RNTI of the terminal device; querying the association list based on the C-RNTI of the terminal device to obtain a target APP identifier that is associated with the C-RNTI of the terminal device; generating an adjustment strategy for the target application identified by the target APP identifier based on the running data, and sending it to the terminal device.

[0011] According to a second aspect of this disclosure, a method for associating identifiers is provided, executed by a terminal device. The method includes: sending a registration request for any APP to an application server, wherein the registration request includes a first IP address of the terminal device; and receiving a first APP identifier of the any APP assigned to the terminal device by the application server according to the registration request.

[0012] In one embodiment of this disclosure, after receiving the first APP identifier of any APP assigned to the terminal device by the application server according to the registration request, the method further includes: sending a re-registration request for any APP to the application server; and receiving the second APP identifier reassigned to any APP by the application server.

[0013] In one embodiment of this disclosure, the method further includes: receiving a second IP address assigned to the terminal device after it has been re-registered in the network, sent by the network device.

[0014] In one embodiment of this disclosure, after receiving the second IP address assigned to the terminal device after re-registering in the network sent by the network device, the method further includes: in response to the network link being disconnected by the terminal device, sending a link reconstruction request to the application server, wherein the link reconstruction request includes the second IP address assigned to the terminal device after re-registering in the network.

[0015] In one embodiment of this disclosure, the method further includes: sending the operating data of the terminal device to the application server, wherein the operating data includes the C-RNTI of the terminal device; and receiving an adjustment strategy for the target application generated by the application server based on the operating data.

[0016] According to a third aspect of this disclosure, performed by a network device, another method for associating identifiers is provided, the method comprising: sending a first RIC message of a terminal device to an application server, wherein the first RIC message includes the first IP address and the Cell Radio Network Temporary Identifier (C-RNTI) of the terminal device.

[0017] In one embodiment of this disclosure, before sending the first RIC message of the terminal device to the application server, the method further includes: receiving the first IP address and the first C-RNTI sent by the core network device.

[0018] In one embodiment of this disclosure, before sending the first RIC message of the terminal device to the application server, the method further includes: enabling the RIC message reporting function and successfully subscribing to the RIC message.

[0019] In one embodiment of this disclosure, after sending the first RIC message of the terminal device to the application server, the method further includes: receiving a request for the terminal device to re-register in the network; and sending a second RIC message of the terminal device to the application server, wherein the second RIC message includes a second IP address assigned to the terminal device after re-registering in the network and a second C-RNTI of the terminal device.

[0020] In one embodiment of this disclosure, the method further includes: sending the first RIC message and the second RIC message to the near real-time wireless intelligent controller via the E2 application protocol link between the network device and the near real-time wireless intelligent controller, wherein the first RIC message and the second RIC message are sent to the application server through the near real-time wireless intelligent controller.

[0021] According to a fourth aspect of this disclosure, an association apparatus for identifiers is provided, comprising: an allocation module, configured to receive a registration request sent by any application (APP) on a terminal device, and allocate a first APP identifier to the APP according to the registration request, wherein the registration request includes a first Internet Protocol (IP) address of the terminal device; a receiving module, configured to receive a first RIC message from a network device of the terminal device, wherein the first RIC message includes the first IP address and a Cell Radio Network Temporary Identifier (C-RNTI) of the terminal device; and an updating module, configured to construct an association relationship between the first IP address, the first C-RNTI, and the first APP identifier, and update the association relationship list in the application server.

[0022] In one embodiment of this disclosure, the update module is further configured to: receive a re-registration request from the terminal device for any of the APPs, and reassign a second APP identifier to any of the APPs; update the first APP identifier associated with the first IP address and the first C-RNTI to the second APP identifier.

[0023] In one embodiment of this disclosure, the update module is further configured to: obtain a second IP address assigned to the terminal device after it re-registers in the network, wherein the second IP address is associated with the first APP identifier; obtain a second RIC message sent by the network device, wherein the second RIC message includes the second IP address and the second C-RNTI of the terminal device; obtain the first C-RNTI and the first IP address that are associated with the first APP identifier, and update the first C-RNTI to the second C-RNTI and the first IP address to the second IP address.

[0024] In one embodiment of this disclosure, the update module is further configured to: receive a link reconstruction request sent by the terminal device, wherein the link reconstruction request includes the second IP address.

[0025] In one embodiment of this disclosure, the update module is further configured to: receive the first RIC message and the second RIC message sent by the near real-time wireless intelligent controller, wherein the first RIC message and the second RIC message are sent by the network device to the near real-time wireless intelligent controller through the E2 application protocol link between the network device and the near real-time wireless intelligent controller.

[0026] In one embodiment of this disclosure, the apparatus is further configured to: receive running data sent by the terminal device, wherein the running data includes the C-RNTI of the terminal device; query the association list according to the C-RNTI of the terminal device to obtain a target APP identifier that is associated with the C-RNTI of the terminal device; generate an adjustment strategy for the target application identified by the target APP identifier according to the running data, and send it to the terminal device.

[0027] According to a fifth aspect of this disclosure, an association device between identifiers is provided, the device comprising: a registration module for sending a registration request for any APP to an application server, wherein the registration request includes a first IP address of the terminal device; and a receiving module for receiving a first APP identifier of any APP assigned to the terminal device by the application server according to the registration request.

[0028] In one embodiment of this disclosure, the receiving module is further configured to: send a re-registration request for any APP to the application server; and receive a second APP identifier reassigned to any APP by the application server.

[0029] In one embodiment of this disclosure, the receiving module is further configured to: receive a second IP address assigned to the terminal device after it has been re-registered in the network, sent by the network device.

[0030] In one embodiment of this disclosure, the receiving module is further configured to: in response to a network connection loss of the terminal device, send a link reconstruction request to the application server, wherein the link reconstruction request includes a second IP address assigned to the terminal device after it has re-registered in the network.

[0031] In one embodiment of this disclosure, the apparatus is further configured to: send the operating data of the terminal device to the application server, wherein the operating data includes the C-RNTI of the terminal device; and receive the adjustment strategy of the target application generated by the application server based on the operating data.

[0032] According to a sixth aspect of this disclosure, an inter-identifier association apparatus is provided, the apparatus comprising: a sending module configured to send a first RIC message of a terminal device to an application server, wherein the first RIC message includes the first IP address and the Cell Radio Network Temporary Identifier (C-RNTI) of the terminal device.

[0033] In one embodiment of this disclosure, the sending module is further configured to: receive the first IP address and the first C-RNTI sent by the core network device.

[0034] In one embodiment of this disclosure, the sending module is further configured to: enable the RIC message reporting function and successfully subscribe to the RIC message.

[0035] In one embodiment of this disclosure, the sending module is further configured to: receive a request for the terminal device to re-register in the network; and send a second RIC message of the terminal device to the application server, wherein the second RIC message includes a second IP address assigned to the terminal device after re-registering in the network and a second C-RNTI of the terminal device.

[0036] In one embodiment of this disclosure, the sending module is further configured to: send the first RIC message and the second RIC message to the near real-time wireless intelligent controller via the E2 application protocol link between the network device and the near real-time wireless intelligent controller, wherein the first RIC message and the second RIC message are sent to the application server via the near real-time wireless intelligent controller.

[0037] According to a seventh aspect of this disclosure, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the association method between identifiers described in the first aspect of this disclosure.

[0038] According to an eighth aspect of this disclosure, a processor-readable storage medium is provided, the processor-readable storage medium storing a computer program for causing the processor to perform the association method between identifiers described in the first aspect embodiment.

[0039] The technical solutions provided by the embodiments of this disclosure bring at least the following beneficial effects: by adding the storage and update function of the association list of the application server, the consistency of the application server and the base station in identifying the terminal device can be achieved, thereby enabling more accurate location of the terminal device and adjustment of related strategies.

[0040] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0041] The above and / or additional aspects and advantages of this disclosure will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, in which:

[0042] Figure 1 This is a flowchart illustrating a method for associating identifiers according to an embodiment of the present disclosure;

[0043] Figure 2 This is a flowchart illustrating a method for associating identifiers according to another embodiment of the present disclosure;

[0044] Figure 3 This is a flowchart illustrating a method for associating identifiers according to another embodiment of the present disclosure;

[0045] Figure 4 This is a flowchart illustrating a method for associating identifiers according to another embodiment of the present disclosure;

[0046] Figure 5 This is a flowchart illustrating a method for associating identifiers according to another embodiment of the present disclosure;

[0047] Figure 6 This is a flowchart illustrating a method for associating identifiers according to another embodiment of the present disclosure;

[0048] Figure 7 This is a flowchart illustrating a method for associating identifiers according to another embodiment of the present disclosure;

[0049] Figure 8 This is a flowchart illustrating a method for associating identifiers according to another embodiment of the present disclosure;

[0050] Figure 9 This is a flowchart illustrating a method for associating identifiers according to another embodiment of the present disclosure;

[0051] Figure 10 This is a flowchart illustrating the overall process of the association method between identifiers according to an embodiment of this disclosure.

[0052] Figure 11This is a block diagram of an association device between identifiers according to an embodiment of the present disclosure;

[0053] Figure 12 This is a block diagram of an association device between identifiers according to another embodiment of the present disclosure;

[0054] Figure 13 This is a block diagram of an association device between identifiers according to another embodiment of the present disclosure;

[0055] Figure 14 This is a block diagram of an electronic device associated with identifiers according to an embodiment of the present disclosure. Detailed Implementation

[0056] In this disclosure, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0057] In this disclosure, the term "multiple" refers to two or more, and other quantifiers are similar.

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

[0059] This disclosure provides a method, network device, apparatus, electronic device, and storage medium for associating identifiers, which addresses the technical problem in the related art of being unable to accurately select the terminal application (APP) for relevant policy adjustments based on the current network environment of the user terminal (UE).

[0060] The method and apparatus are based on the same disclosed concept. Since the methods and apparatus solve problems in similar ways, the implementation of the apparatus and methods can refer to each other, and repeated parts will not be described again.

[0061] Figure 1 This is a flowchart illustrating a method for associating identifiers according to an embodiment of the present disclosure.

[0062] like Figure 1 As shown, the method for associating identifiers in this embodiment includes:

[0063] S101, receive a registration request sent by any application (APP) on the terminal device, and assign a first APP identifier to any APP according to the registration request, wherein the registration request includes the first Internet Protocol (IP) address of the terminal device.

[0064] The entity executing the association method between identifiers described in this disclosure is an application server, and the terminal device can connect to the application server via a wireless network. Specifically, the terminal device can connect to the application server via an Open-Radio Access Network (O-RAN). For example, the O-RAN can be a public wireless access network such as 2G, 3G, 4G, or 5G.

[0065] It should be noted that terminal devices may include personal computers (PCs), tablets, or mobile phones, etc.

[0066] In this embodiment of the disclosure, when a terminal device installs an application (APP), in order to use the functions provided by the APP, it is necessary to register the APP on the application server corresponding to the APP.

[0067] The first Internet Protocol (IP) address can be the UE IP. It should be noted that the UE IP is assigned to the terminal device by the network device.

[0068] Specifically, when a UE registers with a network device, the core network device assigns a UE IP address to the terminal device based on the UE's registration request. Simultaneously, it sends this UE IP address to the base station, which then forwards it to the application server. Understandably, different terminal devices within the same network device will have different UE IP addresses. Therefore, different terminal devices can be distinguished using their UE IP addresses, providing a basis for subsequent terminal device location.

[0069] In this embodiment of the disclosure, after receiving a registration request, the application server can generate a first APP identifier (Identity document, ID) based on the registration request. It should be noted that within the same application server, different APPs on different terminal devices can have different APP identifiers, thus allowing for accurate location of the APP on the terminal device. For example, the APP identifier can be 1, 2, 3, etc., and the server can be configured according to actual needs.

[0070] In this embodiment of the disclosure, after receiving a registration request sent by the application APP, the application server can assign the APP ID to the terminal device, and the application server can quickly match the APP of the corresponding terminal device through the APP ID.

[0071] S102, receive the first RIC message of the terminal device sent by the network device, wherein the first RIC message includes the first IP address and the cell radio network temporary identifier (C-RNTI) of the terminal device.

[0072] In this embodiment, the network device can be a base station. Further, a Near-Real Time RAN Intelligent Controller (nRT RIC) can be deployed on the base station side. It should be noted that the nRT RIC includes radio resource management (RRM) functions, excluding dynamic resource allocation (DRA) related radio resource control. Artificial intelligence technology is introduced into the nRT RIC, enabling intelligent management of radio resources driven by big data and artificial intelligence, thus improving the device's adaptability to complex environments. The base station can generate RIC messages through the nRT RIC and send them to the application server for processing.

[0073] The base station and the nRT RIC can be connected via a network link. In this embodiment, the link between the base station and the nRT RIC can be enhanced with RIC message functionality, which is used by the base station to send UE IP and UE C-RNTI, etc.

[0074] It should be noted that the Cell-Radio Network Temporary Identifier (C-RNTI) can be the UE ID, which is assigned by the core network equipment to the terminal device and sent to the application server through the base station. For example, this UE ID can be 111, 112, 113, etc. The specific configuration can be set by the base station according to actual needs.

[0075] It is understandable that different terminal devices have different UE IDs. Therefore, the terminal device can be accurately located by matching the UE ID.

[0076] S103, construct the association between the first IP address, the first C-RNTI, and the first APP identifier, and update the association list in the application server.

[0077] In this embodiment of the disclosure, within the same application server, different terminal devices have different first IP addresses and first C-RNTIs, and different apps have different first app identifiers. Therefore, the first IP address, first C-RNTI, and first app identifier can be associated through the aforementioned relationship, and the mapping relationship can be updated in the association list on the application server. The application server can then locate the target app or target terminal based on the association list.

[0078] In this embodiment, a registration request from any application (APP) on the terminal device is first received, and a first APP identifier is assigned to each APP based on the registration request. It should be noted that the registration request includes the terminal device's first Internet Protocol (IP) address. Simultaneously, a first RIC message from the network device is received, whereby the first RIC message includes the first IP address and the terminal device's Cell Radio Network Temporary Identifier (C-RNTI). Then, an association relationship is constructed between the first IP address, the first C-RNTI, and the first APP identifier, and updated in the association relationship list in the application server. Therefore, by adding the storage and updating function of the application server's association relationship list, consistency in the identification of the terminal device by the application server and the network device is achieved, thereby enabling more accurate location of the terminal device and related policy adjustments.

[0079] Furthermore, the application server can have an APP ID entry. Within the corresponding APP ID entry file, a set of parameters for the terminal device can be stored. These parameters may include object location, filename, etc. Therefore, the parameters of the corresponding terminal device can be obtained by accessing the corresponding APP ID entry through the APP ID.

[0080] In this embodiment of the disclosure, except for the first application of UE IP to establish a one-to-one correspondence between APP ID and UEC-RNTI to generate a relationship list, UE IP is no longer used during subsequent data transmission. This can improve the security of data transmission and prevent data leakage from causing losses.

[0081] Based on any of the above embodiments, such as Figure 2 As shown, in step S103, after updating the association list in the application server, the following steps are also included:

[0082] S201, receive a re-registration request from any APP sent by the terminal device, and reassign a second APP identifier to any APP.

[0083] In practice, due to reasons such as APP updates or re-downloading of the APP, the APP on the terminal device needs to be re-registered. At this time, the application server needs to reassign the APP ID to the terminal device in order to identify the newly registered APP and prevent the server from being unable to locate the APP through the APP ID due to the APP re-registration.

[0084] S202, update the first APP identifier that is associated with the first IP address and the first C-RNTI to the second APP identifier.

[0085] After receiving a re-registration request from any APP sent by the end device, the first APP identifier that is associated with the first IP address and the first C-RNTI can be found in the association list through the mapping relationship, and the first APP identifier in the association list can be replaced with the second APP identifier to update the association list.

[0086] In this embodiment, a re-registration request from any APP sent by the terminal device is first received, and a second APP identifier is reassigned to each APP. The first APP identifier associated with the first IP address and the first C-RNTI is updated to the second APP identifier. Therefore, after receiving the APP re-registration request, the application server can allocate an APP ID through the re-registration request and update the association list, thereby improving the consistency of UE identification between the base station and the application subsystem.

[0087] Based on any of the above embodiments, such as Figure 3 As shown, in step S103, after updating the association list in the application server, the following steps are also included:

[0088] S301, Obtain the second IP address assigned after the terminal device re-registers in the network, wherein the second IP address is associated with the first APP identifier.

[0089] In this embodiment of the disclosure, after receiving a re-registration request from a terminal device, the application server generates a second IP address and assigns it to the terminal device.

[0090] In implementation, a UE's registration failure with the server will cause changes to its UE IP and UE C-RNTI. Therefore, we need to update the association list with the changed UE IP and UE C-RNTI to prevent the server from being unable to locate the terminal device through the association list. It should be noted that there are various reasons why a UE may re-register in the network, including UE registration failure, server restart, and link disconnection. It should also be noted that the new UE IP is generated by the core network equipment and sent to the base station, which then forwards it to the application server.

[0091] Furthermore, the terminal device will initiate a link reconstruction request to the base station due to network disconnection, and the reconstruction request message will include a second IP address. Further, after generating the second IP address, the server can associate the second IP address in the association list with the first APP identifier through a mapping relationship.

[0092] S302, Obtain the second RIC message sent by the network device, wherein the second RIC message includes the second IP address and the second C-RNTI of the terminal device.

[0093] In this embodiment of the disclosure, after receiving a re-registration request from a terminal device, the base station can assign a second C-RNTI to the terminal device and generate a second RIC message, which is then sent to the application server for processing. The second RIC message includes a second IP address and the terminal device's second C-RNTI.

[0094] Specifically, the application server can receive a first RIC message and a second RIC message from the nRT RIC. These messages are sent by the network device to the nRT RIC via the E2 application protocol link. Thus, through the nRT RIC link, additional RIC messages can be sent to the server, including UE IP and UE ID information, providing a basis for updating and using the association list.

[0095] S303, obtain the first C-RNTI and the first IP address that are associated with the first APP identifier, and update the first to the second C-RNTI and the first IP address to the second IP address.

[0096] After receiving a re-registration request from any APP sent by the end device, the application server can find the first C-RNTI and the first IP address that are associated with the first APP identifier through the mapping relationship, and update the first C-RNTI and the first IP address in the association relationship list to the second C-RNTI and the second IP address respectively.

[0097] In this embodiment, the system first obtains the second IP address assigned to the terminal device after re-registering in the network. This second IP address is associated with the first APP identifier. Then, it obtains the second RIC message sent by the network device, which includes the second IP address and the terminal device's second C-RNTI. Finally, it obtains the first C-RNTI and the first IP address associated with the first APP identifier, updating the first C-RNTI to the second C-RNTI and the first IP address to the second IP address. Therefore, after receiving a re-registration request from the terminal device, the application server can update the association list through the re-registration request, preventing inaccurate location of the terminal device due to changes in the association list.

[0098] Based on any of the above embodiments, such as Figure 4 As shown in the embodiments of this disclosure, the method for associating identifiers further includes:

[0099] S401, receive operation data sent by the terminal device, wherein the operation data includes the terminal device's C-RNTI.

[0100] It should be noted that the operational data sent by the terminal device may also include signal strength, wireless network-related measurement data, and APP operating parameters. Specific settings need to be configured according to actual needs; no limitations are made here.

[0101] It is understandable that different terminal devices and different apps may send different operational data. For example, the operational data sent by a navigation map app may include the car's driving data, while the operational data sent by a shopping app may include the user's purchase history.

[0102] In this embodiment of the disclosure, the runtime data includes the C-RNTI of the terminal device to facilitate the application server in matching the terminal device.

[0103] S402, based on the C-RNTI of the terminal device, query the association list to obtain the target APP identifier that is associated with the C-RNTI of the terminal device.

[0104] In this embodiment of the disclosure, after the application server obtains the C-RNTI of the terminal device, it can match the target APP identifier in the association list through the mapping relationship to determine the terminal device and target APP that issued the running data, so as to bind the running data with the target APP.

[0105] S403: Based on the running data, generate the adjustment strategy for the target application identified by the target APP identifier and send it to the terminal device.

[0106] In this embodiment of the disclosure, the adjustment strategy of the target APP can be pre-set. For example, the adjustment strategy can be speed limit, peak traffic restriction, etc. The specific settings need to be set according to actual needs, and no limitation is made here.

[0107] Optionally, the adjustment strategy can vary depending on the type of target app. For example, the adjustment strategy for a navigation map app could be to adjust road speed limits based on operational data, while the adjustment strategy for a shopping app could be to adjust product prices based on operational data.

[0108] In this embodiment, the system first receives runtime data from a terminal device, including the terminal device's C-RNTI. Then, based on the terminal device's C-RNTI, it queries an association list to obtain target app identifiers associated with the terminal device's C-RNTI. Finally, based on the runtime data, it generates an adjustment strategy for the target application identified by the target app identifier and sends it to the terminal device. Therefore, the association list can accurately match the app that generated the runtime data, allowing the adjustment strategy to be accurately sent to the terminal device, significantly reducing adjustment costs.

[0109] Figure 5 This is a flowchart illustrating a method for associating identifiers according to an embodiment of this disclosure.

[0110] like Figure 5 As shown, the association method between these identifiers includes:

[0111] S501 sends a registration request for any APP to the application server, wherein the registration request includes the first IP address of the terminal device.

[0112] It should be noted that the association method between identifiers in this embodiment is executed by the terminal device.

[0113] It should be noted that there can be various reasons for app registration, such as first-time login, changing the app login account, or re-login after a connection failure. The terminal device needs to send a registration request to the server to obtain the app ID.

[0114] It should be noted that the registration request includes the terminal device's first IP address, which can be the UEIP. This UEIP is assigned to the terminal device by the core network device when the device registers with the network device.

[0115] S502, the terminal device receives the first APP identifier of any APP assigned by the application server to the terminal device according to the registration request. In this embodiment of the disclosure, the first APP identifier of any APP received by the terminal device is unique, thereby facilitating the application server to accurately locate the re-registered APP.

[0116] In this embodiment, a registration request for any app is first sent to the application server. The registration request includes the terminal device's first IP address. Then, the terminal device receives the first app identifier assigned to it by the application server based on the registration request. Thus, by sending a registration request for any app to the application server, the server assigns an app ID to that app, enabling the subsequent generation of an association list and facilitating app location.

[0117] Based on any of the above embodiments, such as Figure 6 As shown, in step S502, after receiving the first APP identifier of any APP assigned to the terminal device by the application server according to the registration request, the following steps are also included:

[0118] S601 sends a re-registration request for any app to the application server.

[0119] In this embodiment of the disclosure, due to reasons such as APP login account or link disconnection, the APP needs to re-register, and the terminal device needs to generate a re-registration request and send it to the server.

[0120] S602, the application server reassigns a second APP identifier to any APP.

[0121] The application server will reassign a second app identifier (APP ID) to any app on the terminal device based on the re-registration request. This is to prevent the server from being unable to accurately locate the app on the terminal device using the APP ID due to the app's re-registration.

[0122] In this embodiment, a re-registration request for any app is first sent to the application server, and then the application server reassigns a second app identifier to any app. Therefore, when app registration information changes, the server can assign a second app identifier to any app based on the re-registration request, preventing the server from being unable to accurately locate the app's position due to changes in app registration information.

[0123] Furthermore, when any app on the terminal device needs to re-register, the terminal device can send the app's registration request to the server, and the server will send the assigned first IP address to the terminal device through the network device.

[0124] Furthermore, in response to a network link loss at the terminal device, a new UE IP address needs to be generated to prevent the server from being unable to accurately locate the terminal device due to changes in its registration information. Specifically, the terminal device can send a link reconstruction request to the application server, which includes a second IP address assigned to the terminal device after re-registration in the network.

[0125] It should be noted that the second IP address is reassigned to the terminal device by the core network device after receiving the terminal device's re-registration request, and is sent to the application server by the base station. Therefore, when a terminal device needs to re-register, it can send a registration request, and the core network device will assign a new UE ID and UE IP, which will then be reported to the application server by the network device. This allows the application server to update the association list, preventing the terminal device from being unable to be identified through the association list due to changes in the UE IP and UE ID.

[0126] Based on any of the above embodiments, such as Figure 7 As shown in the embodiments of this disclosure, the method for associating identifiers further includes:

[0127] S701 sends the terminal device's operating data to the application server, including the terminal device's C-RNTI.

[0128] In the disclosed embodiments, the terminal device sends operational data to the server via a network device. This operational data may include signal strength, wireless network-related measurement data, etc. Specific details need to be configured according to actual requirements, and no limitations are made here.

[0129] It is understandable that different terminal devices and different apps may send different operational data. For example, the operational data sent by a navigation map app may include the car's driving data, while the operational data sent by a shopping app may include the user's purchase history.

[0130] It should be noted that the runtime data includes C-RNTI, which allows the application server to accurately locate the corresponding terminal device after processing the runtime data.

[0131] S702 receives the adjustment strategy for the target application generated by the application server based on the running data.

[0132] In this embodiment, the terminal device first sends its operating data, including the terminal device's C-RNTI, to the application server. Then, it receives the adjustment strategy for the target application generated by the application server based on the operating data. Thus, by sending operating data to the server, the terminal device can obtain the adjustment strategy for the target application and adjust the application accordingly to optimize it.

[0133] Figure 8 This is a flowchart illustrating a method for associating identifiers according to an embodiment of this disclosure.

[0134] like Figure 8 As shown, the method includes:

[0135] S801, send the first RIC message of the terminal device to the application server, wherein the first RIC message includes the first IP address and the cell radio network temporary identifier (C-RNTI) of the terminal device.

[0136] It should be noted that the association method between identifiers in this embodiment is performed by a network device.

[0137] In this embodiment of the disclosure, the network device may be a base station deployed with a Near-RealTime RAN Intelligent Controller (nRT RIC). It should be noted that the nRT RIC includes the Radio Resource Management (RRM) function described in the 38.300 protocol, excluding the radio resource control related to Dynamic Resource Allocation (DRA). The nRT RIC introduces artificial intelligence technology, enabling intelligent management of radio resources driven by big data and artificial intelligence, thereby improving the device's adaptability to complex environments.

[0138] In this embodiment of the disclosure, RIC messages can be added to the link between the base station and the nRT RIC for the base station to send UEIP and UE C-RNTI, etc. Therefore, adding RIC messages via the E2AP link provides a basis for updating and using the association list.

[0139] It should be noted that enabling the RIC message sending function and successfully subscribing to RIC messages are required. Specifically, when the base station enables the RIC information sending function and the RIC subscription is successful, the base station will proactively send an RIC UE Information message to the application server for each UE when it registers or reconnects to the wireless network. This RIC UE Information message contains information such as the UE IP and UE C-RNTI.

[0140] Based on any of the above embodiments, such as Figure 9 As shown, after sending the first RIC message of the terminal device to the application server in step S801, the following steps are also included:

[0141] S901: Receives a request from a terminal device to re-register in the network.

[0142] In this embodiment of the disclosure, when a terminal device generates a re-registration request due to a network disconnection, the re-registration request can be sent to the server for processing via a network device.

[0143] Furthermore, the base station will send the newly assigned UE ID to the application server so that the application server can update the association list based on the new UE ID.

[0144] S902, send a second RIC message of the terminal device to the application server, wherein the second RIC message includes the second IP address assigned to the terminal device after it is re-registered in the network and the second C-RNTI of the terminal device.

[0145] In this embodiment, the network device first receives a request for the terminal device to re-register in the network, and then sends a second RIC message of the terminal device to the application server. The second RIC message includes a second IP address assigned to the terminal device after re-registration and a second C-RNTI for the terminal device. Thus, when the terminal device re-registers, the network device assigns a new UE ID to the terminal device, preventing the server from being unable to accurately locate the terminal device due to changes in the terminal device information caused by re-registration.

[0146] Figure 10 This is a general flowchart of an embodiment of the present disclosure, as follows: Figure 10As shown, on the terminal device side, the terminal device initiates a registration request to the application server, which includes the UE IP. It should be noted that the UE IP is assigned by the core network device during terminal device registration and sent to the base station. The base station then reports this to the application server. The APP can obtain the UE IP through the terminal device entity and send it to the application server for device identification. The application server responds to the registration request and sends the APP ID to the terminal device to bind the APP. The application server updates the association list in the application server based on the UE IP, UE ID, and APP ID. On the base station side, the terminal device first connects to the wireless network (which can be NR or LTE). It then determines whether the base station has enabled RIC information transmission and whether the RIC subscription is successful. If successful, the base station sends an RIC message containing the UE IP and UE ID. After receiving the RIC message from the base station, the application server updates the UE ID and UE IP in the association list. If unsuccessful, the application server cannot upload the RIC message. On the application server side, it determines whether the terminal device has experienced a network disconnection and reconnected to the network. If so, after receiving the updated RIC message, the application server updates the association list, formulates relevant policies, and sends them to the terminal device APP for adjustment. If not, the application server associates the identifiers based on the running data sent by the terminal device APP, formulates relevant policies, and sends them to the terminal device APP for adjustment.

[0147] The technical solutions provided in this disclosure are applicable to a variety of systems, especially 5G systems. For example, applicable systems may include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G systems (5GS).

[0148] The terminal devices involved in the embodiments of this disclosure can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in a 5G system, a terminal device can be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments disclosed herein.

[0149] The network device disclosed in this embodiment may be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, the base station may also be called an access point, or a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network equipment involved in this disclosure can be a base transceiver station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA) system, a NodeB in a Wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in this disclosure. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0150] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multiple-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0151] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multiple-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0152] Figure 11 This is a structural block diagram of an association device between identifiers according to another embodiment of the present disclosure.

[0153] like Figure 11 As shown, the association device 1100 between identifiers in this embodiment of the present disclosure includes: an allocation module 1110, a receiving module 1120, and an update module 1130.

[0154] The allocation module 1110 is used to receive a registration request sent by any application (APP) on the terminal device, and to allocate a first APP identifier to any APP according to the registration request, wherein the registration request includes the first Internet Protocol (IP) address of the terminal device.

[0155] The receiving module 1120 is used to receive a first RIC message from the terminal device sent by the network device, wherein the first RIC message includes a first IP address and the cell radio network temporary identifier (C-RNTI) of the terminal device.

[0156] The update module 1130 is used to build the association between the first IP address, the first C-RNTI and the first APP identifier, and update the association list in the application server.

[0157] In one embodiment of this disclosure, the update module 1130 is further configured to: receive a re-registration request from any APP sent by the terminal device, and reassign a second APP identifier to any APP; update the first APP identifier associated with the first IP address and the first C-RNTI to the second APP identifier.

[0158] In one embodiment of this disclosure, the update module 1130 is further configured to: obtain a second IP address assigned to the terminal device after it re-registers in the network, wherein the second IP address is associated with the first APP identifier; obtain a second RIC message sent by the network device, wherein the second RIC message includes the second IP address and the second C-RNTI of the terminal device; obtain a first C-RNTI and a first IP address that are associated with the first APP identifier, and update the first C-RNTI to the second C-RNTI and the first IP address to the second IP address.

[0159] In one embodiment of this disclosure, the update module 1130 is further configured to: receive a link reconstruction request sent by a terminal device, wherein the link reconstruction request includes a second IP address.

[0160] In one embodiment of this disclosure, the update module 1130 is further configured to: receive a first RIC message and a second RIC message sent by the near real-time wireless intelligent controller, wherein the first RIC message and the second RIC message are sent by the network device to the near real-time wireless intelligent controller through the E2 application protocol link between the network device and the near real-time wireless intelligent controller.

[0161] In one embodiment of this disclosure, the aforementioned association device 1100 between identifiers is further configured to: receive running data sent by a terminal device, wherein the running data includes the terminal device's C-RNTI; query the association list based on the terminal device's C-RNTI to obtain a target APP identifier that is associated with the terminal device's C-RNTI; and generate an adjustment strategy for the target application identified by the target APP identifier based on the running data, and send it to the terminal device.

[0162] Figure 12 This is a structural block diagram of an association device between identifiers according to another embodiment of the present disclosure.

[0163] like Figure 12 As shown, the identifier association device 1200 of this embodiment includes: a registration module 1210, used to send a registration request for any APP to an application server, wherein the registration request includes a first IP address of the terminal device; and a receiving module 1220, used to receive a first APP identifier of any APP assigned to the terminal device by the application server according to the registration request.

[0164] In one embodiment of this disclosure, the receiving module 1220 is further configured to: send a re-registration request for any APP to the application server; and receive a second APP identifier reassigned to any APP by the application server.

[0165] In one embodiment of this disclosure, the receiving module 1220 is further configured to: receive a second IP address assigned to the terminal device after it has re-registered in the network, sent by the network device.

[0166] In one embodiment of this disclosure, the receiving module 1220 is further configured to: in response to a network link disconnection of the terminal device, send a link reconstruction request to the application server, wherein the link reconstruction request includes a second IP address assigned after the terminal device re-registers in the network.

[0167] In one embodiment of this disclosure, the identifier association device 1200 of this embodiment further includes: sending terminal device operation data to an application server, wherein the operation data includes the terminal device's C-RNTI; and receiving an adjustment strategy for a target application generated by the application server based on the operation data. Figure 13 This is a structural block diagram of an association device between identifiers according to another embodiment of the present disclosure.

[0168] like Figure 13 As shown, the identifier association device 1300 of this embodiment includes: a sending module 1310, configured to send a first RIC message of a terminal device to an application server, wherein the first RIC message includes a first IP address and a cell radio network temporary identifier (C-RNTI) of the terminal device.

[0169] In one embodiment of this disclosure, the sending module 1310 is further configured to: receive a first IP address and a first C-RNTI sent by the core network device.

[0170] In one embodiment of this disclosure, the sending module 1310 is further configured to: enable the RIC message sending function and successfully subscribe to RIC messages.

[0171] In one embodiment of this disclosure, the sending module 1310 is further configured to: receive a request for the terminal device to re-register in the network; and send a second RIC message of the terminal device to the application server, wherein the second RIC message includes a second IP address assigned to the terminal device after re-registering in the network and a second C-RNTI of the terminal device.

[0172] In one embodiment of this disclosure, the sending module 1310 is further configured to: send a first RIC message and a second RIC message to the near real-time wireless intelligent controller via the E2 application protocol link between the network device and the near real-time wireless intelligent controller, wherein the first RIC message and the second RIC message are sent to the application server through the near real-time wireless intelligent controller.

[0173] It should be noted that the division of units in the embodiments of this disclosure is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0174] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or all or part of the technical solution, 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.) or processor to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0175] To implement the above embodiments, this disclosure also proposes an electronic device 1400, such as... Figure 14 As shown, the electronic device 1400 includes: a processor 1401, a memory 1402 communicatively connected to the processor, and a transceiver 1403 for receiving and sending information. The memory 1402 stores instructions executable by at least one processor. The instructions are executed by at least one processor 1401 to implement the association method between identifiers as described in the first aspect of this disclosure.

[0176] According to embodiments of this disclosure, this disclosure also provides a processor-readable storage medium.

[0177] The processor-readable storage medium stores a computer program that causes the processor to execute the association method between identifiers described in the above embodiments of this disclosure.

[0178] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0179] To implement the above embodiments, this disclosure also proposes a computer program product, including a computer program that, when executed by a processor, implements a method for associating identifiers of goods as described in the first aspect of this disclosure.

[0180] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0181] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other inter-programmable identifier associated device to produce a machine, such that the instructions, which execute via the processor of the computer or other inter-programmable identifier associated device, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0182] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other associated device between programmable identifiers to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0183] These processors can execute instructions that can also be loaded onto a computer or other associated device with a programmable identifier, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0184] Obviously, those skilled in the art can make various modifications and variations to this disclosure without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.

Claims

1. A method for associating identifiers, characterized in that, The method, executed by the application server, includes: Receive a registration request sent by any application (APP) on the terminal device, and assign a first APP identifier to the APP according to the registration request, wherein the registration request includes the first Internet Protocol (IP) address of the terminal device; The terminal device receives a first RIC message sent by the network device, wherein the first RIC message includes the first IP address and the Cell Radio Network Temporary Identifier (C-RNTI) of the terminal device; Establish the association between the first IP address, the first C-RNTI, and the first APP identifier, and update the association list in the application server; Receive operation data sent by the terminal device, wherein the operation data includes the C-RNTI of the terminal device; Based on the C-RNTI of the terminal device, query the association list to obtain the target APP identifier that is associated with the C-RNTI of the terminal device; Based on the operational data, an adjustment strategy for the target application identified by the target APP identifier is generated and sent to the terminal device.

2. The method according to claim 1, characterized in that, After updating the association list in the application server, the following is also included: Receive a re-registration request from any of the apps sent by the terminal device, and reassign a second app identifier to any of the apps; Update the first APP identifier, which is associated with the first IP address and the first C-RNTI, to the second APP identifier.

3. The method according to claim 1, characterized in that, After updating the association list in the application server, the following is also included: Obtain the second IP address assigned to the terminal device after it re-registers in the network, wherein the second IP address is associated with the first APP identifier; Obtain the second RIC message sent by the network device, wherein the second RIC message includes the second IP address and the second C-RNTI of the terminal device; Obtain the first C-RNTI and the first IP address that are associated with the first APP identifier, and update the first C-RNTI to the second C-RNTI and the first IP address to the second IP address.

4. The method according to claim 3, characterized in that, The step of obtaining the second IP address assigned after the terminal device re-registers in the network includes: The terminal device receives a link reconstruction request, wherein the link reconstruction request includes the second IP address.

5. The method according to claim 4, characterized in that, The method further includes: The network device receives the first RIC message and the second RIC message from the near real-time wireless intelligent controller, wherein the first RIC message and the second RIC message are sent to the near real-time wireless intelligent controller by the network device through the E2 application protocol link with the near real-time wireless intelligent controller.

6. A method for associating identifiers, characterized in that, The method, executed by a terminal device, includes: Send a registration request for any APP to the application server, wherein the registration request includes the first IP address of the terminal device; Receive the first APP identifier of any APP assigned to the terminal device by the application server according to the registration request; Send the terminal device's operating data to the application server, wherein the operating data includes the terminal device's C-RNTI; The system receives an adjustment strategy for a target application generated by the application server based on the runtime data. The adjustment strategy involves the application server querying an association list based on the C-RNTI of the terminal device to obtain a target APP identifier associated with the C-RNTI of the terminal device. Based on the runtime data, the system generates an adjustment strategy for the target application identified by the target APP identifier. The association list is constructed from the associations between a first IP address, a first C-RNTI, and the first APP identifier.

7. The method according to claim 6, characterized in that, After receiving the first APP identifier of any APP assigned to the terminal device by the application server according to the registration request, the method further includes: Send a re-registration request for any of the apps to the application server; The application server reassigns a second APP identifier to any of the APPs.

8. The method according to claim 6, characterized in that, The method further includes: The terminal device receives a second IP address assigned after it has re-registered in the network, sent by the network device.

9. The method according to claim 8, characterized in that, After receiving the second IP address assigned to the terminal device after it has re-registered in the network, sent by the network device, the method further includes: In response to a network connection loss at the terminal device, a link reconstruction request is sent to the application server, wherein the link reconstruction request includes a second IP address assigned to the terminal device after it has re-registered in the network.

10. A method for associating identifiers, characterized in that, Performed by a network device, the method includes: Send a first RIC message of the terminal device to the application server, wherein the first RIC message includes a first IP address and the cell radio network temporary identifier (C-RNTI) of the terminal device; The system receives operational data sent by a terminal device and sends the operational data of the terminal device to the application server, wherein the operational data includes the C-RNTI of the terminal device. The system receives an adjustment strategy for a target application generated by the application server based on the runtime data, and sends the adjustment strategy to the terminal device. The adjustment strategy is generated by the application server querying an association list based on the terminal device's C-RNTI to obtain a target APP identifier associated with the terminal device's C-RNTI; and generating an adjustment strategy for the target application identified by the target APP identifier based on the runtime data. The association list is constructed from the association relationships between a first IP address, a first C-RNTI, and a first APP identifier.

11. The method according to claim 10, characterized in that, Before sending the first RIC message of the terminal device to the application server, the method further includes: Receive the first IP address and the first C-RNTI sent by the core network device.

12. The method according to claim 10, characterized in that, Before sending the first RIC message of the terminal device to the application server, the method further includes: Enable the RIC message reporting function and successfully subscribe to the RIC message.

13. The method according to claim 10, characterized in that, After sending the first RIC message of the terminal device to the application server, the method further includes: Receive the request from the terminal device to re-register in the network; Send a second RIC message of the terminal device to the application server, wherein the second RIC message includes a second IP address assigned to the terminal device after it is re-registered in the network and a second C-RNTI of the terminal device.

14. The method according to claim 13, characterized in that, The method further includes: The first RIC message and the second RIC message are sent to the near real-time wireless intelligent controller via the E2 application protocol link between the network device and the near real-time wireless intelligent controller, wherein the first RIC message and the second RIC message are sent to the application server through the near real-time wireless intelligent controller.

15. A device for associating identifiers, characterized in that, The device includes: The allocation module is used to receive a registration request sent by any application (APP) on the terminal device, and to allocate a first APP identifier to the APP according to the registration request, wherein the registration request includes the first Internet Protocol (IP) address of the terminal device; The receiving module is configured to receive a first RIC message from the terminal device sent by the network device, wherein the first RIC message includes the first IP address and the Cell Radio Network Temporary Identifier (C-RNTI) of the terminal device; The update module is used to construct the association between the first IP address, the first C-RNTI, and the first APP identifier, and update the association list in the application server; The device is also used for: Receive operation data sent by the terminal device, wherein the operation data includes the C-RNTI of the terminal device; Based on the C-RNTI of the terminal device, query the association list to obtain the target APP identifier that is associated with the C-RNTI of the terminal device; Based on the operational data, an adjustment strategy for the target application identified by the target APP identifier is generated and sent to the terminal device.

16. The apparatus according to claim 15, characterized in that, The update module is also used for: Receive a re-registration request from any of the apps sent by the terminal device, and reassign a second app identifier to any of the apps; Update the first APP identifier, which is associated with the first IP address and the first C-RNTI, to the second APP identifier.

17. The apparatus according to claim 15, characterized in that, The update module is also used for: Obtain the second IP address assigned to the terminal device after it re-registers in the network, wherein the second IP address is associated with the first APP identifier; Obtain the second RIC message sent by the network device, wherein the second RIC message includes the second IP address and the second C-RNTI of the terminal device; Obtain the first C-RNTI and the first IP address that are associated with the first APP identifier, and update the first C-RNTI to the second C-RNTI and the first IP address to the second IP address.

18. The apparatus according to claim 17, characterized in that, The update module is also used for: The terminal device receives a link reconstruction request, wherein the link reconstruction request includes the second IP address.

19. The apparatus according to claim 18, characterized in that, The update module is also used for: The network device receives the first RIC message and the second RIC message from the near real-time wireless intelligent controller, wherein the first RIC message and the second RIC message are sent to the near real-time wireless intelligent controller by the network device through the E2 application protocol link with the near real-time wireless intelligent controller.

20. A device for associating identifiers, characterized in that, The device includes: The registration module is used to send a registration request for any APP to the application server, wherein the registration request includes the first IP address of the terminal device; The receiving module is used to receive the first APP identifier of any APP assigned to the terminal device by the application server according to the registration request; The device is also used for: Send the terminal device's operating data to the application server, wherein the operating data includes the terminal device's C-RNTI; The system receives an adjustment strategy for a target application generated by the application server based on the runtime data. The adjustment strategy involves the application server querying an association list based on the C-RNTI of the terminal device to obtain a target APP identifier associated with the C-RNTI of the terminal device. Based on the runtime data, the system generates an adjustment strategy for the target application identified by the target APP identifier. The association list is constructed from the associations between a first IP address, a first C-RNTI, and the first APP identifier.

21. The apparatus according to claim 20, characterized in that, The receiving module is also used for: Send a re-registration request for any of the apps to the application server; The application server reassigns a second APP identifier to any of the APPs.

22. The apparatus according to claim 20, characterized in that, The receiving module is also used for: The terminal device receives a second IP address assigned after it has re-registered in the network, sent by the network device.

23. The apparatus according to claim 22, characterized in that, The receiving module is also used for: In response to a network connection loss at the terminal device, a link reconstruction request is sent to the application server, wherein the link reconstruction request includes a second IP address assigned to the terminal device after it has re-registered in the network.

24. A device for associating identifiers, characterized in that, The device includes: The sending module is used to send a first RIC message of the terminal device to the application server, wherein the first RIC message includes a first IP address and the cell radio network temporary identifier (C-RNTI) of the terminal device; The device is further configured to: receive operating data sent by the terminal device, and send the operating data of the terminal device to the application server, wherein the operating data includes the C-RNTI of the terminal device; The system receives an adjustment strategy for a target application generated by the application server based on the runtime data, and sends the adjustment strategy to the terminal device. The adjustment strategy is generated by the application server querying an association list based on the terminal device's C-RNTI to obtain a target APP identifier associated with the terminal device's C-RNTI; and generating an adjustment strategy for the target application identified by the target APP identifier based on the runtime data. The association list is constructed from the association relationships between a first IP address, a first C-RNTI, and a first APP identifier.

25. The apparatus according to claim 24, characterized in that, The sending module is further configured to: Receive the first IP address and the first C-RNTI sent by the core network device.

26. The apparatus according to claim 24, characterized in that, The sending module is further configured to: Enable the RIC message reporting function and successfully subscribe to the RIC message.

27. The apparatus according to claim 24, characterized in that, The sending module is further configured to: Receive the request from the terminal device to re-register in the network; Send a second RIC message of the terminal device to the application server, wherein the second RIC message includes a second IP address assigned to the terminal device after it is re-registered in the network and a second C-RNTI of the terminal device.

28. The apparatus according to claim 27, characterized in that, The sending module is further configured to: The first RIC message and the second RIC message are sent to the near real-time wireless intelligent controller via the E2 application protocol link between the network device and the near real-time wireless intelligent controller, wherein the first RIC message and the second RIC message are sent to the application server through the near real-time wireless intelligent controller.

29. An electronic device, characterized in that, The device includes a memory, a processor, and a transceiver, wherein the processor runs a program corresponding to the executable program code stored in the memory to implement the method as described in any one of claims 1-14.

30. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-14.

31. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method according to any one of claims 1-14.

Images