Terminal information sharing method and communication device

Abstract

The present application relates to the field of wireless communication technology, and provides a method and communication device for sharing terminal information, which can reduce the waste of terminal resources and air interface signaling resources. An information management network element receives a first request from a first network element supporting a first service, and a third request from a second network element supporting a second service, for requesting terminal information. The information management network element sends a second request to the terminal, and the second request is used to request the information of the terminal. Next, the information management network element receives the information from the terminal, and then sends the information to the first network element and the second network element. When multiple network elements supporting different services request the information of the terminal from the information management network element, the information management network element only sends a request to the terminal once, and the terminal only needs to report the terminal information for this request, which can avoid repeated reporting of the terminal information and reduce the waste of terminal resources and air interface signaling resources.

Description

Technical Field

[0001] The embodiments of the present application relate to fields such as wireless communications, and in particular to a method and a communication device for sharing terminal information. Background Art

[0002] With the development of mobile communications, more and more services can be transmitted using mobile communication networks. Services such as mission critical push-to-talk (MCPTT) services, mission critical video (MCVideo) services, mission critical data (MCData) services, drone-related services, smart factory-related services, and Internet of Vehicles-related services may require terminal information. Terminal information includes location information, heartbeat information, core network type information accessed, and radio access technology (RAT) type information adopted. The terminal information required by different services may be the same. For example, both MCPTT and MCVideo services may use the terminal's location information.

[0003] Currently, different services obtain terminal information separately. When different services obtain the same information, the terminal needs to repeatedly report the terminal information, such as repeatedly reporting location information, resulting in consumption of terminal resources and air interface signaling resources. Summary of the Invention

[0004] The embodiments of the present application provide a method and a communication device for sharing terminal information, which can reduce the waste of terminal resources and air interface signaling resources.

[0005] In a first aspect, a method for sharing terminal information is provided. An information management network element receives a first request from a first network element that supports a first service. The information management network element may also receive a third request from a second network element that supports a second service. Both the first and third requests are for requesting terminal information. The information management network element may send a second request to the terminal, the second request being for requesting the information. The information management network element receives the information from the terminal and then sends the information to the first and second network elements. Optionally, the information is location information or heartbeat information.

[0006] When multiple network elements (the first network element and the second network element) that support different services request terminal information from the information management network element, the information management network element only sends a request to the terminal once (that is, sends a second request to the terminal). The terminal only needs to report the terminal information for this request, which can avoid repeated reporting of terminal information and thereby reduce the waste of terminal resources and air interface signaling resources.

[0007] In one possible implementation, after receiving the third request from the second network element, the information management network element may further send an update request for the second request to the terminal, where the update request is used to request the information of the terminal. Furthermore, the information management network element receives the information from the terminal. This information is sent to the information management network element by the terminal in response to the update request. The information management network element adjusts the request sent to the terminal based on the requests from multiple network elements supporting different services, eliminating the need to request information from the terminal multiple times and better meeting the request requirements of multiple network elements supporting different services.

[0008] In one possible implementation, the information management network element obtains a sharing policy, where the sharing policy is used to describe whether the information is allowed to be shared between the first service and the second service. Furthermore, the information management network element may send the information to the first network element and the second network element based on the sharing policy. Optionally, the sharing policy is used to describe which services can share information, including but not limited to the first service and the second service.

[0009] In a possible implementation, the sharing policy is used to indicate: the first service and the second service. For example, the sharing policy includes but is not limited to the first service identifier and the second service identifier.

[0010] In one possible implementation, the sharing policy further indicates one or more of the following: the type of information, a sharing indication, and the terminals to which the sharing policy applies, where the terminals to which the sharing policy applies include the terminal. It is understood that the sharing policy includes, but is not limited to, application to the terminal, and may also apply to other terminals. For example, a sharing policy may include the identifier of a terminal or the identifiers of a group of terminals.

[0011] In one possible implementation, when the information management network element obtains the sharing policy, it may receive the sharing policy from the first device; the first device includes but is not limited to one or more of the following: a configuration network element, the first network element, the second network element, and the terminal.

[0012] In one possible implementation, the first request received by the information management network element from the first network element includes one or more of the following: the identifier of the first network element, the first trigger, the first service identifier, the identifier of the terminal, the type of information, and the first subscription transaction identifier. The third request received by the information management network element from the second network element includes one or more of the following: the identifier of the second network element, the third trigger, the second service identifier, the identifier of the terminal, the type of information, and the third subscription transaction identifier. The third trigger is the same as or compatible with the first trigger. Compatible can be understood as the first trigger being a subset of the third trigger, or the third trigger being a subset of the first trigger. Alternatively, the third trigger and the first trigger may have an intersection, or may be different.

[0013] In a possible implementation, the second request includes one or more of the following: the first trigger, the type of the information, and a second subscription transaction identifier.

[0014] In one possible implementation, the update request includes a fourth trigger; wherein the fourth trigger is determined based on the first trigger and the third trigger. The fourth trigger is determined based on the triggers of the first network element and the second network element, and can meet the requirements of the first network element and the second network element.

[0015] In one possible implementation, after receiving the third request from the second network element, the information management network element determines whether it is necessary to send a request to the terminal in response to the third request to request the terminal's information. If not, no request is sent. In this way, when receiving the information from the terminal, the information management network element sends the information to the first network element and the second network element based on the second request. This avoids repeated reporting of terminal information and reduces waste of terminal resources and air interface signaling resources.

[0016] In a possible implementation, after receiving the third request from the second network element, the information management network element may determine, based on a sharing policy, whether it is necessary to send a request to the terminal in response to the third request to request the information of the terminal.

[0017] In a second aspect, a method for sharing terminal information is provided, wherein an information management network element receives a first request from a first network element and a third request from a second network element, wherein the first network element supports a first service and the second network element supports a second service, and wherein the first request and the third request are both used to request information of the terminal; then, the information management network element sends a second request and a fourth request to the terminal, wherein the second request and the fourth request are both used to request the information. Next, the information management network element receives the information and first indication information from the terminal, wherein the first indication information is used to indicate that the information is allowed to be shared by the first service (i.e., the first network element) and the second service (i.e., the second network element). Furthermore, the information management network element sends the information to the first network element and the second network element.

[0018] The information management network element sends two requests to the terminal (i.e., the second request and the fourth request). The terminal aggregates (also called aggregates) these two requests into a single request event. The terminal reports terminal information only for this aggregated request event and also reports the sharing policy, so that the information management network element can decide to send this information to the first network element and / or the second network element based on the sharing policy. By reporting terminal information only for a single request event, the terminal avoids repeated reporting of terminal information and reduces the waste of terminal resources and air interface signaling resources.

[0019] In a possible implementation, the first indication information includes a sharing indication. The terminal may indicate that the information can be shared through the sharing indication, without limiting the services between which the information can be shared.

[0020] In one possible implementation, the second request sent by the information management network element to the terminal includes but is not limited to one or more of the following: a second trigger, the type of the information, and a second subscription transaction identifier. The fourth request sent by the information management network element to the terminal includes but is not limited to one or more of the following: a fifth trigger, the type of the information, and a fifth subscription transaction identifier. Furthermore, the first indication information includes: the second subscription transaction identifier and the fifth subscription transaction identifier, and / or, the identifier of the second trigger and the identifier of the fifth trigger. The terminal informs the information management network element through the subscription transaction identifier or the trigger identifier: between which services or network elements the information can be shared.

[0021] According to a third aspect, a method for sharing terminal information is provided. A terminal receives a second request from an information management network element, the second request being used to request information about the terminal. The terminal receives a fourth request from the information management network element, the fourth request being used to request the information. The terminal then sends the information and first indication information to the information management network element, the first indication information being used to indicate that the information is allowed to be shared.

[0022] The information management network element sends two requests to the terminal (i.e., the second request and the fourth request). The terminal aggregates (also called aggregates) these two requests into a single request event. The terminal reports terminal information only for this aggregated request event and also reports the sharing policy, so that the information management network element can decide to send this information to the first network element and / or the second network element based on the sharing policy. By reporting terminal information only for a single request event, the terminal avoids repeated reporting of terminal information and reduces the waste of terminal resources and air interface signaling resources.

[0023] In a possible implementation, the first indication information includes a sharing indication. The terminal may indicate that the information can be shared through the sharing indication, without limiting the services between which the information can be shared.

[0024] In one possible implementation, the second request sent by the information management network element to the terminal includes but is not limited to one or more of the following: a second trigger, the type of the information, and a second subscription transaction identifier. The fourth request sent by the information management network element to the terminal includes but is not limited to one or more of the following: a fifth trigger, the type of the information, and a fifth subscription transaction identifier. Furthermore, the first indication information includes: the second subscription transaction identifier and the fifth subscription transaction identifier, and / or, the identifier of the second trigger and the identifier of the fifth trigger. The terminal informs the information management network element through the subscription transaction identifier or the trigger identifier: between which services or network elements the information can be shared.

[0025] In a possible implementation, the terminal may obtain a sharing policy, which is used to describe the terminal information allowed to be shared, that is, which terminal information is allowed to be shared, including but not limited to the terminal information requested in the second request and the fourth request, and may also include other terminal information.

[0026] Furthermore, the first indication information is determined according to the sharing policy. When the sharing policy indicates that the information is allowed to be shared, the first indication information may be used to indicate that the information is allowed to be shared. When there is no sharing policy for storing the information, or when the sharing policy for the information indicates that sharing is not allowed, the terminal may not send the first indication information to the information management network element.

[0027] In a fourth aspect, a communication device is provided, wherein the device has the functions of implementing the first aspect and any possible implementation of the first aspect, or implementing the functions of the second aspect and any possible implementation of the second aspect, or implementing the functions of the third aspect and any possible implementation of the third aspect. These functions can be implemented through hardware or through hardware executing corresponding software. The hardware or software includes one or more functional modules corresponding to the above functions.

[0028] In a fifth aspect, a communication device is provided, comprising a processor and, optionally, a memory coupled to the processor. The memory is configured to store computer programs or instructions; the processor is configured to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, the device is configured to implement the functions of the information management network element in the method of the first aspect and any possible implementation of the first aspect, or the functions of the information management network element in the second aspect and any possible implementation of the second aspect, or the functions of the terminal in the third aspect and any possible implementation of the third aspect.

[0029] In one possible implementation, the apparatus may further include a transceiver configured to transmit a signal processed by the processor or receive a signal input to the processor. The transceiver may perform the transmitting or receiving action performed by the information management network element in the first aspect and any possible implementation of the first aspect; or perform the transmitting or receiving action performed by the information management network element in the second aspect and any possible implementation of the second aspect; or perform the transmitting or receiving action performed by the terminal in the third aspect and any possible implementation of the third aspect.

[0030] In the sixth aspect, the present application provides a chip system, which includes one or more processors (also referred to as processing circuits), and the processors are electrically coupled to a memory (also referred to as a storage medium); the memory may be located in the chip system or not in the chip system; the memory is used to store computer programs or instructions; the processor is used to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, they are used to implement the functions of the information management network element in the above-mentioned first aspect and any possible implementation method of the first aspect, or to implement the functions of the information management network element in the above-mentioned second aspect and any possible implementation of the second aspect, or to implement the functions of the terminal in the above-mentioned third aspect and any possible implementation of the third aspect.

[0031] In one possible implementation, the chip system may further include an input / output interface (also referred to as a communication interface), the input / output interface being configured to output signals processed by the processor or receive signals input to the processor. The input / output interface may perform the sending action or receiving action performed by the information management network element in the first aspect and any possible implementation of the first aspect; or, perform the sending action or receiving action performed by the information management network element in the second aspect and any possible implementation of the second aspect; or, perform the sending action or receiving action performed by the terminal in the third aspect and any possible implementation of the third aspect. Specifically, the output interface performs the sending action, and the input interface performs the receiving action.

[0032] In a possible implementation, the chip system may be composed of a chip, or may include a chip and other discrete devices.

[0033] In the seventh aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program includes instructions for implementing the functions of the first aspect and any possible implementation of the first aspect, or instructions for implementing the functions of the second aspect and any possible implementation of the second aspect, or instructions for implementing the functions of the third aspect and any possible implementation of the third aspect.

[0034] Alternatively, a computer-readable storage medium is used to store a computer program, which, when executed by a computer, can enable the computer to execute the method executed by the information management network element in the above-mentioned first aspect and any possible implementation of the first aspect, or execute the method executed by the information management network element in the above-mentioned second aspect and any possible implementation of the second aspect, or execute the method executed by the terminal in the above-mentioned third aspect and any possible implementation of the third aspect.

[0035] In the eighth aspect, a computer program product is provided, which includes instructions. When the instructions are run on a computer, the computer executes the method executed by the information management network element in the above-mentioned first aspect and any possible implementation of the first aspect, or executes the method executed by the information management network element in the above-mentioned second aspect and any possible implementation of the second aspect, or executes the method executed by the terminal in the above-mentioned third aspect and any possible implementation of the third aspect.

[0036] In the ninth aspect, a communication system is provided, which includes an information management network element that executes the method of the second aspect and any possible implementation of the second aspect and a terminal that executes the method of the third aspect and any possible implementation of the third aspect.

