Charging method, device and system and computer readable storage medium

Abstract

The present disclosure provides a charging method, device and system and a computer readable storage medium, and relates to the technical field of communications, the method comprising: a GMLC obtains positioning information of a target UE, the positioning information being obtained through a sidelink positioning process between the target UE and a positioning UE; and after the positioning information is acquired, the GMLC sends a charging data request to a CHF network element, so that the CHF network element generates a charging data record CDR related to the sidelink positioning process.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a charging method, device, system and computer-readable storage medium. Background Art

[0002] Location Service (LCS) in a mobile communication network refers to a service that obtains the location information of a User Equipment (UE) through positioning technology.

[0003] As competition in mobile communication networks becomes increasingly fierce, operators can improve their competitiveness by providing differentiated services to users. LCS services refer to value-added services that provide various location-based applications after determining the location of the UE using positioning technology. As a mobile value-added service, LCS services have good development prospects. Summary of the invention

[0004] According to one aspect of an embodiment of the present disclosure, a billing method is provided, comprising: GMLC acquiring positioning information of a target user equipment UE, wherein the positioning information is acquired through a sidelink positioning process between the target UE and the positioning UE; after acquiring the positioning information, the GMLC sends a billing data request to a billing function CHF network element, so that the CHF network element generates a billing data record CDR related to the sidelink positioning process.

[0005] In some embodiments, the sidelink positioning process is performed after the access and mobility management function AMF network element receives a mobile initial positioning request MO-LR from the target UE.

[0006] In some embodiments, the GMLC obtains the positioning information from the location management function LMF network element via the AMF network element.

[0007] In some embodiments, the positioning information is included in a location update service message received by the GMLC from the AMF network element, and the location update service message is sent by the AMF network element after receiving the MO-LR from the target UE and obtaining the positioning information from the LMF network element.

[0008] In some embodiments, the GMLC sends the billing data request when a reporting condition is met, and the reporting condition includes that the GMLC obtains the positioning information a preset number of times or a preset time has passed since the last time the GMLC sent the billing data request.

[0009] In some embodiments, when the reporting condition includes that the GMLC obtains the positioning information a preset number of times, the billing data request is generated based on the positioning information received by the GMLC the preset number of times.

[0010] In some embodiments, when the reporting condition includes that a preset time has passed since the last time the GMLC sent the billing data request, the billing data request is generated based on the positioning information received by the GMLC within the preset time.

[0011] In some embodiments, the billing data request includes billing information, and the billing information includes one or more of the identifier of the target UE, the identifier of the positioning UE, the positioning role of the UE involved in the sidelink positioning process, the identifier of the GMLC, and the positioning service record type.

[0012] According to another aspect of an embodiment of the present disclosure, a charging method is provided, including: a CHF network element receives a charging data request from a GMLC; and the CHF network element generates a CDR related to a sidelink positioning process between a target UE and a positioning UE according to the charging data request.

[0013] In some embodiments, the method further includes: the CHF network element sending the CDR to the charging domain via a charging gateway function CGF network element.

[0014] In some embodiments, the method further includes: the CHF network element sending a charging data response to the GMLC.

[0015] According to another aspect of an embodiment of the present disclosure, a charging device is provided, comprising: a module configured to execute the method described in any one of the above embodiments.

[0016] According to another aspect of an embodiment of the present disclosure, a billing device is provided, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute the method described in any one of the above embodiments based on instructions stored in the memory.

[0017] According to another aspect of an embodiment of the present disclosure, a charging device is provided, including: a device configured to execute the method described in any one of the above embodiments.

[0018] According to another aspect of an embodiment of the present disclosure, a billing device is provided, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute the method described in any one of the above embodiments based on instructions stored in the memory.

[0019] According to another aspect of the embodiments of the present disclosure, a billing system is provided, including: a gateway mobile location center including the billing device described in any one of the above embodiments; and a billing function network element including the billing device described in any one of the above embodiments.

[0020] According to another aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, comprising computer program instructions, wherein when the computer program instructions are executed by a processor, the method described in any one of the above embodiments is implemented.

[0021] In the disclosed embodiment, after the GMLC obtains the positioning information of the target UE obtained through the sidelink positioning process between the target UE and the positioning UE, it sends a billing data request to the CHF network element, so that the CHF network element generates a CDR related to the sidelink positioning process, so as to subsequently charge the positioning service related to the sidelink positioning process. In this way, the problem that the mobile communication network cannot charge the positioning service related to the sidelink positioning process (i.e., the positioning service in which the UE is positioned with the assistance of other UEs) is solved.

