A terminal communication method and device across service platforms

Abstract

An embodiment of the present application provides a terminal communication method and device across service platforms, the method comprising: receiving a cross-service platform session request initiated by a first terminal belonging to a first service platform, the target terminal of the cross-service platform session request being a second terminal belonging to a second service platform; the cross-service platform session request carries address information of the second terminal on the second service platform; obtaining the communication identification number of the second service platform from a platform authentication center, and activating the user plane function UPF diversion, and establishing a diversion link between the first terminal and the second terminal based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform; based on the diversion link, transmitting service traffic from the first terminal to the second terminal, so that when terminals of different service platforms communicate across service platforms, it is no longer necessary to develop complex API interfaces for each other, and communication latency is reduced.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a terminal communication method and device across service platforms. Background Art

[0002] Currently, for terminal communication across service platforms, complex APIs (Application Programming Interfaces) need to be developed on both sides, and the communication delay is high. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide a terminal communication method and device across service platforms, so that when terminals on different service platforms communicate across service platforms, it is no longer necessary to develop complex API interfaces for each other, and communication delays are reduced. The specific technical solutions are as follows:

[0004] To achieve the above object, an embodiment of the present application provides a terminal communication method across service platforms, the method comprising:

[0005] receiving a cross-service platform session request initiated by a first terminal belonging to a first service platform, wherein a target terminal of the cross-service platform session request is a second terminal belonging to a second service platform; the cross-service platform session request carries address information of the second terminal on the second service platform;

[0006] Obtain the communication identification number of the second service platform from the platform authentication center, activate the user plane function UPF offload, and establish a offload link between the first terminal and the second terminal based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform;

[0007] Based on the offload link, the service traffic is transmitted from the first terminal to the second terminal.

[0008] Optionally, the platform authentication center authenticates each service platform in advance and allocates a communication identification number to each service platform.

[0009] Optionally, cross-service platform communication between various service platforms authenticated by the platform authentication center follows a predefined unified data format.

[0010] Optionally, the UPF diversion is UL CL diversion provided by the UPF, and the step of activating the UPF diversion includes:

[0011] A UPF shunt node is inserted into the current cross-service platform session as a relay node of the shunt link; the UPF shunt node includes: UL CL UPF and auxiliary anchor point UPF.

[0012] Optionally, the service platform is a metaverse platform, and the first terminal corresponds to a first digital human in the first metaverse platform; the second terminal corresponds to a second digital human in the second metaverse platform.

[0013] To achieve the above-mentioned purpose, an embodiment of the present application further provides a terminal communication device across service platforms, the device comprising:

[0014] A receiving module, configured to receive a cross-service platform session request initiated by a first terminal belonging to a first service platform, wherein a target terminal of the cross-service platform session request is a second terminal belonging to a second service platform; the cross-service platform session request carries address information of the second terminal on the second service platform;

[0015] A shunt module, configured to obtain the communication identification number of the second service platform from the platform authentication center, activate the user plane function UPF shunt, and establish a shunt link between the first terminal and the second terminal based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform;

[0016] A transmission module is used to transmit the service traffic from the first terminal to the second terminal based on the diversion link.

[0017] Optionally, the platform authentication center authenticates each service platform in advance and allocates a communication identification number to each service platform.

[0018] Optionally, cross-service platform communication between various service platforms authenticated by the platform authentication center follows a predefined unified data format.

[0019] Optionally, the UPF split is UL CL split provided by the UPF, and the split module is specifically used to:

[0020] A UPF shunt node is inserted into the current cross-service platform session as a relay node of the shunt link; the UPF shunt node includes: UL CL UPF and auxiliary anchor point UPF.

[0021] Optionally, the service platform is a metaverse platform, and the first terminal corresponds to a first digital human in the first metaverse platform; the second terminal corresponds to a second digital human in the second metaverse platform.

[0022] To achieve the above-mentioned purpose, an embodiment of the present application further provides an electronic device, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus;

[0023] Memory, used to store computer programs;

[0024] The processor is used to implement any of the above method steps when executing the program stored in the memory.

[0025] To achieve the above objectives, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, any of the above method steps is implemented.

[0026] Beneficial effects of the embodiments of the present application:

[0027] It can be seen that the terminal communication method and device across service platforms provided in the embodiments of the present application are applied to receive a cross-service platform session request initiated by a first terminal belonging to a first service platform, and the target terminal of the cross-service platform session request is a second terminal belonging to a second service platform; the cross-service platform session request carries the address information of the second terminal on the second service platform; the communication identification number of the second service platform is obtained from the platform authentication center, and the user plane function UPF diversion is activated, and a diversion link between the first terminal and the second terminal is established based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform; based on the diversion link, the service traffic is transmitted from the first terminal to the second terminal.

[0028] Therefore, when a terminal initiates a cross-service platform session request, 5G UPF diversion is triggered, and a diversion link is directly established between terminals belonging to different service platforms, so that the business traffic across service platforms is directly transmitted through the diversion link. Therefore, when terminals on different service platforms communicate across service platforms, there is no need to develop complex API interfaces for each other.

[0029] In addition, since the relay node of the diversion link is usually the UPF diversion node located at the edge base station, the transmission path is greatly reduced compared to the method of forwarding through the server in the cloud, thereby reducing the communication delay.

[0030] Of course, implementing any product or method of the present application does not necessarily require achieving all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0032] Figure 1 A flowchart of a terminal communication method across service platforms provided in an embodiment of the present application.

[0033] Figure 2 A schematic diagram of a terminal communication method across service platforms provided in an embodiment of the present application;

[0034] Figure 3 A schematic diagram of the structure of a terminal communication device across service platforms provided in an embodiment of the present application;

[0035] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field based on the present application belong to the scope of protection of the present application.

[0037] The Metaverse is a virtual space based on the real world, which builds social, living, and even economic systems in the virtual world to achieve the integration of the real world and the virtual world. Major companies are rushing to launch independent Metaverse social networks, e-commerce and other scenarios.

[0038] However, when terminals in different metaverses communicate across metaverses, they need to develop complex APIs (Application Programming Interfaces) with each other, and the communication latency is high. When users wear XR (Extended Reality) headsets to access the metaverse, they are prone to dizziness.

[0039] Among them, the metaverse can be regarded as a service platform, that is, this service platform can provide users with social and living services in the virtual world.

[0040] Those skilled in the art will appreciate that the service platform is not limited to the metaverse. For example, a VR (Virtual Reality) game platform can also be regarded as a service platform, that is, the service platform can provide users with virtual reality game experience services.

[0041] For the same type of service, each manufacturer has developed its own service platform. The communication between terminals connected to the service platforms of different manufacturers is called cross-service platform communication.

[0042] Currently, for the above-mentioned cross-service platform communications, it is necessary to develop complex API interfaces, and the communication latency is high.

[0043] In order to solve the technical problem that when terminals across service platforms communicate, it is necessary to develop complex API interfaces and the communication delay is high, the embodiments of the present application provide a terminal communication method and device across service platforms.

[0044] See also Figure 1 , Figure 1 A schematic diagram of a flow chart of a terminal communication method across service platforms provided in an embodiment of the present application, such as Figure 1 As shown, the method may include:

[0045] S101: receiving a cross-service platform session request initiated by a first terminal belonging to a first service platform, wherein a target terminal of the cross-service platform session request is a second terminal belonging to a second service platform; and the cross-service platform session request carries address information of the second terminal on the second service platform.

[0046] In the embodiment of the present application, terminal communication across service platforms refers to: communication between terminals belonging to different service platforms for a certain type of service. Different service platforms may be service platforms provided by different manufacturers. For example, for the same type of service, manufacturer 1 and manufacturer 2 respectively launch service platform 1 and service platform 2. Then, terminal communication across service platforms can be understood as communication between a terminal accessing service platform 1 and a terminal accessing service platform 2.

[0047] As mentioned above, the service platform can be of multiple types and is not limited to the Metaverse platform. However, for ease of understanding, the Metaverse platform is used as an example in the following embodiments.

[0048] As an example, when the service type is metaverse service, that is, the service platform is a metaverse platform, terminal communication across service platforms refers to: communication between terminals accessing different metaverses, such as communication between terminal a accessing metaverse A and terminal b accessing metaverse B.

[0049] In the embodiment of the present application, a user can access a service platform through a terminal device. When a user in a service platform wants to communicate with a user in another service platform, a cross-service platform session request can be initiated to the operator's network through the user's terminal. The session request is for a terminal in another service platform. The terminal device can be a mobile phone, an XR headset, etc.