[0037] In the tenth aspect, a communication system is provided, which includes an information management network element that executes the above-mentioned first aspect and any possible implementation method of the first aspect, and a first network element and / or a second network element that communicates with the information management network element.

[0038] The technical effects of the above-mentioned fourth to tenth aspects can refer to the descriptions in the first to third aspects, and the repeated parts will not be repeated. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A schematic diagram of a communication system provided in an embodiment of the present application;

[0040] Figure 2 A schematic diagram of a process for requesting terminal information provided in an embodiment of the present application;

[0041] Figure 3 A schematic diagram of a terminal information sharing process provided in an embodiment of the present application;

[0042] Figure 4 A schematic diagram of a terminal information sharing process provided in an embodiment of the present application;

[0043] Figure 5 A schematic diagram of a terminal information sharing process provided in an embodiment of the present application;

[0044] Figure 6 A schematic diagram of a terminal information sharing process provided in an embodiment of the present application;

[0045] Figure 7 A structural diagram of a communication device provided in an embodiment of the present application;

[0046] Figure 8 This is a structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0048] To facilitate understanding of the technical solutions of the embodiments of the present application, the system architecture of the method provided in the embodiments of the present application is briefly described below. It is understood that the system architecture described in the embodiments of the present application is for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application and does not constitute a limitation on the technical solutions provided in the embodiments of the present application.

[0049] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: wireless local area network (WLAN) communication system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), world-wide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system (5GS) or new radio (NR), sixth generation (6G) system, e-mail paging system (EPS), and future communication systems.

[0050] To facilitate understanding of the embodiments of the present application, the application scenarios of the present application are introduced below. The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Ordinary technicians in this field can know that with the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0051] With the development of mobile communications, more and more services can be transmitted using mobile communication networks. Services such as MCPTT service (hereinafter referred to as PTT service), MCVideo service (hereinafter referred to as Video service), MCData service (hereinafter referred to as Data service), drone-related services, smart factory-related services, Internet of Vehicles-related services, etc. These services may need to obtain terminal information. Terminal information includes location information, heartbeat information, the type of core network currently accessed by the UE, the type of wireless access technology RAT currently used by the UE, whether the UE is currently in an emergency state, etc. The terminal information required for different services may be the same. For example Figure 1 As shown, the location information is taken as an example for explanation.

[0052] The terminal can perform various services, such as push-to-talk PTT service, video service, and data service. The terminal is installed with MCPTT service client (hereinafter referred to as PTT service client), MCVideo service client (hereinafter referred to as Video service client), MCData service client (hereinafter referred to as Data service client), etc. The push-to-talk PTT service server, video service server, and data service server communicate with the push-to-talk PTT service client, video service client, and data service client installed on the terminal respectively. When the PTT service server, video service server, and data service server need to obtain the location information of the terminal, they can communicate with the location client (Loc Client) on the terminal through the location server (Loc Server). The location client reports the location information of the terminal to the location server, and the location server sends the location information of the terminal to the PTT service server, video service server, and data service server.

[0053] Currently, different services obtain terminal information separately, and multiple services cannot share information about the same terminal. For example, the location information of the terminal cannot be shared between the PTT service server and the Video service server. Figure 2 As shown, the PTT service server and the Video service server respectively obtain the location information of the terminal as an example for introduction.

[0054] Step 11a: The PTT service server sends a request message to the location management server to request the location information of the terminal.

[0055] The request message may include, but is not limited to, one or more of the following:

[0056] The identifier of the requesting party (i.e., the PTT service server), the identifier of the requested target terminal, the type of terminal information requested: i.e., location information (e.g., two-dimensional location information, speed, direction, requested location format, accuracy requirements, etc.), and the first trigger, which is used to indicate the conditions for triggering location reporting.

[0057] The conditions for triggering location reporting include but are not limited to one or more of the following: immediate reporting, time interval for continuous reporting, reporting when the terminal's cell changes, or reporting when the terminal's tracking area (TA) changes, reporting when the terminal's radio access technology RAT changes, reporting when the core network (core) accessed by the terminal changes, reporting when the terminal (or a client installed on the terminal) sends voice and / or data and / or video, reporting when the terminal enters an emergency state, or reporting according to a timer.

[0058] The location management server executes steps 12a to 14a in response to the request message in step 11a.

[0059] Step 12a: The location management server sends a request message to the target terminal to request location information.

[0060] For example, the location management server executes a location subscription process or a location request process to the target terminal. Specifically, the location management server executes a location subscription process or a location request process to a location management client installed on the target terminal.

[0061] Step 13a: After determining that the location reporting condition indicated by the first trigger is satisfied, the target terminal reports the location information of the target terminal to the location management server.

[0062] Step 14a: The location management server sends the location information of the target terminal to the requesting party (ie, the PTT service server).

[0063] Step 11b: The video service server sends a request message to the location management server to request the location information of the terminal.

[0064] The request message may include, but is not limited to, one or more of the following:

[0065] The identifier of the requesting party (i.e., the Video service server), the identifier of the requested target UE, the type of terminal information requested: i.e., location information (e.g., two-dimensional location information, speed, direction, requested location format, accuracy requirements, etc.), and a second trigger, which is used to indicate the conditions for triggering location reporting.

[0066] The second trigger may be the same as the first trigger.

[0067] The location management server executes steps 12b to 14b in response to the request message in step 11b.

[0068] Step 12b (similar to step 12a): the location management server sends a request message to the target terminal to request location information.

[0069] For example, the location management server executes a location subscription process or a location request process to the target terminal. Specifically, the location management server executes a location subscription process or a location request process to a location management client installed on the target UE.

[0070] Step 13b (similar to step 13a): after determining that the location reporting condition indicated by the second trigger is satisfied, the target terminal reports the location information of the target terminal to the location management server.

[0071] Step 14b (similar to step 14a): the location management server sends the location information of the target terminal to the requesting party (ie, the Video service server).

[0072] Figure 2 The order of steps 11a to 14a and steps 11b to 14b is not limited.

[0073] Assume that the terminal information type requested in step 11a is the same as that in step 11b, for example, both are location information, and the conditions for triggering location reporting in step 11a and step 11b (i.e., the first trigger and the second trigger) are the same, for example, both are reporting every 10 seconds. For the terminal, the location information will be repeatedly reported.

[0074] Based on this, the present application provides a variety of technical solutions to achieve that when different services obtain the same information, the terminal does not need to repeatedly report the terminal information, which can reduce the waste of terminal resources and air interface signaling resources.

[0075] In one solution, the information management server integrates and processes the requests from multiple business servers (also known as aggregation processing) to avoid repeatedly requesting the terminal's information from the terminal, thereby eliminating the need for the terminal to report the same information of the terminal multiple times (repeatedly). The specific process of this solution can be found in the description of Example 1. It should be noted that the "no need to report multiple times (repeatedly) separately" here means that there is no need to report separately for multiple requests. Multiple reports for one request fall within the scope of protection of this application.

[0076] For example, the information management server sends requests A and B to the terminal, both of which report the terminal's location information every 10 seconds. The terminal reports its location information every 10 seconds for request A and again every 10 seconds for request B.

[0077] For example, multiple reports for one request are: the information management server sends a request to the terminal, requesting the terminal's location information to be reported every 10 seconds, and the terminal reports the terminal's location information multiple times (every 10 seconds) in response to this request.

[0078] In another solution, the information management server requests the terminal information from the terminal in response to requests from multiple business servers. The terminal can integrate and process multiple requests from the information management server (also called aggregation processing) to achieve the need to report the same information of the terminal multiple times (repeatedly) separately. The specific process of this solution can be found in the description of Example 2. It should be noted that "no need to report multiple times (repeatedly) separately" here means that there is no need to report separately for multiple requests. Multiple reports for one request fall within the scope of protection of this application.

[0079] For reporting multiple requests separately, please refer to the above description and will not be repeated here.

[0080] For example, multiple reports for a request might be: the information management server sends requests A and B to the terminal, both of which report the terminal's location information every 10 seconds. The terminal then combines requests A and B into one request and reports its location information multiple times (every 10 seconds) for this combined request.

[0081] It is understandable that the embodiment 1, embodiment 2 and various examples introduced below can be respectively regarded as separate embodiments, or can be mutually referenced and combined to form a new embodiment.

[0082] A terminal, also known as user equipment (UE), mobile station (MS), mobile terminal (MT), or terminal device, is a device that provides voice and / or data connectivity to users. For example, terminal devices include handheld devices and vehicle-mounted devices with wireless connectivity. Currently, terminal devices can include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals (e.g., sensors) in industrial control, wireless terminals in self-driving systems, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, or wireless terminals with vehicle-to-vehicle (V2V) connectivity.

[0083] In addition, the "network element" mentioned below should not be limited to the "network element" on the core network side. As long as the functional entities of the "network element" are met, they are within the protection scope.

[0084] A service network element is a network element that supports a certain service. For example, a first service network element can be understood as a network element that supports the first service and can be referred to as the first network element for short; a second service network element can be understood as a network element that supports the second service and can be referred to as the second network element for short.

[0085] A service network element can also be called a service / application server, which can be a service server, a vertical application layer (VAL) server, a mission critical service (MCX) server, Figure 1 PTT server, data server, video server, etc. Optionally, the terminal can be installed with a service client corresponding to the service network element. The service client can be a vertical service application layer VAL client, a mission-critical service MCX client, Figure 1 PTT client, data client, video client, etc.

[0086] The information management network element is a functional entity that manages terminal information. It is responsible for one or more management functions such as acquisition, collection, update, aggregation, and authorization of terminal information. It can receive request messages sent by other requesting entities and return terminal information to the requesting entity. The information management network element can be a UE information management server (UE info management server), which is responsible for the management of multiple UE information (such as location, heartbeat, access information, etc.). Figure 1 The location server (responsible for the management of UE location), UE heartbeat management server (responsible for the management of UE heartbeat), UE access information management server (responsible for the management of UE access information), mobile edge computing (MEC) platform with one or more functions such as UE location management, heartbeat management, access information management, and other logical functional entities with the above functions. Optionally, an information management client corresponding to the information management network element can be installed on the terminal, and the information management client can be a UE information management server (UE info management Client), Figure 1 The location client (Loc Client), UE heartbeat management client, and UE access information management client in the UE are clients with one or more functions such as UE location management, heartbeat management, and access information management. It can be understood that UE heartbeat management can be heartbeat management of applications installed on the UE.

[0087] The configuration network element may be a configuration management server, which is responsible for configuration management of user profiles, device profiles, or service profiles, including distribution, update, and deletion of profiles.

[0088] This application includes but is not limited to being applicable to: vertical industry enterprise fields, mobile edge computing (MEC) platforms, enterprise self-built service platforms, operator capability exposure platforms, operator business operation platforms, etc. Among them, the information management network element can be integrated into the above platforms or as a native functional module of the above platforms.

[0089] It can be understood that the "sharing policy includes" in this application can be replaced with "sharing policy is used to indicate", that is, when the sharing policy introduced in this application includes a certain information, the information can be included in the sharing policy, or the sharing policy can implicitly indicate the information. Similarly, the "request includes" in this application can be replaced with "request is used to indicate", that is, when the request introduced in this application includes a certain information, the information can be included in the request, or the request can implicitly indicate the information. "Terminal information" and "terminal information" can be interchangeable. "Trigger" and "reporting trigger" can be interchangeable. "First request, second request, third request" can be referred to as "first subscription message, second subscription message, third subscription message", for example, a request or subscription message can be generated based on a request-response model, or a request or subscription message can be generated based on a subscription-notification model. "Request terminal information" can also be referred to as "subscription terminal information". "Request event" can be referred to as "subscription event".

[0090] In the following text, "trigger 1, trigger 2, trigger 3, trigger 4, trigger 5, trigger 6" can be replaced with "first trigger, second trigger, third trigger, fourth trigger, fifth trigger, sixth trigger," respectively. Similarly, "subscription transaction identifier 1, subscription transaction identifier 2, subscription transaction identifier 3, subscription transaction identifier 4, subscription transaction identifier 5" can be replaced with "first subscription transaction identifier, second subscription transaction identifier, third subscription transaction identifier, fourth subscription transaction identifier, fifth subscription identifier," respectively. "Service identifier 1, service identifier 2" can be replaced with "first service identifier, second service identifier," respectively.

[0091] The first service network element mentioned below refers to a network element or service network element, for example, a first network element, which supports a first service. For ease of understanding, this may be referred to as the first service network element. Similarly, the second service network element mentioned below refers to a network element or service network element, for example, a second network element, which supports a second service. For ease of understanding, this may be referred to as the second service network element.

[0092] The multiple service network elements mentioned below refer to multiple network elements that respectively support different services, that is, the multiple service network elements each support different services.

[0093] Example 1: The information management network element integrates and processes the requests of multiple service network elements (also called aggregation processing) to avoid repeatedly requesting the same information of the terminal from the terminal, thereby eliminating the need for the terminal to repeatedly report the terminal information, that is, the terminal does not need to report the same information of the terminal multiple times.

[0094] like Figure 3 As shown, a schematic diagram of the process of terminal information sharing is provided, including but not limited to the following steps:

[0095] Step 31: The first service network element sends a first request to the information management network element. Correspondingly, the information management network element receives the first request from the first service network element, where the first request is used to request information of the terminal.