[0022] The technical solution of the present disclosure is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0024] Figure 1 It is a flowchart of a billing method according to some embodiments of the present disclosure.

[0025] Figure 2 It is a flowchart of a billing method according to some other embodiments of the present disclosure.

[0026] Figure 3 It is a flowchart of a billing method according to some other embodiments of the present disclosure.

[0027] Figure 4 It is a flowchart of a billing method according to some further embodiments of the present disclosure.

[0028] Figure 5 It is a structural diagram of a billing device according to some embodiments of the present disclosure.

[0029] Figure 6 It is a structural schematic diagram of a billing device according to some other embodiments of the present disclosure.

[0030] Figure 7 It is a structural diagram of a billing device according to some other embodiments of the present disclosure.

[0031] Figure 8 It is a structural diagram of a billing system according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0032] The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.

[0033] Unless specifically stated otherwise, the relative arrangement of components and steps, the numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure.

[0034] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0035] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered part of the specification.

[0036] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0037] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0038] In a mobile communication network, a UE usually adopts a self-positioning method to obtain its own positioning information. That is, when the UE is within the coverage of the network, the UE can use the network signal to obtain its current location, and can inform other UEs or other external clients (such as LCS clients) that need the location information of the UE of its current location.

[0039] In the related art, when the UE signal is weak or is not within the network coverage, the UE cannot use the network signal to perform self-positioning. In this case, the UE can obtain its own positioning information by performing auxiliary positioning with other UEs.

[0040] However, in the related art, it is impossible to charge for the positioning service in which the UE is positioned with the assistance of other UEs.

[0041] In view of this, the embodiments of the present disclosure propose the following solutions.

[0042] Figure 1 It is a flowchart of a billing method according to some embodiments of the present disclosure.

[0043] like Figure 1 As shown, the charging method may include one or more of steps 102 and 104 .

[0044] In step 102, a Gateway Mobile Location Centre (GMLC) obtains location information of a target UE.

[0045] Here, the positioning information of the target UE can be obtained through a sidelink positioning process between the target UE (Target UE) and the positioned UE (Located UE). The positioning information may include, for example, longitude and latitude information.

[0046] The target UE refers to the UE being positioned in the mobile communication network. When the target UE cannot perform self-positioning, the positioning information of the target UE can be obtained through the sidelink positioning procedure between the positioning UE (also known as positioning assisted UE or known position UE). In the present disclosure, the sidelink positioning procedure is the ranging / sidelink positioning procedure (Ranging / Sidelink Positioning Procedure).

[0047] The sidelink positioning process refers to the process of positioning based on the sidelink (SL) between UEs. The target UE can be absolutely positioned or relatively positioned through the sidelink positioning process. Absolute positioning can determine the absolute coordinates of the UE, for example, and relative positioning can determine the coordinates of the UE relative to a reference position, for example. Ranging refers to determining the distance and / or angle of the UE relative to a reference position.

[0048] In some embodiments, the positioning UE may include one or more UEs. That is, in the sidelink positioning process, one or more positioning UEs may assist in positioning the target UE to determine the positioning information of the target UE.

[0049] In some embodiments, the positioning UE may be a relay UE or a road side unit (RSU) with relay capability.

[0050] In some embodiments, the GMLC may obtain the location information of the target UE through an Access and Mobility Management Function (AMF) network element, which will be further described below.

[0051] In step 104, after acquiring the location information of the target UE, the GMLC sends a charging data request to a charging function (CHF) network element so that the CHF network element generates a charging data record (CDR) related to the sidelink location process.

[0052] In some embodiments, a charging trigger function (CTF) network element may be built in the GMLC. After the GMLC obtains the location information of the target UE, the CTF network element in the GMLC may generate a charging data request based on the location information of the target UE and report it to the CHF network element.

[0053] In some embodiments, the CHF network element may send the CDR to a billing domain so that the billing domain charges for the positioning service related to the sidelink positioning procedure.

[0054] In some embodiments, the charging data request may include a field defining a transmission type. For example, the transmission type of the charging data request may be defined as an event through the field.

[0055] In the above embodiment, after the GMLC obtains the positioning information of the target UE obtained through the sidelink positioning process between the target UE and the positioning UE, it sends a billing data request to the CHF network element, so that the CHF network element generates a CDR related to the sidelink positioning process, so as to subsequently charge the positioning service related to the sidelink positioning process. In this way, the problem that the mobile communication network cannot charge the positioning service related to the sidelink positioning process (i.e., the positioning service in which the UE is positioned with the assistance of other UEs) is solved.