[0050] Specifically, a first terminal accessing a first service platform may initiate a cross-service platform session request to a neighboring base station, and the target terminal of the session request is a second terminal accessing a second service platform. Therefore, the session request may carry the address information of the second terminal on the second service platform, such as an IP address. In addition, the identifier of the second service platform may also be carried.

[0051] After receiving the session request, the base station determines that the session request is a cross-service platform session request by identifying the address information of the target terminal carried in the session request, and then executes subsequent steps.

[0052] Taking the service platform as a metaverse platform as an example, the first terminal connected to the first metaverse initiates a cross-metaverse session request to the second metaverse. The target terminal of the session request is the second terminal belonging to the second metaverse, and the session request carries the address information of the second terminal in the second metaverse.

[0053] S102: Obtain the communication identification number of the second service platform from the platform authentication center, activate the user plane function UPF diversion, and establish a diversion link between the first terminal and the second terminal based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform.

[0054] In an embodiment of the present application, when the base station identifies that the session request is a cross-service platform session request, the communication identification number of the target service platform can be obtained from the platform authentication center.

[0055] Among them, the platform authentication center can be composed of multiple network elements of the 5GC control plane, such as PCF (Policy Control function), SMF (Session Management function), AMF (Access and Mobility Management Function), etc.

[0056] Specifically, each service platform participating in cross-service platform communication can sign a contract with the operator in advance and be uniformly authenticated at the platform authentication center. The platform authentication center authenticates each service platform and assigns a communication identification number. Taking the Metaverse as an example, each Metaverse that needs to participate in cross-Metaverse communication can interact with the 5G network cloud, such as PCF, through the N5 / N33 interface in advance. PCF can authenticate each Metaverse and assign a communication identification number.

[0057] That is to say, in the embodiment of the present application, by uniformly configuring the communication identification numbers of each service platform at the 5GC control level, unified management of security authentication and forwarding rules for communications between service platforms is achieved.

[0058] In this embodiment of the present application, the base station can obtain the communication identification number of the second service platform from the 5G network element, and then activate the UPF (User plane function) diversion.

[0059] Specifically, diversion is a function provided by 5G UPF. When UPF diversion is activated, the 5G network element SMF inserts the UPF diversion node into the current session to establish a diversion link. The UPF diversion node serves as a relay node for the diversion link.

[0060] In the embodiment of the present application, a shunt link between the first terminal and the second terminal is established based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform. In other words, the communication link between the first terminal and the second terminal is directly established through the shunt function provided by the 5G UPF. During the communication between the first terminal and the second terminal, the service traffic is directly forwarded via the shunt node of the UPF inside the edge base station without passing through the servers of the first service platform and the second service platform.

[0061] S103: Based on the offload link, transmit the service traffic from the first terminal to the second terminal.

[0062] In an embodiment of the present application, the established diversion link is a communication link between the first terminal and the second terminal. Therefore, the business traffic for communication between the first terminal and the second terminal does not need to be forwarded through the server of the service platform, and the business traffic can be directly transmitted from the first terminal to the second terminal.

[0063] It can be seen that the terminal communication method across service platforms provided in the embodiment of the present application is applied to receive a cross-service platform session request initiated by a first terminal belonging to a first service platform, and the target terminal of the cross-service platform session request is a second terminal belonging to a second service platform; the cross-service platform session request carries the address information of the second terminal on the second service platform; the communication identification number of the second service platform is obtained from the platform authentication center, and the user plane function UPF diversion is activated, and a diversion link between the first terminal and the second terminal is established based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform; based on the diversion link, the service traffic is transmitted from the first terminal to the second terminal.

[0064] Therefore, when a terminal initiates a cross-service platform session request, 5G UPF diversion is triggered, and a diversion link is directly established between terminals belonging to different service platforms, so that the business traffic across service platforms is directly transmitted through the diversion link. Therefore, when terminals on different service platforms communicate across service platforms, there is no need to develop complex API interfaces for each other.

[0065] In addition, since the relay node of the diversion link is usually the UPF diversion node located at the edge base station, the transmission path is greatly reduced compared to the method of forwarding through the server in the cloud, thereby reducing the communication delay.

