Communication method, and related apparatus

Abstract

The present application is applied to the technical field of communications. Provided are a communication method, and a related apparatus. In the embodiments of the present application, a first positioning service network element SU is deployed on an RAN side, so that positioning calculation is performed on the RAN side, and the first SU can directly exchange, on the RAN side, channel information with a first CU deployed on the RAN side. In this case, the channel information does not enter a core network, and thus positioning service localization is realized. During RAN localized positioning, the first SU directly interfaces with a gNB-CU, and the interaction between the first SU and the first CU does not need to be relayed by means of a first core network device, but the first SU can directly determine a serving CU of a first terminal, such that the first SU can determine which CU serves the first terminal, and thus when a service function network element on the RAN side is used for terminal positioning, the first SU can request a correct CU for a measurement configuration, thereby effectively ensuring the accuracy of the requested measurement configuration.

Description

Communication methods and related devices

[0001] This application claims priority to Chinese Patent Application No. 202410911592.6, filed on July 8, 2024, entitled "Communication Method and Related Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to communication methods and related devices. Background Technology

[0003] With the accelerated development of 5G industry digitalization, the demand for location services in complex indoor environments, such as warehousing and logistics, smart manufacturing, robot navigation, and hospital equipment management, is becoming increasingly strong, building upon outdoor positioning capabilities. Accurate positioning information can enhance the management of digital assets and personnel, improving production efficiency and the efficiency of managing people and materials.

[0004] Existing network services (including location services) are deployed in the core network. For location services, if they are based on AI algorithms, channel information (such as the H-channel matrix) may be required as input parameters. The calculation of the H-channel matrix is ​​a core capability of the base station. When the core network and the base station are from different manufacturers, the exchange of channel information between the base station manufacturer and the core network manufacturer is relatively difficult. In the case of a third-party manufacturer (such as a manufacturer that specializes in producing LMF network elements, which is different from both the base station manufacturer and the core network manufacturer), the exchange of channel information becomes even more difficult, thus causing the location service to become unavailable.

[0005] Therefore, how to successfully implement location services is a hot topic of research for those skilled in the art. Summary of the Invention

[0006] This application provides a communication method and related apparatus that can effectively ensure the accuracy of requested measurement configurations while realizing the localization of location services.

[0007] Firstly, this application provides a communication method that can be applied to the SU side, such as the SU or a communication module within the SU, or a circuit or chip within the SU responsible for communication functions (such as a modem chip, also known as a baseband chip, or a System-on-Chip (SoC) chip containing a modem core, or a System-in-Package (SIP) chip). Taking the application of this method to a first SU as an example, the method includes: determining a first access network communication element (CU) serving a first terminal; sending a measurement configuration request message about the first terminal to the first CU; and receiving measurement results about the first terminal from the first CU.

[0008] In this application, by deploying a first positioning service network element (SU) on the RAN side, positioning calculations are performed on the RAN side. The first SU can directly interact with the first CU deployed on the RAN side to exchange channel information. Since the channel information does not enter the core network in this case, localized positioning service is achieved. In RAN-localized positioning, the first SU directly interfaces with the gNB-CU. The interaction between the first SU and the first CU does not need to be relayed through the first core network equipment. Instead, the first SU can directly determine the serving CU of the first terminal, enabling the first SU to determine which CU the first terminal is serving. Therefore, when using the RAN-side service function network element for terminal positioning, the first SU can request measurement configuration from the correct CU, effectively ensuring the accuracy of the requested measurement configuration.

[0009] In one possible implementation of the first aspect, determining the first access network communication element (CU) serving the first terminal includes: obtaining the identification information of the first terminal and the identification information of the first CU from the first CU or the first core network device, wherein the first core network device serves the first terminal, and the identification information of the first terminal includes first identification information and second identification information of the first terminal. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the UE NsuAP ID of the first terminal on the interface Nsu of the first SU and the first core network device; the second identification information includes one or more of the UE SIAP ID of the first terminal on the interface SI between the first CU and the first SU, or the cell radio network temporary identification information (C-RNTI) of the first terminal under the first CU. Based on the identification information of the first terminal and the identification information of the first CU, it is determined that the first terminal is associated with the first CU.

[0010] In the above implementation, when the first SU subsequently receives a location request from the terminal, the first SU only knows which CU to send the measurement configuration request to and how to identify the terminal when sending the measurement configuration request if it knows the identification information of the first terminal and the identification information of the first CU. This solution can effectively ensure the accuracy of the requested measurement configuration while realizing the localization of the location service.

[0011] In another possible implementation of the first aspect, the method further includes: sending first information to a first core network device, wherein the first information is used to indicate that the first terminal is associated with the first SU, and the first information includes the TMSI information of the first terminal and the identification information of the first SU.

[0012] In the above embodiments, when the first core network device initiates a location request to the first SU, after the first terminal registers on the first SU, the TMSI information of the first terminal and the identification information of the first SU can be used to indicate that the first terminal has been registered on the first SU. That is, it indicates that the first terminal is associated with the first SU, so that the first core network device knows the association between the first terminal and the first SU, and can then send the location request to the correct first SU. In this way, while achieving localization of the location service, the accuracy of sending the location request to the correct network element can be effectively guaranteed.

[0013] In another possible implementation of the first aspect, the first information further includes the identification information UENsuAP ID of the first terminal on the interface Nsu of the first SU and the first core network device.

[0014] In another possible implementation of the first aspect, the method further includes: receiving an SI interface establishment request message or an SI interface update request message from the first CU; or sending an SI interface establishment request message or an SI interface update request message to the first CU and receiving an SI interface establishment response message or an SI interface update response message from the first CU.

[0015] In the above embodiments, if the connection relationship between the first terminal and the first CU remains unchanged, but the SI interface between the first CU and the first SU is newly established or updated, the CU with the newly established / updated SI interface or the core network equipment connected to this CU needs to promptly inform the SU which terminals are under this CU. This allows the SU to determine which CU the associated terminal is under its service, and thus request measurement configuration from the correct CU when performing terminal location.

[0016] In another possible implementation of the first aspect, the SI interface establishment request message or SI interface update request message or the SI interface establishment response message or SI interface update response message from the first CU carries the Transmission Receiver Point (TRP) information under the first CU, wherein the TRP information includes the identification information of the TRP and the location information of the TRP.

[0017] In the above implementation, TRP information is only carried when the first CU sends an SI interface establishment request message, SI interface update request message, SI interface establishment response message, or SI interface update response message to the first SU. The TRP information obtained by the first SU can be used to improve the positioning accuracy when performing terminal positioning in the future.

[0018] In another possible implementation of the first aspect, the method further includes: sending second information to the first core network device, wherein the second information is used to indicate the association relationship between the first CU and the first SU, and the second information includes the identification information of the first CU and the identification information of the first SU.

[0019] In the above implementation, the first core network device successfully learns the association between the first CU and the first SU, enabling it to send the terminal identification information under the CU to the correct SU, or to send a location request to the correct SU. This effectively ensures the accuracy of the location service.

[0020] Secondly, embodiments of this application provide a communication method. This method can be executed by a first CU, or by a component of the first CU, such as a processor, chip, or chip system of the first CU, or by a logic module or software capable of implementing all or part of the functions of the first CU. Taking the method being executed by the first CU as an example, the method includes: receiving a measurement configuration request message about a first terminal from a first access network serving element SU, and sending measurement results to the first SU.

[0021] In this application, by deploying a first positioning service network element (SU) on the RAN side, positioning calculations are performed on the RAN side. The first SU can directly interact with the first CU deployed on the RAN side to exchange channel information. Since the channel information does not enter the core network in this case, localized positioning service is achieved. In RAN-localized positioning, the first SU directly interfaces with the gNB-CU. The interaction between the first SU and the first CU does not need to be relayed through the first core network equipment. Instead, the first SU can directly determine the serving CU of the first terminal, enabling the first SU to determine which CU the first terminal is serving. Therefore, when using the RAN-side service function network element for terminal positioning, the first SU can request measurement configuration from the correct CU, effectively ensuring the accuracy of the requested measurement configuration.

[0022] In one possible implementation of the second aspect, the method further includes: sending an SI interface establishment request message or an SI interface update request message to the first SU; or receiving an SI interface establishment request message or an SI interface update request message from the first SU and sending an SI interface establishment response message or an SI interface update response message to the first SU.

[0023] In the above embodiments, if the connection relationship between the first terminal and the first CU remains unchanged, but the SI interface between the first CU and the first SU is newly established or updated, the CU with the newly established / updated SI interface or the core network equipment connected to this CU needs to promptly inform the SU which terminals are under this CU. This allows the SU to determine which CU the associated terminal is under its service, and thus request measurement configuration from the correct CU when performing terminal location.

[0024] In another possible implementation of the second aspect, the SI interface establishment request message or SI interface update request message or the SI interface establishment response message or SI interface update response message from the first CU carries the Transmission Receiver Point (TRP) information under the first CU, wherein the TRP information includes the identification information of the TRP and the location information of the TRP.

[0025] In the above implementation, TRP information is only carried when the first CU sends an SI interface establishment request message, SI interface update request message, SI interface establishment response message, or SI interface update response message to the first SU. The TRP information obtained by the first SU can be used to improve the positioning accuracy when performing terminal positioning in the future.

[0026] In another possible implementation of the second aspect, the method further includes: sending second information to the first core network device, wherein the second information is used to indicate the association relationship between the first CU and the first SU, and the second information includes the identification information of the first CU and the identification information of the first SU.

[0027] In the above implementation, the first core network device successfully learns the association between the first CU and the first SU, enabling it to send the terminal identification information under the CU to the correct SU, or to send a location request to the correct SU. This effectively ensures the accuracy of the location service.

[0028] In another possible implementation of the second aspect, the method further includes: sending the identification information of the first terminal and the identification information of the first CU to the first SU, wherein the identification information of the first terminal and the identification information of the first CU are used to indicate that the first terminal is associated with the first CU, the identification information of the first terminal includes first identification information and second identification information of the first terminal, the first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information (UENsuAP ID) of the first terminal on the interface (Nsu) between the first SU and the first core network equipment, the first core network equipment serving the first terminal; the second identification information includes the identification information (UE SIAP ID) of the first terminal on the interface (SI) between the first CU and the first SU, and one or more of the cell radio network temporary identification information (C-RNTI) of the first terminal under the first CU.

[0029] In the above implementation, the identification information of the first terminal and the identification information of the first CU can be sent from the first CU to the first SU. When the first SU subsequently receives a positioning request from the terminal, it only knows which CU to send the measurement configuration request to and how to identify the terminal when sending the measurement configuration request if it knows the identification information of the first terminal and the first CU. This solution can effectively ensure the accuracy of the requested measurement configuration while realizing the localization of positioning services.

[0030] In another possible implementation of the second aspect, before sending the identification information of the first terminal and the identification information of the first CU to the first SU, the method further includes: receiving the identification information of the first terminal from the first core network device.

[0031] In the above implementation, the first CU can receive the above information from the first core network device.

[0032] In another possible implementation of the second aspect, the method further includes: sending third information to a first core network device, wherein the first core network device serves the first terminal, the third information is used to indicate that the first terminal is associated with the first SU, the third information includes third identification information of the first terminal and identification information of the first SU, the third identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the UE NGAP ID of the first terminal on the interface NG of the first CU and the first core network device.