[0056] In some embodiments, the GMLC may send a charging data request if a reporting condition is met. Here, the reporting condition may include that the GMLC obtains the location information of the target UE for a preset number of times or that a preset time has passed since the last time the GMLC sent a charging data request.

[0057] In some embodiments, when the reporting condition includes that the GMLC obtains the location information of the target UE for a preset number of times, the charging data request sent by the GMLC to the CHF network element can be generated based on the location information received by the GMLC for the preset number of times. For example, the preset number of times can be pre-configured in the GMLC.

[0058] In some embodiments, the preset number of times is 1. That is, the GMLC sends a charging data request to the CHF network element each time after receiving the location information of the target UE, and the charging data request is generated based on the location information of the target UE received this time.

[0059] In other embodiments, the preset number of times is multiple times. For example, if the preset number of times is 5 times, then after receiving the positioning information of the target UE 5 times, the GMLC will send a billing data request to the CHF network element (i.e., the GMLC sends a billing data request once for every 5 positioning information of the target UE received by the GMLC), and the billing data request is generated based on all the positioning information of the target UE received 5 times. In this way, the GMLC can send a billing data request after receiving the positioning information of the target UE multiple times to uniformly bill these multiple positioning services, thereby reducing the signaling interaction related to billing on the basis of realizing billing.

[0060] In some embodiments, when the reporting condition includes that a preset time has passed since the last time the GMLC sent a charging data request, the charging data request sent by the GMLC to the CHF network element is generated based on the positioning information of the target UE received by the GMLC within the preset time.

[0061] For example, the GMLC may start a built-in timer to start timing each time a charging data request is sent, and when the timing time reaches a preset time, a charging data request is generated based on the positioning information of the target UE received within the preset time, and the charging data request is sent to the CHF network element. For example, the GMLC may count the positioning information of the target UE received within the preset time continuously during the timing process or once when the timing time reaches the preset time, and generate a charging data request based on the received positioning information of the target UE.

[0062] In this way, GMLC can send billing data requests at regular intervals to uniformly bill one or more positioning services performed in the past period of time, thereby reducing billing-related signaling interactions while implementing billing.

[0063] In some embodiments, the sidelink positioning process can be performed after the AMF network element receives a mobile originated positioning request (Mobile Originated-Location Request, MO-LR) (also known as a terminal originated positioning request) from the target UE.

[0064] In this way, the mobile communication network can charge for the positioning services in the MO-LR positioning scenario, which solves the problem that the mobile communication network cannot charge for the positioning services related to the sidelink positioning process in the MO-LR positioning scenario.

[0065] In other embodiments, the sidelink positioning process may be performed after the GMLC receives a Mobile Terminated-Location Request (MT-LR) (also known as a Terminal Terminated-Location Request).

[0066] In this way, the mobile communication network can charge for the positioning services in the MT-LR positioning scenario, thereby solving the problem that the mobile communication network cannot charge for the positioning services related to the sidelink positioning process in the MT-LR positioning scenario.

[0067] In some embodiments, the GMLC may obtain the positioning information of the target UE from the Location Management Function (LMF) network element via the AMF network element.

[0068] The charging method in the MO-LR positioning scenario is further described below in conjunction with some embodiments.

[0069] In some embodiments, in the MO-LR positioning scenario, the positioning information of the target UE may be included in the location update service message received by the GMLC from the AMF network element. Here, the location update service message may be sent by the AMF network element after receiving the MO-LR from the target UE and obtaining the positioning information from the LMF network element.

[0070] Figure 2 It is a flowchart of a billing method according to some other embodiments of the present disclosure.

[0071] like Figure 2 As shown, the charging method may include one or more steps from step 202 to step 222 .

[0072] In step 202, the target UE sends the MO-LR to the AMF network element.

[0073] In some embodiments, the MO-LR sent by the target UE may include but is not limited to one or more of the following: whether to transmit the positioning information to the LCS client (LCS client) or application function (AF), and whether it is an indication of absolute positioning or relative positioning.

[0074] In step 204, the AMF network element selects the LMF network element.

[0075] For example, the AMF network element can select the LMF network element that provides positioning services for the target UE based on local configuration or the UE's positioning registration data.