[0066] For the Metaverse platform, the communication method provided in the embodiment of the present application is adopted. Since the latency of cross-Metaverse communication is reduced, users are less likely to feel dizzy when wearing terminal devices to access the Metaverse.

[0067] In one embodiment of the present application, cross-service platform communication between various service platforms authenticated at the platform authentication center follows a predefined unified data format.

[0068] Specifically, since the data structure requirements for communication between various service platforms may be different, the platform authentication center can also define a unified data format to reduce the coupling of complex API interfaces and the complexity of data formats between various service platforms. As a result, cross-service platform communication between various platforms can follow a unified data format, making data exchange between each other more convenient.

[0069] In one embodiment of the present application, the UPF offloading may be a UL CL (Uplink Classifier) ​​offloading solution provided by the UPF. Accordingly, the step of activating the UPF offloading may include:

[0070] Insert a UPF shunt node into the current cross-service platform session as a relay node for the shunt link; the UPF shunt node includes: UL CL UPF and auxiliary anchor point UPF.

[0071] Among them, UL CL UPF is the UPF that implements the Uplink Classifier function. It is inserted into the session by SMF when activating the diversion. UL CL UPF can be connected to the anchor UPF through the N9 interface. For uplink traffic, after identification according to the diversion rules, it distinguishes and forwards the messages that need to be sent to the primary anchor UPF and the auxiliary anchor UPF. For downlink traffic, the messages from the anchor UPF are aggregated and forwarded to the base station through the N3 interface.

[0072] When activating the traffic diversion, the auxiliary anchor point UPF is inserted into the session at the same time, and the auxiliary anchor point UPF can be connected to the local DN through the N6 interface. During the user session, as the anchor point of the PDU session, it forwards the user data between the UL CL UPF-auxiliary anchor point UPF-local DN, and completes the functions of billing, monitoring, and service control.

[0073] In the embodiment of the present application, the UL CL UPF and the auxiliary anchor point UPF serve as relay nodes of the offload link and are used to forward the service traffic carried on the offload link.

[0074] As an example, see Figure 2 , Figure 2 A schematic diagram of a terminal communication method across service platforms provided in an embodiment of the present application, such as Figure 2 As shown in the figure, the service platform is the Metaverse platform. After terminal a of Metaverse A initiates a cross-Metaverse session, a diversion link is established through the 5G UPF diversion function. The UL CL UPF and anchor node UPF in the diversion link serve as relay nodes. Terminal a can directly send communication traffic to terminal b of Metaverse B through the diversion link.

[0075] In one embodiment of the present application, the service platform is a metaverse platform, the first terminal corresponds to a first digital human in the first metaverse platform; and the second terminal corresponds to a second digital human in the second metaverse platform.

[0076] Specifically, in the field of metaverse, digital human refers to the user's avatar in the metaverse. Therefore, the terminal used by the user can correspond to the digital human in the metaverse. The terminal communication method across service platforms provided in the embodiment of the present application can realize efficient, convenient, and low-latency communication between digital humans in different metaverses, thereby meeting the needs of digital humans for communication between different metaverses.

[0077] In one embodiment of the present application, the method may further include: optimizing and adjusting the deployment area and coverage of the UPF according to traffic data of terminal communications across service platforms in various areas counted within a preset time period.

[0078] Specifically, operators can count the traffic data of cross-service platform communications in each region and deploy UPFs reasonably based on the traffic data to meet the traffic diversion needs of cross-service platform communications in each region. For example, if there is a lot of traffic data of cross-service platform communications in a certain region, more edge base stations will be deployed in this region to meet the traffic diversion needs in the region.

[0079] See also Figure 3 , Figure 3 A schematic diagram of a structure of a terminal communication device across service platforms provided in an embodiment of the present application, the device may include the following modules:

[0080] A receiving module 301 is configured to receive a cross-service platform session request initiated by a first terminal belonging to a first service platform, wherein a target terminal of the cross-service platform session request is a second terminal belonging to a second service platform; the cross-service platform session request carries address information of the second terminal on the second service platform;

[0081] A traffic distribution module 302 is configured to obtain a communication identification number of the second service platform from a platform authentication center, activate a user plane function UPF traffic distribution, and establish a traffic distribution link between the first terminal and the second terminal based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform;