[0033] In the above implementation, the first terminal can be indicated by TMSI or UE NGAP ID.

[0034] In another possible implementation of the second aspect, the method further includes: sending the second identification information of the first terminal to the first core network device, wherein the second identification information includes one or more of the identification information UE SIAP ID of the first terminal on the interface SI between the first CU and the first SU, and the cell radio network temporary identification information C-RNTI of the first terminal under the first CU.

[0035] In the above implementation, since the first core network device needs to carry the second identification information of the first terminal when sending messages, this solution can indicate the second identification information of the first terminal to the first core network device.

[0036] Thirdly, embodiments of this application provide a communication method, which can be executed by a first core network device, or by a component of the first core network device, such as the processor, chip, or chip system of the first core network device, or by a logic module or software that can implement all or part of the functions of the first core network device. Taking the method executed by a first core network device as an example, the method includes: sending the identification information of a first terminal and the identification information of a first access network communication element (CU) to a first access network serving element (SU), wherein the first core network device serves the first terminal, and the identification information of the first terminal and the identification information of the first CU are used to indicate that the first terminal is associated with the first CU. The identification information of the first terminal includes first identification information and second identification information of the first terminal. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information UENsuAP ID of the first terminal on the interface Nsu of the first SU and the first core network device. The second identification information includes one or more of the identification information UESIAPID of the first terminal on the interface SI between the first CU and the first SU, or the temporary cell radio network identification information C-RNTI of the first terminal under the first CU.

[0037] In one possible implementation of the third aspect, the method further includes: receiving second information from the first SU or the first CU, wherein the second information is used to indicate the association between the first CU and the first SU, and the second information includes identification information of the first CU and identification information of the first SU.

[0038] In another possible implementation of the third aspect, the method further includes: receiving second identification information of the first terminal from the first CU.

[0039] Fourthly, embodiments of this application provide a communication method. This method can be executed by a first core network device, or by a component of the first core network device, such as a processor, chip, or chip system of the first core network device, or by a logic module or software capable of implementing all or part of the functions of the first core network device. Taking the method executed by the first core network device as an example, the method includes: receiving first information from a first access network serving element (SU) or receiving third information from a first access network communication element (CU), wherein the first core network device serves a first terminal, the first information is used to indicate that the first terminal is associated with the first SU, the first information includes the TMSI information of the first terminal and the identification information of the first SU, the third information is used to indicate that the first terminal is associated with the first SU, the third information includes the third identification information of the first terminal and the identification information of the first SU, the third identification information includes one or more of the TMSI information of the first terminal and the UE NGAP ID identification information of the first terminal on the interface NG of the first CU and the first core network device.

[0040] In one possible implementation of the fourth aspect, the first information further includes the identification information UENsuAP ID of the first terminal on the interface Nsu of the first SU and the first core network device.

[0041] In another possible implementation of the fourth aspect, the method further includes: receiving second information from the first SU or the first CU, wherein the second information is used to indicate the association between the first CU and the first SU, and the second information includes identification information of the first CU and identification information of the first SU.

[0042] Fifthly, embodiments of this application provide a communication device, which may be a first unit, a device in the first unit (e.g., a chip, a chip system, or a circuit), or a device that can be used in conjunction with the first unit, or a logic module or software that can implement all or part of the functions of the first unit.

[0043] In one possible implementation, the communication device may include modules or units that perform the methods / operations / steps / actions described in the first aspect. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0044] Sixthly, embodiments of this application provide a communication device, which may be a first CU, a device in the first CU (e.g., a chip, a chip system, or a circuit), a device that can be used in conjunction with the first CU, or a logic module or software that can implement all or part of the functions of the first CU.

[0045] In one possible implementation, the communication device may include modules or units that perform the methods / operations / steps / actions described in the second aspect one by one. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0046] In a seventh aspect, embodiments of this application provide a communication device, which may be a first core network device, or a device (e.g., a chip, a chip system, or a circuit) within the first core network device, or a device that can be used in conjunction with the first core network device, or a logic module or software that can implement all or part of the functions of the first core network device.

[0047] In one possible implementation, the communication device may include modules or units that perform the methods / operations / steps / actions described in the third or fourth aspect. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0048] Eighthly, embodiments of this application provide a communication device, which can be a standalone device, such as a first unit, or a component included in a standalone device, such as a chip, software module, or integrated circuit. The communication device may include at least one processor and a communication interface; the communication interface is used for inputting and / or outputting information, and the at least one processor is used to invoke a computer program stored in at least one memory to implement the method described in any of the embodiments of the first aspect.

[0049] In one possible implementation of the eighth aspect, the communication device further includes at least one of the aforementioned memories. Optionally, the memory and processor are integrated together.

[0050] Optionally, at least one processor in the communication device is configured to execute computer instructions to perform the following operations: determine a first access network communication element (CU) serving the first terminal; send a measurement configuration request message regarding the first terminal to the first CU; and receive measurement results regarding the first terminal from the first CU.

[0051] Optionally, the processor is further configured to: obtain the identification information of the first terminal and the identification information of the first CU from the first CU or the first core network device, wherein the first core network device serves the first terminal, and the identification information of the first terminal includes first identification information and second identification information of the first terminal; the first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information (UENsuAP ID) of the first terminal on the interface (Nsu) between the first SU and the first core network device; the second identification information includes one or more of the identification information (UESIAPID) of the first terminal on the interface (SI) between the first CU and the first SU, or the temporary cell radio network identification information (C-RNTI) of the first terminal under the first CU. Based on the identification information of the first terminal and the identification information of the first CU, it is determined that the first terminal is associated with the first CU.

[0052] Optionally, the processor is further configured to: send first information to a first core network device, wherein the first information is used to indicate that the first terminal is associated with the first SU, and the first information includes the TMSI information of the first terminal and the identification information of the first SU.

[0053] Optionally, the first information may also include the identification information UENsuAP ID of the first terminal on the interface Nsu of the first SU and the first core network device.

[0054] Optionally, the processor is further configured to: receive an SI interface establishment request message or an SI interface update request message from the first CU; or send an SI interface establishment request message or an SI interface update request message to the first CU and receive an SI interface establishment response message or an SI interface update response message from the first CU.

[0055] Optionally, the SI interface establishment request message or SI interface update request message or the SI interface establishment response message or SI interface update response message from the first CU carries the Transmission Receiver Point (TRP) information under the first CU, wherein the TRP information includes the identification information of the TRP and the location information of the TRP.

[0056] Optionally, the processor is further configured to: send second information to the first core network device, wherein the second information is used to indicate the association relationship between the first CU and the first SU, and the second information includes the identification information of the first CU and the identification information of the first SU.

[0057] Ninthly, embodiments of this application provide a communication device, which can be a standalone device, such as a first CU, or a component included in a standalone device, such as a chip, software module, or integrated circuit. The communication device may include at least one processor and a communication interface; the communication interface is used for inputting and / or outputting information, and the at least one processor is used to invoke a computer program stored in at least one memory to implement the method described in any of the embodiments of the first aspect.

[0058] In one possible implementation of the ninth aspect, the communication device further includes at least one of the aforementioned memories. Optionally, the memory and processor are integrated together.

[0059] Optionally, at least one processor in the communication device is configured to execute computer commands to perform the following operations: receive a measurement configuration request message from a first access network serving element (SU) regarding a first terminal; and send measurement results to the first SU.

[0060] Optionally, the processor is further configured to: send an SI interface establishment request message or an SI interface update request message to the first SU; or receive an SI interface establishment request message or an SI interface update request message from the first SU and send an SI interface establishment response message or an SI interface update response message to the first SU.

[0061] Optionally, the SI interface establishment request message or SI interface update request message or the SI interface establishment response message or SI interface update response message from the first CU carries the Transmission Receiver Point (TRP) information under the first CU, wherein the TRP information includes the identification information of the TRP and the location information of the TRP.

[0062] Optionally, the processor is further configured to: send second information to the first core network device, wherein the second information is used to indicate the association relationship between the first CU and the first SU, and the second information includes the identification information of the first CU and the identification information of the first SU.

[0063] Optionally, the processor is further configured to: send the identification information of the first terminal and the identification information of the first CU to the first SU, wherein the identification information of the first terminal and the identification information of the first CU are used to indicate that the first terminal is associated with the first CU, the identification information of the first terminal includes first identification information and second identification information of the first terminal, the first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information (UENsuAP ID) of the first terminal on the interface Nsu of the first SU and the first core network equipment, the first core network equipment serving the first terminal; the second identification information includes the identification information (UE SIAP ID) of the first terminal on the interface SI between the first CU and the first SU, and one or more of the cell radio network temporary identification information (C-RNTI) of the first terminal under the first CU.

[0064] Optionally, the processor is further configured to: receive identification information of the first terminal from the first core network device.

[0065] Optionally, the processor is further configured to: send third information to the first core network device, wherein the first core network device serves the first terminal, the third information is used to indicate that the first terminal is associated with the first SU, the third information includes third identification information of the first terminal and identification information of the first SU, the third identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the UE NGAP ID of the first terminal on the interface NG of the first CU and the first core network device.

[0066] Optionally, the processor is further configured to: send the second identification information of the first terminal to the first core network device, wherein the second identification information includes one or more of the identification information UE SIAP ID of the first terminal on the interface SI between the first CU and the first SU, and the cell radio network temporary identification information C-RNTI of the first terminal under the first CU.

[0067] In a tenth aspect, embodiments of this application provide a communication device, which can be a standalone device, such as a first core network device, or a component included in a standalone device, such as a chip, software module, or integrated circuit. The communication device may include at least one processor and a communication interface; the communication interface is used for inputting and / or outputting information, and the at least one processor is used to invoke a computer program stored in at least one memory to implement the method described in any of the embodiments of the first aspect.

[0068] In one possible implementation of the tenth aspect, the communication device further includes at least one of the aforementioned memories. Optionally, the memory and processor are integrated together.

[0069] Optionally, at least one processor in the communication device is configured to execute computer instructions to perform the following operations: sending identification information of a first terminal and identification information of a first access network communication element (CU) to a first access network serving element (SU), wherein the first core network device serves the first terminal, and the identification information of the first terminal and the identification information of the first CU are used to indicate that the first terminal is associated with the first CU. The identification information of the first terminal includes first identification information and second identification information of the first terminal. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information UENsuAP ID of the first terminal on the interface Nsu of the first SU and the first core network device. The second identification information includes one or more of the identification information UESIAPID of the first terminal on the interface SI between the first CU and the first SU, or the temporary identification information C-RNTI of the first terminal in the cell radio network under the first CU.

[0070] Optionally, the processor is further configured to: receive second information from the first SU or the first CU, wherein the second information is used to indicate the association relationship between the first CU and the first SU, and the second information includes the identification information of the first CU and the identification information of the first SU.

[0071] Optionally, the processor is further configured to: receive second identification information of the first terminal from the first CU.

[0072] Eleventhly, embodiments of this application provide a communication device, which can be a standalone device, such as a first core network device, or a component included in a standalone device, such as a chip, software module, or integrated circuit. The communication device may include at least one processor and a communication interface; the communication interface is used for inputting and / or outputting information, and the at least one processor is used to call a computer program stored in at least one memory to implement the method described in any of the embodiments of the first aspect.