[0076] In step 206, the AMF network element sends a determine location request to the LMF network element.

[0077] For example, the AMF network element can call the location determination service (ie, Nlmf_Location_Determine Location Service) operation to the LMF network element through the Nlmf interface, that is, send a location determination request (ie, Nlmf_Location_Determin Location Request) to the LMF network element.

[0078] In step 208, the LMF network element performs a sidelink positioning procedure.

[0079] Here, the sidelink positioning process may include one or more of the following processes: a process for discovering the positioning UE, a process for the positioning UE to obtain its own positioning information, a process for performing ranging / sidelink positioning between the target UE and the positioning UE, and a process for the target UE to report relevant ranging / sidelink positioning measurement results to the LMF network element.

[0080] For example, if the MO-LR sent by the target UE indicates that the target UE needs to be absolutely positioned, the positioning UE will execute the process of obtaining its own positioning information, and the positioning information obtained by the positioning UE includes the absolute position of the positioning UE (such as the specific coordinates of the positioning UE).

[0081] In step 210, the LMF network element sends a location determination response to the AMF network element.

[0082] Here, it is determined that the location response includes the positioning information of the target UE.

[0083] For example, the LMF network element may send a location determination response (ie, Nlmf_Location_Determine Location Response) to the AMF network element via the Nlmf interface.

[0084] In step 212, the AMF network element sends a location update service message to the GMLC.

[0085] Here, the location update service message includes the positioning information of the target UE.

[0086] For example, the AMF network element can call the location update service (ie, Ngmlc_Location_Location Update service) operation to the GMLC through the Ngmlc interface, that is, send a location update service message to the GMLC.

[0087] In step 214, the GMLC sends a location update service response to the AMF network element.

[0088] For example, GMLC can send a location update service response (Ngmlc_Location_Location Update Response) to the AMF network element through the Ngmlc interface.

[0089] In step 216, the AMF network element sends the positioning information of the target UE to the target UE.

[0090] For example, the AMF network element may send an MO-LR response carrying the positioning information of the target UE to the target UE.

[0091] It should be noted that the aforementioned steps 202 to 216 are all related steps of the side link positioning process performed to obtain the positioning information of the target UE in the MO-LR positioning scenario.

[0092] Here, after step 212, GMLC can determine whether the reporting condition is met. If the reporting condition is met, step 218 is executed; if the reporting condition is not met, step 218 is not executed. That is, if step 218 is executed, step 218 can be executed in parallel with step 214, and the order of step 218 and step 214 is not limited here. In addition, after step 210, the AMF network element can send the positioning information of the target UE to the GMLC and the target UE respectively, that is, step 212 and step 216 can be executed in parallel, and the order of step 212 and step 216 is not limited here.

[0093] In step 218, the GMLC sends a charging data request to the CHF network element.

[0094] For example, when the GMLC confirms that the reporting condition is met, the CTF network element built in the GMLC is triggered to generate a charging data request and send the charging data request to the CHF network element.

[0095] In step 220, the CHF network element generates a CDR related to the sidelink positioning procedure.

[0096] In some embodiments, the CHF network element may send the generated CDR related to the sidelink positioning procedure to the charging domain via the Charging Gateway Function (CGF) network element so that the charging domain charges for the positioning service related to the sidelink positioning procedure.

[0097] In step 222, the CHF network element sends a charging data response (Charging data Response) to the GMLC.

[0098] In some embodiments, the CHF network element may send a charging data response to the GMLC after generating a CDR related to the sidelink positioning process to inform the GMLC that the CDR has been generated.

[0099] In some embodiments, in step 202, if a non-access stratum (NAS) signaling connection is established between the target UE and the AMF network element, the target UE may send an MO-LR to the AMF network element via an uplink NAS transmission message.

[0100] In other embodiments, in step 202, if a NAS signaling connection is not established between the target UE and the AMF network element, the target UE may discover the positioning UE through a UE discovery process (e.g., a relay service discovery process), and send the MO-LR to the AMF network element through the positioning UE. For example, the target UE may send the MO-LR to the positioning UE through a PC5 connection established with the positioning UE, and then the positioning UE may send the MO-LR from the target UE to the AMF network element through a NAS signaling connection established with the AMF network element.