[0082] The transmission module 303 is used to transmit the service traffic from the first terminal to the second terminal based on the offload link.

[0083] A terminal communication device across service platforms provided in an embodiment of the present application is applied to receive a cross-service platform session request initiated by a first terminal belonging to a first service platform, wherein the target terminal of the cross-service platform session request is a second terminal belonging to a second service platform; the cross-service platform session request carries address information of the second terminal on the second service platform; the communication identification number of the second service platform is obtained from the platform authentication center, and the user plane function UPF diversion is activated, and a diversion link is established between the first terminal and the second terminal based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform; based on the diversion link, the service traffic is transmitted from the first terminal to the second terminal.

[0084] Therefore, when a terminal initiates a cross-service platform session request, 5G UPF diversion is triggered, and a diversion link is directly established between terminals belonging to different service platforms, so that the business traffic across service platforms is directly transmitted through the diversion link. Therefore, when terminals on different service platforms communicate across service platforms, there is no need to develop complex API interfaces for each other.

[0085] In addition, since the relay node of the diversion link is usually the UPF diversion node located at the edge base station, the transmission path is greatly reduced compared to the method of forwarding through the server in the cloud, thereby reducing the communication delay.

[0086] For the Metaverse platform, the communication method provided in the embodiment of the present application is adopted. Since the latency of cross-Metaverse communication is reduced, users are less likely to feel dizzy when wearing terminal devices to access the Metaverse.

[0087] In one embodiment of the present application, the platform authentication center authenticates each service platform in advance and allocates a communication identification number to each service platform.

[0088] It can be seen that by uniformly configuring the communication identification numbers of each service platform at the 5GC control level, unified management of security authentication and forwarding rules for communications between service platforms can be achieved.

[0089] In one embodiment of the present application, cross-service platform communication between various service platforms authenticated by the platform authentication center follows a predefined unified data format.

[0090] It can be seen that the platform authentication center can also define a unified data format to reduce the coupling of complex API interfaces and the complexity of data formats between various service platforms. Therefore, cross-service platform communication between various platforms can follow a unified data format, making data exchange between each other more convenient.

[0091] In one embodiment of the present application, the UPF split is UL CL split provided by the UPF, and the split module is specifically used for:

[0092] A UPF shunt node is inserted into the current cross-service platform session as a relay node of the shunt link; the UPF shunt node includes: UL CL UPF and auxiliary anchor point UPF.

[0093] In one embodiment of the present application, the service platform is a metaverse platform, the first terminal corresponds to a first digital human in the first metaverse platform; the second terminal corresponds to a second digital human in the second metaverse platform.

[0094] It can be seen that the cross-service platform terminal communication device provided by the embodiment of the present application can realize efficient, convenient, and low-latency communication between digital people in different metaverses, and meet the needs of digital people for communication between different metaverses.

[0095] The present application also provides an electronic device, such as Figure 4 As shown, it includes a processor 401, a communication interface 402, a memory 403 and a communication bus 404, wherein the processor 401, the communication interface 402, and the memory 403 communicate with each other through the communication bus 404.

[0096] Memory 403, used for storing computer programs;

[0097] The processor 401 is used to execute the program stored in the memory 403 to implement the following steps:

[0098] receiving a cross-service platform session request initiated by a first terminal belonging to a first service platform, wherein a target terminal of the cross-service platform session request is a second terminal belonging to a second service platform; the cross-service platform session request carries address information of the second terminal on the second service platform;

[0099] Obtain the communication identification number of the second service platform from the platform authentication center, activate the user plane function UPF offload, and establish a offload link between the first terminal and the second terminal based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform;

[0100] Based on the offload link, the service traffic is transmitted from the first terminal to the second terminal.

[0101] The communication bus mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0102] The communication interface is used for communication between the above electronic device and other devices.

[0103] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0104] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0105] It can be seen that the electronic device provided by the embodiment of the present application receives a cross-service platform session request initiated by a first terminal belonging to a first service platform, and the target terminal of the cross-service platform session request is a second terminal belonging to a second service platform; the cross-service platform session request carries the address information of the second terminal on the second service platform; the communication identification number of the second service platform is obtained from the platform authentication center, and the user plane function UPF diversion is activated, and a diversion link is established between the first terminal and the second terminal based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform; based on the diversion link, the service traffic is transmitted from the first terminal to the second terminal.