[0073] In one possible implementation of the eleventh aspect, the communication device further includes at least one of the aforementioned memories. Optionally, the memory and processor are integrated together.

[0074] Optionally, at least one processor in the communication device is configured to execute a computer instruction to perform the following operations: receiving first information from a first access network serving element (SU) or receiving third information from a first access network communication element (CU), wherein the first core network device serves a first terminal, the first information is used to indicate that the first terminal is associated with the first SU, the first information includes the TMSI information of the first terminal and the identification information of the first SU, the third information is used to indicate that the first terminal is associated with the first SU, the third information includes the third identification information of the first terminal and the identification information of the first SU, the third identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the UE NGAP ID of the first terminal on the interface NG of the first CU and the first core network device.

[0075] Optionally, the first information may also include the identification information UENsuAP ID of the first terminal on the interface Nsu of the first SU and the first core network device.

[0076] Optionally, the processor is further configured to: receive second information from the first SU or the first CU, wherein the second information is used to indicate the association relationship between the first CU and the first SU, and the second information includes the identification information of the first CU and the identification information of the first SU.

[0077] In a twelfth aspect, embodiments of this application provide a communication device including a logic circuit and an interface, the logic circuit and the interface being coupled; the interface is used for inputting and / or outputting information, and the logic circuit is used for implementing the method described in any of the embodiments of the first to fourth aspects.

[0078] In one possible implementation of the twelfth aspect, the communication device is a chip or chip system.

[0079] In a thirteenth aspect, embodiments of this application provide a communication system comprising a first SU, a first CU, a first core network device, and at least one terminal, wherein the first SU, the first CU, the first core network device, and the at least one terminal are communicatively connected. The first SU is used to implement the method of any embodiment of the first aspect, the first CU is used to implement the method of any embodiment of the second aspect, and the first core network device is used to implement the method of any embodiment of the third to fourth aspects.

[0080] In a fourteenth aspect, embodiments of this application provide a communication system that includes the apparatus described in aspects five through seven.

[0081] In a fifteenth aspect, embodiments of this application provide a communication system comprising the apparatus described in aspects eight through twelfth.

[0082] In a sixteenth aspect, embodiments of this application provide a computer-readable storage medium for storing instructions or a computer program; when the instructions or the computer program are executed, the method of any one of the embodiments of the first to fourth aspects is implemented.

[0083] In a seventeenth aspect, this application provides a computer program product including computer instructions that, when executed on at least one processor, can implement the methods described in any of the first to fourth aspects or any possible implementations thereof. Exemplarily, the computer program product can be a software installation package, which can be downloaded and executed on a computing device when the aforementioned methods are required.

[0084] The beneficial effects of the technical solutions provided in aspects three to seventeen of this application can be referred to the beneficial effects of the technical solutions in aspects one and two, and will not be repeated here. Attached Figure Description

[0085] Figures 1a-1c are schematic diagrams of the architecture of a communication system provided in an embodiment of this application;

[0086] Figures 2a-2c are schematic diagrams of the architecture of an O-RAN system provided in an embodiment of this application;

[0087] Figure 3a is a schematic diagram of a service-oriented network structure provided in an embodiment of this application;

[0088] Figure 3b is a schematic diagram of an application scenario of a location service provided in an embodiment of this application;

[0089] Figure 3c is a schematic diagram of a 5G positioning network architecture in an existing protocol provided in an embodiment of this application;

[0090] Figure 3d is a general positioning flowchart provided in an embodiment of this application;

[0091] Figure 3e is a schematic diagram of a positioning method provided in an embodiment of this application;

[0092] Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0093] Figure 5a is a schematic diagram of the process of determining the first CU of the first terminal in a scenario where a CU is newly connected to the network or the target CU is switched, according to an embodiment of this application.

[0094] Figure 5b is a flowchart illustrating the process of determining the first CU of the first terminal in an application scenario of creating / updating the SI interface, provided by an embodiment of this application.

[0095] Figure 6 is a schematic diagram of the structure of a communication device 60 provided in an embodiment of this application;

[0096] Figure 7 is a schematic diagram of another communication device 70 provided in an embodiment of this application;

[0097] Figure 8 is a structural schematic diagram of another communication device 80 provided in an embodiment of this application;

[0098] Figure 9 is a structural schematic diagram of another communication device 90 provided in an embodiment of this application. Detailed Implementation

[0099] The system architecture of the embodiments of this application is described below with reference to the accompanying drawings.

[0100] Please refer to Figures 1a-1c, which are schematic diagrams of the architecture of a communication system provided in an embodiment of this application. As shown in Figures 1a-1c, the communication system includes a first access network serving element SU101, a first access network communication element CU102, a first core network device 103, a first terminal 104, a gateway mobile location center (GMLC) 105, a location management function (LMF) element 106, a location service client (LCS Client) 107, a distributed unit (DU) 108, and a radio unit (RU) 109. Optionally, the communication system may not include the first CU; the first CU can be replaced by a DU that interacts with the first SU. The first SU101, first CU102, DU108, and RU109 are classified as network elements in the access network RAN, and the first core network device 103 and LMF106 are classified as network elements in the core network CN. Optionally, the GMLC105 and LCS Client107 can be deployed in the core network or as devices that exist independently of the core network or access network.

[0101] As shown in Figure 1a, the LMF106 network element is indicated by a dashed box, signifying that information exchange in the architecture of Figure 1a can occur either without or through the LMF106 network element. Specifically, the first SU101 is directly connected to the core network CN bus, and the GMLC105 can request services from the first SU101 through the first core network device 103. Optionally, the interface between the first SU101 and the first core network device 103 can be defined as an Nsu interface, and the first SU101, as a network element deployed in the Radio Access Network (RAN), also directly interfaces with the first CU 102. Optionally, the interface between the first SU101 and the first CU 102 can be defined as a Si interface.

[0102] As shown in Figure 1b, the LMF106 network element is indicated by a dashed box, signifying that information exchange in the architecture of Figure 1b can be performed either without or through the LMF106 network element. Specifically, the first SU101 exposes a local API interface, directly connecting to the GMLC105 on the RAN side. Service generation and execution are both performed within a closed loop within the RAN. The connection method between the first SU101 and the core network in Figure 1b can be either connected or disconnected; this application does not impose any limitations on this.

[0103] As shown in Figure 1c, in the architecture of Figure 1c, the first SU101 is directly connected to the LMF106 network element. After the first SU101 receives the location service offloaded by the LMF106 network element, the first SU101 executes the services that the LMF106 network element is responsible for.

[0104] It should be noted that in each of the application scenarios illustrated in the above architecture diagrams, the first SU101 can be connected to the first CU102. The first SU101 and the first CU102 can be deployed in the same device (e.g., in an xNB) or deployed separately (for example, the first SU101 or the first CU102 can be configured to have more protocol layer functions, or the first SU101 or the first CU102 can be configured to have partial protocol layer processing functions. For example, some functions of the RLC layer and the protocol layer functions above the RLC layer can be set in the first SU101, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer can be set in the first CU102. Alternatively, the functions of the first SU101 or the first CU102 can be divided according to service type or other system requirements, such as by latency, setting functions that need to meet low latency requirements in the first CU102, and functions that do not need to meet this latency requirement in the first SU101). It should be understood that the above configuration of the first SU101 or the first CU102 is merely an example, and the functions of the first SU101 or the first CU102 can also be configured as needed. This application does not impose any limitations on this. In addition, some steps in the embodiments of this application may correspond to different scenarios. Please refer to the description in the embodiments. For steps without special description, it is assumed that they are applicable to three scenarios simultaneously.

[0105] In this embodiment of the application, the first SU101 and the first CU102 can be classified as network elements in the access network RAN.

[0106] In some examples, the first core network device 103 can be a standalone device or a network element deployed within a standalone device, such as an access and mobility management function (AMF) network element. Taking the first core network device 103 as an AMF network element as an example, the main uses of the AMF network element include: supporting the reception of location requests (location requests can be initiated by the terminal, the GMLC, or the AMF network element) and managing location requests; supporting LMF network element selection; supporting NRPPa to implement location-related interactions with 5G base stations (the next generation Node B, gNodeB); and transparently transmitting relevant location messages between LMF network elements, gNodeB, terminals, and other entities.

[0107] In this application embodiment, the terminal involved may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities. The terminal may also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., or a device used to provide voice or data connectivity to a user, or an Internet of Things (IoT) device. 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 (such as smartwatches, smart bracelets, pedometers, smart glasses, etc.), in-vehicle devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), satellite terminals, virtual reality (VR) devices, augmented reality (AR) devices, point-of-sale (POS) machines, customer-premises equipment (CPE), light user equipment (UE), reduced capability user equipment (REDCAP UE), wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. Terminal devices can also be vehicle devices, such as vehicle devices, vehicle modules, vehicle chips, on-board units (OBUs) or telematics boxes (T-BOXs). Terminal devices can also be other devices with terminal functions. For example, a terminal device can also be a device that performs terminal functions in D2D communication.

[0108] In some examples, the primary uses of the first terminal 104 include terminating the Lightweight Representation Protocol (LPP) to complete the interaction of positioning-related processes; supporting the reporting of terminal positioning capability information to the LMF106 network element; reporting positioning measurement results to the LMF106 network element with the assistance of the terminal or based on the LMF106 network element mode; and reporting positioning calculation results to the LMF106 network element based on the terminal mode.

[0109] In some examples, the GMLC105 serves as the operating platform for the location-based service system, primarily used to implement functions such as user data management, business data management, business contract information management, service provider (SP) data management and billing, and authentication for value-added service applications. Additionally, the GMLC105 is also used to process terminal location requests from the LCS client107, that is, to obtain the user's latitude and longitude information and return it to the LCS client107.

[0110] In some examples, the main uses of the LMF106 network element include: receiving and processing positioning requests or positioning-related data requests sent from the first core network device 103; sending positioning request results or related positioning data to the first core network device 103; selecting a positioning method (optionally, it can be a single simple positioning method or a mixed complex positioning method); controlling related positioning measurements based on different positioning methods; calculating positioning auxiliary data and sending it to the associated terminal (it should be noted that in the E-CID positioning method, the LMF106 network element does not need to calculate additional positioning auxiliary data); and calculating location information and estimating positioning accuracy.

[0111] In some examples, LCS Client107 is a logical functional entity, which can be an entity within the PLMN, such as an O&M tool; or an entity outside the PLMN, such as a third-party location server deployed outside the carrier. The LCS client is mainly used to initiate location request messages carrying parameters such as QoS, requesting to obtain the location information of one or more terminals.

[0112] In some examples, a DU is a logical node that carries the radio link control (RLC) layer, MAC layer, higher physical layer (PHY) layer, and other functions. In some examples, a DU can control at least one RU. The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0113] In some examples, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency chain (RF chain) processing. In some examples, the RU can be a 3GPPTRP, a remote radio head (RRH), or other similar functionalities. In some examples, the Low-PHY includes PHY processing functions such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more terminals via a wireless link.

[0114] Optionally, the method provided in this application embodiment can also be applied to an O-RAN system. Please refer to Figures 2a-2c, which are schematic diagrams of the architecture of an O-RAN system provided in this application embodiment. The O-RAN system may also include other components besides those shown in Figures 2a-2c, and this application does not limit this. It should be noted that all components in this O-RAN system support O-RAN functions.