[0101] In some embodiments, the LMF network element may choose to calculate the positioning information of the target UE by itself (i.e., the sidelink positioning procedure initiated by the LMF network element is a network-based sidelink positioning procedure (Procedures for Networkbased SL positioning)), or the LMF network element may choose to have the positioning UE calculate the positioning information of the target UE (i.e., the sidelink positioning procedure initiated by the LMF network element is a network-assisted sidelink positioning procedure (Procedures for Network assisted SL Positioning)). The network-assisted sidelink positioning procedure is also called a UE-based sidelink positioning procedure.

[0102] The sidelink positioning procedure involves four cases, namely: a network-based sidelink positioning procedure for a target UE without a NAS connection, a network-based sidelink positioning procedure for a target UE with a NAS connection, a network-assisted sidelink positioning procedure for a target UE without a NAS connection, and a network-assisted sidelink positioning procedure for a target UE with a NAS connection.

[0103] Therefore, in the MO-LR positioning scenario, for any of the above four situations, GMLC can send the corresponding charging data request to the CHF network element after obtaining the positioning information of the target UE, so as to support the mobile communication network to charge the positioning service. That is, the mobile communication network can charge the positioning services involved in various sidelink positioning processes in the MO-LR positioning scenario, further increasing the revenue obtained by the operator by providing LCS services.

[0104] Next, the charging method in the MT-LR positioning scenario is further described in conjunction with some embodiments.

[0105] In some embodiments, in the MT-LR positioning scenario, the positioning information of the target UE may be included in the location providing positioning information response received by the GMLC, wherein the location providing positioning information response may be sent by the AMF network element after receiving the location providing positioning information request from the GMLC and obtaining the positioning information from the LMF network element.

[0106] Figure 3 It is a flowchart of a billing method according to some other embodiments of the present disclosure.

[0107] like Figure 3 As shown, the charging method may include one or more steps from step 302 to step 322 .

[0108] In step 302, the GMLC receives the MT-LR from the AF or LCS client.

[0109] For example, in step 302a, the AF may send an LCS service request (i.e., MT-LR) to a network exposure function (NEF) network element; in step 302b, the NEF network element sends the LCS service request to the GMLC. That is, the AF may send an LCS service request (i.e., MT-LR) to the GMLC through the NEF network element to request the acquisition of the positioning information of the target UE.

[0110] In step 304, the GMLC sends a location provision information request to the AMF network element.

[0111] For example, GMLC can first obtain the address of the AMF network element through the unified data management (UDM) network element, and then call the location provision positioning information service (i.e., Namf_Location_Provide Positioning Info service) operation to the AMF network element through the Namf interface, that is, send a location provision positioning information request (i.e., Namf_Location_Provide Positioning Info Request) to the AMF network element.

[0112] In step 306, the AMF network element selects the LMF network element.

[0113] In step 308, the AMF network element sends a determine location request to the LMF network element.

[0114] In step 310, the LMF network element performs a sidelink positioning procedure.

[0115] Here, the sidelink positioning process may include one or more of the following processes: a process for discovering the positioning UE, a process for the positioning UE to obtain its own positioning information, a process for performing ranging / sidelink positioning between the target UE and the positioning UE, and a process for the target UE to report relevant ranging / sidelink positioning measurement results to the LMF network element.

[0116] In step 312, the LMF network element sends a location determination response to the AMF network element.

[0117] In step 314, the AMF network element sends a location providing positioning information response to the GMLC.

[0118] For example, the AMF network element can send a location providing positioning information response (ie, Namf_Location_Provide Positioning Info_Response) to the GMLC via the Namf interface.

[0119] In step 316, the GMLC sends a positioning service reply message to the AF or LCS client. Here, the positioning service reply message includes the positioning information of the target UE.

[0120] For example, in step 316a, GMLC may send a positioning service reply message to the NEF network element; in step 316b, the NEF network element sends the positioning service reply message to the AF. That is, GMLC may send a positioning service reply message to the AF through the NEF network element.

[0121] It should be noted that the aforementioned steps 302 to 316 are all related steps of the sidelink positioning process performed to obtain the positioning information of the target UE in the MT-LR positioning scenario.

[0122] Here, after step 314, the GMLC can determine whether the reporting condition is met. If the reporting condition is met, step 318 is executed; if the reporting condition is not met, step 318 is not executed. That is, if step 318 is executed, step 318 can be executed in parallel with step 314, and the order of step 318 and step 314 is not limited here.

[0123] In step 318, the GMLC sends a charging data request to the CHF network element.

[0124] For example, when the GMLC confirms that the reporting condition is met, the CTF network element built in the GMLC is triggered to generate a charging data request and send the charging data request to the CHF network element.