[0096] Step 32: The information management network element sends a second request to the terminal. Correspondingly, the terminal receives the second request sent by the information management network element. The second request message is used to request the information of the terminal.

[0097] For example, the information management network element sends the second request to the terminal based on the first request.

[0098] Step 33: The second service network element sends a third request to the information management network element. Correspondingly, the information management network element receives the third request from the second service network element, where the third request is used to request the information of the terminal.

[0099] The terminal information requested by the second request and the third request is the same, for example, both request the location information of the terminal, or both request the heartbeat information of the terminal.

[0100] Optionally, the first service network element and the second service network element have different services. For example, the first service network element is a network element for the PTT service, and the second service network element is a network element for the video service.

[0101] The information management network element will not repeatedly request the terminal for the information of the terminal based on the third request.

[0102] It is understandable that the order of step 33 and step 32 is not limited.

[0103] Step 34: The terminal sends the information requested in step 32 to the information management network element. Correspondingly, the information management network element receives the information from the terminal.

[0104] For example, the terminal may send the terminal information to the information management network element based on the second request in step 32 .

[0105] Step 35a: The information management network element sends the information to the first service network element.

[0106] Step 35b: The information management network element sends the information to the second service network element.

[0107] The order of step 35a and step 35b is not limited. Step 35a and step 35b can send the information in different messages, or they can be sent in a single message, for example, the information management network element uses broadcast or multicast to send the information to the first service network element and the second service network element.

[0108] When multiple service network elements (the first service network element and the second service network element) request the terminal information from the information management network element, the information management network element only establishes a request event to the terminal once (i.e., sends a second request to the terminal). The terminal only needs to report the terminal information for this request event, which can avoid repeated reporting of terminal information and reduce the waste of terminal resources and air interface signaling resources.

[0109] Example 1:

[0110] Next, Figure 4 As shown in FIG, the process of terminal information sharing is further introduced in detail.

[0111] In Example 1, the configuration network element sends a terminal information sharing policy to the information management network element. For example, the sharing policy describes which services are allowed to share terminal information (i.e., between which services, terminal information can be shared). The number of services is at least two. This can also be understood as describing that terminal information can be shared between at least two services. For example, the sharing policy includes a service identifier (an identifier, a list of identifiers, or a range of identifiers). Optionally, the sharing policy includes a sharing indication and / or the types of terminal information allowed to be shared. Terminal information types include, but are not limited to, one or more of the following: heartbeat, location, core network type accessed, radio access technology (RAT) type employed, the terminal's affiliation status with a specific group, the terminal's presence status, the terminal's emergency status, and the terminal's connected state. Core network types include, for example, 4G, 5G, and 6G. Radio access technology types include, for example, Wi-Fi access and cellular network access. The affiliation status includes, for example, associated or unassociated. The terminal's presence status includes, for example, present or absent. The terminal's emergency status, for example, in the field of public security, when law enforcement officers are attacked, the attacked person's terminal should be given priority to ensure communication, and other terminals cannot interrupt. At this time, the attacked person's terminal can send an emergency status.

[0112] After receiving requests for terminal information from multiple business network elements, the information management network element can aggregate / integrate the multiple requests and send only one request to the terminal for the requests from multiple business network elements to request the terminal information (which can be called establishing a request event to the terminal).

[0113] Hereinafter, sending a request to a terminal to request information of the terminal and establishing a request event to the terminal can be used interchangeably and will not be described again.

[0114] After obtaining terminal information from the terminal, the information management network element can determine to which service network element, which service network elements, or all service network elements the terminal information should be sent based on the sharing policy and requests from multiple service network elements.

[0115] Figure 4 The following steps are involved:

[0116] Optionally, step 400: the information management network element obtains a sharing policy.

[0117] In one example, the sharing policy is configured by the configuration network element for the information management network element. For example, the configuration network element sends the sharing policy to the information management network element, and the information management network element receives the sharing policy from the configuration network element. The sharing policy can be proactively sent by the configuration network element to the information management network element, which is understood as a push. The sharing policy can also be proactively requested by the information management network element from the configuration network element, which is understood as a pull.

[0118] For example, the configuration network element may obtain the sharing policy from other devices (such as terminals) and then send it to the information management network element. In another example, the configuration network element configures the sharing policy through a system administrator.

[0119] In one example, the sharing policy is used to describe: which services are allowed to share terminal information (that is, which services allow terminal information to be shared). If there are at least two services, it can also be understood that the sharing policy is used to describe: terminal information is allowed to be shared between at least two services. In the present application, terminal information can be shared between a first service supported by a first service network element (the service with service identifier 1 hereinafter) and a second service supported by a second service network element (the service with service identifier 2 hereinafter). It can be understood that the sharing policy is used to describe that terminal information is allowed to be shared between the first service supported by the first service network element and the second service supported by the second service network element.

[0120] For example, the sharing policy includes: information that characterizes the service. For example, the sharing policy includes: a service identifier, or multiple service identifiers (for example, in the form of a service identifier list) (for example, service identifier 1 and service identifier 2 below), or a range of service identifiers, etc. The "service identifier" here can be understood as a "service identifier that allows sharing of terminal information". The service identifier is a set of characters that identifies a specific service, which can be an application identifier (application identifier), or a service identifier (service identifier), a fully qualified domain name (FQDN), etc. The range of the service identifier is used to indicate that terminal information is allowed to be shared between services within the range. The service identifier in this application can also be understood as a service type. Different service identifiers can be understood as different service types, for example, service identifier 1 is used to identify services of service type 1, and service identifier 2 is used to identify services of service type 2. Service types, for example, those introduced above: PTT service, Video service, Data service, etc.

[0121] In an optional example, the sharing policy is used to describe: services that are allowed to share one or more types of terminal information (which can be understood as: which types of terminal information can be shared between which services). For example, the sharing policy also includes: the type of terminal information (i.e., the type of terminal information allowed to be shared), such as location, heartbeat, etc. For example, the sharing policy can indicate: which services are allowed to share the first type (such as location) of terminal information, which services are allowed to share the second type (such as heartbeat) of terminal information, or, which services are allowed to share XX types of terminal information, etc. Optionally, if the sharing policy does not include or does not limit the type of terminal information, it can be considered that all types of terminal information that can be obtained by the information management network element are allowed to be shared.

[0122] In an optional example, the sharing policy also includes a sharing indicator, which may indicate whether the terminal information can be shared. The sharing indicator may occupy one bit. For example, if the bit is 0, it indicates that sharing is not allowed, and if the bit is 1, it indicates that sharing is allowed. Optionally, if the sharing policy does not include or define the sharing indicator, it may be considered that the terminal information is allowed to be shared. Optionally, if the sharing policy does not include or define the sharing indicator, it may be considered that the terminal information is not allowed to be shared.

[0123] In an optional example, a sharing policy is further used to describe the objects to which the sharing policy applies (which can be understood as: which objects can use the sharing policy). For example, the objects are terminals. For example, the objects can be one terminal, multiple terminals, or terminals that meet certain conditions. The certain conditions can include, for example, performing a certain service, possessing a certain capability, or belonging to a certain group. For example, the sharing policy also includes (indicates): information about the objects (e.g., terminals) to which the sharing policy applies. This object information can be the identifier of one terminal, multiple terminal identifiers (e.g., a list of terminal identifiers), a service identifier, or multiple service identifiers. When the object information is one or more service identifiers, it can be understood that all terminals using the one or more services can use the sharing policy. It can also be understood that the sharing policy can be formulated for one terminal, several terminals, or terminals using certain services. Optionally, if the sharing policy does not include or limit the object information to which the sharing policy applies, it can be considered that the sharing policy is formulated for all terminals served by the information management network element (i.e., the sharing policy can apply to all terminals served by the information management network element).

[0124] Subsequently, when the information management network element receives requests from multiple service network elements, it can decide whether to repeatedly request the terminal information from the terminal based on the sharing policy. Furthermore, when the information management network element receives information from the terminal, it can also decide to which service network element to feed the information back based on the sharing policy.

[0125] As shown in Table 1 below, a schematic diagram of a sharing strategy is provided. Table 1 is only an example and should not limit the present application.

[0126] Table 1

[0127]

[0128] As follows, we introduce another sharing strategy:

[0129] >UE ID / a list of UE IDs / service ID; [indicates the object to which the sharing policy applies]

[0130] >Sharing indicator (indicates whether UE information sharing is allowed)

[0131] >UE information list [indicates which type of UE information is allowed to be shared]

[0132] > location;

[0133] > A list of shared services [indicates which services can share UE information]

[0134] >MCPTT

[0135] >MCVideo

[0136] >heartbeat;

[0137] > A list of shared services [indicates which services can share UE information]

[0138] >MCPTT

[0139] >MCData

[0140] >Access RAT;

[0141] > A list of shared services [indicates which services can share UE information]

[0142] >MCVideo

[0143] >MCData

[0144] >Access core network;

[0145] > A list of shared services [indicates which services can share UE information]

[0146] >MCPTT

[0147] >MCVideo

[0148] >MCData

[0149] …

[0150] From the above diagram, it can be seen that location information is allowed to be shared between MCPTT service and MCVideo service, heartbeat is allowed to be shared between MCPTT service and MCData service, access RAT type is allowed to be shared between MCVideo service and MCData service, and access core network type is allowed to be shared between MCPTT service, MCVideo service and MCData service.

[0151] In Example 1, the validity period of the shared policy is the interval between two shared policy configurations. That is, the time from when the NE configures the shared policy to when the NE configures a new shared policy.

[0152] Step 401: The first service network element sends a first request to the information management network element. Correspondingly, the information management network element receives the first request from the first service network element, where the first request is used to request information of a terminal.

[0153] The first request includes but is not limited to one or more of the following:

[0154] The identifier of the first service network element, reporting trigger 1, service identifier 1 (the first service network element supports the service of the service identifier 1), terminal identifier, terminal information type, and subscription transaction identifier 1.

[0155] Optionally, the identifier of the first service network element may be understood as the identifier of the requester, for example, the name, identifier, Internet Protocol (IP) address, etc. of the first service network element.

[0156] Optionally, reporting trigger 1 is used to indicate condition 1 for triggering terminal information reporting. When the terminal determines that condition 1 in trigger 1 is met, the terminal information is reported to the information management network element. The event filter of trigger 1 (i.e., condition 1 for triggering terminal information reporting) includes but is not limited to one or more of the following: immediate reporting, time interval for continuous reporting, reporting when the terminal's cell changes, or reporting when the terminal's tracking area (TA) sends changes, reporting when the terminal's radio access technology RAT changes, reporting when the core network (core) the terminal accesses changes, reporting when the terminal (or a client installed on the terminal) sends voice and / or data and / or video, reporting when the terminal enters an emergency state, or reporting according to a timer, etc.

[0157] Optionally, the conditions for the terminal to report information are specified by the protocol. In this way, there is no need to include the reporting trigger 1 in the first request, and the terminal can also report information according to the conditions specified by the protocol.

[0158] Optionally, the subscription transaction identifier 1 is an optional parameter used to identify the transaction identifier of this request or subscription between the first service network element and the information management network element, and may not be included in the first request. The subscription transaction identifier 1 can be understood as the identifier of this request event triggered by the first service network element.

[0159] Optionally, the UE information type is an optional parameter indicating the type of information requested in step 401 and may not be included in the first request. For example, if the information management network element is a specific type of information management network element, such as a location management network element or a heartbeat management network element, then even if the first request does not include the UE information type, the information management network element knows which type of terminal information the first service network element is requesting.

[0160] Optionally, the service identifier 1 (for example, the identifier of the first service / application network element) is an optional parameter and may not be included in the first request. The first service network element supports the service with the service identifier 1. The information management network element may determine the service identifier 1 of the first service network element through the identifier of the first service network element, or the Internet Protocol (IP) address, or the uniform resource locator (URL), etc. One implementation method is that the service network element / application network element has previously registered its own service identifier 1 with the information management network element, and the information management network element has already saved the association between the service identifier 1 and the identifier (or IP address, or URL, etc.) of the first service network element.

[0161] Optionally, for technical details of step 401 , reference may be made to the technical details of an existing service network element requesting terminal information from an information management network element.

[0162] In one example, the first request may be a UE information subscription request or a UE information reporting configuration request.

[0163] Optionally, the request (e.g., the first request, the third request below) sent by the service network element to the information management network element may use an application layer protocol as the applicable transmission protocol, such as the hypertext transfer protocol (HTTP) or the session initiation protocol (SIP).

[0164] Optionally, the information management network element sends a response message of the first request to the first service network element to inform the first service network element that the request is successful.

[0165] Optionally, step 402: the information management network element determines whether it is necessary to send a request to the terminal in response to the first request to request the terminal information (which may also be referred to as establishing a request event to the terminal).

[0166] The information management network element may determine, based on the sharing policy, whether it is necessary to send a request to the terminal to request the terminal information (ie, establish a request event to the terminal) in response to the first request.

[0167] For example, the information management network element determines whether there is already a sharing policy for the terminal information (the terminal information is the terminal information requested by the first request in step 401).

[0168] For another example, the information management network element determines whether it has sent a request to the terminal for the terminal information (the terminal information is the terminal information requested by the first request in step 401) to request the terminal information (also referred to as establishing a request event to the terminal).