[0115] As shown in Figure 2a, the LMF network element is indicated by a dashed box, signifying that information exchange in the architecture of Figure 2a can occur either without or through the LMF network element. The first SU is directly connected to the core network CN bus, and the GMLC can request services from the first SU through the first core network equipment. Optionally, the interface between the first SU and the first core network equipment can be defined as an Nsu interface, and the first SU, as a network element deployed in the radio access network RAN, also directly interfaces with the first CU. Optionally, the interface between the first SU and the first CU can be defined as a Si interface.

[0116] As shown in Figure 2b, the LMF network element is indicated by a dashed box, signifying that information exchange in the architecture of Figure 2b can be conducted either without or through the LMF network element. The first SU opens a local API interface, directly connecting to the GMLC on the RAN side. Service generation and execution are both closed-loop within the RAN. The connection method between the first SU and the core network in Figure 2b can be either connected or disconnected; this application does not impose any limitations on this.

[0117] As shown in Figure 2c, in the architecture of Figure 2c, the first SU is directly connected to the LMF network element. After the first SU receives the location service offloaded by the LMF network element, the first SU executes the service that the LMF network element is responsible for.

[0118] Optionally, an RIC (Intelligent Controller for O-RAN) is added to the architectures shown in Figures 2a-2c. The RIC collects network information and performs necessary optimization tasks. It communicates with the gNB via the E2 interface and can interface with both the gNB-CU and gNB-DU. Additionally, the RIC can communicate with the first SU via the Nz interface.

[0119] Optionally, the access network equipment shown in Figures 2a-2c can be an eNB or gNB or a next-generation access network equipment supporting O-RAN functionality, and supports CU-DU separation. The access network equipment communicates with the core network (CN) via a backhaul link and with terminals via an air interface. The BBU in the access network equipment communicates with the core network via a backhaul link, and the RU in the access network equipment communicates with at least one terminal via an air interface. The BBU communicates with at least one RU via a fronthaul link; the BBU and RU may or may not be co-located. The BBU includes at least one CU and at least one DU, which can communicate via at least one midhaul link.

[0120] Optionally, the DU and RU may or may not be co-located. The DU and RU exchange control plane information via a fronthaul link through a lower-layer split-control, user plane information (LLS-CUS) and synchronization interface. The LLS-CUS may include LLS-C and LLS-U interfaces that respectively provide the control plane (C-Plane) and user plane (U-Plane). In some examples, the control plane (C-Plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0121] Optionally, the DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways depending on the design. For example, the DU can be configured to implement baseband functions, and the RU can be configured to implement mid-RF functions. Alternatively, the DU can be configured to implement higher-level functions in the PHY layer, and the RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer may include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer may include another portion of the physical layer's functions that are closer to the mid-RF side.

[0122] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. The network device deployment methods listed here are only examples; as standard technologies evolve, network devices may have other deployment forms.

[0123] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions and network architectures provided in the embodiments of this application are also applicable to similar technical problems.

[0124] Please refer to Figure 3a, which is a schematic diagram of a service-based network structure provided in an embodiment of this application. As shown in Figure 3a, service-based architecture (SBA) is an important feature of 5G core network architecture, which divides network functions into reusable module "services". These "services" communicate using a unified lightweight interface. Its goal is to achieve high efficiency, software-defined architecture, and openness in 5G systems. In contrast, traditional 2G, 3G, and 4G network architectures use a "point-to-point" architecture, where interfaces between network elements need to be predefined and configured, and the defined interfaces can only be used between specific types of network elements, resulting in limited flexibility.

[0125] The characteristics of a service-oriented architecture include: (1) control plane network element decoupling. The functions of the original network elements are decoupled from each other, and the same functions are aggregated and presented in the form of network functions (NF).

[0126] (2) Service-oriented management. First, after a new NF comes online, it registers with the network repository function (NRF). Second, the NRF notifies surrounding NFs of the NF's information. Third, the surrounding NFs and the new NF interact using the communication method obtained in the second step.

[0127] (3) Unified interface. All service interfaces are implemented based on Hypertext Transfer Protocol Secure (HTTPS).

[0128] In addition, 3GPP defines the following services: Authentication Server Function (AUSF), AMF, Session Management Function (SMF), Network Repository Function (NRF), Policy Control Function (PCF), Unified Data Management (UDM), Network Exposure Function (NEF), etc.

[0129] With the accelerated development of 5G industry digitalization, in addition to outdoor positioning, the demand for location services is increasingly strong in complex indoor environments such as warehousing and logistics, intelligent manufacturing, robot navigation, and hospital equipment management, as shown in Figure 3b. Furthermore, 5G positioning is also widely used in location management in industries such as civil defense and fire protection, military training, campuses, transportation, and shopping malls, as shown in Table 1. Accurate location information can enhance the management of digital assets and personnel, improving production efficiency and the efficiency of personnel and material management.

[0130] Table 1

[0131] Figure 3c shows a schematic diagram of the 5G positioning network architecture in the existing protocol. The basic network architecture and process of 5G positioning are defined in 3GPP TS23.273. 5G positioning is achieved through cooperation among the UE, 5G access network, AMF network element, LMF network element, UDM, GMLC, and LCS Client.

[0132] The 5G positioning protocol is the NRPPa (NR Positioning Protocol A), which is the positioning protocol that terminates between the gNB and the LMF network element. The gNB and the LMF network element exchange positioning information based on the NRPPa positioning protocol, and the NRPPa protocol is transparently transmitted through the AMF network element.

[0133] Location service requests can be initiated through different network element modules, such as through the terminal or AMF network element itself, or indirectly through GMLC (e.g., handling location service requests initiated by LCS Clients). The specific location process is as follows (not shown in Figure 3c):

[0134] 1. When the location service request is initiated by the AMF network element (e.g., the AMF network element itself decides to enable the location service for certain UEs), proceed directly to the next step; when the location service is initiated by the UE, the location service request is sent to the gNodeB through the NR-Uu interface, and the gNodeB sends the location service request to the AMF network element through the N2 interface; when the location service request is initiated by the LCS Client, the location service request is sent to the GMLC through the Le interface, and the GMLC sends the location service request to the AMF network element through the NL2 interface.

[0135] 2. The AMF network element sends a location service request to the LMF network element through the NL1 interface.

[0136] 3. After receiving the location service request, the LMF network element sends location assistance data to the UE through the NL1, N2 and NR-Uu interfaces, and queries the UE or gNodeB for relevant measurements. After calculation, the final location result of the UE is obtained.

[0137] 4. The LMF network element returns the location result to the AMF network element through the NL1 interface. If the location function was initiated by the AMF network element, the process ends; otherwise, proceed to the next step.

[0138] 5. The AMF network element transmits the location result to the initiating entity, i.e., the UE or GMLC. When the location service request is initiated by the LCS Client, the GMLC then sends the calculated location information to the LCS Client that initiated the location request.

[0139] The general positioning flowchart is shown in Figure 3d. Specifically, the general positioning process is as follows:

[0140] 1. The initiator of the location service request can be a UE, GMLC, or AMF network element. The 3GPP protocol defines the following three types of positioning procedures:

[0141] 1a. MO-LR (Mobile Originated Location Request): The UE sends a relevant location service request to the serving AMF network element through NAS messages, such as requesting its own location information or requesting auxiliary data for a certain positioning method.

[0142] 1b. MT-LR (Mobile Terminated Location Request): GMLC sends a location service request for a specific UE, such as the UE's location information, to the serving AMF network element.

[0143] 1c. NI-LR (Network Induced Location Request): The location request originates from within the Public Land Mobile Network (PLMN) that is providing services to the mobile terminal. For example, an AMF network element needs to initiate an emergency call service to one of its UEs.

[0144] Taking the 1a Location Service Request scenario in the above process as an example, the detailed location flowchart is shown in Figure 3e, which will not be elaborated further in this application.

[0145] It should be noted that detailed location procedures for other types can be found in section 6, Location Service Procedures, of 3GPP protocol TS23.273, and will not be described in this application.

[0146] 2. The AMF network element sends a relevant location service request to the LMF network element.

[0147] 3. Optionally, the UE reports positioning capability information to the LMF network element.

[0148] 4. The LMF network element selects the positioning method based on the following factors: (1) Positioning QoS required by the application, including horizontal accuracy, latency, etc. (2) Positioning method configured by the LMF network element. (3) Positioning function activation flag of the cell where the UE is located. (4) Positioning capability of the UE.

[0149] 5. If the LMF network element determines that the gNodeB needs to participate in this positioning process, it will interact with the serving gNodeB where the target terminal is located to obtain positioning measurements or auxiliary data. If the LMF network element determines that the terminal needs to participate in this positioning process, it will interact with the UE through NAS messages to obtain location information, positioning measurements or auxiliary data, etc.

[0150] 6. The LMF network element sends the positioning result to the AMF network element, including success, failure, and error information.

[0151] 7. The AMF network element sends location results, defining the following three types of location results:

[0152] 7a. If 1a occurs, the AMF network element will transmit the positioning result to the UE.

[0153] 7b. If 1b occurs, the AMF network element will transmit the positioning result to the GMLC.

[0154] 7c. If 1c occurs, the AMF network element will transmit the location result to the relevant interface service.

[0155] Additionally, for example, taking multi-site positioning as an example, the specific steps may include: 1) The LMF network element requests measurement configuration from the serving gNB of the terminal; 2) The serving gNB of the terminal determines the measurement configuration and sends the measurement configuration to the UE; 3) The serving gNB of the terminal reports back to the LMF network element that the measurement configuration is complete, carrying the measurement configuration; 4) The LMF network element sends a measurement request to the gNBs near the terminal, carrying the measurement configuration information received in the previous step; 5) The gNBs near the terminal measure the uplink reference signal of the terminal on the resources indicated by the above measurement configuration information and return the measurement result to the LMF network element. Optionally, depending on the positioning algorithm selected by the LMF network element, the specific signal characteristics measured will differ. For example, the E-CID (Enhanced Cell ID) positioning algorithm requires distance and angle information between the terminal and the TRP of the gNB (e.g., the TRP can be the signal transmission and reception part of the gNB). As another example, the UL-TDOA (Uplink Time Difference of Arrival) positioning algorithm requires propagation delay information between the terminal and the TRPs of three gNBs. UL-TDOA is a multi-site positioning method, and the principle of this positioning method is shown in Figure 3e. In R19, we will study AI-based positioning technology, which requires accurate channel parameter information of the terminal, such as the H-channel matrix including terminal multipath information.

[0156] As the above examples illustrate, existing network service functions (including location services) are all deployed in the core network. For location services, if they are based on AI algorithms, channel information (such as the H-channel matrix) may be required as input parameters. The calculation of the H-channel matrix is ​​a core capability of the base station. When the core network and the base station are from different manufacturers, the base station manufacturer may be unwilling to report channel information to the core network manufacturer, or even to third-party manufacturers (such as manufacturers that specialize in producing LMF network elements, which are different from both the base station manufacturer and the core network manufacturer), resulting in the unavailability of the location service.