[0125] In step 320, the CHF network element generates a CDR associated with the sidelink positioning procedure.

[0126] In step 322, the CHF network element sends a charging data response (Charging data Response) to the GMLC.

[0127] Figure 3 For other specific descriptions of steps 306 to 322 in the method shown, please refer to the aforementioned Figure 2 The description in the related embodiments shown will not be repeated here.

[0128] Similarly, in the MT-LR positioning scenario, for any of the four situations of the aforementioned sidelink positioning process, the GMLC can send a corresponding charging data request to the CHF network element after obtaining the positioning information of the target UE, so as to support the mobile communication network to charge the positioning service. That is, the mobile communication network can charge the positioning services involved in various sidelink positioning processes in the MT-LR positioning scenario, further increasing the revenue obtained by the operator by providing LCS services.

[0129] In some embodiments, the charging data request sent by the GMLC may include charging information. That is, after acquiring the location information of the target UE, the GMLC may generate a charging data request including the charging information based on the location information of the target UE.

[0130] In some embodiments, the billing information may include one or more of the identifier of the target UE, the identifier of the positioning UE, the positioning role of the UE involved in the sidelink positioning process (i.e., the positioning role of the UE in the sidelink positioning process), the identifier of the GMLC, and the location service record type. This helps the mobile communication network to perform accurate billing based on the billing information provided by the GMLC in the future, and further improves the accuracy of billing while increasing the revenue obtained by the operator by providing LCS services.

[0131] Table 1 shows the contents of billing information according to some embodiments of the present disclosure.

[0132] Table 1

[0133]

[0134]

[0135]

[0136] As shown in Table 1, for example, in the MO-LR positioning scenario, the billing information provided by the GMLC may include: the identifier of the target UE, the identifier of the positioning UE, the positioning role of the UE in the sidelink positioning process, the identifier of the GMLC, the positioning service record type, the identifier of the PLMN serving the target UE, the identifier of the PLMN serving the positioning UE, the identifier of the PLMN serving the GMLC, the request timestamp, the location information estimation accuracy, the requested positioning QoS, and one or more of the privacy check.

[0137] For another example, in the MT-LR positioning scenario, the billing information provided by the GMLC may include: the identifier of the target UE, the identifier of the positioning UE, the positioning role of the UE in the sidelink positioning process, the identifier of the GMLC, the positioning service record type, the identifier of the PLMN serving the target UE, the identifier of the PLMN serving the positioning UE, the identifier of the PLMN serving the GMLC, the AF identifier, the LCS client type, the LCS client identifier, the request timestamp, the location information estimation accuracy, the requested positioning QoS, and one or more of the privacy check.

[0138] Figure 4 It is a flowchart of a billing method according to some further embodiments of the present disclosure.

[0139] like Figure 4 As shown, the charging method may include one or more of steps 402 and 404 .

[0140] In step 402, the CHF network element receives a charging data request from the GMLC.

[0141] In step 404, the CHF network element generates a CDR related to the sidelink positioning procedure between the target UE and the positioning UE according to the charging data request.

[0142] In this way, the CHF network element can generate CDR related to the sidelink positioning process between the target UE and the positioning UE based on the billing data request from the GMLC, so as to support the mobile communication network to charge the positioning services related to the sidelink positioning process, thereby helping to increase the revenue obtained by the operator from providing LCS services.

[0143] In some embodiments, the CHF network element may send the CDR related to the sidelink positioning procedure between the target UE and the positioning UE to the charging domain via the CGF network element.

[0144] In some embodiments, after receiving the charging data request from the GMLC, the CHF network element may send a charging data response to the GMLC.

[0145] Figure 4 For other detailed descriptions of the method shown, please refer to the aforementioned Figures 1 to 3 The description in the related embodiments will not be repeated here.

[0146] Each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0147] Figure 5 It is a structural diagram of a billing device according to some embodiments of the present disclosure.

[0148] like Figure 5 As shown, the charging device 500 includes an acquisition module 501 and a sending module 502 .

[0149] The acquisition module 501 may be configured to acquire the positioning information of the target user equipment UE. Here, the positioning information of the target UE is acquired through a sidelink positioning process between the target UE and the positioning UE.

[0150] The sending module 502 may be configured to send a charging data request to the CHF network element after acquiring the positioning information of the target UE, so that the CHF network element generates a CDR related to the sidelink positioning procedure.

[0151] In some embodiments, the sidelink positioning procedure is performed after the charging device 500 receives the MT-LR.