[0169] There is no restriction on the order of these two determination actions.

[0170] If no request is sent to the terminal for the information to request the terminal information (regardless of whether there is a sharing policy for the terminal information), a request needs to be sent to the terminal for the terminal information to request the terminal information, for example, executing the process of step 403.

[0171] If there is no sharing policy for the terminal information (regardless of whether a request event has been established for the terminal information), a request needs to be sent to the terminal to request the terminal information, for example, executing step 403 .

[0172] If a sharing policy for the terminal information already exists and a request has been sent to the terminal for that terminal information, it is also possible to determine whether the trigger in the previously sent request is identical to or compatible with the trigger for this request (e.g., trigger 2 or trigger 1). Compatibility between trigger a and trigger b can be understood as follows: condition a corresponding to trigger a is a subset of condition b corresponding to trigger b, or condition b corresponding to trigger b is a subset of condition a corresponding to trigger a, or condition a corresponding to trigger a and condition b corresponding to trigger b have some overlap or are different.

[0173] If the two triggers are not the same or compatible, it is necessary to create a request event to the terminal for the trigger of the current request for the terminal information, for example, executing the process of step 403 .

[0174] If the two triggers are the same or compatible, there is no need to create a request event to the terminal.

[0175] In one optional example, determining whether a sharing policy already exists for the information can involve determining whether any existing sharing policy includes a sharing policy for the terminal information type corresponding to the information. For example, a sharing policy that includes the terminal information type corresponding to the information can be considered the existing sharing policy. Alternatively, an existing sharing policy may not specify the types of terminal information permitted for sharing. In this case, as long as a sharing policy exists, it is considered that a sharing policy already exists for the information.

[0176] In an optional example, determining whether a request event has been established to the terminal for the information may be determining whether a request event has been established to the terminal for the terminal information type corresponding to the information.

[0177] Optionally, before step 402, the information management network element may further determine whether the first service network element is authorized to initiate the first request. If authorized to initiate the first request, step 402 is further executed.

[0178] For example, the first service network element carries security credentials in the first request message, and the information management network element verifies the security credentials. If the verification is successful, it means that the first service network element is authorized to initiate the first request.

[0179] Step 403: The information management network element sends a second request to the terminal. Correspondingly, the terminal receives the second request from the information management network element. The second request is used to request information of the terminal.

[0180] In an optional example, the terminal information requested by the second request is the same as the terminal information requested by the first request, for example, both request the location of the UE.

[0181] In an optional example, the information management network element sends a second request to the terminal, and the terminal receives the second request from the information management network element. The terminal here can be replaced by: an information management client installed on the terminal. For example, when the information management network element is a location management network element, the information management client can be a location management client, for example, Figure 1 The location client installed on the terminal is Loc Client.

[0182] The second request includes but is not limited to one or more of the following:

[0183] Report trigger 2, business identifier 1, terminal identifier, terminal information type, subscription transaction identifier 2.

[0184] Reporting trigger 2 is determined based on reporting trigger 1. Typically, reporting trigger 2 is the same as reporting trigger 1. Reporting trigger 2 indicates condition 2, which triggers terminal information reporting. When the terminal determines that condition 2 in trigger 2 is met, it reports the terminal information to the information management network element. The details of the event filter for trigger 2 (i.e., condition 2, which triggers terminal information reporting) are the same as those for reporting trigger 1, and can be referenced in conjunction with each other. These details are not repeated here.

[0185] Optionally, the protocol specifies the conditions for the terminal to report information. In this way, there is no need to include reporting trigger 2 in the second request, and the terminal can also report information according to the conditions specified in the protocol.

[0186] Optionally, subscription transaction identifier 2 is an optional parameter and may not be included in the second request. Subscription transaction identifier 2 can be understood as the identifier of the request event triggered by the information management network element. The subscription transaction identifier 1 between the first service network element and the information management network element and the subscription transaction identifier 2 between the information management network element and the terminal are usually different, but the possibility of them being the same is not excluded. Optionally, the information management network element associates subscription transaction identifier 1 and / or trigger 1 with subscription transaction identifier 2 and / or trigger 2.

[0187] Optionally, the terminal information type is an optional parameter that indicates the type of information requested in step 403 (including step 401) and may not be included in the second request. For example, if the information management network element is a specific type of information management network element, such as a location management network element or a heartbeat management network element, then even if the terminal information type is not included in the second request, the terminal knows which type of terminal information the information management network element is requesting.

[0188] Optionally, the terminal identifier may be understood as the identifier of the destination party to be requested.

[0189] Optionally, the service identifier 1 is an optional parameter and may not be included in the second request. The terminal may not need to know which service uses the terminal information.

[0190] In one example, the second request may be a UE information subscription request or a UE information reporting configuration request.

[0191] Optionally, the terminal (or the information management client installed on the terminal) sends a response message of the second request to the information management network element to inform the information management network element and confirm that the request is successful.

[0192] Optionally, for technical details of step 403, reference may be made to the technical details of an existing information management network element requesting terminal information from a terminal.

[0193] Step 404 (similar to step 401): the second service network element sends a third request to the information management network element. Correspondingly, the information management network element receives the third request from the second service network element, where the third request is used to request information of the terminal.

[0194] In an optional example, the terminal information requested in the first request is the same as the terminal information requested in the third request, or can be understood as the same type of terminal information, for example, both request location information or heartbeat information.

[0195] The third request includes but is not limited to one or more of the following:

[0196] The identifier of the second service network element, reporting trigger 3, service identifier 2 (the second service network element supports the service of the service identifier 2), terminal identifier, terminal information type, subscription transaction identifier 3.

[0197] For details of these information, please refer to the introduction in step 401, and just replace "first, second, 1, 2, 3" with the corresponding ones. No further details will be given.

[0198] It can be understood that trigger 3 in the third request has the same function as trigger 1 in the first request, but the event filters (specific parameter values) may be the same, or different, or partially the same and partially different. Alternatively, it can be understood that trigger 3 and trigger 1 may be the same or compatible. Compatibility can be understood as: condition 1 corresponding to trigger 1 is a subset of condition 3 corresponding to trigger 3, or condition 3 corresponding to trigger 3 is a subset of condition 1 corresponding to trigger 1, or condition 1 corresponding to trigger 1 and condition 3 corresponding to trigger 3 have an intersection or are different.

[0199] When trigger 3 is the same as trigger 1, for example, condition 1 corresponding to trigger 1 and condition 3 corresponding to trigger 3 are both: reporting once every C seconds (C is greater than 0, such as 10s, 25s, etc.), or reporting when the terminal's cell changes, or reporting when the terminal's tracking area TA sends a change, or any of the event filters of any trigger introduced above.

[0200] When trigger 3 is compatible with trigger 1, for example, if condition 1 for trigger 1 is: report every A seconds (e.g., 10 seconds), condition 3 for trigger 3 is: report every B seconds (e.g., 30 seconds, 20 seconds, 40 seconds, etc.). A is greater than 0, and B is greater than 0. When B is an integer multiple of A, B is a subset of A; when B is a non-integer multiple of A, B and A both overlap and differ. Similarly, when A is an integer multiple of B, A is a subset of B; when A is a non-integer multiple of B, A and B both overlap and differ.

[0201] When trigger 3 is compatible with trigger 1, for example, if condition 1 for trigger 1 is: report once when the terminal's cell changes, and condition 3 for trigger 3 is: report once when the terminal's tracking area (TA) changes, then the report is also sent. Generally, cell granularity is relatively small, while tracking area granularity is relatively large, with a TA comprising one or more cells. Therefore, trigger 3 is considered compatible with trigger 1.

[0202] In one example, the third request may be a UE information subscription request or a UE information reporting configuration request.

[0203] Optionally, the information management network element sends a response message of the third request to the second service network element to inform the second service network element that the request is successful.

[0204] There is no restriction on the order of step 404 and step 403 , and there is no restriction on the order of step 404 and step 402 .

[0205] Optionally, step 405 (similar to step 402): the information management network element determines whether it is necessary to send a request to the terminal to request terminal information (ie, establish a request event to the terminal) in response to the third request.

[0206] The information management network element may determine, according to the sharing policy, whether it is necessary to send a request to the terminal to request the terminal information (ie, establish a request event to the terminal) in response to the third request.

[0207] For example, the information management network element determines whether there is already a sharing policy for the terminal information (the terminal information is the terminal information requested by the third request in step 404).

[0208] For another example, the information management network element determines whether a request event has been established to the terminal for the terminal information (the terminal information is the terminal information requested by the third request in step 404) (establishing a request event can be understood as sending a request to the terminal to request the information).

[0209] The order of these two determination actions is not limited. Specific details can be found in the description of step 402, and the details will not be repeated here.

[0210] If no request event is established to the terminal for the information (regardless of whether there is a sharing policy for the information), a request event needs to be established to the terminal for the terminal information.

[0211] If there is no sharing policy for the terminal information (it may not be necessary to consider whether a request event has been established to the terminal for the information), it is necessary to establish a request event to the terminal for the terminal information.

[0212] If there is already a sharing policy for the terminal information and a request event has been established for the terminal information, it is also possible to determine whether the trigger of the previously established request event (such as trigger 2 or trigger 1) is the same or compatible with the trigger of this request for the information (such as trigger 3).

[0213] If the two triggers are different or incompatible, a request event needs to be created to the terminal for the trigger that requests the information this time.

[0214] In this example, step 405 can be understood as the information management network element determining whether to reuse the existing second request for terminal information according to trigger 1, trigger 3 and the sharing policy.

[0215] In an optional example, if two triggers (eg, trigger 1 and trigger 3) are identical or compatible, there is no need to establish a request event to the terminal.

[0216] For example, trigger 2 (or trigger 1) is the same as trigger 3. For example, trigger 1 indicates that terminal information (e.g., location information) should be reported every 30 seconds, and trigger 3 indicates that terminal information (e.g., location information) should be reported every 30 seconds. The information management network element can reuse the request event (i.e., the second request) generated by trigger 2 (i.e., subscription transaction identifier 2) in step 403 for the third request. The information management network element does not need to repeatedly establish a request event to the terminal for the third request, that is, it does not need to perform a process similar to step 403 to avoid repeated reporting by the terminal.

[0217] Optionally, the information management network element associates the subscription transaction identifier 3 and / or trigger 3 with the subscription transaction identifier 2 and / or trigger 2.

[0218] If, in step 403, the information management network element associates subscription transaction identifier 1 and / or trigger 1 with subscription transaction identifier 2 and / or trigger 2, this can be understood as the information management network element associating subscription transaction identifier 1 (or trigger 1) and subscription transaction identifier 3 (or trigger 3) with the same subscription transaction identifier 2 (or trigger 2). This scenario is applicable to scenarios where a second request for terminal information that already exists is determined to be reused based on trigger 1, trigger 3, and a sharing policy.

[0219] In an optional example, if two triggers (e.g., trigger 1 and trigger 3) are compatible, the previously established request event can be updated to the terminal (e.g., the request event established in step 403 is updated). When updating the previously established request event, one example is to update the trigger (e.g., trigger 2) in the previously established request event to avoid repeated reporting by the terminal.

[0220] For example, Trigger 1 instructs reporting terminal information (e.g., location information) every 30 seconds, while Trigger 3 instructs reporting terminal information (e.g., location information) every 10 seconds. While the request for terminal information in step 403 (i.e., the request event generated by subscribing to transaction identifier 2) can be reused, Trigger 2 needs to be updated. For example, Trigger 2 is updated to Trigger 4 (i.e., Trigger 4 is used to update Trigger 2). Trigger 4 is determined based on Trigger 3 and Trigger 2 (or Trigger 1). The update process is described in the subsequent step 406.

[0221] Optionally, before step 405 , the information management network element may further determine whether the second service network element is authorized to initiate the second request. If the second service network element is authorized to initiate the second request, step 405 is further executed.

[0222] The authorization determination process of the information management network element for the second service network element in step 405 is the same as the authorization determination process of the information management network element for the first service network element in step 402, and they can be referenced to each other and will not be repeated.

[0223] Optionally, in step 406, the information management network element sends an update request to the terminal (e.g., an information management client installed on the terminal). In response, the terminal (e.g., the information management client installed on the terminal) receives the update request from the information management network element. The update request is used to update the request event established by the second request in step 403, and the update request is used to request information about the terminal. It can be understood that the update is an update request for the second request.

[0224] When the information management network element determines that the request event established in step 403 needs to be updated in response to the third request from the second service network element, it may send an update request to the terminal. For example, if the information management network element determines that trigger 2 or trigger 1 is compatible with trigger 3, it may update the request event established in step 403 based on trigger 2.

[0225] In one example, the update request includes trigger 4. Trigger 4 is used to represent the updated trigger (i.e., condition 4 for reporting the updated trigger information). Trigger 4 is determined based on trigger 3 and trigger 1, or trigger 4 is determined based on trigger 3 and trigger 2.

[0226] For example, condition 4 corresponding to trigger 4 is the intersection of condition 3 corresponding to trigger 3 and condition 2 corresponding to trigger 2. For example, condition 4 corresponding to trigger 4 is the union of condition 3 corresponding to trigger 3 and condition 2 corresponding to trigger 2. For example, trigger 4 is the same as trigger 1 (or trigger 2). For example, trigger 4 is the same as trigger 3.