[0157] Generally, base station manufacturers are reluctant to report channel information to core network manufacturers or LMF (Local Modem) network element manufacturers. While introducing localized positioning services on the RAN (Radio Access Network) side theoretically requires support for inter-vendor interfaces, in practice, RAN-side interfaces are typically closed (e.g., the F1 interface between CU and DU, although standardized, is usually not open; while the NG interface between CU and AMF is always open), giving base station manufacturers a greater incentive to deploy positioning services. Furthermore, in the existing core network-based positioning architecture, the LMF network element sends measurement configuration to the terminal's serving gNB through the AMF network element. The LMF network element doesn't need to know the terminal's serving gNB; it only needs to interface with the AMF network element. Specifically, the serving terminal's AMF network element first locates the LMF network element, and subsequently, the LMF network element interacts with this AMF network element about the terminal's positioning information. The LMF network element and AMF network element identify the terminal through SUPI (Supplemental Interface Proportion). Then, the AMF network element determines the UE's serving gNB and interacts with the serving base station to exchange measurement configuration information, etc. In this approach, localized positioning services cannot be achieved.

[0158] In view of this, embodiments of this application provide a communication method and related apparatus, in which a positioning service network element (SU) is deployed on the RAN side, so that positioning calculations are performed on the RAN side and channel information does not enter the core network. In RAN localized positioning, the SU directly interfaces with the gNB-CU, and the interaction between the SU and the CU does not need to be relayed through the AMF network element. The SU can directly determine the UE's serving CU, enabling the SU to determine which CU the UE is serving. Thus, when using the RAN-side service function network element for terminal positioning, the SU can request measurement configuration from the correct CU.

[0159] In the communication method shown below (as shown in Figure 4), the specific descriptions of the SU, CU, and core network equipment can be found in Figures 1a to 1c, and will not be detailed here. For ease of description, specific examples in the embodiments of this application may be described using the first SU, the first CU, and the first core network equipment, but this should not be construed as a limitation on the embodiments of this application.

[0160] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0161] Please refer to Figure 4, which is a flowchart illustrating a communication method provided in an embodiment of this application. This flowchart describes the interaction of a first CU, a first SU, and a first core network device as the executing entities. The first CU or first SU can be a standalone device or a communication module within a standalone device, or a circuit or chip (such as a modem chip, also known as a baseband chip, or a System-on-Chip (SoC) chip containing a modem core, or a System-in-Package (SIP) chip) responsible for communication functions within a standalone device. The first core network device can be a satellite as a standalone device, or a component within a standalone device, such as a satellite processor, chip, or chip system, or a logic module or software capable of implementing all or part of the satellite's functions. Optionally, this method can be applied to a communication system, such as the communication system shown in Figures 1a-2c.

[0162] The communication method shown in Figure 4 may include multiple steps in steps S401-S404. It should be understood that this application describes the steps in the order of S401-S404 for ease of description, and is not intended to limit the execution to this order. This application's embodiments do not limit the order of execution, the execution time, or the number of executions of one or more of the above steps. Steps S401-S404 are as follows:

[0163] Step S401: The first SU obtains the identification information of the first terminal and the identification information of the first CU from the first CU or the first core network device.

[0164] Optionally, the first CU directly sends the identification information of the first terminal and the identification information of the first CU to the first SU (without requiring other devices to forward the above information).

[0165] Accordingly, the first SU obtains the identification information of the first terminal and the identification information of the first CU from the first CU. Optionally, the first SU can also obtain the identification information of the first terminal and the identification information of the first CU from the first core network device. Further optionally, the first SU can obtain them directly from the first core network device (i.e., without forwarding through other devices), or the first SU can obtain the identification information of the first terminal and the identification information of the first CU by first sending them to the first CU from the first core network device, and then forwarding them to the first SU from the first CU.

[0166] The identification information of the first terminal includes first identification information and second identification information of the first terminal. The identification information of the first terminal and the identification information of the first CU are used to indicate that the first terminal is associated with the first CU. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information (UENsuAP ID) of the first terminal on the interface (Nsu) between the first SU and the first core network equipment. The first core network equipment serves the first terminal. The second identification information includes one or more of the identification information (UE SIAP ID) of the first terminal on the interface (SI) between the first CU and the first SU and the cell radio network temporary identifier (C-RNTI) of the first terminal under the first CU.