[0152] In some embodiments, the charging device 500 may further include other modules for executing other steps of any of the above embodiments, which will not be described in detail here.

[0153] Figure 6 It is a structural schematic diagram of a billing device according to some other embodiments of the present disclosure.

[0154] like Figure 6 As described above, the charging device 600 includes a receiving module 601 and a generating module 602 .

[0155] The receiving module 601 may be configured to receive a charging data request from the GMLC.

[0156] The generating module 602 may be configured to generate a CDR related to a sidelink positioning procedure between the target UE and the positioning UE according to the charging data request.

[0157] In some embodiments, the charging apparatus 600 may further include a sending module. The sending module is configured to send the CDR related to the sidelink positioning procedure between the target UE and the positioning UE to the charging domain via the CGF network element.

[0158] In some embodiments, the sending module in the charging device 600 may also be configured to send a charging data response to the GMLC.

[0159] In some embodiments, the charging device 600 may further include other modules for executing other steps of any of the above embodiments, which will not be described in detail here.

[0160] Figure 7 It is a structural diagram of a billing device according to some other embodiments of the present disclosure.

[0161] like Figure 7 As shown, the charging device 700 includes a memory 701 and a processor 702 coupled to the memory 701 , and the processor 702 is configured to execute the method of any one of the aforementioned embodiments based on the instructions stored in the memory 701 .

[0162] The memory 701 may include, for example, a system memory, a fixed non-volatile storage medium, etc. The system memory may store, for example, an operating system, an application program, a boot loader, and other programs.

[0163] The charging device 700 may also include an input / output interface 703, a network interface 704, a storage interface 705, etc. These interfaces 703, 704, 705, and the memory 701 and the processor 702 may be connected, for example, via a bus 706. The input / output interface 703 provides a connection interface for input / output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 704 provides a connection interface for various networked devices. The storage interface 705 provides a connection interface for external storage devices such as an SD card and a USB flash drive.

[0164] In some embodiments, the charging device 700 may be configured to perform the aforementioned Figures 1 to 3 In some other embodiments, the charging device 700 may be configured to perform the above-mentioned Figure 4 Steps in the illustrated embodiment.

[0165] Figure 8 It is a structural diagram of a billing system according to some embodiments of the present disclosure. Figure 8 It includes three sub-figures (1) to (3) in dashed boxes.

[0166] like Figure 8 As shown in (1) to (3) in FIG. 1 , the charging system may include a GMLC 801 and a CHF network element 802. The GMLC 801 may include a processor that executes the aforementioned Figures 1 to 3 The charging device (eg, charging device 500) of any one of the embodiments shown in the figure, the CHF network element 802 may include executing the aforementioned Figure 4 A billing device (eg, billing device 600 ) for the method in the illustrated embodiment.

[0167] In some embodiments, the GMLC 801 and the CHF network element 802 may exchange information via an Nchf interface. For example, the GMLC 801 may send a charging data request to the CHF network element 802 via the Nchf interface.

[0168] In some embodiments, the CTF network element 803 may be built in the GMLC 801. For example, after the GMLC 801 obtains the location information of the target UE, the CTF network element 803 in the GMLC 801 may generate a charging data request based on the location information of the target UE and report it to the CHF network element 802 via the Nchf interface.

[0169] In some embodiments, the charging system may further include a CGF network element 804 and a charging domain 805. In these embodiments, the CHF network element 802 may send the generated CDR to the charging domain 805 via the CGF network element 804 to charge for the positioning service related to the sidelink positioning procedure.

[0170] In some embodiments, Figure 8 As shown in (1), the CGF network element 804 exchanges information with the CHF network element 802 through an internal interface (not shown in the figure), and exchanges information with the charging domain 805 through a Bpr interface. For example, the CGF network element 804 can receive a CDR from the CHF network element 802 through an internal interface, and send the CDR to the charging domain 805 through the Bpr interface.

[0171] In other embodiments, Figure 8 As shown in (2), the CGF network element 804 may be located between the CHF network element 802 and the charging domain 805, wherein the CGF network element 804 and the CHF network element 802 exchange information via the Ga interface, and the CGF network element 804 and the charging domain 805 exchange information via the Bpr interface. For example, the CGF network element 804 may receive a CDR from the CHF network element 802 via the Ga interface, and send the CDR to the charging domain 805 via the Bpr interface.