[0227] For example, Condition 2 for Trigger 2 is: Report every 10 seconds, Condition 3 for Trigger 3 is: Report every 5 seconds, and Condition 4 for Trigger 4 is: Report every 5 seconds. In this case, Condition 4 for Trigger 4 is the intersection of Condition 3 for Trigger 3 and Condition 2 for Trigger 2. Alternatively, Trigger 4 is the same as Trigger 3.

[0228] For example, Condition 1 for Trigger 2 is: Report every 10 seconds, Condition 3 for Trigger 3 is: Report every 15 seconds, and Condition 4 for Trigger 4 is: Report every {10 seconds and 15 seconds}. In this case, Condition 4 for Trigger 4 is the union of Condition 3 for Trigger 3 and Condition 2 for Trigger 2.

[0229] Optionally, the terminal (eg, an information management client installed on the terminal) stores and updates the received trigger 4 .

[0230] Furthermore, trigger 1 (or trigger 2) and trigger 3 are both reported once at a preset time interval, for example, once every 10 seconds, for example, once every 30 seconds. If the receiving time of trigger 1 and trigger 3 is different, for example, trigger 1 is received at 19:00:00 and trigger 3 is received at 19:00:05:

[0231] When the information management network element obtains trigger 4 based on trigger 1 (or trigger 2) and trigger 3, it can also adjust the first effective time of trigger 4 so that it coincides with the reporting time of either trigger 1 or trigger 3. For example, the effective time of trigger 4 can be adjusted to 19:00:10. This can reduce the number of reports and reduce the consumption of terminal resources and air interface resources.

[0232] Optionally, the update request may further include but is not limited to one or more of the following: terminal information type, trigger 2, subscription transaction identifier 2, subscription transaction identifier 4, service identifier 2, and terminal identifier.

[0233] Optionally, the terminal information type indicates the type of information requested in step 404 .

[0234] Optionally, subscription transaction identifier 4 is an optional parameter and may not be included in the update request. Subscription transaction identifier 4 can be understood as the identifier of this request event (also called update event) triggered by the information management network element. Subscription transaction identifier 3 and subscription transaction identifier 4 are usually different, but the same situation is not excluded. Subscription transaction identifier 4 and subscription transaction identifier 2 are usually different, but the same situation is not excluded. Optionally, the information management network element associates subscription transaction identifier 4 and / or trigger 4 with subscription transaction identifier 3 and / or trigger 3. Optionally, the information management network element associates subscription transaction identifier 4 and / or trigger 4 with subscription transaction identifier 2 and / or trigger 2.

[0235] Optionally, Subscription Transaction ID 2 and Trigger 2 are optional parameters and may not be included in the update request. Subscription Transaction ID 2 and / or Trigger 2 are used to inform the terminal which trigger to update. For example, to update Trigger 2, or to update the trigger corresponding to Subscription Transaction ID 2 (i.e., Trigger 2).

[0236] Optionally, service identifier 2 is an optional parameter and may not be included in the update request. The terminal may not need to be aware of which service uses the terminal information.

[0237] In one example, the update request may be a UE information subscription update request or a UE information reporting configuration update request.

[0238] Optionally, the terminal sends a response to the update request to the information management network element to inform the information management network element that the update is successful.

[0239] Step 407: The terminal determines whether the information reporting conditions are met. If the information reporting conditions are met, step 408 is executed: reporting the terminal information to the information management network element.

[0240] In one example, the terminal may determine whether the condition of trigger 2 is met.

[0241] In another example, if step 406 is executed, the terminal may determine whether the condition of trigger 4 is met.

[0242] For example, one or more of the information management client installed on the terminal, the first service client corresponding to the first service network element, and the second service client corresponding to the second service network element determine whether the trigger conditions are met. Which client determines the conditions depends on the conditions in the trigger. Some conditions can be directly determined by the information management client to determine whether the trigger conditions are met (for example, time expiration, UE location movement), and some service-related conditions (for example, entering an emergency state) are determined by the service client to determine whether the trigger conditions are met.

[0243] Step 408: The terminal (eg, the information management client installed on the terminal) sends the terminal information to the information management network element. Correspondingly, the information management network element receives the terminal information from the terminal (eg, the information management client installed on the terminal).

[0244] In an optional example, trigger 2 is not updated, the terminal detects trigger 2, and executes step 408 when it is determined that trigger 2 is satisfied.

[0245] When sending the terminal information to the information management network element, the terminal (eg, the information management client installed on the terminal) may also send the subscription transaction identifier 2 and / or the identifier, number, or name of the trigger 2.

[0246] It can be understood that the terminal sends a response to the second request to the information management network element. The response to the second request includes information about the terminal. Optionally, the response to the second request also includes but is not limited to one or more of the following:

[0247] Subscription transaction ID 2, trigger 2 ID, number, or name.

[0248] The subscription transaction identifier 2 is an optional parameter, and is used to indicate that the identifier of the request event that triggers the information reporting is the subscription transaction identifier 2.

[0249] The identifier, number or name of trigger 2 is an optional parameter. Trigger 2 is used to indicate that the trigger that triggers the information reporting is the trigger with the identifier (number or name) 2.

[0250] In an optional example, trigger 4 is used to update trigger 2. The terminal detects trigger 4 and, when it determines that trigger 4 is satisfied, executes step 408. When the terminal (e.g., an information management client installed on the terminal) sends the terminal information to the information management network element, it may also send one or more of subscription transaction identifier 2, trigger 2, subscription transaction identifier 4, and trigger 4.

[0251] It can be understood that the terminal sends a response to the update request to the information management network element. The response to the update request includes the terminal information. Optionally, the response to the update request also includes but is not limited to one or more of the following:

[0252] Subscription transaction ID 2, the ID or number or name of trigger 2, subscription transaction ID 4, the ID or number or name of trigger 4.

[0253] Subscription transaction ID 2 and trigger 2 are described above and will not be repeated here.

[0254] The subscription transaction identifier 4 is an optional parameter, and is used to indicate that the identifier of the request event that triggers the information reporting is the subscription transaction identifier 4.

[0255] The identifier, number or name of trigger 4 is an optional parameter. Trigger 4 is used to indicate that the trigger that triggers the information reporting is the trigger with the identifier (number or name) 4.

[0256] Step 409: The information management network element determines to which service network element the terminal information is to be sent.

[0257] For example, the information management network element decides to send the terminal information received in step 408 to the first service network element and / or the second service network element based on one or more of the sharing policy, the subscription transaction identifier from the terminal, the trigger information from the terminal, the associated information of the subscription transaction identifier, the associated information of the trigger information, etc.

[0258] In one example, the information management network element receives terminal information (without the subscription transaction identifier and trigger identifier, number or name), determines that there is a sharing policy for the terminal information, and then can send the terminal information to the first service network element and the second service network element.

[0259] In another example, the information management network element receives not only terminal information from the terminal but also a subscription transaction identifier from the terminal. The terminal information can be sent to the requester of the request event corresponding to the subscription transaction identifier; or, the terminal information can be sent to the requester of the request event corresponding to other subscription transaction identifiers that are associated with the subscription transaction identifier sent by the terminal.

[0260] For example, if the information management network element receives terminal information and subscription transaction identifier 2, and if subscription transaction identifier 2 is associated with subscription transaction identifier 1, the terminal information is sent to the requester of the request event corresponding to subscription transaction identifier 1, that is, the first service network element. If subscription transaction identifier 2 is associated with subscription transaction identifier 3, the terminal information is sent to the requester of the request event corresponding to subscription transaction identifier 3, that is, the second service network element.

[0261] For another example, the information management network element receives terminal information, subscription transaction identifier 2, and subscription transaction identifier 4. Subscription transaction identifier 2 is associated with subscription transaction identifier 1, and subscription transaction identifier 4 is associated with subscription transaction identifier 3. The terminal information can be sent to the requester of the request event corresponding to subscription transaction identifier 1, that is, the first service network element; and to the requester of the request event corresponding to subscription transaction identifier 3, that is, the second service network element.

[0262] For another example, the information management network element receives terminal information and subscription transaction identifier 4, subscription transaction identifier 4 is associated with subscription transaction identifier 3, and subscription transaction identifier 3 and subscription transaction identifier 1 are both associated with subscription transaction identifier 2. Then it is considered that subscription transaction identifier 4 and subscription transaction identifier 1 also have an association relationship, and the terminal information can be sent to the requester of the request event corresponding to the subscription transaction identifier 1, that is, the first business network element, and to the requester of the request event corresponding to the subscription transaction identifier 3, that is, the second business network element.

[0263] The subscription transaction identifiers in the above examples can be replaced with the identifiers, numbers, or names of the corresponding triggers. For example, subscription transaction identifier 1 can be replaced with the identifier, number, or name of trigger 1, subscription transaction identifier 2 can be replaced with the identifier, number, or name of trigger 2, subscription transaction identifier 3 can be replaced with the identifier, number, or name of trigger 3, and subscription transaction identifier 4 can be replaced with the identifier, number, or name of trigger 4. Alternatively, the identifiers, numbers, or names of the subscription transaction, trigger, or both can be included.

[0264] Optionally, step 410a: the information management network element sends the terminal information to the first service network element. Optionally, the information management network element may also send the subscription transaction identifier 1 and / or the identifier, number, or name of trigger 1 to the first service network element.

[0265] Optionally, step 410b: the information management network element sends the terminal information to the second service network element. Optionally, the information management network element may also send the subscription transaction identifier 3 and / or the identifier, number or name of trigger 3 to the second service network element.

[0266] The information management network element sends terminal information to the corresponding service network element based on the subscription relationship.

[0267] The order of step 410a and step 410b is not limited. Step 410a and step 410b can send the information in different messages or in a single message, for example, the information management network element sends the information to the first service network element and the second service network element by broadcasting or multicasting.

[0268] The information management network element aggregates / integrates requests sent by multiple service network elements. Therefore, when multiple service network elements (the first service network element and the second service network element) request terminal information from the information management network element, the information management network element only establishes a request event for the terminal once (i.e., sends a second request to the terminal) or updates an already established request event. After obtaining the terminal information from the terminal, the information management network element determines whether the terminal information should be sent to one, multiple, or all service network elements that requested the terminal information based on information such as the sharing policy. Terminal information is reported once and can be shared among multiple services. This can prevent the terminal from repeatedly reporting terminal information, reduce the number of signaling interactions between the service network element and the terminal, and reduce the waste of terminal resources and air interface signaling resources.

[0269] Combined with the above Figure 4 Example 1 is described below. Example 2 differs from Example 1 in that the information management network element obtains the sharing policy in a different way. The sharing policy is described above and will not be repeated here.

[0270] In Example 1, the information management NE obtains the shared policy from the configuration NE. In Example 2, the information management NE obtains the shared policy from the service NE, for example, the service NE sends the shared policy to the information management NE. Compared to Example 1, Example 2 does not require the participation of the configuration NE.

[0271] Optionally, the service network element may obtain the shared policy from the configuration network element or from the terminal. Optionally, the service network element obtains the shared policy from the configuration network element through a user profile or a service profile.

[0272] In addition, it is understandable that the service network element has obtained authorization to use the terminal information from the terminal (or the information management client on the terminal).

[0273] In an optional example, in step 401 above, the first request sent by the first service network element to the information management network element may further include a sharing policy. In this case, this may be understood as determining whether the terminal information requested by the first service network element is permitted to be used by other service network elements (i.e., whether the first service network element permits sharing of terminal information with other service network elements). Optionally, the sharing policy is valid from the time the sharing policy is configured until the end of the request event.

[0274] The sub-request event ends when: the terminal information is received for the sub-request event, for example, after executing step 408: the information management network element receives the terminal information. Alternatively, the sub-request event ends when: after receiving the terminal information, it is determined whether the terminal information is sent to the requester of the sub-request event, for example, after executing step 409: it is determined to which service network element to send it. Alternatively, the sub-request event ends when: the terminal information is sent to the requester of the sub-request event, for example, after executing step 410a: the terminal information is sent to the first service network element. Alternatively, the sub-request event ends when: the requester actively sends a message to cancel receiving the terminal information, or cancels the shared device, or the sub-request event ends when: the validity period (timer) of the request expires.

[0275] When the first service network element includes a sharing policy in the first request, the sharing policy can configure whether the terminal information requested by the first request is allowed to be used by other service network elements. The sharing policy can configure or not configure whether the terminal information not requested by the first request is allowed to be used by other service network elements. If the sharing policy only configures whether the terminal information requested by the first request is allowed to be used by other service network elements, the sharing policy can be understood as a sharing policy at the granularity of a single piece of information.

[0276] In addition, if the first service network element no longer wishes to share the terminal information with other service network elements when requesting terminal information next time, it does not need to carry the sharing policy in the next request. This situation can be understood as sharing the terminal information at the granularity of a single request.

[0277] In an optional example, in the above-mentioned step 404, the third request sent by the second service network element to the information management network element may further include: a sharing policy. In this case, it can be understood as whether the terminal information requested by the second service network element is allowed to be used by other service network elements. Optionally, the validity period of the sharing policy is: the time when the sharing policy is configured this time, until the end of the request event. The end of the request event is similar to the above description and will not be repeated. If the sharing policy only configures whether the terminal information requested by the third request is allowed to be used by other service network elements, the sharing policy can be understood as a sharing policy with a single information granularity. In addition, if the second service network element no longer wishes to share the terminal information with other service network elements when requesting terminal information next time, it is not necessary to carry a sharing policy in the next request. In this case, it can be understood that the sharing of terminal information is at the granularity of a single request.