[0106] Therefore, when a terminal initiates a cross-service platform session request, 5G UPF diversion is triggered, and a diversion link is directly established between terminals belonging to different service platforms, so that the business traffic across service platforms is directly transmitted through the diversion link. Therefore, when terminals on different service platforms communicate across service platforms, there is no need to develop complex API interfaces for each other.

[0107] In addition, since the relay node of the diversion link is usually the UPF diversion node located at the edge base station, the transmission path is greatly reduced compared to the method of forwarding through the server in the cloud, thereby reducing the communication delay.

[0108] For the Metaverse platform, the communication method provided in the embodiment of the present application is adopted. Since the latency of cross-Metaverse communication is reduced, users are less likely to feel dizzy when wearing terminal devices to access the Metaverse.

[0109] In another embodiment provided in the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned terminal communication methods across service platforms are implemented.

[0110] In another embodiment provided by the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute any of the terminal communication methods across service platforms in the above embodiments.

[0111] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive Solid State Disk (SSD)), etc.

[0112] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0113] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the terminal communication device, electronic device, computer-readable storage medium, and computer program product embodiments across service platforms, since they are basically similar to the terminal communication method embodiments across service platforms, the description is relatively simple, and the relevant parts can be referred to the partial description of the terminal communication method embodiments across service platforms.

[0114] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A terminal communication method across service platforms, characterized in that: The method comprises: receiving a cross-service platform session request initiated by a first terminal belonging to a first service platform, wherein a target terminal of the cross-service platform session request is a second terminal belonging to a second service platform; the cross-service platform session request carries address information of the second terminal on the second service platform; Obtain the communication identification number of the second service platform from the platform authentication center, activate the user plane function UPF offload, and establish a offload link between the first terminal and the second terminal based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform; Based on the offload link, the service traffic is transmitted from the first terminal to the second terminal.

2. The method according to claim 1, characterized in that The platform authentication center authenticates each service platform in advance and allocates a communication identification number to each service platform.

3. The method according to claim 1, characterized in that The cross-service platform communication between the various service platforms authenticated at the platform authentication center follows a predefined unified data format.

4. The method according to claim 1, characterized in that: The UPF diversion is UL CL diversion provided by the UPF, and the step of activating the UPF diversion includes: A UPF shunt node is inserted into the current cross-service platform session as a relay node of the shunt link; the UPF shunt node includes: UL CL UPF and auxiliary anchor point UPF.

5. The method according to claim 1, characterized in that The service platform is a metaverse platform, the first terminal corresponds to a first digital person in the first metaverse platform; the second terminal corresponds to a second digital person in the second metaverse platform.

6. A terminal communication device across service platforms, characterized in that: The device comprises: A receiving module, configured to receive a cross-service platform session request initiated by a first terminal belonging to a first service platform, wherein a target terminal of the cross-service platform session request is a second terminal belonging to a second service platform; the cross-service platform session request carries address information of the second terminal on the second service platform; A shunt module, configured to obtain the communication identification number of the second service platform from the platform authentication center, activate the user plane function UPF shunt, and establish a shunt link between the first terminal and the second terminal based on the communication identification number of the second service platform and the address information of the second terminal on the second service platform; A transmission module is used to transmit the service traffic from the first terminal to the second terminal based on the diversion link.

7. The device according to claim 6, characterized in that The platform authentication center authenticates each service platform in advance and allocates a communication identification number to each service platform.

8. The device according to claim 6, characterized in that The cross-service platform communication between various service platforms authenticated at the platform authentication center follows a predefined unified data format.

9. The device according to claim 6, characterized in that The UPF shunt is the UL CL shunt provided by the UPF, and the shunt module is specifically used for: A UPF shunt node is inserted into the current cross-service platform session as a relay node of the shunt link; the UPF shunt node includes: UL CL UPF and auxiliary anchor point UPF.

10. The device according to claim 6, characterized in that The service platform is a metaverse platform, the first terminal corresponds to a first digital person in the first metaverse platform; the second terminal corresponds to a second digital person in the second metaverse platform.

11. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing the method steps described in any one of claims 1 to 5 when executing a program stored in a memory.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps described in any one of claims 1 to 5 are implemented.

Images