[0172] In some other embodiments, Figure 8 As shown in (3), the CGF network element 804 is located in the charging domain 805 and exchanges information with the CHF network element 802 through the Ga interface. For example, the CGF network element 804 can receive the CDR from the CHF network element 802 through the Ga interface, so that the charging domain 805 charges the positioning service related to the sidelink positioning process based on the CDR.

[0173] The embodiments of the present disclosure further provide a computer-readable storage medium, comprising computer program instructions, which implement the method of any one of the above embodiments when executed by a processor.

[0174] Since the above-mentioned solution provided by the embodiment of the present disclosure solves the problem that the mobile communication network is unable to charge for the positioning service related to the sidelink positioning process (that is, the positioning service in which the UE is assisted by other UEs), the adoption of the above-mentioned solution provided by the embodiment of the present disclosure helps to increase the revenue obtained by operators from providing LCS services.

[0175] So far, various embodiments of the present disclosure have been described in detail. In order to avoid obscuring the concept of the present disclosure, some details known in the art are not described. Based on the above description, those skilled in the art can fully understand how to implement the technical solution disclosed here.

[0176] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transient storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0177] The present disclosure is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present disclosure. It should be understood that the functions specified in one or more processes in the flowchart and / or one or more blocks in the block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the functions specified in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0178] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0179] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0180] Although some specific embodiments of the present disclosure have been described in detail by way of examples, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. It should be understood by those skilled in the art that the above embodiments may be modified or some technical features may be replaced by equivalents without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.

Claims

1. A billing method, comprising: The gateway mobile location center GMLC obtains the positioning information of the target user equipment UE, and the positioning information is obtained through the sidelink positioning process between the target UE and the positioning UE; After acquiring the positioning information, the GMLC sends a charging data request to a charging function CHF network element so that the CHF network element generates a charging data record CDR related to the sidelink positioning process.

2. The method according to claim 1, wherein: The sidelink positioning process is performed after the access and mobility management function AMF network element receives the mobile initial positioning request MO-LR from the target UE.

3. The method according to claim 2, wherein: The GMLC obtains the positioning information from the location management function LMF network element via the AMF network element.

4. The method according to claim 3, wherein: The positioning information is included in the location update service message received by the GMLC from the AMF network element, and the location update service message is sent by the AMF network element after receiving the MO-LR from the target UE and obtaining the positioning information from the LMF network element.

5. The method according to claim 1, wherein: The GMLC sends the billing data request when a reporting condition is met, where the reporting condition includes that the GMLC obtains the positioning information a preset number of times or a preset time has passed since the last time the GMLC sent the billing data request.

6. The method according to claim 5, wherein: In a case where the reporting condition includes that the GMLC obtains the positioning information a preset number of times, the charging data request is generated based on the positioning information received by the GMLC the preset number of times.

7. The method according to claim 5, wherein: In a case where the reporting condition includes that a preset time has passed since the last time the GMLC sent the charging data request, the charging data request is generated based on the positioning information received by the GMLC within the preset time.

8. The method according to any one of claims 1 to 7, wherein: The billing data request contains billing information, and the billing information includes one or more of the identifier of the target UE, the identifier of the positioning UE, the positioning role of the UE involved in the sidelink positioning process, the identifier of the GMLC and the positioning service record type.

9. A billing method, comprising: The CHF network element receives the charging data request from the GMLC; The CHF network element generates a CDR related to a sidelink positioning procedure between the target UE and the positioning UE according to the charging data request.

10. The method according to claim 9, further comprising: The CHF network element sends the CDR to the charging domain via the charging gateway function CGF network element.

11. The method according to claim 9 or 10, further comprising: The CHF network element sends a charging data response to the GMLC.

12. A charging device, comprising: A module configured to execute the method according to any one of claims 1 to 8.

13. A charging device, comprising: Memory; as well as A processor coupled to the memory, configured to execute the method according to any one of claims 1 to 8 based on instructions stored in the memory.

14. A charging device, comprising: A module configured to execute the method according to any one of claims 9 to 11.

15. A charging device, comprising: Memory; as well as A processor coupled to the memory is configured to execute the method of any one of claims 9 to 11 based on instructions stored in the memory.

16. A billing system comprising: A gateway mobile location center, comprising the billing device according to claim 12 or 13; and The billing function network element comprises the billing device as described in claim 14 or 15.

17. A computer-readable storage medium comprising computer program instructions, wherein: When the computer program instructions are executed by a processor, the method according to any one of claims 1 to 11 is implemented.

Images