[0278] In an optional example, the first service network element may send the sharing policy to the information management network element in a separate message from the first request. For example, in step 400 described above, the first service network element sends the sharing policy to the information management network element. Optionally, the first service network element may be considered a service network element management device among multiple service network elements. Optionally, the sharing policy is valid from the time the first service network element configures the sharing policy for the information management network element to the time a new sharing policy is next configured.

[0279] In an optional example, the second service network element may send the sharing policy to the information management network element in another independent message different from the third request. For example, in the above step 400, the second service network element may also send the sharing policy to the information management network element.

[0280] Optionally, the second service network element can be regarded as a service network element management device among the multiple service network elements. Optionally, the validity period of the sharing policy is: the time when the second service network element configures the sharing policy for the information management network element to the time when a new sharing policy is configured next time.

[0281] When the first service network element or the second service network element sends a sharing policy to the information management network element in step 400, the sharing policy typically includes sharing policies for multiple types of information. That is, the sharing policy configures sharing for multiple types of terminal information. Of course, it is not ruled out that the sharing policy only configures a single type of terminal information.

[0282] Optionally, the information management network element may aggregate triggers and sharing policies from different service network elements (eg, the first service network element and the second service network element), which has been introduced above and will not be repeated here.

[0283] The rest of the technical details of Example 2 can be found in Figure 4Example 1 will not be repeated.

[0284] Combined with the above Figure 4 Example 1 is described below. Example 3 is introduced below. The difference between Example 3 and Example 1 is that the information management network element obtains the sharing policy in a different way. The sharing policy is described above and will not be repeated here.