[0167] In other words, the message sent by the first CU to the first SU with which it has an SI interface can carry the correspondence of three identification information items: {UE TMSI, UE C-RNTI and / or UE SIAP ID, CU's gNB ID and / or IP address}. That is, the first identification information of the first terminal includes UE TMSI and / or UE NsuAP ID, the second identification information of the first terminal includes UE SIAP ID and / or C-RNTI, and the identification information of the first CU includes CU's gNB ID and / or IP address.

[0168] Since the first core network device needs to carry the second identification information of the first terminal when sending messages, this scheme allows the first CU to indicate the second identification information of the first terminal to the first core network device. That is, the first CU sends the second identification information of the first terminal to the first core network device. Correspondingly, the first core network device receives the second identification information of the first terminal from the first CU.

[0169] The following are two examples of how the SU determines the serving CU of the UE:

[0170] Scenario 1: When the first terminal enters the network from the first CU, firstly, the first terminal completes the initial access procedure with the network, establishes an RRC connection, and sends an RRC establishment completion message to the first CU. This message carries the first terminal's TMSI information. Then, the first CU sends the first terminal's TMSI to the first core network equipment. Optionally, it also carries the C-RNTI assigned to the first terminal by the first CU and / or the SI interface identifier (UE SIAP ID) assigned to the first terminal by the first CU. This information is used by the first core network equipment to send to the first SU in subsequent steps, so that the first SU can determine which CU the first terminal is under the service of, and thus request measurement configuration from the correct CU when performing the first terminal location.

[0171] Scenario 2: When the first terminal switches from another CU to the first CU, firstly, the first terminal performs a handover procedure, accessing the target base station from the source base station. The first CU sends a path handover request message to the first core network device. This path handover request message instructs the first terminal to switch from the source base station to the target base station. The path handover request message carries NGIPD, which is used by the first core network device to index the first terminal. The first core network device sends a path handover confirmation message to the first CU. Optionally, the path handover request message also carries the C-RNTI assigned to the first terminal by the first CU and / or the SI interface identifier (UE SI AP ID) assigned to the first terminal by the first CU. This information is used by the first core network device to send to the first SU in subsequent steps, so that the first SU can determine which CU the first terminal is serving, and thus request measurement configuration from the correct CU when performing the first terminal location.

[0172] Step S402: The first SU determines the first access network communication element CU serving the first terminal.

[0173] As one possible implementation, the first SU determines that the first terminal is associated with the first CU based on the identification information of the first terminal and the identification information of the first CU.

[0174] For ease of understanding, two possible implementations for identifying the first terminal and the first CU are provided below as examples, as follows:

[0175] In Implementation Method 1, the identification information of the first CU includes the gNB ID and / or the CU's IP address information. The first CU can be identified through the gNB ID and / or the CU's IP address. Since only the gNB knows the terminal's TMSI during initial access, and the TMSI is generally maintained between the terminal and the core network, it is only visible to the gNB during initial access. The gNB does not store the terminal's TMSI, and the source base station does not transmit the UE TMSI to the target base station during handover. Therefore, the TMSI is only needed during initial access. In the initial access scenario, when the first SU receives a location request from the GMLC or the first core network device, it can identify the first terminal through the TMSI. In summary, this scheme can identify the first CU and the first terminal through a combination of the gNB ID and / or IP address and the TMSI.

[0176] In the second implementation, the identification information of the first CU includes the gNB ID and / or the CU's IP address information, which can be used to indicate the first CU. Alternatively, the first terminal can be directly identified by the UE SIAP ID, which is identifiable by the first SU. Or, the first SU can send a measurement configuration request message to the first CU based on the CU's gNB ID. This measurement configuration request message carries the C-RNTI, which is identifiable by the first CU. In this case, although the first SU cannot directly identify the C-RNTI, it can correctly indicate the first terminal to the first CU using the combination of the CU's gNB ID and the C-RNTI. In summary, this solution can identify the first CU and the first terminal using a combination of the gNB ID and / or IP address and the UE SIAP ID, or it can identify the first CU and the first terminal using the gNB ID and / or IP address, the CU's gNB ID, and the C-RNTI.

[0177] Through the correspondence of the above identification information, the first SU can know which CU to send the measurement configuration request to when it receives the positioning request of the first terminal, that is, to determine the first CU serving the first terminal and how to identify the first terminal when sending the measurement configuration request.

[0178] When the first terminal enters the network from the first CU, the first CU needs to register the first terminal with the first SU so that the first SU can determine which CU the first terminal is under the service of, so that when locating the first terminal, it can send a measurement configuration request to the correct CU.

[0179] Referring to Figure 1a, the first SU or the first CU can further send a message to the first core network device, indicating on which SU the first terminal is registered on, so that the first core network device can know which SU can provide services to the first terminal before sending a location request to the first SU, and thus be able to send a location request to the correct SU.

[0180] As one possible implementation, the first SU sends first information to the first core network device.

[0181] Accordingly, the first core network device receives the first information.

[0182] The first information is used to indicate that the first terminal is associated with the first SU. This first information includes the TMSI information of the first terminal and the identification information of the first SU. Since the first SU has not previously interacted with the first core network equipment regarding the first terminal, and the only UE ID that both the first SU and the first core network equipment can recognize is the TMSI, the first information must carry the TMSI information of the first terminal. Additionally, the first information also needs to include the identification information of the first SU, so that the first core network equipment can know which SU can provide services to the first terminal before sending a location request to the first SU, and thus can send the location request to the correct SU. Optionally, the identification information of the first SU may include the SU ID and / or the SU's IP address information, which can be used to indicate the first SU.

[0183] Optionally, the first SU can also assign an NsuAP ID to the first terminal. That is, the first information also includes the UE NsuAP ID, the identifier of the first terminal on the Nsu interface between the first SU and the first core network equipment. Since the Nsu interface is defined as the interface between the first SU and the first core network equipment, the first CU, unaware of the Nsu interface, does not consider using the UE NsuAP ID as the identifier of the first terminal. This is only applicable when the GMLC or AMF network element initiates a location request to the SU and identifies the first terminal using the TMSI. However, when the first core network equipment initiates a location request to the first SU, the first terminal can still be identified using the UE NsuAP ID.

[0184] As one possible implementation, the first CU sends third information to the first core network device.

[0185] The third information is used to indicate that the first terminal is associated with the first SU. This third information includes the third identification information of the first terminal and the identification information of the first SU. Since the first CU has previously exchanged information about the first terminal with the first core network equipment, it can directly use the UE NGAP ID or the TMSI. Therefore, the third identification information includes one or more of the TMSI of the first terminal and the UE NGAP ID, the identification information of the first terminal on the interface NG between the first CU and the first core network equipment. Optionally, the identification information of the first SU may include the SU ID and / or the SU's IP address information, which can indicate the first SU.

[0186] Step S403: The first SU sends a measurement configuration request message about the first terminal to the first CU.

[0187] Accordingly, the first CU receives a measurement configuration request message for the first terminal.

[0188] Step S404: The first CU sends the measurement results about the first terminal to the first SU.

[0189] Accordingly, the first SU receives the measurement result.

[0190] In some examples, the connection between the terminal and the CU may remain unchanged, but the CU and SU may experience the creation or updating of the SI interface. For instance, in a vehicle-mounted mobile relay (VMR) scenario, the CU is deployed on a vehicle and moves with it, potentially approaching different SUs at different times, requiring the creation, removal, and configuration updates of SI interfaces. When a new SI interface is created, the CU with the newly created / updated SI interface to the SU, or the core network equipment connected to that CU, must also inform the SU which terminals are connected to that CU. This process generally occurs when a new SI interface is created, but it is not limited to scenarios where only SI interface creation occurs; it may also occur in scenarios where SI interface updates occur. This application does not impose any limitations on this. In the scenario of creating / updating the SI interface, the creation / updating of the SI interface can be initiated by either the CU or the SU; this application also does not impose any limitations on this.

[0191] As one possible implementation, the first CU sends an SI interface establishment request message or an SI interface update request message to the first SU.

[0192] In one possible implementation, the first CU receives an SI interface establishment request message or an SI interface update request message from the first SU, and sends an SI interface establishment response message or an SI interface update response message to the first SU.

[0193] Optionally, the SI interface establishment request message or SI interface update request message from the first CU, or the SI interface establishment response message or SI interface update response message from the first CU, carries Transmitter Receiver Point (TRP) information under the first CU. For example, the TRP information includes the TRP's identification information and the TRP's location information.

[0194] In one possible implementation, the first CU sends the second information to the first core network device.

[0195] The second information is used to indicate the association between the first CU and the first SU, and the second information includes the identification information of the first CU and the identification information of the first SU.

[0196] Optionally, the first CU sends the identification information of the first SU with which it has an SI interface to the first core network device it is connected to; or, the first SU sends the identification of the CU with which it has an SI interface to the first core network device it is connected to, thereby enabling the first core network device to send the identification information of the terminal under the CU to the correct SU, or enabling the first core network device to send a location request to the correct SU. After the first SU learns the association between the first terminal and the first CU, it is able to send a measurement request message to the correct first CU when locating the first terminal. Further optionally, the identification of the first CU can be represented by the CU's gNB ID and / or the CU's IP address, and the identification of the first SU can be represented by the first SU's SU ID and / or the SU's IP address.

[0197] Accordingly, the first core network device receives second information from the first SU or the first CU.

[0198] For example, AMF#1 is connected to CU#1, SU#1 has an SI interface with CU#1, and SU#1 is also connected to AMF#1. CU#1 sends the identification information of SU#1 to AMF#1, or SU#1 sends the identification information of CU#1 to AMF#1, thereby enabling AMF#1 to send the identification information of the terminal under CU#1 to SU#1, or AMF#1 can send a positioning request to SU#1, so that when the first SU positions the first terminal, it can correctly send a measurement request message to CU#1.

[0199] When a new SI interface is created / updated, the CU that creates the new SI with the SU, or the core network equipment connected to that CU, needs to promptly inform the SU which terminals are under that CU. Therefore, alternatively, in the case of a new / updated SI interface, the first CU or the first core network equipment can send the identification information of each terminal under the first CU to the first SU.

[0200] When a new SI interface is created or updated, the CU that has a new / updated SI interface with the SU or the core network equipment connected to the CU informs the SU which terminals are under this CU. The subsequent steps can be referred to steps S401-S404, which will not be elaborated here.

[0201] In this application, by deploying a first positioning service network element (SU) on the RAN side, positioning calculations are performed on the RAN side. The first SU can directly interact with the first CU deployed on the RAN side to exchange channel information. Since the channel information does not enter the core network in this case, localized positioning service is achieved. In RAN-localized positioning, the first SU directly interfaces with the gNB-CU. The interaction between the first SU and the first CU does not need to be relayed through the first core network equipment. Instead, the first SU can directly determine the serving CU of the first terminal, enabling the first SU to determine which CU the first terminal is serving. Therefore, when using the RAN-side service function network element for terminal positioning, the first SU can request measurement configuration from the correct CU, effectively ensuring the accuracy of the requested measurement configuration.

[0202] The embodiment shown in Figure 4 provides a detailed explanation of the interaction principle between the first SU and the first CU. To facilitate understanding, Figures 5a and 5b are used to illustrate two specific cases in which the first SU determines the first CU serving the first terminal in different application scenarios.

[0203] Please refer to Figure 5a. Figure 5a is a flowchart illustrating the process by which the first SU determines the first CU serving the first terminal in a scenario where a CU is newly joining the network or switching target CUs, according to an embodiment of this application. It should be understood that, for ease of description, this application describes the process in the order of steps 11-17, and does not intend to limit the execution to this specific order. This application embodiment does not limit the order of execution, execution time, or number of executions of one or more of the above steps. As shown in Figure 5a, the specific steps of Case 1 are as follows:

[0204] Step 11: The first terminal sends an RRC establishment complete message to the first CU.

[0205] The RRC establishment completion message carries the TMSI of the first terminal.

[0206] It should be noted that carrying the TMSI in step 11 only applies to scenarios where a CU is newly joining the network. This is because only the base station at the time of initial access will know the terminal's TMSI. Generally, the TMSI is maintained between the terminal and the core network and is only visible to the base station during initial access. The base station does not save the terminal's TMSI, so when the terminal switches connections with the CU, the source base station will not transmit the terminal's TMSI to the target base station. Therefore, the requirement to carry the TMSI in the RRC establishment completion message in step 11 is only applicable to scenarios where a CU is newly joining the network.

[0207] Step 12: The first SU obtains the identification information of the first terminal and the identification information of the first CU from the first CU or the first core network device.

[0208] The identification information of the first terminal and the identification information of the first CU are used to indicate that the first terminal is associated with the first CU. The identification information of the first terminal includes the first identification information and the second identification information of the first terminal. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information (UENsuAP ID) of the first terminal on the interface (Nsu) between the first SU and the first core network equipment. The second identification information includes one or more of the identification information (UESIAPID) of the first terminal on the interface (SI) between the first CU and the first SU, or the temporary identification information (C-RNTI) of the cell radio network under the first CU.

[0209] As one possible implementation, the first core network device sends the identification information of the first terminal to the first SU through the first CU.

[0210] That is, the first core network device sends the identification information of the first terminal to the first CU, and the first CU forwards the identification information of the first terminal and the identification information of the first CU to the first SU.

[0211] Accordingly, the first SU receives the identification information of the first terminal and the identification information of the first CU from the first CU.

[0212] As one possible implementation, the first core network device directly sends the identification information of the first terminal to the first SU.

[0213] Accordingly, the first SU receives the identification information of the first terminal and the identification information of the first CU from the first core network device.

[0214] It should be noted that in step 12, the first identification information does not include the scheme where the first CU registers the first terminal with the first SU using the UENsuAP ID (e.g., denoted as opt1). The first identification information includes the scheme where the first core network device registers the terminal with the first SU using the UENsuAP ID (e.g., denoted as opt2). The difference between opt2 and opt1 is that, in addition to the UE TMSI, both schemes can use the UE NsuAP ID as the terminal identifier. Because the Nsu interface is defined as the interface between the first SU and the first core network device, but the first CU is unaware of this interface, Opt1 does not consider using the UE NsuAP ID as the terminal identifier. Therefore, Opt1 is only applicable to the scheme where the terminal is identified by the TMSI when the GMLC or the first core network device initiates a location request to the first SU. However, Opt2 adds the option of UE NsuAP ID and is also applicable to the scheme where the UE NsuAP ID is used to identify the UE when the first core network device initiates a location request to the first SU.

[0215] Step 13: The first SU determines that the first terminal is associated with the first CU based on the identification information of the first terminal and the identification information of the first CU.

[0216] Step 14: The first SU sends the first information to the first core network device.

[0217] The first core network device serves the first terminal, and the first information is used to indicate that the first terminal is associated with the first SU. The first information includes the TMSI information of the first terminal (e.g., represented as UE TMSI) and the identification information of the first SU (e.g., represented as SU ID).

[0218] Optionally, the first information also includes the identification information UENsuAP ID of the first terminal on the interface Nsu between the first SU and the first core network device. As a possible implementation, in some scenarios, an alternative to step 14 could be that the first CU sends third information to the first core network device. If step 14 is executed, it means that the scheme of "the first CU sending third information to the first core network device" is not executed, and vice versa.

[0219] The third information is used to indicate that the first terminal is associated with the first SU. The third information includes the third identification information of the first terminal and the identification information of the first SU (e.g., represented as SU ID). The third identification information includes the TMSI of the first terminal and one or more of the identification information UE NGAP ID of the first terminal on the interface NG of the first CU and the first core network equipment.

[0220] Step 15: The first core network device sends a location request for the first terminal to the first SU. Correspondingly, the first SU receives the location request from the first core network device.

[0221] Step 16: The first SU sends a measurement configuration request message about the first terminal to the first CU.

[0222] Accordingly, the first CU receives a measurement configuration request message for the first terminal.

[0223] Step 17: The first CU sends the measurement results about the first terminal to the first SU.

[0224] Accordingly, the first SU receives the measurement results about the first terminal.

[0225] Please refer to Figure 5b. Figure 5b is a flowchart illustrating the process of determining the first CU of the first terminal in an application scenario of creating / updating the SI interface, as provided in an embodiment of this application. As shown in Figure 5b, the specific steps of Case 2 are as follows:

[0226] Step 21: The first CU sends an SI interface establishment request message or an SI interface update request message to the first SU.

[0227] Accordingly, the first SU receives the SI interface establishment request message or the SI interface update request message.

[0228] Optionally, the first SU sends an SI interface establishment request message or an SI interface update request message to the first CU, and the first SU receives an SI interface establishment response message or an SI interface update response message from the first CU.

[0229] Optionally, the SI interface establishment request message or SI interface update request message from the first CU, or the SI interface establishment response message or SI interface update response message from the first CU, carries the Transmission Receiver Point (TRP) information under the first CU.

[0230] The TRP information includes the TRP's identification information and the TRP's location information.

[0231] Step 22: The first SU sends the second information to the first core network device.

[0232] The second information is used to indicate the association between the first CU and the first SU. The second information includes the identification information of the first CU and the identification information of the first SU (e.g., represented as CU ID and SU ID).

[0233] Optionally, the second information received by the first core network device may originate from the identification information of the first SU with which it has an SI interface, sent by the first CU to the connected first core network device. Alternatively, the second information received by the first core network device may also originate from the identification of the CU with which it has an SI interface, sent by the first SU to the connected first core network device. This enables the first core network device to send the identification information of the terminal under the CU to the correct SU, or to send a location request to the correct SU. After the first SU learns the association between the first terminal and the first CU, it can send a measurement request message to the correct first CU when locating the first terminal. Further optionally, the identification of the first CU can be represented by the CU's gNB ID and / or the CU's IP address, and the identification of the first SU can be represented by the first SU's SU ID and / or the SU's IP address.

[0234] Step 23: The first SU obtains the identification information of the first terminal and the identification information of the first CU from the first CU or the first core network device.

[0235] The identification information of the first CU can be represented as CU ID. The identification information of the first terminal includes the first identification information and the second identification information of the first terminal. The first identification information includes the temporary mobile station identification information TMSI of the first terminal (e.g., represented as UE TMSI) and one or more of the identification information UENsuAP ID of the first terminal on the interface Nsu of the first SU and the first core network equipment. The second identification information includes the identification information UESIAPID of the first terminal on the interface SI between the first CU and the first SU, or one or more of the temporary identification information C-RNTI of the cell radio network under the first CU.

[0236] Step 24: The first SU determines that the first terminal is associated with the first CU based on the identification information of the first terminal and the identification information of the first CU.

[0237] Step 25: The first SU sends the first information to the first core network device.

[0238] The first core network device serves the first terminal, and the first information is used to indicate that the first terminal is associated with the first SU. The first information includes the TMSI information of the first terminal (e.g., represented as UE TMSI) and the identification information of the first SU (e.g., represented as SU ID).

[0239] Optionally, the first information also includes the identification information UENsuAP ID of the first terminal on the interface Nsu between the first SU and the first core network device. As a possible implementation, in some scenarios, an alternative to step 25 could be that the first CU sends third information to the first core network device. If step 25 is executed, it means that the scheme of "the first CU sending third information to the first core network device" is not executed, and vice versa.

[0240] The third information is used to indicate that the first terminal is associated with the first SU. The third information includes the third identification information of the first terminal and the identification information of the first SU (e.g., represented as SU ID). The third identification information includes the TMSI of the first terminal and one or more of the identification information UE NGAP ID of the first terminal on the interface NG of the first CU and the first core network equipment.

[0241] Step 26: The first core network device sends a location request for the first terminal to the first SU.

[0242] Step 27: The first SU sends a measurement configuration request message about the first terminal to the first CU.

[0243] Accordingly, the first CU receives a measurement configuration request message for the first terminal.

[0244] Step 28: The first CU sends the measurement results about the first terminal to the first SU.

[0245] Accordingly, the first SU receives the measurement results about the first terminal.

[0246] It should be noted that detailed explanations of steps 11-17 and 21-28 above can be found in the embodiment shown in Figure 4, and will not be repeated here.

[0247] The methods of the embodiments of this application have been described in detail above. The apparatus of the embodiments of this application is provided below.

[0248] It should be understood that the division of units in the apparatus provided in this application embodiment is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units in the apparatus can be implemented by a processor calling software. For example, the apparatus includes a processor connected to a memory, which stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of each unit of the apparatus. The processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is either internal or external to the apparatus.

[0249] Alternatively, the units in the device can be implemented as hardware circuits. The functionality of some or all of the units can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the above units is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the above units.

[0250] In the embodiments of this application, each unit in the device may be one or more processors (or processing circuits) configured to implement the above methods, such as: CPU, graphics processing unit (GPU), neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), microprocessor unit (MPU), digital signal processor (DSP), ASIC, FPGA, or a combination of at least two of these processor forms.

