Business data processing method, device and system, electronic equipment and storage medium
By establishing a MESH communication network connection between base stations and core networks in 5G integrated stations, the handover failure problem between 5G integrated stations was solved, and service continuity and high availability were achieved when terminals move across stations.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-23
- Publication Date
- 2026-03-24
AI Technical Summary
There is a problem of handover failure when terminals move between 5G integrated stations. This is mainly due to the serviceless architecture caused by high integration, which makes it impossible to effectively achieve cross-station communication.
By establishing a MESH communication network connection between the base station and the core network in the 5G integrated station, it is ensured that service request data can be transmitted to the original registered core network through the switched base station during the handover process, avoiding handover failure, and switching to other core networks for processing through the MESH network when the core network fails.
It achieves service continuity when terminals move across sites, avoids handover failures, improves the reliability and high availability of service processing, and reduces configuration complexity and network load.
Smart Images
Figure CN121728526A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to a business data processing method, apparatus, system, electronic device and storage medium. Background Technology
[0002] A 5G (5th Generation Mobile Communication Technology) integrated station includes a 5GC (5th Generation Core Network) and a gNB (5G NewRadio Base Station). The 5GC and gNB are deployed together in a single station device to form a 5G integrated station.
[0003] When communicating across core networks, it is generally necessary to deploy network elements such as NRF to implement a service-oriented architecture. However, the 5GC within a 5G integrated station has a high degree of integration, requiring the removal of non-essential network elements, such as NRF (Network Repository Function) and NEF (Network Exposure Function). This results in a lack of a service-oriented architecture between 5G integrated stations, leading to handover failures for terminals when moving between 5G integrated stations. Summary of the Invention
[0004] This application provides a business data processing method, apparatus, system, electronic device, and storage medium that can reduce handover failure issues.
[0005] Firstly, a service data processing method is proposed, applied to a first base station in a first integrated station, the first integrated station further including a first core network, the method comprising:
[0006] Receive service request data sent by the terminal;
[0007] If the terminal is in a signaling connection state, the service request data is transmitted to the second core network that has completed the terminal registration. The second core network is located at the second integrated station. The service request data instructs the terminal, the first base station, and the second core network to complete the service processing corresponding to the service request data. The first base station and the second core network are connected through the MESH communication network.
[0008] If the terminal does not have a registered second core network, the service request data is transmitted to the first core network, and the service request data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data.
[0009] If the terminal is in an idle state and the terminal is registered with a second core network, the service request data is transmitted to the second core network. The service request data instructs the second core network to generate first rejection request data, which is used to instruct the terminal to deregister.
[0010] In one possible implementation, after transmitting the service request data to the second core network that has completed the terminal registration, the method further includes:
[0011] If the first core network link fails, the service request data is sent to the third core network. If the service request data indicates a signaling access request, the service request data instructs the third core network to generate second rejection request data. If the service request data indicates a SUCI initial registration request, the service request data instructs the terminal, the first base station, and the third core network to complete the service processing corresponding to the service request data. The third core network and the first base station are connected through a MESH communication network. The second rejection request data is used to instruct the terminal to deregister.
[0012] In one possible implementation, the method further includes:
[0013] The fourth response data is sent to the terminal, and the fourth response data indicates a failure of the first core network link.
[0014] At preset time intervals, the system receives service request data sent by the terminal and sends the service request data to the first core network. The service request data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data.
[0015] Secondly, a business data processing method is proposed, applied to a terminal located within the wireless coverage area of a first integrated station; the method includes:
[0016] Send service request data to the first base station in the first integrated station, the first integrated station also includes a first core network;
[0017] When the terminal is in a signaling connection state, it receives first response data. The first response data instructs the terminal, the first base station and the second core network to complete the service processing corresponding to the service request data. The second core network is the core network registered by the terminal in the second integrated station. The first base station and the second core network are connected through the MESH communication network.
[0018] When the terminal is in an idle state and there is no registered second core network for the terminal, a second response data is received. The second response data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data.
[0019] When the terminal is in an idle state and the terminal has a registered second core network, it receives a first rejection request data and, in response to the first rejection request data, performs deregistration. The first rejection request is generated by the second core network in response to the service request data transmitted by the first base station.
[0020] In one possible implementation, the method further includes:
[0021] If the service request data indicates a signaling access request, then a second rejection request data is received. The second rejection request data is generated by the third core network in response to the service processing data transmitted by the first base station when the first core network link fails. The third core network is connected to the first base station through a MESH communication network.
[0022] In response to the second rejection request data, deregistration is performed, and after registration is completed, SUCI initial registration request data is sent to the first base station;
[0023] The third response data is received, which instructs the terminal, the first base station, and the third core network to complete the service processing corresponding to the SUCI initial registration request data.
[0024] In one possible implementation, after sending service request data to the first base station in the first integrated station, the method further includes:
[0025] Receive fourth response data, which indicates a failure in the first core network link;
[0026] At preset time intervals, the service request data is sent again to the first base station.
[0027] Receive the second response data.
[0028] Thirdly, a service data processing device is proposed, applied to a first base station in a first integrated station, the first integrated station further including a first core network, the device comprising:
[0029] The data receiving module is used to receive business request data sent by the terminal;
[0030] The first forwarding module is used to transmit the service request data to the second core network that has completed the registration of the terminal if the terminal is in a signaling connection state. The second core network is located at the second integrated station. The service request data instructs the terminal, the first base station and the second core network to complete the service processing corresponding to the service request data. The first base station and the second core network are connected through a MESH communication network.
[0031] The second forwarding module is used to transmit the service request data to the first core network if the terminal is in an idle state and the terminal does not have a registered second core network. The service request data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data.
[0032] The third forwarding module is used to transmit the service request data to the second core network if the terminal is in an idle state and the terminal is registered with the second core network. The service request data instructs the second core network to generate first rejection request data, which is used to instruct the terminal to deregister.
[0033] Fourthly, a business data processing device is proposed, applied to a terminal located within the wireless coverage area of a first integrated station; the device includes:
[0034] The request data sending module is used to send service request data to the first base station in the first integrated station, and the first integrated station also includes a first core network.
[0035] The first response module is used to receive first response data when the terminal is in a signaling connection state. The first response data instructs the terminal, the first base station and the second core network to complete the service processing corresponding to the service request data. The second core network is the core network registered by the terminal in the second integrated station. The first base station and the second core network are connected through the MESH communication network.
[0036] The second response module is used to receive second response data when the terminal is in an idle state and the terminal does not have a registered second core network. The second response data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data.
[0037] The third response module is used to receive first rejection request data and, in response to the first rejection request data, deregister when the terminal is in an idle state and the terminal has a registered second core network. The first rejection request is generated by the second core network in response to the service request data transmitted by the first base station.
[0038] Fifthly, this application provides a business data processing system, including a first integrated station and a second integrated station, wherein the first integrated station includes a first core network and a first base station, and the second integrated station includes a second core network and a second base station; wherein,
[0039] The first base station is connected to the second core network via a MESH communication network, and the second base station is connected to the first core network via a MESH communication network.
[0040] The terminal sends service request data to the service data processing system, and the service request data instructs the terminal and the integrated multi-site network to complete the service processing corresponding to the service request data; the first base station is used to execute the method as described in the first aspect, and the terminal is used to execute the method as described in the second aspect.
[0041] Sixthly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;
[0042] The memory stores computer-executed instructions;
[0043] The processor executes computer execution instructions stored in the memory to implement the business data processing method as described in the first or second aspect.
[0044] In a seventh aspect, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the business data processing method as described in the first or second aspect.
[0045] Eighthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the business data processing method as described in the first or second aspect.
[0046] The service data processing method, apparatus, system, electronic device, and storage medium provided in this application connect base stations and core networks in different integrated stations through a MESH communication network. When the second core network registered by the terminal is different from the first core network in the current integrated station, the service request data can be sent to the second core network. The service processing is completed through the second core network, the first base station, and the terminal. In this way, during handover, the service request data can be transmitted to the original registered second core network through the first base station after handover, avoiding handover failure. Attached Figure Description
[0047] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0048] Figure 1 This is a structural diagram of a 5G integrated station shown in an exemplary embodiment;
[0049] Figure 2 This is an exemplary embodiment illustrating the structure of a business data processing system;
[0050] Figure 3 This is another exemplary embodiment illustrating a business data processing system architecture diagram;
[0051] Figure 4 This is a flowchart illustrating a business data processing method in an exemplary embodiment;
[0052] Figure 5 This is a schematic diagram illustrating a scenario of a business data processing method in an exemplary embodiment;
[0053] Figure 6 This is a schematic diagram illustrating a scenario of a business data processing method, as shown in another exemplary embodiment.
[0054] Figure 7 This is a flowchart illustrating a business data processing method in another exemplary embodiment;
[0055] Figure 8 This is a schematic diagram illustrating a scenario of a business data processing method, as shown in another exemplary embodiment.
[0056] Figure 9 This is a structural diagram of a business data processing device shown in an exemplary embodiment;
[0057] Figure 10 This is a structural diagram of a business data processing apparatus shown in another exemplary embodiment;
[0058] Figure 11 This is a schematic diagram illustrating the structure of an electronic device in an exemplary embodiment.
[0059] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation
[0060] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0061] Figure 1 This is a structural diagram of a 5G integrated station shown in an exemplary embodiment. The 5G integrated station includes a 5GC and a gNB (or gNodeB).
[0062] 5GC can be configured with multiple network elements, such as Figure 1 The AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), UDM (Unified Data Management), and PCF (Policy Control Function) shown are understandable. Figure 1 The network element in the example is just one example; other network elements may also exist. Figure 1 The image is not shown in the image.
[0063] Due to weight requirements for 5G integrated base stations, the integration of 5GC is relatively high, requiring the removal of non-essential network elements such as NRF and NEF, resulting in a service-free architecture for 5G integrated base stations.
[0064] In a 5G integrated base station, the 5GC and gNB can connect via the N3 interface or the N2 interface (the interface specified by 3GPP (Third Generation Partnership Project)).
[0065] In some embodiments, the terminal can access the 5G integrated station through the cluster Uu air interface to realize 5G broadband data services.
[0066] In some embodiments, the near-end configuration connects to the 5G integrated station via an internal interface to configure and manage services / equipment.
[0067] In some embodiments, the DN (Data Network) can be set up inside or outside the 5G integrated station to perform data processing. The DN can be connected to the 5GC through the N6 interface (the interface specified by 3GPP).
[0068] The 3GPP standard defines the interconnection and interoperability between 5G GCs, involving the interoperability of interfaces such as N8, N9, N12, N14, and N16, and requires the deployment of network elements such as NRF to realize a service-oriented architecture. However, 5G integrated multi-site networking does not have network elements such as NRF, and therefore cannot guarantee the requirements of secure cross-site handover, avoid traffic detours, high service availability, and high ease of network configuration.
[0069] Therefore, in the event of a sudden emergency, where the affected area needs to quickly achieve temporary communication coverage or blind spot coverage, there is a requirement for a standardized 5G integrated multi-site networking solution that supports high bandwidth, cross-site mobile calls without dropped calls, low cost, self-healing high reliability, ease of use, and mobile deployment.
[0070] Based on this, this application proposes a service data processing method, apparatus, system, electronic device, and storage medium that fully connects the base stations and core network of multiple integrated stations. This allows data to be transmitted to the original core network via the switched base station during handover, avoiding handover failure. The base stations and core network are connected via a MESH communication network. Since MESH transmission bandwidth is limited, when a terminal moving across stations finishes its service and transitions to CM-IDLE state (idle state), subsequent data service initiations by the terminal can be terminated locally without detours, preventing increased load on the MESH bearer network and avoiding traffic detours. If any integrated station fails, terminal services under that integrated station can be moved to other integrated stations and can still initiate services normally, achieving high service availability. Integrated stations are connected via a MESH communication network, minimizing interconnection interfaces and configurations to avoid increased service latency, decreased service stability, and complex configuration operations, resulting in high ease of network configuration.
[0071] Figure 2 and Figure 3 This is an exemplary embodiment illustrating a business data processing system architecture diagram, including multiple 5G integrated base stations, such as... Figure 2 The 5G integrated station 1, 5G integrated station 2, 5G integrated station 3, and 5G integrated station 4 are examples of this. Figure 3 The five-G integrated station 1, five-G integrated station 2 and five-G integrated station 3 are included.
[0072] like Figure 2 As shown, any two 5G integrated stations can be connected through a MESH communication network. This MESH communication network module can be set up in each 5G integrated station, and data transmission between the two 5G integrated stations can be realized through the MESH communication network module in each 5G integrated station.
[0073] In some embodiments, such as Figure 3As shown, any two 5G integrated stations can be connected through the MESH communication network, which can provide full connectivity for the gNB and 5GC of multiple 5G integrated stations. That is, the gNB of one 5G integrated station can be connected to the 5GC of another 5G integrated station through the MESH communication network.
[0074] like Figure 3 As shown, 5GC1 in 5G integrated station 1 is connected to gNB2 in 5G integrated station 2 through a MESH communication network, and is also connected to gNB3 in 5G integrated station 3 through a MESH communication network; gNB1 in 5G integrated station 1 is connected to 5GC2 in 5G integrated station 2 through a MESH communication network, and is also connected to 5GC3 in 5G integrated station 3 through a MESH communication network. The same applies to 5G integrated station 2 and 5G integrated station 3.
[0075] In some embodiments, terminals covered by a 5G integrated station can transmit data with the 5G integrated station via a Uu interface.
[0076] In some embodiments, any 5G integrated station is regarded as a first integrated station and another 5G integrated station is regarded as a second integrated station. Then, the first integrated station includes a first core network 5GC and a first base station gNB, and the second integrated station includes a second core network 5GC and a second base station gNB.
[0077] The first base station is connected to the second core network via a MESH communication network, and the second base station is connected to the first core network via a MESH communication network.
[0078] In some embodiments, the terminal sends service request data to the service data processing system, and the service request data instructs the terminal and the service data processing system to complete the service processing corresponding to the service request data.
[0079] In some embodiments, the terminal sends service request data to a 5G integrated station within the corresponding coverage area. The gNB and 5GC in the 5G integrated station within the corresponding coverage area, as well as the terminal, can interact to complete the service processing corresponding to the service request data. Alternatively, the gNB in the 5G integrated station within the corresponding coverage area can also send the service request data to the 5GC in other 5G integrated stations. The gNB in the 5G integrated station within the corresponding coverage area, the 5GC receiving the service request data, and the terminal can interact to complete the service processing corresponding to the service request data.
[0080] The terminal can be mobile or fixed. Network device 110 is a device that can communicate with user terminal 120 via a wireless link, such as a base station or base station controller. Each network device can provide communication coverage for a specific geographical area and can communicate with terminals located within that coverage area (cell).
[0081] In this disclosure, the terminal is a user-side entity used to receive or transmit signals, such as a mobile phone. A user terminal can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), user-side equipment, etc. Terminals can be communication-enabled vehicles, smart cars, mobile phones, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.
[0082] In this embodiment, through Figure 2 and Figure 3 The service data processing system shown in the diagram achieves full connectivity between the 5GC and gNB in the 5G integrated station through the N2 / N3 interface. There are no interfaces between the 5GCs, which simplifies the configuration of inter-station interfaces and improves usability. When the transmission to the destination station is successful, the handover between base stations within the 5GC based on the N2 interface (one handover method) allows terminals in the CM-CONNECTED state (signaling connection state) to switch between the original 5G integrated station and the new 5G integrated station without dropped calls. The system adopts the visited site direct handover (Local Breakout, LBO) method, where a single visited site provides access capabilities and session anchors, and traffic terminates at this site, avoiding the bottleneck of inter-station MESH communication network caused by traffic detours between 5G integrated stations. The 5GC implements the "access control based on GNBID (base station identifier)" function, enabling terminals moving to the visited site to access the site via Local Breakout, achieving the effect of "local traffic termination".
[0083] The embodiments disclosed herein do not limit the specific technology or device form used in the terminal.
[0084] The following description, in conjunction with the accompanying drawings, details the business data processing method and apparatus provided by this disclosure on the aforementioned business data processing system.
[0085] Figure 4 This is a flowchart illustrating an exemplary embodiment of a service data processing method, which is executed by a first base station in a first integrated station. The first integrated station also includes a first core network. The method includes:
[0086] S401, Receive service request data sent by the terminal.
[0087] In this embodiment, the terminal is located within the coverage area of the first integrated station. At this time, the terminal can send service request data. The service request data may include, but is not limited to, signaling access request data, SUCI initial registration request data, or data sent by the terminal during the process of interacting with a certain 5G integrated station and processing a certain service. No specific limitation is made here.
[0088] In this embodiment, the terminal is a 5G terminal.
[0089] S402. If the terminal is in a signaling connection state, the service request data is transmitted to the second core network that has completed the terminal registration. The second core network is located at the second integrated station. The service request data instructs the terminal, the first base station and the second core network to complete the service processing corresponding to the service request data. The first base station and the second core network are connected through the MESH communication network.
[0090] In some embodiments, the terminal is in a signaling connection state, i.e., CM-CONNECTED state, which indicates that the terminal is performing data services. It can be determined that the terminal is registered with the second core network at this time.
[0091] In some embodiments, the second core network is not the first core network, and the second core network is located in the second integrated station. This means that when the terminal is in a signaling connection state, it is located within the coverage area of the second integrated station. During service processing, the terminal moves from the coverage area of the second integrated station to the coverage area of the first integrated station, such as... Figure 5 As shown, the terminal moves from the second integrated station to the first integrated station.
[0092] Since the gNB and 5GC are fully connected in the service data processing system, that is, the first base station and the second core network are connected through the MESH communication network, the first base station can transmit the service request data to the second core network to perform inter-site handover and ensure that the terminal does not drop the call. At this time, the service data flow is an interaction between the terminal, the first base station, and the second core network. The service request data instructs the terminal, the first base station, and the second core network to complete the service processing corresponding to the service request data.
[0093] In this embodiment, after the terminal, the first base station, and the second core network complete the service processing corresponding to the service request data, the resources are released, and the terminal transitions to the CM-IDLE state (idle state). Since the terminal has moved to the coverage area of the first integrated station at this time, the second core network of the second integrated station, after AN Rlease (resource release), actively pages the terminal through the first base station, triggering the terminal to initiate a new Service Request, that is, to send new service request data to the first base station. At this time, the terminal sends new service request data to the first base station in the idle state. The first base station transmits the new service request data to the second core network. The service request data instructs the second core network to generate first rejection request data. The first rejection request data is used to instruct the terminal to deregister.
[0094] After the terminal completes the deregistration, it can initiate an initial registration access request to the first integrated station to complete the registration in the first core network and access the first integrated station.
[0095] S203. If the terminal does not have a registered second core network, the service request data is transmitted to the first core network. The service request data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data.
[0096] In some embodiments, when the terminal is in a signaling connection state and there is no second core network registered with the terminal, but the terminal is registered in the first core network, that is, from the moment the terminal is in the signaling connection state, it has always been within the coverage area of the first integrated base station without moving across stations. In this case, the first base station directly transmits the service request data to the first core network. The service data flows between the terminal, the first base station, and the first core network. The service request data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data. After the service processing is completed, the terminal releases resources.
[0097] In some embodiments, when the terminal is in an idle state and there is no second core network registered with the terminal, the service request data is the data of the initial access request, such as the signaling access request or the SUCI initial registration request data, indicating that the terminal is in the initial registration stage. At this time, the first base station directly transmits the service request data to the first core network. The service data flows between the terminal, the first base station, and the first core network. The service request data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data, so that the terminal registers in the first core network. After completing the service processing, the terminal releases resources.
[0098] S404. If the terminal is in an idle state and there is a registered second core network, the service request data is transmitted to the second core network. The service request data instructs the second core network to generate first rejection request data. The first rejection request data is used to instruct the terminal to deregister.
[0099] In some embodiments, the terminal is in an idle state, and the terminal has a registered second core network, similarly as... Figure 5 As shown, the terminal moves from the second integrated station to the first integrated station and performs cell reselection at the first base station. The service request data is the Registration Request data. Then, the first base station, the second core network, and the terminal perform access control based on GNBID.
[0100] In some embodiments, the AMF weight value of each site's 5GC is set to 255. When a terminal connection is established, the AMF notifies the corresponding gNB of its own load weight based on the GNBID configured at the site. The specific implementation process is as follows: In the 5GC MML (Man-Machine Language) configuration interface of each 5G integrated site: Configure the site's gNB identifier GNBID; For service request data initiated by the gNB, the 5GC identifies whether it is the site's gNB based on the GNBID. If it is, the 5GC replies with NG SETUPRESPONSE (response message) with a weight value of 255. Otherwise, the 5GC replies with NG SETUP RESPONSE with a weight value of 0, indicating that the gNB initiating the service request data is not the gNB of the 5G integrated site where the 5GC that responded with NG SETUP RESPONSE is located. The gNB initiating the service request data stores the AMF's load weight information.
[0101] In some embodiments, mobility access control is performed based on the GNBID configured at this site. The specific process is as follows: A Registration / Service Request is initiated for the CM-IDLE state terminal. The AMF in the 5GC checks whether the GNBID in the INITIAL UE MESSAGE message identifies the local 5G integrated site gNB. If it is, the 5GC processes the Registration / Service Request normally. Otherwise, it checks whether the Registration / Service Request carries the 5G-GUTI. If it carries the 5G-GUTI, the 5GC replies with Registration / Service Reject, carrying the Cause value "#9UE identity cannot be derived by the network". After receiving the information, if the terminal has a local user context, it performs local registration. Subsequently, the terminal deletes the 5G-GUTI, last visited registered TAI, TAI list, etc., and immediately performs an initial registration again. The gNB that receives the initial registration request will select the local 5GC according to the weight value and perform the initial registration process to access the local 5GC.
[0102] If the 5G-GUTI is not carried, it means that the terminal initiated the SUCI initial registration. The visited integrated station gNB does not select its own 5GC, but selects another site's 5GC with a weight value of 0. This indicates that the N2 link between the visited 5G integrated station gNB and the local 5GC is faulty. At this time, the selected 5GC should allow the terminal to access normal services. After the N2 link fault between the visited 5G integrated station gNB and the local 5GC is restored, the terminal will be triggered to re-access when it initiates the AN (access network) Rlease procedure, and will try to select the visited 5GC.
[0103] When the access network initiates an AN Rlease procedure, the AMF checks whether the UE's GNBID is the local gNB. If so, the AN Rlease procedure is executed. Otherwise, after completing the AN Rlease, the AMF actively pages the terminal, triggering the terminal to initiate a Service Request. The AMF checks the GNBID in the INITIAL UE MESSAGE message in the Service Request and identifies it as not being the local gNB. The 5GC replies with Registration / Service Reject, carrying the Cause value "#9UE identity cannot be derived by the network". The terminal receives this and performs local deregistration. Subsequently, the terminal will re-initiate the initial registration to access the 5G integrated station within the radio range.
[0104] In this embodiment, the first base station receives the service request data. The GNBID in the INITIAL UE MESSAGE identifies the first base station. Since the terminal is registered in the second core network, the first base station sends the service request data to the second core network. The second core network detects that the GNBID in the INITIAL UE MESSAGE identifies the first base station. The second core network recognizes that the GNBID is not its own gNB (second base station), and then replies with Registration / ServiceReject, carrying a Cause value of "#9UE identity cannot bederived by the network" (meaning that the UE's identity cannot be deduced from the received request). This first rejection request data reaches the terminal through the second base station, and the terminal receives the first rejection request data to perform local deregistration.
[0105] After the terminal responds to the first rejection request data and performs local deregistration, the terminal will re-initiate the initial registration to access the first integrated single station.
[0106] In some embodiments, the terminal is within the coverage area of the first integrated station and is registered in the first core network, such as... Figure 6 As shown, if the first core network link fails, the first base station will send the service request data to the third core network. If the service request data indicates a signaling access request, the service request data will instruct the third core network to generate second rejection request data. If the service request data indicates a SUCI initial registration request, the service request data will instruct the terminal, the first base station, and the third core network to complete the service processing corresponding to the service request data. The third core network and the first base station are connected through the MESH communication network. The second rejection request data is used to instruct the terminal to deregister.
[0107] In some embodiments, the third core network is the core network of other 5G integrated stations besides the first integrated station.
[0108] In this embodiment, the service request data indicates a signaling access request. If the first base station discovers a link failure in the first core network, it will randomly route the service request data to another core network, such as the third core network. The service request data arrives at the third core network through the first base station. The third core network detects that the 5G-GUT (5G Globally Unique Temporary Identifier, which is a globally unique temporary UE identifier in the 5G system) is not assigned by the third core network. Since the terminal is registered in the first core network, its 5G-GUT is assigned by the first core network. Therefore, the third core network replies with Registration Reject, i.e., the second rejection request data, and carries the Cause value "#9UE identity cannot be derived by the network". The second rejection request data arrives at the terminal through the first base station, and the terminal responds to the second rejection request data to perform local deregistration.
[0109] After the terminal responds to the second rejection request data and performs local deregistration, the terminal sends service request data indicating an initial SUCI registration request. The first base station discovers a link failure with the first core network and can only randomly route to another core network, which may be the core network that generated the second rejection request data or not. Taking the third core network as an example, the third core network checks the GNBID in the INITIALUE MESSAGE message of the service request data indicating the initial SUCI registration request. The GNBID identifies the first base station as a third base station that is not the third integrated station where the third core network is located. However, it finds that UE1 is making an initial SUCI registration request, so it allows the terminal to initially register and access the CM-CONNECTED state service. The terminal can interact with the first base station and the third core network to complete the service processing.
[0110] After the terminal initially registers and accesses CM-CONNECTED mode services, and the services are completed, the terminal enters CM-IDLE mode. Since the terminal is not within the coverage area of the third integrated station, the third core network actively pages the terminal and sends data through the first base station to trigger the terminal to initiate new service request data. This new service request data reaches the third core network through the first base station. The third core network checks the GNBID in the INITIAL UE MESSAGE message to identify that it is not the local gNB, and replies with Registration / Service Reject, carrying the Cause value "#9UE identity cannot be derived by the network". Registration / Service Reject reaches the terminal through the first base station, and the terminal performs local deregistration. Subsequently, the terminal will re-initiate the initial registration. If the link of the first core network is restored, the access under the first integrated station will be completed through the interaction of the terminal, the first base station, and the first core network.
[0111] In some embodiments, when the first core network link fails, the first base station does not randomly route the service request data to other core networks, but instead sends fourth response data to the terminal. The fourth response data indicates that the first core network link has failed. Thus, the terminal can resend the service request data after a preset time interval. During this preset time interval, the first core network link can be restored, so that after successful restoration, the first core network, the first base station, and the terminal can interact to complete the service processing.
[0112] The preset time period can be determined by empirical parameters, such as 10 seconds, 15 seconds, etc., and no specific restrictions are made here.
[0113] In this embodiment, base stations and core networks in different integrated stations are connected through a MESH communication network. When the second core network registered by the terminal is different from the first core network in the current integrated station, the service request data can be sent to the second core network. The service processing is completed through the second core network, the first base station, and the terminal. In this way, during handover, the service request data can be transmitted to the original registered second core network through the first base station after handover, avoiding handover failure. In the event of a failure of the first core network, the service request data can also be sent to other core networks for processing through the MESH communication network, improving the reliability of service processing.
[0114] The 5G integrated inter-site base station and core network management connection can meet the requirements of "high bandwidth, no dropped calls when moving across sites, low cost, high reliability with self-healing, high ease of use, support for mobile deployment, and standardized interfaces" in emergency multi-site networking scenarios.
[0115] Figure 7This is a flowchart illustrating another exemplary embodiment of a service data processing method, performed by a terminal located within the wireless coverage area of a first integrated station. The method includes:
[0116] S701, Send service request data to the first base station in the first integrated station, the first integrated station also includes the first core network.
[0117] In this embodiment, the first base station receives service request data.
[0118] The implementation of step S701 can be referred to step S401 and its related embodiments, and will not be repeated here.
[0119] S702. When the terminal is in the signaling connection state, it receives first response data. The first response data instructs the terminal, the first base station and the second core network to complete the service processing corresponding to the service request data. The second core network is the core network registered by the terminal in the second integrated station. The first base station and the second core network are connected through the MESH communication network.
[0120] In some embodiments, the terminal is in a signaling connection state and the terminal has a registered second core network, such as... Figure 5 As shown, the terminal moves from the second integrated station to the first integrated station. The first terminal sends service request data to the second core network. The terminal, the first base station, and the second core network complete the service processing corresponding to the service request data. The terminal receives first response data, which may be the data received by the terminal during the process of the terminal, the first base station, and the second core network interacting to complete the service processing corresponding to the service request data.
[0121] The implementation of step S702 can be referred to step S402 and its related embodiments, and will not be repeated here.
[0122] S703. When the terminal is in an idle state and there is no registered second core network for the terminal, the terminal receives second response data. The second response data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data.
[0123] In some embodiments, when the terminal is in an idle state and there is no registered second core network, the service request data is the data of the initial access request. The first base station directly transmits the service request data to the first core network. The service data flow is an interaction between the terminal, the first base station, and the first core network to complete the service processing. The second response data is the data received by the terminal during the process of the terminal, the first base station, and the first core network completing the service processing corresponding to the service request data.
[0124] The implementation of step S703 can be referred to step S403 and its related embodiments, and will not be repeated here.
[0125] In some embodiments, the terminal is in a signaling connection state and there is no second core network registered with the terminal. The terminal is registered in the first core network. The service data flow is an interaction between the terminal, the first base station, and the first core network. The service request data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data.
[0126] S704. When the terminal is in an idle state and there is a registered second core network, the terminal receives a first rejection request data and responds to the first rejection request data to deregister. The first rejection request is generated by the second core network in response to the service request data transmitted by the first base station.
[0127] In some embodiments, such as Figure 5 As shown, the terminal moves from the second integrated station to the first integrated station, performs cell reselection at the first base station, and the first base station sends the service request data to the second core network. The first base station, the second core network, and the terminal perform access control based on GNBID.
[0128] The second core network detects that the GNBID in the INITIAL UE MESSAGE message identifies the first base station, which is not the local gNB (second base station). It then generates first rejection request data, which is delivered to the terminal through the first base station. The terminal receives the first rejection request data and performs local deregistration.
[0129] After the terminal responds to the first rejection request data and performs local deregistration, the terminal will re-initiate the initial registration and access the first integrated single station.
[0130] The implementation of step S704 can be referred to the relevant embodiment of step S404, and will not be repeated here.
[0131] In some embodiments, if the service request data indicates a signaling access request, then a second rejection request data is received. The second rejection request data is generated by the third core network in response to the service processing data transmitted by the first base station when the first core network link fails. The third core network and the first base station are connected through a MESH communication network. In response to the second rejection request data, deregistration is performed, and after registration is completed, SUCI initial registration request data is sent to the first base station. A third response data is received, which instructs the terminal, the first base station, and the third core network to complete the service processing corresponding to the SUCI initial registration request data.
[0132] In this embodiment, the third response data is the data received by the terminal during the process of the terminal, the first base station, and the third core network completing the service processing corresponding to the SUCI initial registration request data.
[0133] In some embodiments, a fourth response data is received, which indicates a first core network link failure; after a preset time interval, service request data is sent to the first base station again, and a second response data is received.
[0134] The fourth response data is the data returned to the terminal by the first base station after detecting a failure in the first core network link. The terminal can resend the service request data after a preset time interval. During this preset time interval, the first core network link can be restored so that after successful restoration, the first core network, the first base station and the terminal can interact to complete the service processing.
[0135] based on Figure 4 and Figure 7 This embodiment proposes a business processing method, implemented in Figure 2 and Figure 3 The business processing system in the middle.
[0136] In some embodiments, each terminal can open a full account on a 5G integrated station in the service processing system. If a certain 5G integrated station fails and cannot work, causing the terminals under that 5G integrated station to be unable to access the network, then the 5G integrated station under that 5G integrated station will move to the wireless coverage area of another 5G integrated station. Since the terminals have opened a full account, there is also card opening and account opening data under the other 5G integrated station, so the terminals can normally access the other 5G integrated station to perform service processing.
[0137] like Figure 8 As shown, there are multiple terminals such as UE1, UE2 and UE3. UE2 is within the coverage area of 5G integrated station 2, UE3 is within the coverage area of 5G integrated station 3, and integrated station 1 is malfunctioning and cannot work. UE1 was originally within the coverage area of 5G integrated station 1. At this time, UE1 can move to the coverage area of 5G integrated station 2 and perform normal service processing.
[0138] In some embodiments, such as Figure 5 As shown, the terminal moves from the second integrated station to the area covered by the first integrated station.
[0139] If the terminal is in CM-CONNECTED state and is performing data services, and the terminal moves to the wireless coverage area of the first integrated station, an inter-station handover will be performed to ensure that the terminal does not drop the call. At this time, the data flow is: interaction between the terminal, the first base station, and the second core network.
[0140] After all services of the terminal end and radio resources are released, the terminal transitions to CM-IDLE state. After ANRlease, the second core network actively pages the terminal and triggers the terminal to initiate a Service Request. The second core network checks the GNBID (identifying the first base station) in the INITIAL UEMESSAGE message to identify the non-local gNB (second base station). The second core network replies with Registration / Service Reject, carrying the Cause value "#9UE identity cannot be derived by the network". After receiving the reply, the terminal performs local deregistration. Subsequently, the terminal will re-initiate the initial registration to access the first integrated station.
[0141] If the terminal is in CM-IDLE state, when it moves to the wireless coverage area of the first integrated station, it performs cell reselection based on the first reference. The terminal initiates a mobility registration request (Registration Request). The second core network checks the GNBID (first base station) in the INITIALUE MESSAGE message to identify a non-local gNB (second base station). The second core network replies with a Registration Reject message, carrying the Cause value "#9UE identity cannot be derived by the network". After receiving this, the terminal performs local deregistration. Subsequently, the terminal will re-initiate initial registration to access the first integrated station. Then, the terminal initiates data services through the first integrated station. At this time, the data flow is: terminal, first base station, and first core network, which can ensure that the data flow terminates locally.
[0142] In some embodiments, such as Figure 6 As shown, the first base station in the first integrated station where the terminal is located is normal, while the second base station has a link failure.
[0143] At this time, if a terminal within the coverage area of the first base station initiates a signaling access request, and the first base station discovers a link failure with the first core network, it can only be randomly routed to the third core network or other core networks. For example, if it accesses the third core network, the third core network checks that the 5G-GUTI is not assigned by the third core network. The third core network replies with Registration Reject, carrying the Cause value "#9 Terminal identity cannot be derived by the network", and performs local registration.
[0144] When a terminal initiates an initial registration request in SUCI mode, the first base station discovers a link failure with the first core network and can only randomly route to the third core network or other core networks. For example, it accesses the third core network. The third core network checks the GNBID (identifying the first base station) in the INITIALUE MESSAGE message to identify that it is not its own gNB (the third base station). However, it finds that the terminal is making an initial registration request in SUCI mode and allows the terminal to initially register and access CM-CONNECTED state services.
[0145] After the terminal service ends and an AN Rlease is performed, the third core network actively pages the terminal, triggering the terminal to initiate a Service Request. The third core network checks the GNBID in the INITIALUE MESSAGE message to identify that it is not the local gNB. The third core network replies with Registration / Service Reject, carrying the Cause value "#9 Terminal identity cannot be derived by the network". The terminal receives the data and performs local deregistration. Subsequently, the terminal will re-initiate the initial registration: if the link failure between the first base station and the first core network is restored at this time, the terminal will access the first core network; otherwise, the terminal will initiate an initial registration request in SUCI mode.
[0146] In other embodiments, Figure 6 In the scenario of a first core network link failure, a signaling access request is initiated at a preset time interval, and the system waits for the first core network to start successfully before accessing the first core network.
[0147] Figure 9 This is an exemplary embodiment illustrating a service data processing apparatus structure diagram, applied to a first base station in a first integrated station. The first integrated station further includes a first core network. The apparatus includes:
[0148] The data receiving module 910 is used to receive service request data sent by the terminal;
[0149] The first forwarding module 930 is used to transmit service request data to the second core network that has completed terminal registration if the terminal is in a signaling connection state. The second core network is located at the second integrated station. The service request data instructs the terminal, the first base station and the second core network to complete the service processing corresponding to the service request data. The first base station and the second core network are connected through the MESH communication network.
[0150] The second forwarding module 950 is used to transmit the service request data to the first core network if the terminal is in an idle state and the terminal does not have a registered second core network. The service request data instructs the terminal, the first base station and the first core network to complete the service processing corresponding to the service request data.
[0151] The third forwarding module 970 is used to transmit service request data to the second core network if the terminal is in an idle state and the terminal is registered with the second core network. The service request data instructs the second core network to generate first rejection request data, which is used to instruct the terminal to deregister.
[0152] In one possible implementation, the apparatus further includes:
[0153] The second data transmission module is used to send service request data to the third core network if the first core network link fails. If the service request data indicates a signaling access request, the service request data instructs the third core network to generate second rejection request data. If the service request data indicates a SUCI initial registration request, the service request data instructs the terminal, the first base station, and the third core network to complete the service processing corresponding to the service request data. The third core network and the first base station are connected through the MESH communication network. The second rejection request data is used to instruct the terminal to deregister.
[0154] In one possible implementation, the apparatus further includes:
[0155] The second data transmission module is used to send the fourth response data to the terminal, the fourth response data indicating a first core network link failure;
[0156] The third data transmission module is used to receive service request data sent by the terminal at preset time intervals and send the service request data to the first core network. The service request data instructs the terminal, the first base station and the first core network to complete the service processing corresponding to the service request data.
[0157] Figure 10 This is a structural diagram of a service data processing device illustrated in another exemplary embodiment, applied to a terminal located within the wireless coverage area of a first integrated station; the device includes:
[0158] The request data sending module 1010 is used to send service request data to the first base station in the first integrated station. The first integrated station also includes a first core network.
[0159] The first response module 1030 is used to receive first response data when the terminal is in the signaling connection state. The first response data instructs the terminal, the first base station and the second core network to complete the service processing corresponding to the service request data. The second core network is the core network registered by the terminal in the second integrated station. The first base station and the second core network are connected through the MESH communication network.
[0160] The second response module 1050 is used to receive second response data when the terminal is in an idle state and there is no registered second core network. The second response data instructs the terminal, the first base station and the first core network to complete the service processing corresponding to the service request data.
[0161] The third response module 1070 is used to receive first rejection request data and, in response to the first rejection request data, deregister when the terminal is in an idle state and the terminal has a registered second core network. The first rejection request is generated by the second core network in response to the service request data transmitted by the first base station.
[0162] In one possible implementation, the apparatus further includes:
[0163] The data rejection module is used to receive second rejection request data if the service request data indicates a signaling access request. The second rejection request data is generated by the third core network in response to the service processing data transmitted by the first base station when the first core network link fails. The third core network and the first base station are connected through the MESH communication network.
[0164] The deregistration module is used to deregister in response to the second rejection request data, and send SUCI initial registration request data to the first base station after registration is completed;
[0165] The fourth response module is used to receive the third response data, which instructs the terminal, the first base station, and the third core network to complete the service processing corresponding to the SUCI initial registration request data.
[0166] In one possible implementation, after sending service request data to the first base station in the first integrated station, the method further includes:
[0167] The fifth response module is used to receive the fourth response data, which indicates a failure in the first core network link.
[0168] The data retransmission module is used to resend the service request data to the first base station at preset time intervals.
[0169] The sixth response module is used to receive the second response data.
[0170] The business data processing apparatus provided in this embodiment can be used to execute the above-described business data processing method. Its implementation principle and technical effect are similar, and will not be described again in this embodiment.
[0171] Figure 11 This is a schematic diagram illustrating the structure of an electronic device in an exemplary embodiment. Please refer to [link / reference]. Figure 11The terminal 1100 may include a processor 1101 and a memory 1102, wherein the processor 1101 and the memory 1102 can communicate; for example, the processor 1101 and the memory 1102 communicate through a communication bus 1103, the memory 1102 is used to store computer execution instructions, and the processor 1101 is used to call the computer execution instructions in the memory to execute the business data processing method shown in any of the above method embodiments.
[0172] The aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.
[0173] The aforementioned electronic devices can be terminals, base stations, or other network devices.
[0174] This application provides a computer-readable storage medium storing computer-executable instructions; when executed by a processor, the computer-executable instructions are used to implement the business data processing method as described in any of the above embodiments.
[0175] This application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it causes the computer to perform the above-described business data processing method.
[0176] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.
[0177] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.
Claims
1. A business data processing method, characterized in that, A first base station applied in a first integrated station, the first integrated station further comprising a first core network, the method comprising: Receive service request data sent by the terminal; If the terminal is in a signaling connection state, the service request data is transmitted to the second core network that has completed the terminal registration. The second core network is located at the second integrated station. The service request data instructs the terminal, the first base station, and the second core network to complete the service processing corresponding to the service request data. The first base station and the second core network are connected through the MESH communication network. If the terminal does not have a registered second core network, the service request data is transmitted to the first core network, and the service request data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data. If the terminal is in an idle state and the terminal is registered with a second core network, the service request data is transmitted to the second core network. The service request data instructs the second core network to generate first rejection request data, which is used to instruct the terminal to deregister.
2. The method according to claim 1, characterized in that, After transmitting the service request data to the second core network that has completed the terminal registration, the method further includes: If the first core network link fails, the service request data is sent to the third core network. If the service request data indicates a signaling access request, the service request data instructs the third core network to generate second rejection request data. If the service request data indicates a SUCI initial registration request, the service request data instructs the terminal, the first base station, and the third core network to complete the service processing corresponding to the service request data. The third core network and the first base station are connected through a MESH communication network. The second rejection request data is used to instruct the terminal to deregister.
3. The method according to claim 2, characterized in that, The method further includes: The fourth response data is sent to the terminal, and the fourth response data indicates a failure of the first core network link. At preset time intervals, the system receives service request data sent by the terminal and sends the service request data to the first core network. The service request data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data.
4. A business data processing method, characterized in that, The method is applied to a terminal located within the wireless coverage area of a first integrated station; the method includes: Send service request data to the first base station in the first integrated station, the first integrated station also includes a first core network; When the terminal is in a signaling connection state, it receives first response data. The first response data instructs the terminal, the first base station and the second core network to complete the service processing corresponding to the service request data. The second core network is the core network registered by the terminal in the second integrated station. The first base station and the second core network are connected through the MESH communication network. When the terminal is in an idle state and there is no registered second core network for the terminal, a second response data is received. The second response data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data. When the terminal is in an idle state and the terminal has a registered second core network, it receives a first rejection request data and, in response to the first rejection request data, performs deregistration. The first rejection request is generated by the second core network in response to the service request data transmitted by the first base station.
5. The method according to claim 4, characterized in that, The method further includes: If the service request data indicates a signaling access request, then a second rejection request data is received. The second rejection request data is generated by the third core network in response to the service processing data transmitted by the first base station when the first core network link fails. The third core network is connected to the first base station through a MESH communication network. In response to the second rejection request data, deregistration is performed, and after registration is completed, SUCI initial registration request data is sent to the first base station; The third response data is received, which instructs the terminal, the first base station, and the third core network to complete the service processing corresponding to the SUCI initial registration request data.
6. The method according to claim 4, characterized in that, After sending service request data to the first base station in the first integrated station, the method further includes: Receive fourth response data, which indicates a failure in the first core network link; At a preset time interval, the service request data is sent again to the first base station; Receive the second response data.
7. A business data processing device, characterized in that, A first base station applied in a first integrated station, the first integrated station further including a first core network, the device comprising: The data receiving module is used to receive business request data sent by the terminal; The first forwarding module is used to transmit the service request data to the second core network that has completed the registration of the terminal if the terminal is in a signaling connection state. The second core network is located at the second integrated station. The service request data instructs the terminal, the first base station and the second core network to complete the service processing corresponding to the service request data. The first base station and the second core network are connected through a MESH communication network. The second forwarding module is used to transmit the service request data to the first core network if the terminal is in an idle state and the terminal does not have a registered second core network. The service request data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data. The third forwarding module is used to transmit the service request data to the second core network if the terminal is in an idle state and the terminal is registered with the second core network. The service request data instructs the second core network to generate first rejection request data, which is used to instruct the terminal to deregister.
8. A business data processing device, characterized in that, Applied to a terminal located within the wireless coverage area of the first integrated station; the device includes: The request data sending module is used to send service request data to the first base station in the first integrated station, and the first integrated station also includes a first core network. The first response module is used to receive first response data when the terminal is in a signaling connection state. The first response data instructs the terminal, the first base station and the second core network to complete the service processing corresponding to the service request data. The second core network is the core network registered by the terminal in the second integrated station. The first base station and the second core network are connected through the MESH communication network. The second response module is used to receive second response data when the terminal is in an idle state and the terminal does not have a registered second core network. The second response data instructs the terminal, the first base station, and the first core network to complete the service processing corresponding to the service request data. The third response module is used to receive first rejection request data and, in response to the first rejection request data, deregister when the terminal is in an idle state and the terminal has a registered second core network. The first rejection request is generated by the second core network in response to the service request data transmitted by the first base station.
9. A business data processing system, characterized in that, It includes a first integrated station and a second integrated station. The first integrated station includes a first core network and a first base station, and the second integrated station includes a second core network and a second base station; wherein, The first base station is connected to the second core network via a MESH communication network, and the second base station is connected to the first core network via a MESH communication network. The terminal sends service request data to the service data processing system, and the service request data instructs the terminal and the integrated multi-site network to complete the service processing corresponding to the service request data; the first base station is used to execute the method as described in any one of claims 1-3, and the terminal is used to execute the method as described in any one of claims 4-6.
10. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-6.
11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-6.
12. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-6.