[0285] In Example 1, the information management network element obtains the sharing policy from the configuration network element. In Example 3, the information management network element obtains the sharing policy from the terminal. For example, in the above step 400, the terminal sends the sharing policy to the information management network element, and accordingly, the information management network element receives the sharing policy from the terminal. For example, the information management network element obtains the sharing policy from the information management client installed on the terminal (for example Figure 1 The location client in the .

[0286] Optionally, the information management client receives information from a business client (eg Figure 1 PTT client in Figure 1 The service client here may include: a first service client (eg, VAL client #1) corresponding to the first service network element, and a second service client (eg, VAL client #2) corresponding to the second service network element.

[0287] Optionally, a service client (e.g., VAL client #1 or VAL client #2) can obtain the sharing policy from a configuration network element. For example, a terminal (e.g., a service client installed on the terminal) obtains the sharing policy from the configuration network element via a user profile or a service profile. Optionally, the service client can obtain the sharing policy from the user, for example, through a human-computer interaction interface. Optionally, an application service provider (ASP) pre-sets the sharing policy in the service client.

[0288] Optionally, the sharing policies configured in the first service client and the second service client are the same.

[0289] In one example, the sharing policy in the service client is read by the information management client through the internal implementation of the UE. That is, the sharing policy in the service client can be sent to the information management client, which then sends it to the information management network element.

[0290] The rest of the technical details of Example 3 can be found in Figure 4 Example 1 will not be repeated.

[0291] In Example 3, the participation of the configuration network element is not required, and the sharing of terminal information is controlled by the terminal (eg, the service client on the terminal) based on a program, allowing the terminal user to control it through a human-computer interaction interface.

[0292] Example 2: The information management network element requests the terminal information from multiple service network elements respectively. The terminal can integrate multiple requests from the information management network element (also called aggregation processing) to avoid reporting the same information of the terminal multiple times (repeatedly).

[0293] like Figure 5 As shown, a schematic diagram of the process of terminal information sharing is provided, including but not limited to the following steps:

[0294] Step 51: The first service network element sends a first request to the information management network element. Correspondingly, the information management network element receives the first request from the first service network element, where the first request is used to request information of the terminal.

[0295] Step 52: The information management network element sends a second request to the terminal. Correspondingly, the terminal receives the second request sent by the information management network element. The second request message is used to request the information of the terminal.

[0296] For example, the information management network element sends the second request to the terminal based on the first request.

[0297] Step 53: The second service network element sends a third request to the information management network element. Correspondingly, the information management network element receives the third request from the second service network element, where the third request is used to request the information of the terminal.

[0298] For example, the terminal information requested by the second service network element and the first service network element is the same, for example, both request the location information of the terminal, or both request the heartbeat information of the terminal.

[0299] Optionally, the first service network element and the second service network element have different services. For example, the first service network element is a network element for the PTT service, and the second service network element is a network element for the video service.

[0300] It is understandable that the order of step 53 and step 52 is not limited.

[0301] Step 54: The information management network element sends a fourth request to the terminal. Correspondingly, the terminal receives the fourth request sent by the information management network element. The fourth request message is used to request the information of the terminal.

[0302] For example, the information management network element sends the fourth request to the terminal based on the third request.

[0303] It is understandable that the order of step 54 and step 52 is not limited.

[0304] Step 55: The terminal sends the information and the first indication information to the information management network element. Correspondingly, the information management network element receives the information and the first indication information from the terminal.

[0305] For example, the terminal may report the terminal information based on the second request in step 52 and the fourth request in step 54 .

[0306] The first indication information is used to describe that: the information is allowed to be shared, or the information is allowed to be shared by the first service network element and the second service network element.

[0307] Step 56a: The information management network element sends the information to the first service network element.

[0308] Step 56b: The information management network element sends the information to the second service network element.

[0309] The order of step 56a and step 56b is not limited. Step 56a and step 56b can send the information in different messages, or they can be sent in a single message, for example, the information management network element uses broadcast or multicast to send the information to the first service network element and the second service network element.

[0310] The information management network element sends two requests to the terminal (i.e., the second request and the fourth request). The terminal aggregates (also called aggregates) these two requests into a single request event. The terminal reports terminal information only for this aggregated request event and also reports the sharing policy, so that the information management network element can decide to send this information to the first service network element and / or the second service network element based on the sharing policy. By reporting terminal information only for a single request event, the terminal avoids repeated reporting of terminal information and reduces the waste of terminal resources and air interface signaling resources.

[0311] Next, Figure 6 As shown in the figure, the process of terminal information sharing is further described in detail. Figure 6 In Example 4, it is not necessary to perform the process of determining whether it is necessary to establish a request event to the terminal for the request from the service network element (with Figure 4 (similar process to steps 402 and 405 in FIG. 1 ).

[0312] Step 600: The terminal obtains a sharing policy.

[0313] For example, the information management client installed on the terminal (corresponding to the information management network element) obtains the sharing policy from the first service client (corresponding to the first service network element (for example, VAL client #1)), and / or obtains the sharing policy from the second service client (corresponding to the second service network element (for example, VAL client #2)).

[0314] Optionally, a service client (e.g., VAL client #1 or VAL client #2) can obtain the sharing policy from a configuration network element. For example, a terminal (e.g., a service client installed on the terminal) obtains the sharing policy from the configuration network element via a user profile or a service profile. Optionally, the service client can obtain the sharing policy from the user, for example, through a human-computer interaction interface. Optionally, an application service provider (ASP) pre-sets the sharing policy in the service client.

[0315] Optionally, the sharing policies configured in the first service client and the second service client are the same.

[0316] In one example, the sharing policy in the service client is implemented internally by the UE and read by the information management client, that is, the sharing policy in the service client can be sent to the information management client.

[0317] In one example, the introduction of the sharing strategy can be found in the above description (eg, step 400 ), which will not be repeated here.

[0318] In another example, in the sharing policy, information representing the service is an optional parameter. The remaining technical details can be found in the description above and will not be repeated here. The sharing policy does not specify which services are allowed to share terminal information; for example, all services may share terminal information. For example, the sharing policy is used to describe the terminal information that is allowed to be shared, that is, which terminal information is allowed to be shared. For example, this includes, but is not limited to, the terminal information requested in the second and fourth requests described below, and may also include other terminal information.

[0319] Step 601 (same as step 401): The first service network element sends a first request to the information management network element. Correspondingly, the information management network element receives the first request from the first service network element, where the first request is used to request terminal information.

[0320] Please refer to the description in step 401 and will not repeat it here.

[0321] Step 603 (same as step 403): the information management network element sends a second request to the terminal. Correspondingly, the terminal receives the second request from the information management network element, where the second request is used to request information of the terminal.

[0322] Please refer to the description in step 403 and will not repeat it here.

[0323] It should be noted that, optionally, the second request may include service identifier 1 (the first service network element supports the service with service identifier 1), and the terminal may sense which service uses the terminal information.

[0324] Step 604 (same as step 404): the second service network element sends a third request to the information management network element. Correspondingly, the information management network element receives the third request from the second service network element, where the third request is used to request information of the terminal.

[0325] Please refer to the description in step 404 and will not repeat it here.

[0326] In an optional example, the terminal information requested in the first request is the same as the terminal information requested in the third request, or can be understood as the same type of terminal information, for example, both request location information or heartbeat information.

[0327] Step 606 (similar to step 603 and step 403): the information management network element sends a fourth request to the terminal. Correspondingly, the terminal receives the fourth request from the information management network element, where the fourth request is used to request information of the terminal.

[0328] In step 606, the information in step 603 and step 403 may be replaced by the following, including but not limited to one or more of the following:

[0329] The second request is replaced by the fourth request; the first request is replaced by the third request, trigger 1 is replaced by trigger 3, trigger 2 is replaced by trigger 5, subscription transaction identifier 1 is replaced by subscription transaction identifier 3, subscription transaction identifier 2 is replaced by subscription transaction identifier 5, and business identifier 1 is replaced by business identifier 2.

[0330] It should be noted that, optionally, the fourth request may include service identifier 2 (the second service network element supports the service with service identifier 2), and the terminal may sense which service uses the terminal information.

[0331] In an optional example, the terminal information requested in the second request is the same as the terminal information requested in the fourth request, or can be understood as the same type of terminal information, for example, both request location information or heartbeat information.

[0332] Step 607: The terminal (eg, the information management client installed on the terminal) determines whether it is necessary to report the terminal information to the information management network element respectively for the second request and the fourth request.

[0333] For example, the terminal (e.g., an information management client installed on the terminal) can determine, based on the sharing policy, whether it is necessary to report the terminal information separately for the second request and the fourth request. If the sharing policy allows the terminal information requested by the second request and the fourth request to be shared, then it is not necessary to report the terminal information separately for the second request and the fourth request. If there is no sharing policy for storing the information, or the sharing policy for the information indicates that sharing is not allowed, the terminal needs to report the terminal information separately for the second request and the fourth request.

[0334] In one example, determining whether terminal information needs to be reported separately for the second request and the fourth request can also be understood as determining whether trigger 2 and trigger 5 need to be integrated to obtain a new trigger 6. If it is determined that terminal information needs to be reported separately, there is no need to integrate trigger 2 and trigger 5. If it is determined that terminal information does not need to be reported separately, trigger 2 and trigger 5 can be integrated, and the terminal information can be subsequently reported based on trigger 6.

[0335] In the present application, if the reporting conditions for the terminal information requested by the second request and the fourth request are the same or compatible, and the terminal information is allowed to be shared between the first service network element and the second service network element, in order to avoid duplicate reporting, the terminal does not need to report the terminal information separately for the second request and the fourth request. The terminal can report the terminal information for either the second request or the fourth request, and the reported terminal information can be used by the requester of the first request and the requester of the third request. Alternatively, the terminal can integrate the second request and the fourth request, and report the terminal information for the event after the integration process, and the reported terminal information can be used by the requester of the first request and the requester of the third request.

[0336] In one example, the sharing policy does not include information characterizing a service. The sharing policy does not define which services are allowed to share the terminal, for example, it may be information that all services can share the terminal.

[0337] The second request in step 603 does not include service identifier 1, and the fourth request in step 606 does not include service identifier 2, that is, the terminal does not perceive which services use the terminal information.

[0338] When the terminal determines whether to report the terminal information to the information management network element for the second request and the fourth request respectively:

[0339] For example, if the protocol specifies the conditions for a terminal to report information, there is no need to include trigger 2 in the second request or trigger 5 in the fourth request. The terminal can still report information according to the conditions specified in the protocol. The terminal can determine whether there is a sharing policy for the terminal information. If so, it determines that the terminal information requested in the second and fourth requests can be shared between any services. In this case, there is no need to report the terminal information to the information management network element for each of the second and fourth requests. This means that the terminal information reported for either the request event of the second request or the fourth request can be used by the requester of the first request and the requester of the third request.

[0340] For another example, the second request includes trigger 2, and the fourth request includes trigger 5. When the terminal determines that there is a sharing policy for the terminal information and that trigger 2 and trigger 5 are the same or compatible, there is no need to report the terminal information to the information management network element for the second request and the fourth request respectively. It can be understood that the terminal information is reported for the request event of the second request or for one of the fourth request events (it can be understood that the terminal reports the terminal information when it determines that the conditions of trigger 2 or trigger 5 are met), and the reported terminal information can be used by the requester of the first request and the requester of the third request.

[0341] For example, the second request includes trigger 2, and the fourth request includes trigger 5. When the terminal determines that there is a sharing policy for the terminal information and that trigger 2 and trigger 5 are compatible, the terminal determines a new trigger 6 based on trigger 2 and trigger 5, and reports the terminal information to the information management network element for the new trigger 6. It can be understood that the request event of the second request (trigger 2) and the fourth request event (trigger 5) are integrated to obtain a new request event (trigger 6), and the terminal reports the terminal information for the new request event (trigger 6) (it can be understood that the terminal reports the terminal information when it determines that the conditions of trigger 6 are met). The reported terminal information can be used by the requester of the first request and the requester of the third request.

[0342] In another example, the sharing policy configured in step 600 is the same as that configured in step 400. The sharing policy includes information representing the service. The sharing policy defines which services are allowed to share terminal information. For example, a service with service ID 1 and a service with service ID 2 may be allowed to share terminal information.

[0343] The second request in step 603 includes service identifier 1, and the fourth request in step 605 includes service identifier 2.

[0344] When the terminal determines whether to report the terminal information to the information management network element for the second request and the fourth request respectively:

[0345] For example, the conditions for a terminal to report information, as specified in the protocol, do not require that trigger 2 be included in the second request, nor that trigger 5 be included in the fourth request. The terminal can also report information according to the conditions specified in the protocol. The terminal can determine, based on the terminal information sharing policy, whether the terminal information requested in the second and fourth requests is allowed to be shared between the service with service identifier 1 and the service with service identifier 2. If so, there is no need to report the terminal information to the information management network element for each of the second and fourth requests. It can be understood that the terminal information reported for either the request event of the second request or the fourth request event can be used by the requester of the first request and the requester of the third request.

[0346] For another example, the second request includes trigger 2, and the fourth request includes trigger 5. Based on the sharing policy, trigger 2, and trigger 5, the terminal can determine whether the terminal information requested in the second and fourth requests can be shared between the service with service ID 1 and the service with service ID 2, and whether trigger 2 and trigger 5 are identical or compatible. The order of these two determination processes is not restricted.

[0347] If both determinations are yes, there is no need to report the terminal information to the information management network element for the second request and the fourth request respectively. It can be understood that the terminal information is reported for either the request event of the second request or the fourth request event (it can be understood that the terminal determines whether the conditions of trigger 2 or trigger 5 are met, and when it is determined that the conditions of trigger 2 or trigger 5 are met, the terminal information is reported). The reported terminal information can be used by the requester of the first request and the requester of the third request.

[0348] For example, the second request includes trigger 2, and the fourth request includes trigger 5. Based on the sharing policy, trigger 2, and trigger 5, the terminal can determine whether the terminal information requested in the second and fourth requests can be shared between the service with service ID 1 and the service with service ID 2, and whether trigger 2 and trigger 5 are compatible. The order of these two determination processes is not restricted.

[0349] If both determination processes are yes, the terminal determines a new trigger 6 based on trigger 2 and trigger 5, and reports the terminal information to the information management network element for the new trigger 6. It can be understood that the request event (trigger 2) of the second request and the fourth request event (trigger 5) are integrated to obtain a new request event (trigger 6), and the terminal reports the terminal information for the new request event (trigger 6) (it can be understood that the terminal determines whether the conditions of trigger 6 are met, and when it is determined that the conditions of trigger 6 are met, the terminal information is reported). The reported terminal information can be used by the requester of the first request and the requester of the third request.

[0350] Trigger 6 is determined based on trigger 2 and trigger 5, which is similar to trigger 4 described above being determined based on trigger 1 and trigger 3. Trigger 6 can be compared to trigger 4 described above, trigger 2 can be compared to trigger 1 described above, and trigger 5 can be compared to trigger 3 described above.

[0351] For example, condition 6 corresponding to trigger 6 is the intersection of condition 2 corresponding to trigger 2 and condition 5 corresponding to trigger 5. For example, condition 6 corresponding to trigger 6 is the union of condition 2 corresponding to trigger 2 and condition 5 corresponding to trigger 5. For example, trigger 6 is the same as trigger 2. For example, trigger 6 is the same as trigger 5.

[0352] Step 608: The terminal determines whether the information reporting conditions are met. If the information reporting conditions are met, step 608 is executed: reporting the terminal information to the information management network element.

[0353] For example, the terminal may determine whether the condition of trigger 2 is met, or determine whether the condition of trigger 5 is met, or determine whether the condition of trigger 6 is met.

[0354] For example, one or more of the information management client installed on the terminal, the first service client corresponding to the first service network element, and the second service client corresponding to the second service network element determine whether the trigger conditions are met. Which client determines the conditions depends on the conditions in the trigger. Some conditions are directly determined by the information management client to determine whether the trigger conditions are met (for example, time expiration, UE location movement), and some service-related conditions (for example, entering an emergency state) are determined by the service client to determine whether the trigger conditions are met.

[0355] Step 609: The terminal (eg, the information management client installed on the terminal) sends the information of the terminal to the information management network element.

[0356] Optionally, the terminal sends a first indication message to the information management network element, where the first indication message is used to indicate that the information of the terminal is allowed to be shared; or, the first indication message is used to indicate that the information of the terminal is allowed to be shared between the first service (or the first service network element) and the second service (or the second service network element).

[0357] The terminal may determine the first indication information based on the sharing policy. The first indication information is determined based on the sharing policy. For example, when the sharing policy indicates that the information is allowed to be shared, the first indication information may be sent to the information management network element. If no sharing policy is stored for the information, or the sharing policy for the information indicates that sharing is not allowed, the terminal may not send the first indication information to the information management network element.

[0358] In an example, the first indication information includes: an indication for indicating that the terminal information can be sent to a first service network element, and an indication for indicating that the terminal information can be sent to a second service network element.

[0359] Optionally, the first indication information includes a sharing indication, which may indicate whether the terminal information can be shared. The sharing indication may occupy 1 bit, for example, when the 1 bit is 0, it indicates that sharing is not allowed, and when the 1 bit is 1, it indicates that sharing is allowed.

[0360] Optionally, the first indication information includes: subscription transaction identifier 2 and / or identifier, number or name of trigger 2.

[0361] Subscription transaction identifier 2 is used to indicate that the identifier of the request event that triggers the information reporting is subscription transaction identifier 2. Trigger 2 is used to indicate that the trigger that triggers the information reporting is the trigger with identifier (number or name) 2.

[0362] The subscription transaction identifier 2 and / or the identifier, number, or name of the trigger 2 may also be an example of an indication that the terminal information can be sent to the first service network element.

[0363] Optionally, the first indication information includes: subscription transaction identifier 5 and / or identifier, number or name of trigger 5.

[0364] Subscription transaction identifier 5 is used to indicate that the identifier of the request event that triggers the information reporting is subscription transaction identifier 5. Trigger 5 is used to indicate that the trigger that triggers the information reporting is the trigger with identifier (number or name) 5.

[0365] The subscription transaction identifier 5 and / or the identifier, number or name of the trigger 5 may also be an example of an indication that the terminal information can be sent to the second service network element.

[0366] Optionally, the sharing instruction may further include: a sharing strategy. The sharing strategy is similar to the sharing strategy introduced in step 400 and will not be repeated. Figure 4 .

[0367] Step 610a: The information management network element sends the terminal information to the first service network element. Optionally, the information management network element may also send the subscription transaction identifier 1 and / or the identifier, number, or name of trigger 1 to the first service network element.

[0368] Optionally, step 610b: the information management network element sends the terminal information to the second service network element. Optionally, the information management network element may also send the subscription transaction identifier 3 and / or the identifier, number or name of trigger 3 to the second service network element.

[0369] The information management network element sends terminal information to the corresponding service network element based on the subscription relationship.

[0370] The order of step 610a and step 610b is not limited. Step 610a and step 610b can send the information in different messages or in a single message, for example, the information management network element sends the information to the first service network element and the second service network element by broadcasting or multicasting.

[0371] In this Figure 6 In the example, there is no need to configure the participation of network elements. The terminal decides whether its information can be shared and with which services its information can be shared. Therefore, terminal information sharing is based on the granularity of a single UE. In addition, terminal information sharing is based on the granularity of a single request. Each time the terminal reports information, it can indicate whether it can be shared, or between which services it can be shared. If the terminal does not want to share information, the terminal can not carry the first indication information when feeding back the terminal information to the information management network element (for example, step 609), so that information sharing can be achieved. The sharing of UE information is controlled based on the granularity of a single message. On the basis of sharing and resource consumption, it also protects the shared information to a certain extent, and can prevent it from being maliciously distributed and used.

[0372] The preceding text describes the method of the embodiment of the present application. The following text describes the device of the embodiment of the present application. The method and device are based on the same technical concept. Since the principles of the method and device to solve the problem are similar, the implementation of the device and method can refer to each other, and the repeated parts will not be repeated.

[0373] In the embodiments of the present application, the functional modules of the device can be divided according to the above method examples. For example, each function can be divided into various functional modules, or two or more functions can be integrated into one module. These modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical functional division. Other division methods may be used in specific implementations.

[0374] Based on the same technical concept as the above method, see Figure 7 , provides a schematic structural diagram of a terminal information sharing apparatus 700 (a terminal information sharing apparatus may also be considered a communication apparatus). The apparatus 700 may include a processing module 710 and, optionally, a receiving module 720a, a sending module 720b, and a storage module 730. The processing module 710 may be connected to the storage module 730, the receiving module 720a, and the sending module 720b, respectively. The storage module 730 may also be connected to the receiving module 720a and the sending module 720b.

[0375] In an example, the above-mentioned receiving module 720a and sending module 720b can also be integrated together and defined as a transceiver module.

[0376] In one example, the device 700 may be an information management network element, or a chip or functional unit used in an information management network element. The device 700 has any function of the information management network element in the above method, for example, the device 700 can execute the above Figure 2 、 Figure 3 、 Figure 4 、 Figure 5 、 Figure 6 The various steps in the method are performed by the information management network element.

[0377] The receiving module 720a can execute the receiving action performed by the information management network element in the above method embodiment.

[0378] The sending module 720b can execute the sending action performed by the information management network element in the above method embodiment.

[0379] The processing module 710 may execute other actions except the sending action and the receiving action among the actions executed by the information management network element in the above method embodiment.

[0380] In one example, the receiving module 720a is configured to receive a first request from a first network element, where the first network element supports a first service, and the first request is used to request information of a terminal;

[0381] A sending module 720b is configured to send a second request to the terminal, where the second request is used to request the information;

[0382] The receiving module 720a is further configured to receive a third request from a second network element, where the second network element supports a second service, and the third request is used to request the information of the terminal;

[0383] The receiving module 720a is further configured to receive the information from the terminal;

[0384] The sending module 720b is further configured to send the information to the first network element and the second network element.

[0385] In an example, the sending module 720b is further used to send an update request of the second request to the terminal, where the update request is used to request the information of the terminal.

[0386] In an example, the receiving module 720a is further configured to obtain a sharing policy, where the sharing policy is used to describe whether the information is allowed to be shared between the first service and the second service;

[0387] The sending module 720b is specifically configured to send the information to the first network element and the second network element according to the sharing policy.

[0388] In one example, the receiving module 720a is specifically used to receive the sharing policy from a first device; the first device includes one or more of the following: a configuration network element, the first network element, the second network element, and the terminal.

[0389] In an example, the processing module 710 is configured to determine that there is no need to send a request to the terminal in response to the third request to request the information of the terminal.

[0390] In one example, the receiving module 720a is configured to receive a first request from a first network element, where the first network element supports a first service, and the first request is used to request information of a terminal;

[0391] A sending module 720b is configured to send a second request to the terminal, where the second request is used to request the information;

[0392] The receiving module 720a is further configured to receive a third request from a second network element, where the second network element supports a second service, and the third request is used to request the information of the terminal;

[0393] The sending module 720b is further configured to send a fourth request to the terminal, where the fourth request is configured to request the information;

[0394] The receiving module 720a is further configured to receive the information and first indication information from the terminal, where the first indication information is configured to indicate that the information is allowed to be shared;

[0395] The sending module 720b is further configured to send the information to the first network element and the second network element.

[0396] In an example, the storage module 730 may store computer-executable instructions for the method executed by the information management network element, so that the processing module 710, the receiving module 720a, and the sending module 720b execute the method executed by the information management network element in the above example.

[0397] For example, the storage module may include one or more memories, which may be devices in one or more devices or circuits used to store programs or data. The storage module may be a register, cache, or RAM, etc., and the storage module may be integrated with the processing module. The storage module may be a ROM or other type of static storage device that can store static information and instructions, and the storage module may be independent of the processing module.

[0398] The transceiver module may be an input or output interface, a pin or a circuit, etc.

[0399] In an example, the device 700 may be a terminal, or a chip or functional unit used in a terminal. The device 700 has any function of the terminal in the above method, for example, the device 700 can execute the above Figure 2 、 Figure 3 、 Figure 4 、 Figure 5 、 Figure 6 The steps in the method are performed by the terminal.

[0400] The receiving module 720a can execute the receiving action performed by the terminal in the above method embodiment.

[0401] The sending module 720b can execute the sending action performed by the terminal in the above method embodiment.

[0402] The processing module 710 may execute other actions except the sending action and the receiving action among the actions executed by the terminal in the above method embodiment.

[0403] In one example, the receiving module 720a is configured to receive a second request from an information management network element, where the second request is used to request information of the terminal;

[0404] The receiving module 720a is further configured to receive a fourth request from the information management network element, the fourth request being for the information;

[0405] The sending module 720b is used to send the information and first indication information to the information management network element, where the first indication information is used to indicate that the information is allowed to be shared.

[0406] In an example, the processing module 710 is configured to obtain a sharing policy, where the sharing policy is used to describe terminal information that is allowed to be shared, and the terminal information that is allowed to be shared includes the information; and determine the first indication information according to the sharing policy.

[0407] In an example, the storage module 730 may store computer-executable instructions of the terminal-executed method, so that the processing module 710 , the receiving module 720 a , and the sending module 720 b execute the terminal-executed method in the above example.

[0408] For example, the storage module may include one or more memories, which may be devices in one or more devices or circuits used to store programs or data. The storage module may be a register, cache, or RAM, etc., and the storage module may be integrated with the processing module. The storage module may be a ROM or other type of static storage device that can store static information and instructions, and the storage module may be independent of the processing module.

[0409] The transceiver module may be an input or output interface, a pin or a circuit, etc.

[0410] The above describes the device applied to the information management network element and the device applied to the terminal in the embodiment of the present application. The following describes the possible product forms of the device applied to the information management network element and the device applied to the terminal. It should be understood that any device with the above Figure 7 Any product having the characteristics of the device applied to the information management network element, and any product having the characteristics of the device applied to the terminal, falls within the scope of protection of this application. It should also be understood that the following description is for illustrative purposes only and should not limit the product forms of the device applied to the information management network element and the product forms of the device applied to the terminal in the embodiments of this application to these examples.

[0411] As a possible product form, the device can be implemented by a general bus architecture.

[0412] like Figure 8 As shown, a schematic block diagram of a terminal information sharing device (the terminal information sharing device can also be regarded as a communication device) 800 is provided.

[0413] The apparatus 800 may include a processor 810 and, optionally, a transceiver 820 and a memory 830. The transceiver 820 may be configured to receive programs or instructions and transmit them to the processor 810. Alternatively, the transceiver 820 may be configured to communicate between the apparatus 800 and other communication devices, such as exchanging control signaling and / or service data. The transceiver 820 may be a code and / or data reader / writer, or a signal transmission transceiver between the processor and the transceiver. The processor 810 and the memory 830 are electrically coupled.

[0414] The device 800 may be an information management network element, or a chip used in an information management network element. It should be understood that the device has any function of the information management network element in the above method, for example, the device 800 can execute the above Figure 2 、 Figure 3 、 Figure 4 、 Figure 5 、 Figure 6 The steps of the method performed by the information management network element are as follows. For example, the memory 830 is used to store a computer program; the processor 810 can be used to call the computer program or instructions stored in the memory 830 to execute the method performed by the information management network element in the above example, or to execute the method performed by the information management network element in the above example through the transceiver 820.

[0415] The device 800 may be a terminal or a chip used in a terminal. It should be understood that the device has any function of the terminal in the above method. For example, the device 800 can execute the above method. Figure 2 、 Figure 3 、 Figure 4 、 Figure 5 、 Figure 6 For example, the memory 830 is used to store a computer program; the processor 810 can be used to call the computer program or instructions stored in the memory 830 to execute the method executed by the terminal in the above example, or to execute the method executed by the terminal in the above example through the transceiver 820.

[0416] Figure 7 The processing module 710 in can be implemented by the processor 810.

[0417] Figure 7 The receiving module 720a and the sending module 720b in the embodiment can be implemented by the transceiver 820. Alternatively, the transceiver 820 is divided into a receiver and a transmitter, the receiver performs the function of the receiving module, and the transmitter performs the function of the sending module.

[0418] Figure 7The storage module 730 in can be implemented by the memory 830.

[0419] As a possible product form, the device may be implemented by a general-purpose processor (a general-purpose processor may also be referred to as a chip or a chip system).

[0420] In one possible implementation, a general processor of a device or terminal for an information management network element includes: a processing circuit (a processing circuit may also be referred to as a processor); optionally, it also includes: an input and output interface for internally connecting and communicating with the processing circuit, and a storage medium (storage medium may also be referred to as a memory), wherein the storage medium is used to store instructions executed by the processing circuit to execute the method executed by the information management network element or terminal in the above example.

[0421] Figure 7 The processing module 710 in can be implemented by a processing circuit.

[0422] Figure 7 The receiving module 720a and the sending module 720b in the embodiment can be implemented by an input / output interface. Alternatively, the input / output interface is divided into an input interface and an output interface, the input interface performs the function of the receiving module, and the output interface performs the function of the sending module.

[0423] Figure 7 The storage module 730 can be implemented by a storage medium.

[0424] As a possible product form, the device of the embodiment of the present application can also be implemented using the following: one or more FPGAs (field programmable gate arrays), PLDs (programmable logic devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits that can perform the various functions described throughout this application.

[0425] An embodiment of the present application also provides a communication system, which includes an information management network element that executes the above-mentioned terminal information sharing method, and a first network element and / or a second network element that communicates with the information management network element.

[0426] The present application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, enables the computer to perform the aforementioned terminal information sharing method. In other words, the computer program includes instructions for implementing the aforementioned terminal information sharing method.

[0427] An embodiment of the present application further provides a computer program product, including: computer program code, which, when executed on a computer, enables the computer to execute the terminal information sharing method provided above.

[0428] In addition, the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), a baseband processor, the baseband processor and the CPU may be integrated together or separated, or may be a network processor (NP) or a combination of a CPU and an NP. The processor may further include a hardware chip or other general-purpose processor. The above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) and other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. or any combination thereof. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0429] The memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0430] The transceiver mentioned in the embodiments of the present application may include a separate transmitter and / or a separate receiver, or may be an integrated transmitter and receiver. The transceiver may operate under the instructions of a corresponding processor. Optionally, the transmitter may correspond to a transmitter in a physical device, and the receiver may correspond to a receiver in a physical device.

[0431] Those skilled in the art will appreciate that the various method steps and units described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the steps and components of each embodiment have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0432] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. 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 mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0433] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

[0434] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0435] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially 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, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0436] The term "and / or" in this application describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated with each other are in an "or" relationship. The term "multiple" referred to in this application refers to two or more. In addition, it should be understood that in the description of this application, words such as "first" and "second" are only used to distinguish the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order.

[0437] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present application.

[0438] Obviously, those skilled in the art may make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations.

Claims

1. A method for sharing terminal information, characterized in that: Applied to information management network elements, including: receiving a first request from a first network element, where the first network element supports a first service, and the first request is used to request information of a terminal; Sending a second request to the terminal based on the first request, where the second request is used to request the information; receiving a third request from a second network element, where the second network element supports a second service, the third request being used to request the information of the terminal; receiving the information from the terminal; The information is sent to the first network element and the second network element.

2. The method according to claim 1, wherein After receiving the third request from the second network element and before receiving the information from the terminal, the method further includes: An update request of the second request is sent to the terminal, where the update request is used to request the information of the terminal.

3. The method according to claim 1, wherein Also includes: Acquire a sharing policy, where the sharing policy is used to describe whether the information is allowed to be shared between the first service and the second service; The sending the information to the first network element and the second network element includes: sending the information to the first network element and the second network element according to the sharing policy.

4. The method according to claim 3, wherein The sharing strategy includes: an identifier of the first service and an identifier of the second service.

5. The method according to claim 4, wherein The sharing strategy also includes one or more of the following: The type of the information, the sharing indication, and the terminals to which the sharing policy applies, wherein the terminals to which the sharing policy applies include the terminal.

6. The method according to any one of claims 3 to 5, characterized in that The acquisition sharing strategy includes: receiving the sharing policy from the first device; The first device includes one or more of the following: a configuration network element, the first network element, the second network element, and the terminal.

7. The method according to claim 1, wherein The first request includes one or more of the following: The identifier of the first network element, the first trigger, the first service identifier, the identifier of the terminal, the type of the information, and the first subscription transaction identifier; The third request includes one or more of the following: The identifier of the second network element, a third trigger, a second service identifier, an identifier of the terminal, the type of information, and a third subscription transaction identifier; The third trigger is the same as or compatible with the first trigger.

8. The method according to claim 7, wherein The second request includes one or more of the following: The first trigger, the type of information, and the second subscription transaction identifier.

9. The method according to claim 7 or 8, wherein After receiving the third request from the second network element and before receiving the information from the terminal, the method further includes: An update request of the second request is sent to the terminal, where the update request is used to request the information of the terminal; the update request includes: a fourth trigger; wherein the fourth trigger is determined according to the first trigger and the third trigger.

10. The method according to claim 1, wherein After receiving the third request from the second network element and before receiving the information from the terminal, the method further includes: It is determined that there is no need to send a fourth request for the information to the terminal in response to the third request.

11. The method according to claim 1, wherein Also includes: Sending a fourth request to the terminal based on the third request, where the fourth request is used to request the information; receiving first indication information from the terminal, where the first indication information is used to indicate that the information is allowed to be shared by the first service and the second service; Sending the information to the first network element and the second network element includes: Based on the first indication information, the information is sent to the first network element and the second network element.

12. The method according to claim 11, wherein The first indication information includes: a sharing indication.

13. The method according to claim 11 or 12, wherein: The second request includes one or more of the following: a second trigger, the type of information, and a second subscription transaction identifier; The fourth request includes one or more of the following: a fifth trigger, the type of the information, and a fifth subscription transaction identifier; The first indication information includes: the second subscription transaction identifier and the fifth subscription transaction identifier, and / or the identifier of the second trigger and the identifier of the fifth trigger.

14. A communication device, characterized in that: include: a receiving module, configured to receive a first request from a first network element, the first network element supporting a first service, the first request being used to request information of a terminal; a sending module, configured to send a second request to the terminal based on the first request, where the second request is used to request the information; The receiving module is further configured to receive a third request from a second network element, where the second network element supports a second service, and the third request is used to request the information of the terminal; The receiving module is further configured to receive the information from the terminal; The sending module is further used to send the information to the first network element and the second network element.

15. The device according to claim 14, wherein The sending module is further configured to send an update request of the second request to the terminal, where the update request is used to request the information of the terminal.

16. The device according to claim 14, wherein The receiving module is further configured to obtain a sharing policy, where the sharing policy is used to describe whether the information is allowed to be shared between the first service and the second service; The sending module is specifically configured to send the information to the first network element and the second network element according to the sharing policy.

17. The device according to claim 16, characterized in that The sharing strategy includes: an identifier of the first service and an identifier of the second service.

18. The device according to claim 17, wherein The sharing strategy also includes one or more of the following: The type of the information, the sharing indication, and the terminal to which the sharing policy is applicable, wherein the terminal to which the sharing policy is applicable includes the terminal.

19. The device according to any one of claims 16 to 18, characterized in that The receiving module is specifically configured to receive the sharing policy from a first device; the first device includes one or more of the following: a configuration network element, the first network element, the second network element, and the terminal.

20. The device according to claim 14, wherein The first request includes one or more of the following: The identifier of the first network element, the first trigger, the first service identifier, the identifier of the terminal, the type of the information, and the first subscription transaction identifier; The third request includes one or more of the following: The identifier of the second network element, a third trigger, a second service identifier, an identifier of the terminal, the type of information, and a third subscription transaction identifier; The third trigger is the same as or compatible with the first trigger.

21. The device according to claim 20, characterized in that The second request includes one or more of the following: The first trigger, the type of information, and the second subscription transaction identifier.

22. The device according to claim 20 or 21, characterized in that The sending module is further used to send an update request of the second request to the terminal, and the update request is used to request the information of the terminal; the update request includes: a fourth trigger; wherein the fourth trigger is determined based on the first trigger and the third trigger.

23. The device according to claim 14, wherein Also includes: The processing module is configured to determine that there is no need to send a fourth request for requesting the information to the terminal in response to the third request.

24. The device according to claim 14, wherein The sending module is further configured to send a fourth request to the terminal based on the third request, where the fourth request is used to request the information; The receiving module is further configured to receive first indication information from the terminal, where the first indication information is used to indicate that the information is allowed to be shared by the first service and the second service; The sending module is specifically configured to send the information to the first network element and the second network element based on the first indication information.

25. The device according to claim 24, wherein The first indication information includes: a sharing indication.

26. The device according to claim 24 or 25, characterized in that The second request includes one or more of the following: a second trigger, the type of information, and a second subscription transaction identifier; The fourth request includes one or more of the following: a fifth trigger, the type of the information, and a fifth subscription transaction identifier; The first indication information includes: the second subscription transaction identifier and the fifth subscription transaction identifier, and / or the identifier of the second trigger and the identifier of the fifth trigger.

27. A communication device, characterized in that: comprising a processor; the processor being coupled to a memory; The memory is used to store computer program instructions; The processor is configured to execute part or all of the computer program instructions in the memory, and when the part or all of the computer program instructions are executed, is configured to implement the method according to any one of claims 1 to 13.

28. A computer-readable storage medium, characterized in that Used to store a computer program, wherein the computer program includes instructions for implementing the method according to any one of claims 1 to 13.

Images