[0251] Furthermore, the units in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units are integrated together as a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or for implementing the functions of the units in the device. The at least one processor can be of different types, such as including a CPU and an FPGA, or including a CPU and an AI processor, or including a CPU and a GPU, etc. Several possible devices are listed below.

[0252] Please refer to Figure 6, which is a schematic diagram of the structure of a communication device 60 provided in an embodiment of this application. Optionally, the communication device 60 can be a standalone device, such as a first unit (SU). Alternatively, the communication device 60 can also be a component within a standalone device (such as a first SU), such as a chip or integrated circuit. The communication device 60 is used to implement the aforementioned communication method, such as the communication method shown in Figure 4.

[0253] In one possible design, the communication device 60 includes a processing unit 601 and a communication unit 602. The communication device 60 is used to implement the aforementioned communication method, such as the communication method shown in FIG. 4. Exemplarily, the communication device is used, for example, to execute a method performed by the first SU.

[0254] In one possible implementation, the processing unit 601 is configured to determine a first access network communication element (CU) serving the first terminal. The communication unit 602 is configured to send a measurement configuration request message about the first terminal to the first CU, and the communication unit 602 is also configured to receive measurement results about the first terminal from the first CU.

[0255] In another possible implementation, regarding the determination of the first access network communication element (CU) serving the first terminal, the processing unit 601 is specifically configured to: obtain the identification information of the first terminal and the identification information of the first CU from the first CU or the first core network device, wherein the first core network device serves the first terminal, and the identification information of the first terminal includes first identification information and second identification information of the first terminal. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information (UENsuAP ID) of the first terminal on the interface (Nsu) between the first SU and the first core network device; the second identification information includes one or more of the identification information (UESIAPID) of the first terminal on the interface (SI) between the first CU and the first SU, or the temporary cell radio network identification information (C-RNTI) of the first terminal under the first CU. Based on the identification information of the first terminal and the identification information of the first CU, it is determined that the first terminal is associated with the first CU.

[0256] In another possible implementation, the communication unit 602 is further configured to send first information to the first core network device, wherein the first information is used to indicate that the first terminal is associated with the first SU, and the first information includes the TMSI information of the first terminal and the identification information of the first SU.

[0257] In another possible implementation, the first information may also include the identification information UENsuAP ID of the first terminal on the interface Nsu of the first SU and the first core network device.

[0258] In another possible implementation, the communication unit 602 is further configured to receive an SI interface establishment request message or an SI interface update request message from the first CU. Alternatively, the communication unit 602 is further configured to send an SI interface establishment request message or an SI interface update request message to the first CU, and receive an SI interface establishment response message or an SI interface update response message from the first CU.

[0259] In another possible implementation, the SI interface establishment request message or SI interface update request message or the SI interface establishment response message or SI interface update response message from the first CU carries the Transmission Receiver Point (TRP) information under the first CU, wherein the TRP information includes the identification information of the TRP and the location information of the TRP.

[0260] In another possible implementation, the communication unit 602 is further configured to send second information to the first core network device, wherein the second information is used to indicate the association relationship between the first CU and the first SU, and the second information includes the identification information of the first CU and the identification information of the first SU.

[0261] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0262] Please refer to Figure 7, which is a schematic diagram of another communication device 70 provided in an embodiment of this application. Optionally, the communication device 70 can be an independent device, such as a first CU. Alternatively, the communication device 70 can also be a component in an independent device (such as a first CU), such as a chip or integrated circuit. The communication device 70 is used to implement the aforementioned communication method, such as the communication method shown in Figure 4.

[0263] In one possible design, the communication device 70 includes a communication unit 701 and a processing unit 702. The communication device 70 is used to implement the aforementioned communication method, such as the communication method shown in FIG. 4. Exemplarily, the communication device is used, for example, to execute a method executed by the first CU.

[0264] In one possible implementation, the communication unit 701 is configured to receive a measurement configuration request message about the first terminal from the first access network serving element (SU), and the communication unit 701 is further configured to send measurement results to the first SU. The processing unit 702 is configured to process the transmitted and received data.

[0265] In another possible implementation, the communication unit 701 is further configured to send an SI interface establishment request message or an SI interface update request message to the first SU. Alternatively, the communication unit 701 is further configured to receive an SI interface establishment request message or an SI interface update request message from the first SU, and send an SI interface establishment response message or an SI interface update response message to the first SU.

[0266] In another possible implementation, the SI interface establishment request message or SI interface update request message or the SI interface establishment response message or SI interface update response message from the first CU carries the Transmission Receiver Point (TRP) information under the first CU, wherein the TRP information includes the identification information of the TRP and the location information of the TRP.

[0267] In another possible implementation, the communication unit 701 is further configured to send second information to the first core network device, wherein the second information is used to indicate the association relationship between the first CU and the first SU, and the second information includes the identification information of the first CU and the identification information of the first SU.

[0268] In another possible implementation, the communication unit 701 is further configured to send the identification information of the first terminal and the identification information of the first CU to the first SU, wherein the identification information of the first terminal and the identification information of the first CU are used to indicate that the first terminal is associated with the first CU. The identification information of the first terminal includes first identification information and second identification information of the first terminal. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information (UENsuAP ID) of the first terminal on the interface Nsu of the first SU and the first core network equipment, wherein the first core network equipment serves the first terminal. The second identification information includes one or more of the identification information (UE SIAP ID) of the first terminal on the interface SI between the first CU and the first SU and the cell radio network temporary identification information (C-RNTI) of the first terminal under the first CU.

[0269] In another possible implementation, the communication unit 701 is further configured to receive identification information of the first terminal from the first core network device.

[0270] In another possible implementation, the communication unit 701 is further configured to send third information to the first core network device, wherein the first core network device serves the first terminal, the third information is used to indicate that the first terminal is associated with the first SU, and the third information includes third identification information of the first terminal and identification information of the first SU. The third identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the UE NGAP ID of the first terminal on the interface NG of the first CU and the first core network device.

[0271] In another possible implementation, the communication unit 701 is further configured to send the second identification information of the first terminal to the first core network device, wherein the second identification information includes one or more of the identification information UE SIAP ID of the first terminal on the interface SI between the first CU and the first SU, and the cell radio network temporary identification information C-RNTI of the first terminal under the first CU.

[0272] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0273] Please refer to Figure 8, which is a schematic diagram of another communication device 80 provided in an embodiment of this application. Optionally, the communication device 80 can be an independent device, such as a first core network device. Alternatively, the communication device 80 can also be a component within an independent device (such as a first core network device), such as a chip or integrated circuit. The communication device 80 is used to implement the aforementioned communication method, such as the communication method shown in Figure 4.

[0274] In one possible design, the communication device 80 includes a communication unit 801 and a processing unit 802. The communication device 80 is used to implement the aforementioned communication method, such as the communication method shown in FIG4. Exemplarily, the communication device is used, for example, to execute a method performed by a first core network device.

[0275] In one possible implementation, the communication unit 801 is used to send the identification information of the first terminal and the identification information of the first access network communication element CU to the first access network serving network element SU, wherein the first core network equipment serves the first terminal, and the identification information of the first terminal and the identification information of the first CU are used to indicate that the first terminal is associated with the first CU. The identification information of the first terminal includes first identification information and second identification information of the first terminal. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information UENsuAP ID of the first terminal on the interface Nsu of the first SU and the first core network equipment. The second identification information includes one or more of the identification information UESIAPID of the first terminal on the interface SI between the first CU and the first SU, or the temporary radio network identification information C-RNTI of the first terminal under the first CU. The processing unit 802 is used to process the transmitted and received data.

[0276] In another possible implementation, the communication unit 801 is further configured to receive second information from the first SU or the first CU, wherein the second information is used to indicate the association between the first CU and the first SU, and the second information includes the identification information of the first CU and the identification information of the first SU.

[0277] In another possible implementation, the communication unit 801 is further configured to receive second identification information of the first terminal from the first CU.

[0278] In another possible design, the communication device 80 includes a communication unit 801 and a processing unit 802. The communication device 80 is used to implement the aforementioned communication method, such as the communication method shown in FIG4. Exemplarily, the communication device is used, for example, to execute a method performed by a first core network device.

[0279] In one possible implementation, the communication unit 801 is configured to receive first information from a first access network serving element (SU) or third information from a first access network communication element (CU), wherein the first core network device serves a first terminal, the first information is used to indicate that the first terminal is associated with the first SU, and the first information includes the TMSI information of the first terminal and the identification information of the first SU; the third information is used to indicate that the first terminal is associated with the first SU, and the third information includes the third identification information of the first terminal and the identification information of the first SU, the third identification information including one or more of the TMSI information of the first terminal and the UE NGAP ID identification information of the first terminal on the interface NG of the first CU and the first core network device. The processing unit 802 is configured to process the transmitted and received data.

[0280] In another possible implementation, the first information may also include the identification information UENsuAP ID of the first terminal on the interface Nsu of the first SU and the first core network device.

[0281] In another possible implementation, the communication unit 801 is further configured to receive second information from the first SU or the first CU, wherein the second information is used to indicate the association between the first CU and the first SU, and the second information includes the identification information of the first CU and the identification information of the first SU.

[0282] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0283] Please refer to Figure 9, which is a schematic diagram of another communication device 90 provided in an embodiment of this application. The communication device 90 can be a standalone device, such as a first SU, a first CU, or a first core network device, or it can be a component included in a standalone device, such as a chip, software module, or integrated circuit. The communication device 90 may include at least one processor 901 and a communication interface 902. Optionally, it may also include at least one memory 903. Further optionally, it may also include a connection line 904, wherein the processor 901, the communication interface 902, and / or the memory 903 are connected through the connection line 904, and / or communicate with each other through the connection line 904 to transmit control signals and / or data signals.

[0284] Wherein: Processor 901 is a module that performs arithmetic and / or logical operations, and may specifically include one or more of the following modules: filter, modem, power amplifier, low noise amplifier (LNA), baseband processor, radio frequency processor, radio frequency circuit, CPU, AP, microcontroller unit (MCU), electronic control unit (ECU), GPU, MPU, ASIC, image signal processor (ISP), DSP, FPGA, complex programmable logic device (CPLD), or coprocessor, etc.

[0285] The communication interface 902 can be used to provide information input or output to at least one processor, or to receive signals sent externally and / or send signals to externally.

[0286] For example, the communication interface 902 may include interface circuitry, such as input / output interfaces, chip pins, etc.

[0287] For example, the communication interface 902 may include a wired link interface such as an Ethernet cable, or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission and other short-range wireless communication technologies, etc.).

[0288] Optionally, the communication interface 902 may also include a radio frequency transmitter, an antenna, etc. When the communication interface 902 includes an antenna, the number of antennas can be one or more.

[0289] As one possible design, if the communication device 90 is a standalone device, the communication interface 902 may include a receiver and a transmitter. The receiver and transmitter may be the same component or different components. When the receiver and transmitter are the same component, this component can be referred to as a transceiver.

[0290] As another possible design, if the communication device 90 is a chip or circuit, the communication interface 902 may include an input interface and an output interface. The input interface and the output interface may be the same interface or they may be different interfaces.

[0291] Alternatively, the functions of the communication interface 902 can be implemented by a transceiver circuit or a dedicated transceiver chip.

[0292] Memory 903 provides storage space, in which data such as the operating system and computer programs can be stored. Memory 903 can be one or a combination of several of the following: cache, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), compact disc read-only memory (CD-ROM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD), solid-state drive (SSD), etc. Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store computer programs or instructions, and / or data.

[0293] The functions and actions of each module or unit in the communication device 90 listed above are merely illustrative examples.

[0294] Each functional unit in the communication device 90 can be used to implement the aforementioned communication method, such as the communication method shown in FIG4, FIG5a, and FIG5b, for example, a method for executing the first SU, or a method for executing the first CU, or a method for executing the first core network device.

[0295] Optionally, processor 901 may be a processor specifically designed to perform the aforementioned methods (for ease of distinction, referred to as a dedicated processor), or a processor that performs the aforementioned methods by calling a computer program (for ease of distinction, referred to as a dedicated processor). Optionally, at least one processor may include both dedicated processors and general-purpose processors.

[0296] Optionally, if the communication device 90 includes at least one memory 903, and the processor 901 implements the aforementioned communication method by calling a computer program, the computer program can be stored in the memory 903.

[0297] This application also provides a chip, which includes logic circuitry and a communication interface. The communication interface is used to receive or transmit signals; the logic circuitry is used to receive or transmit signals through the communication interface. The chip is used to implement the aforementioned communication methods, such as the communication methods shown in Figures 4, 5a, and 5b, for example, a method executed by a first SU, a method executed by a first CU, or a method executed by a first core network device.

[0298] This application also provides a computer-readable storage medium storing instructions that, when executed on at least one processor (or communication device), implement the aforementioned communication method, such as the communication method shown in FIG4, FIG5a, and FIG5b, for example, a method for executing a first SU, or a method for executing a first CU, or a method for executing a first core network device.

[0299] This application also provides a computer program product, which includes computer instructions for implementing the aforementioned communication methods, such as the communication methods shown in FIG4, FIG5a, and FIG5b, for example, for executing a method executed by a first SU, or for executing a method executed by a first CU, or for executing a method executed by a first core network device.

[0300] It should be noted that, in the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplarily" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0301] In the embodiments of this application, "at least one" refers to one or more items, and "more than one" refers to two or more items. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items.

[0302] For example, at least one of a, b, or c can be represented as: a, b, c, (a and b), (a and c), (b and c), or (a and b and c), where a, b, and c can be single or multiple. "AND / OR" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects have an "OR" relationship.

[0303] Furthermore, unless otherwise stated, the use of ordinal numbers such as "first" and "second" in the embodiments of this application is for distinguishing multiple objects and is not for limiting the order, sequence, priority, or importance of multiple objects. Similarly, terms like "first node" and "second node" are merely for convenience in describing new parameters in different implementations and do not indicate differences in their execution operations, importance, structure, etc.

[0304] In the above embodiments, the term "when..." can be interpreted, depending on the context, as meaning "if...", "before...", "determined...", or "detected...". The above descriptions are merely optional embodiments of this application and are not intended to limit the application. Any modifications, equivalent substitutions, improvements, etc., made within the concept and principles of this application should be included within the scope of protection of this application.

[0305] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

Claims

1. A communication method, characterized in that, The method, applied to a first access network serving element (SU), includes: Identify the first access network communication element (CU) serving the first terminal; Send a measurement configuration request message about the first terminal to the first CU; Receive measurement results about the first terminal from the first CU.

2. The method according to claim 1, characterized in that, The determination of the first access network communication element (CU) serving the first terminal includes: The identification information of the first terminal and the identification information of the first CU are obtained from the first CU or the first core network device. The first core network device serves the first terminal. The identification information of the first terminal includes first identification information and second identification information of the first terminal. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information (UENsuAP ID) of the first terminal on the interface (Nsu) between the first SU and the first core network device. The second identification information includes one or more of the identification information (UESIAPID) of the first terminal on the interface (SI) between the first CU and the first SU, or the temporary radio network identification information (C-RNTI) of the first terminal under the first CU. Based on the identification information of the first terminal and the identification information of the first CU, it is determined that the first terminal is associated with the first CU.

3. The method according to claim 1, characterized in that, The method further includes: Send first information to a first core network device, wherein the first core network device serves the first terminal, and the first information is used to indicate that the first terminal is associated with the first SU, and the first information includes the TMSI information of the first terminal and the identification information of the first SU.

4. A communication method, characterized in that, The method, applied to the first access network communication element (CU), includes: Receive a measurement configuration request message for the first terminal from the first access network serving element SU; The measurement results are sent to the first SU.

5. The method according to claim 4, characterized in that, The method further includes: The identification information of the first terminal and the identification information of the first CU are sent to the first SU. The identification information of the first terminal and the identification information of the first CU are used to indicate that the first terminal is associated with the first CU. The identification information of the first terminal includes first identification information and second identification information of the first terminal. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information (UENsuAP ID) of the first terminal on the interface (Nsu) between the first SU and the first core network device, and the first core network device serves the first terminal. The second identification information includes one or more of the identification information (UE SIAP ID) of the first terminal on the interface (SI) between the first CU and the first SU and the cell radio network temporary identification information (C-RNTI) of the first terminal under the first CU.

6. The method according to claim 5, characterized in that, Before sending the identification information of the first terminal and the identification information of the first CU to the first SU, the method further includes: The identification information of the first terminal is received from the first core network device.

7. The method according to claim 4, characterized in that, The method further includes: Send third information to a first core network device, wherein the first core network device serves the first terminal, the third information is used to indicate that the first terminal is associated with the first SU, the third information includes the third identification information of the first terminal and the identification information of the first SU, the third identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the UE NGAP ID of the first terminal on the interface NG of the first CU and the first core network device.

8. A communication device, characterized in that, The communication device includes a communication unit and a processing unit, wherein: The processing unit is used to determine the first access network communication element (CU) serving the first terminal; The communication unit is used to send a measurement configuration request message about the first terminal to the first CU; The communication unit is also configured to receive measurement results from the first CU regarding the first terminal.

9. The apparatus according to claim 8, characterized in that, Regarding the determination of the first access network communication element (CU) serving the first terminal, the processing unit is specifically used for: The identification information of the first terminal and the identification information of the first CU are obtained from the first CU or the first core network device. The first core network device serves the first terminal. The identification information of the first terminal includes first identification information and second identification information of the first terminal. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information (UENsuAP ID) of the first terminal on the interface (Nsu) between the first SU and the first core network device. The second identification information includes one or more of the identification information (UESIAPID) of the first terminal on the interface (SI) between the first CU and the first SU, or the temporary radio network identification information (C-RNTI) of the first terminal under the first CU. Based on the identification information of the first terminal and the identification information of the first CU, it is determined that the first terminal is associated with the first CU.

10. The apparatus according to claim 8, characterized in that, The communication unit is further configured to send first information to a first core network device, wherein the first core network device serves the first terminal, the first information is used to indicate that the first terminal is associated with the first SU, and the first information includes the TMSI information of the first terminal and the identification information of the first SU.

11. A communication device, characterized in that, The communication device includes a communication unit and a processing unit, wherein: The communication unit is used to receive a measurement configuration request message about the first terminal from the first access network serving element SU; The communication unit is also used to send measurement results to the first SU; The processing unit is used to process the data sent and received.

12. The apparatus according to claim 11, characterized in that, The communication unit is further configured to send the identification information of the first terminal and the identification information of the first CU to the first SU, wherein the identification information of the first terminal and the identification information of the first CU are used to indicate that the first terminal is associated with the first CU. The identification information of the first terminal includes first identification information and second identification information of the first terminal. The first identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the identification information (UENsuAP ID) of the first terminal on the interface (Nsu) between the first SU and the first core network device, wherein the first core network device serves the first terminal. The second identification information includes one or more of the identification information (UE SIAP ID) of the first terminal on the interface (SI) between the first CU and the first SU and the cell radio network temporary identification information (C-RNTI) of the first terminal under the first CU.

13. The apparatus according to claim 12, characterized in that, The communication unit is further configured to receive identification information of the first terminal from the first core network device.

14. The apparatus according to claim 11, characterized in that, The communication unit is further configured to send third information to a first core network device, wherein the first core network device serves the first terminal, and the third information is used to indicate that the first terminal is associated with the first SU. The third information includes third identification information of the first terminal and identification information of the first SU. The third identification information includes one or more of the temporary mobile station identification information (TMSI) of the first terminal and the UE NGAP ID of the first terminal on the interface NG of the first CU and the first core network device.

15. A communication system, characterized in that, The communication system includes the communication device as described in claim 8; or the communication system includes the communication device as described in claim 11.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store instructions or computer programs; When the instructions or the computer program are executed, the method described in any one of claims 1-7 is implemented.

Images