Implementation method and device for supporting emergency service by communication base station, and communication base station

Abstract

The invention discloses a method and a device for realizing emergency service support of a communication base station, and the communication base station. The method comprises the following steps: a first base station centralized entity receives emergency service support related information of a service cell sent by a first base station separation entity through a first message, the related information comprises at least one of an IP multimedia subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication and an IMS emergency service support indication for an independent non-public network SNPN; the first base station centralized entity determines whether the RRC establishment of the terminal equipment is associated with a session of an emergency call according to a reason value carried in a radio resource control RRC message sent by the terminal equipment; and the first base station centralized entity determines whether the session is used for emergency service according to a second message sent by the core network. The present application solves the technical problem that a base station cannot meet the demand of a terminal to make an emergency call in a limited service state due to the fact that the base station adopts an architecture in which a centralized entity and a separate entity are separated.

Description

Technical Field

[0001] The present application relates to the field of wireless communications, and more specifically, to a method and device for implementing a communication base station supporting emergency services, and a communication base station. Background Art

[0002] An emergency call is a call request initiated by a user in an emergency by dialing an alarm or distress number through a communication terminal such as a mobile phone or landline. The communication network connects the call to the nearest emergency special service center based on the user's location information. The emergency numbers corresponding to the same emergency service type may be different in different countries. The emergency special service numbers currently used in mainland my country include 110 (alarm), 119 (fire), 120 (ambulance) and 122 (traffic accidents). Operators usually bind the emergency service type with the emergency number and store it in the Subscriber Identity Module (SIM) or the Universal Subscriber Identity Module (USIM). When the terminal equipment (UE) has a card, the emergency number has three sources: from the elementary file (EF) in the SIM card or USIM card, configured by the network, and configured by the UE itself. According to the current protocol, the 5G communication system supports UE to obtain emergency services in limited service state and normal service state. UE in limited service state can obtain emergency services without signing a contract with the operator (based on local operator policies, the network may also reject emergency service registration requests initiated by UE that has been determined to be in limited service state), that is, users can successfully make emergency calls when there is no card inserted, or the card is in arrears or shut down. Therefore, the terminal needs to support cardless emergency calls. Terminal manufacturers usually configure the emergency numbers and service types of different operators in the terminal, and can configure the emergency numbers into two states of "false emergency" and "true emergency" according to the operator configuration: false emergency means that non-UE detects the emergency session process, and this state will be dialed as a normal number; true emergency means that UE detects the emergency session process, and this state will be dialed in emergency mode.

[0003] Figure 1a It is a schematic diagram of a 5G base station architecture with a centralized entity and a separate entity, such as Figure 1aAs shown in the figure, the 5G system architecture is divided into two parts: 5G core (5GC) and 5G access network (NG-RAN). 5GC includes control plane network elements and user plane network elements. The control plane network elements include access and mobility management functions (AMF) and session management functions (SMF); the user plane network elements include user plane functions (UPF). NG-RAN is connected to AMF / UPF through a flexible NG interface. Each node of NG-RAN can be connected to multiple AMFs and UPFs.

[0004] Figure 1b This is a schematic diagram comparing the base station architecture of 4G network and 5G network. Figure 1b As shown in the figure, in the 4G network, the base station is directly connected to the core network through the indoor baseband processing unit (Building Base band Unit, BBU), but in order to support the cloudification and slicing of wireless access, the 5G base station splits the BBU in the 4G base station into a centralized entity (Centralized Unit, CU) and a distributed entity (Distributed Unit, DU). At the same time, the large-scale active antenna unit (Active Antenna Unit, AAU) replaces the functions of the radio remote unit (Radio Remote Unit, RRU) and antenna, and the CU also integrates some functions from the core network. Multiple DUs share a CU for centralized management, which can realize the sharing of base station resources, thereby improving the efficiency of inter-station interaction.

[0005] According to the current protocol, when the base station separation architecture is adopted, the separation entity (gNB-DU) in the 5G base station generates all the information displayed in SIB1 and MIB, and the centralized entity (gNB-CU) in the 5G base station does not read any information encoded in the RRC ASN.1 format, but the gNB-CU still needs to obtain the necessary information related to the self-organizing network (SON) and AMF contained in SIB1 (System Information Block #1) and MIB (Master Information Block) for further operations. Therefore, when the base station adopts the architecture of gNB-CU and gNB-DU separation, there will be the following problems when supporting emergency services (emergency calls):

[0006] The gNB-CU cannot determine whether the local Radio Access Technology (RAT) supports emergency services: According to the current protocol, the gNB-CU does not read any information encoded in the Radio Resource Control (RRC) ASN.1 format, and therefore cannot obtain the necessary information contained in the messages generated by the gNB-DU for further operations.

[0007] When the 5G network does not support emergency services, the gNB-CU cannot obtain relevant configuration information in time, affecting the core network configuration emergency service fallback process: the current Served Cell Information IE cannot indicate to the gNB-CU key information about IP Multimedia Subsystem (IMS) emergency service support, IMS-based eCall emergency call support, and Stand-alone Non-Public Network (SNPN) IMS emergency service emergency call support.

[0008] When the 5G network supports emergency services, the core network cannot obtain the corresponding cell information in time and cannot provide emergency services to users in time: Since the gNB-CU does not receive the indication of the cell's support for emergency services, the core network cannot carry the indication in the registration acceptance message in time to indicate that the 5GC network supports emergency services.

[0009] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0010] The embodiments of the present application provide a method and device for implementing a communication base station to support emergency services, and a communication base station, so as to at least solve the technical problem that the need for terminals in a limited service state to make emergency calls cannot be met due to the base station adopting an architecture with a centralized entity and a separated entity.

[0011] According to a first aspect of an embodiment of the present application, a method for implementing emergency service support by a communication base station is provided, comprising: a first base station centralized entity receives emergency service support related information of a service cell sent by a first base station separated entity through a first message, wherein the emergency service support related information of the service cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; the first base station centralized entity determines whether the RRC establishment of a terminal device is associated with a session for an emergency call based on a cause value carried in a radio resource control RRC message sent by the terminal device; the first base station centralized entity determines whether the session is used for emergency services based on a second message sent by the core network.

[0012] Optionally, the first message is an intra-base station interface message, which includes at least one of the following: an F1 interface establishment request message and an update configuration message of the first base station separation entity, wherein the F1 interface is a connection interface between the first base station centralized entity and the first base station separation entity.

[0013] Optionally, the second message is a core network message sent by the core network, and the first message may be an indication for establishing an emergency call, including the configuration of allocating and reserving priority ARP values; the first base station centralized entity determines whether the session is used for an emergency call based on the ARP value configured in the core network, and the ARP value indicates the usage of the emergency service to the first base station.

[0014] Optionally, the above method also includes: the first base station centralized entity determines the target cell for providing emergency services and the form of providing emergency services based on the first message; at least includes: when at least one indication information of the IMS emergency service support indication, the IMS-based eCall emergency service support indication and the IMS emergency service support indication for SNPN exists in the information field of the service cell, determining the target cell for providing emergency services and the form of providing emergency services based on the first message.

[0015] Optionally, the terminal device determines the form of implementing the emergency service through the following method: the terminal device reads the emergency service related information supported by the service cell from the broadcast message, wherein the broadcast message is generated by the first base station separation entity and sent to the terminal device; when the terminal device is in a normal state and in the SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN and determines whether the emergency service can be obtained through the SNPN; if the terminal device can register for the emergency service through the SNPN, it is determined that the emergency service is obtained through the SNPN; if the terminal device cannot search for a cell that supports emergency services in any available SNPN, the terminal device Deactivate SNPN access mode; when the terminal device is in a normal state and not in SNPN access mode, the terminal device reads the IMS-based eCall emergency service support indication and determines whether it can obtain eCall emergency service based on IMS; if the public land mobile network PLMN in a non-shared environment or all PLMNs in a shared environment support obtaining eCall emergency service based on IMS, the terminal device determines to obtain eCall emergency service based on IMS; if the PLMN in a non-shared environment or all PLMNs in a shared environment do not support obtaining eCall emergency service based on IMS, the terminal device determines to perform IMS emergency service registration.

[0016] Optionally, the terminal device also determines the form of implementing the emergency service through the following method: when the terminal device is in an abnormal state and in the SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN and determines whether the emergency service can be obtained through the SNPN, wherein the terminal device being in an abnormal state includes: the terminal device is in a limited service state, or the terminal device resides normally in the cell but fails to successfully register with the network; if the terminal device can register for emergency services through the SNPN, it is determined that the emergency service is obtained through the SNPN; if the terminal device cannot search for a cell that supports emergency services in any available SNPN, the terminal device deactivates the SNPN access mode; when the terminal device is in an abnormal state and is not in the SNPN access mode, the terminal device reads the IMS emergency service support indication based on the SNPN, and determines whether the emergency service can be obtained through the SNPN. S's eCall emergency service support indication and IMS emergency service support indication; if the PLMN in the non-shared environment or all PLMNs in the shared environment support obtaining eCall emergency services based on IMS, the terminal device determines to obtain eCall emergency services based on IMS; if the PLMN in the non-shared environment or all PLMNs in the shared environment do not support obtaining eCall emergency services based on IMS, and the enumeration type corresponding to the IMS emergency service support indication is true, the terminal device determines to perform IMS emergency service registration; if the PLMN in the non-shared environment or all PLMNs in the shared environment do not support the terminal device in an abnormal state to perform IMS emergency service registration, a fallback process is triggered, wherein the fallback process is used to execute emergency services from a 4G network or a network below the 4G network.

[0017] Optionally, the broadcast message is generated by the first base station separation entity after determining that the cell supports emergency call services according to the configuration, wherein the configuration includes the configuration of the network management; the emergency call services include: at least one of IMS emergency calls, IMS-based eCall emergency calls and IMS emergency services for SNPN; the broadcast message is a SIB message, and the SIB message includes: at least one of IMS emergency service support indication, IMS-based eCall emergency service support indication and IMS emergency service support indication for SNPN.

[0018] Optionally, the above method further includes: the first base station centralized entity receives separation entity system information sent by the first base station separation entity through a first message, wherein the SIB message is encapsulated in the separation entity system information.

[0019] Optionally, the existence of the emergency service support related information of the serving cell is used to indicate that the emergency service support related information is broadcast to the terminal device in the broadcast message of the corresponding cell.

[0020] Optionally, the above method also includes: the first base station centralized entity sends a request message for establishing a terminal device context to the first base station separated entity and a third message instructing the first base station separated entity to establish a session bearer, wherein the request message carries an ARP value.

[0021] Optionally, the above method also includes: the first base station sends the emergency service support related information of the service cell to the second base station through the XN interface, wherein the second base station is any base station different from the first base station; the emergency service support related information of the service cell is used to provide emergency services for the terminal device in the second base station after the terminal device is switched.

[0022] According to the second aspect of an embodiment of the present application, another method for implementing emergency service support by a communication base station is also provided, including: a first base station separation entity sends emergency service support related information of a service cell to a first base station centralized entity through a first message, wherein the emergency service support related information of the service cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; the first base station separation entity receives a third message sent by the first base station centralized entity, wherein the third message is used to instruct the first base station separation entity to establish a session bearer for emergency services; the first base station separation entity establishes a session bearer in response to the third message.

[0023] Optionally, the first message is an intra-base station interface message, which includes at least one of the following: an F1 interface establishment request message and an update configuration message of the first base station separation entity, wherein the F1 interface is a connection interface between the first base station centralized entity and the first base station separation entity.

[0024] Optionally, the above method also includes: the first base station separation entity generates a broadcast message after determining that the cell supports the emergency call service according to the configuration, and sends the broadcast message to the terminal device, wherein the configuration includes the configuration of the network management; the emergency call service includes: at least one of IMS emergency call, IMS-based eCall emergency call and IMS emergency service for SNPN; the broadcast message is a SIB message, and the SIB message includes: at least one of IMS emergency service support indication, IMS-based eCall emergency service support indication and IMS emergency service support indication for SNPN.

[0025] Optionally, the above method further includes: the first base station separation entity sends separation entity system information to the first base station centralized entity through a first message, wherein the SIB message is encapsulated in the separation entity system information.

[0026] Optionally, the above method also includes: the first base station separation entity receives a request message for the terminal device context sent by the first base station centralized entity, wherein the request message carries an allocation and retention priority ARP value; the first base station separation entity responds to the request message and establishes a terminal device context; the first base station separation entity compares a pre-configured ARP value with the ARP value carried in the request message, and if the two are consistent, determines that the session bearer is an emergency service bearer.

[0027] Optionally, the above method also includes: the first base station separation entity receives a registration completion message sent by the terminal device, wherein the registration completion message is sent by the terminal device after completing registration in the core network.

[0028] According to the third aspect of the embodiment of the present application, another method for implementing emergency services supported by a communication base station is also provided, including: a terminal device receives a broadcast message sent by a first base station separation entity, wherein the broadcast message includes information related to emergency service support of a service cell, and the information related to emergency service support of the service cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; the terminal device reads the emergency service support information of the service cell from the broadcast message; the terminal device determines the form of implementing the emergency service based on the emergency service support information of the service cell.

[0029] Optionally, the terminal device determines the form of implementing the emergency service based on the emergency service support related information of the service cell, including: when the terminal device is in a normal state and in an SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN and determines whether the emergency service can be obtained through the SNPN; if the terminal device can register for emergency services through the SNPN, it determines to obtain the emergency service through the SNPN; if the terminal device cannot search for a cell that supports emergency services in any available SNPN, the terminal device deactivates the SNPN access mode; when the terminal device is in a normal state and not in an SNPN access mode, the terminal device reads the IMS-based eCall emergency service support indication and determines whether the eCall emergency service can be obtained based on the IMS; if the public land mobile network PLMN in a non-shared environment or all PLMNs in a shared environment support obtaining eCall emergency services based on the IMS, the terminal device determines to obtain eCall emergency services based on the IMS; if the PLMN in a non-shared environment or all PLMNs in a shared environment do not support obtaining eCall emergency services based on the IMS, the terminal device determines to perform IMS emergency service registration.

[0030] Optionally, the terminal device determines the form of implementing the emergency service based on the emergency service support related information of the service cell, and also includes: when the terminal device is in an abnormal state and in the SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN, and determines whether the emergency service can be obtained through the SNPN, wherein the terminal device being in an abnormal state includes: the terminal device is in a limited service state, or the terminal device resides normally in the cell but fails to successfully register with the network; if the terminal device can register for emergency services through the SNPN, it is determined that the emergency service is obtained through the SNPN; if the terminal device cannot search for a cell that supports emergency services in any available SNPN, the terminal device deactivates the SNPN access mode; when the terminal device is in an abnormal state and is not in the SNPN access mode, the terminal device The terminal device is prepared to read the IMS-based eCall emergency service support indication and the IMS emergency service support indication; if the PLMN in the non-shared environment or all PLMNs in the shared environment support obtaining eCall emergency services based on IMS, the terminal device determines to obtain eCall emergency services based on IMS; if the PLMN in the non-shared environment or all PLMNs in the shared environment do not support obtaining eCall emergency services based on IMS, and the enumeration type corresponding to the IMS emergency service support indication is true, the terminal device determines to perform IMS emergency service registration; if the PLMN in the non-shared environment or all PLMNs in the shared environment do not support the terminal device in an abnormal state to perform IMS emergency service registration, a fallback process is triggered, wherein the fallback process is used to execute emergency services from a 4G network or a network below the 4G network.

[0031] Optionally, the above method also includes: the terminal device sends a radio resource control RRC message to the first base station centralized entity, wherein the RRC message includes a cause value, and the cause value is used to indicate whether the RRC message is associated with a session of an emergency service in the emergency service.

[0032] Optionally, the above method also includes: the terminal device sends a registration completion message to the first base station separation entity after completing registration in the core network.

[0033] According to the fourth aspect of the embodiment of the present application, another method for implementing emergency services supported by a communication base station is also provided, including: a core network receives emergency service support related information of a service cell sent by a first base station centralized entity, wherein the emergency service support related information of the service cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; the core network sends a core network message to the first base station centralized entity, wherein the core network message is used to instruct the base station to establish a session for emergency services.

[0034] Optionally, the core network message also includes allocation and reservation priority ARP values.

[0035] According to the fifth aspect of an embodiment of the present application, a communication base station is also provided, including: multiple separate entities and a centralized entity, wherein the multiple separate entities are connected to the centralized entity, wherein the centralized entity is configured to execute the above-mentioned method for implementing the communication base station supporting emergency services; any one of the multiple separate entities is configured to execute the above-mentioned method for implementing the communication base station supporting emergency services.

[0036] According to the sixth aspect of the embodiment of the present application, there is also provided a system for implementing a communication base station supporting emergency services, including: a communication base station, a terminal device and a core network device, wherein the communication base station includes the above communication base station; the terminal device is respectively communicated with the communication base station and the core network device, and is configured to execute the above communication base station support emergency service implementation method; the core network device is configured to execute the above communication base station support emergency service implementation method.

[0037] According to the seventh aspect of the embodiment of the present application, a non-volatile storage medium is also provided, in which a program is stored, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the above-mentioned method for implementing the communication base station supporting emergency services.

[0038] According to the eighth aspect of the embodiments of the present application, there is also provided an electronic device, including: a memory and a processor, the processor being used to run a program stored in the memory, wherein the above method for implementing the communication base station supporting emergency services is executed when the program is running.

[0039] In an embodiment of the present application, a first base station centralized entity receives emergency service support related information of a service cell sent by a first base station separated entity through a first message, wherein the emergency service support related information of the service cell includes: an IP multimedia subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN. At least one of the following; the first base station centralized entity determines whether the RRC establishment of the terminal device is associated with an emergency call session based on a cause value carried in a radio resource control RRC message sent by the terminal device; the first base station centralized entity determines whether the session is used for emergency services based on a second message sent by the core network, and by completing the indication forwarding of the service cell emergency call support information in a separated architecture, the purpose of supporting the centralized entity to obtain the support strategy of each RAT for emergency calls is achieved, thereby achieving the technical effect of enhancing the interoperability between the separated entity and the centralized entity in the base station of the separated architecture, so that the centralized entity promptly reports the cell's support capability for emergency calls to the core network, and ensures the normal implementation of the terminal's emergency call service, thereby solving the technical problem that the base station adopts a separated architecture of the centralized entity and the separated entity, resulting in the inability to meet the demand for emergency calls made by the terminal in a limited service state. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0041] Figure 1a A schematic diagram of a 5G base station architecture with a centralized entity and a separate entity is shown;

[0042] Figure 1b A schematic diagram comparing the base station architecture of a 4G network and a 5G network is shown;

[0043] Figure 1c A hardware structure block diagram of a computer terminal (or mobile device) for implementing a method for a communication base station to support emergency services is shown;

[0044] Figure 2 is a flow chart of a method for implementing a communication base station supporting emergency services according to an embodiment of the present application;

[0045] Figure 3 is a flowchart of another method for implementing a communication base station supporting emergency services according to an embodiment of the present application;

[0046] Figure 4 is a flowchart of another method for implementing a communication base station supporting emergency services according to an embodiment of the present application;

[0047] Figure 5 is a flowchart of another method for implementing a communication base station supporting emergency services according to an embodiment of the present application;

[0048] Figure 6 is a structural schematic diagram of a communication base station according to an embodiment of the present application;

[0049] Figure 7 It is a structural diagram of an implementation system of a communication base station supporting emergency services according to an embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings 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 without creative work should fall within the scope of protection of this application.

[0051] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0052] In the related art, there is a problem that the base station adopts a centralized entity and a separate entity architecture, which leads to the problem that the terminal in the limited service state cannot meet the need to make emergency calls. In order to solve this problem, in the embodiment of the present application, an enhanced function is provided to provide emergency services through a new standardized method to meet the need of the terminal to make emergency calls in the limited service state. The following is a detailed description.

[0053] According to an embodiment of the present application, an embodiment of a method for implementing a communication base station supporting emergency services is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0054] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1c The hardware structure block diagram of a computer terminal (or mobile device) for implementing a method for a communication base station to support emergency services is shown. Figure 1c As shown, the computer terminal 10 (or mobile device 10) may include one or more (102a, 102b, ..., 102n are used to illustrate) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1c The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1c More or fewer components as shown, or with Figure 1c Different configurations are shown.

[0055] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0056] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the implementation method of the communication base station supporting emergency services in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the implementation method of the communication base station supporting emergency services of the above-mentioned application program. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0057] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0058] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0059] In the above operating environment, the embodiment of the present application provides a method for implementing a communication base station supporting emergency services, such as Figure 2 As shown, the method comprises the following steps:

[0060] In step S202, the first base station centralized entity receives the emergency service support related information of the service cell sent by the first base station separated entity through the first message, wherein the emergency service support related information of the service cell includes: at least one of: IP Multimedia Subsystem IMS emergency service support indication, IMS-based eCall emergency service support indication and IMS emergency service support indication for an independent non-public network SNPN.

[0061] In this step, the base station separation entity sends the serving cell emergency service support related information to the base station concentration entity through the base station internal interface message. The following describes the three emergency service support indications mentioned above respectively:

[0062] 1) IMS emergency service support indication (enumeration type, the value includes at least "True"): ims-EmergencySupport; when the indication is "True", it means that the cell supports providing emergency bearer services for terminal equipment UE in limited service state. If this field does not exist, it means that the network of the cell does not support IMS emergency services for UE in limited service state.

[0063] 2) Indication of eCall emergency call support based on IMS (enumeration type, the value includes at least "True"): eCallOverIMS-Support; when this indication is "True", it indicates that the cell supports eCall services based on IMS services. If this field does not exist, the cell network does not support eCall services based on IMS services. eCall is an in-vehicle emergency call system launched by the European Union and Russia.

[0064] 3) Indication of IMS emergency service support for independent non-public network (enumeration type, the value includes at least "True"): imsEmergencySupportForSNPN; when the indication is "True", it indicates that the independent non-public network supports the provision of IMS emergency bearer services for UEs in limited service status in the cell; if this field does not exist, the independent non-public network of the cell does not support the provision of IMS emergency call services for UEs in limited service status.

[0065] Step S204: The first base station centralized entity determines whether the RRC establishment of the terminal device is associated with an emergency call session based on the cause value carried in the radio resource control RRC message sent by the terminal device.

[0066] As some optional embodiments of the present application, the RRC message may be an RRC establishment request message or an RRC Esume request message.

[0067] Step S206: The first base station centralized entity determines whether the session is used for emergency services according to the second message sent by the core network.

[0068] In this step, the first base station centralized entity receives a core network message sent by the core network, which instructs the base station to establish a session for an emergency call, for example, to establish a protocol data unit (PDU) session, and the first base station centralized entity determines whether the session is used for an emergency call.

[0069] Through the above steps, by completing the indication forwarding of the service cell emergency call support information in the separated architecture, the purpose of supporting the centralized entity to obtain the support strategy of each RAT for emergency calls is achieved, thereby realizing the technical effect of enhancing the interoperability between the separated entity and the centralized entity in the base station of the separated architecture, enabling the centralized entity to report the cell's support capability for emergency calls to the core network in a timely manner, thereby ensuring the normal implementation of the terminal's emergency call service.

[0070] According to some optional embodiments of the present application, the first message in step S202 is an intra-base station interface message, and the intra-base station interface message includes at least one of the following: an F1 interface establishment request message and an update configuration message of the first base station separation entity, wherein the F1 interface is a connection interface between the first base station centralized entity and the first base station separation entity.

[0071] The base station internal interface message may be an F1 establishment request message and / or a base station separation entity configuration update message.

[0072] According to other optional embodiments of the present application, the second message mentioned in step S206 is a core network message sent by the core network, and the first message may be an indication of session establishment for an emergency call, including allocation and reservation of priority ARP value configuration; the first base station centralized entity determines whether the session is used for an emergency call based on the ARP value configured in the core network, and the ARP value indicates the usage of the emergency service to the first base station.

[0073] As some optional embodiments of the present application, the core network sends a core network message to the first base station centralized entity, instructing the first base station centralized entity to establish a PDU session and set an ARP value specific to the emergency call session; the ARP value specific to the emergency call session can be set according to the configuration information of the network management. The first base station centralized entity determines whether the session is used for an emergency call based on the ARP value of the session.

[0074] In an embodiment of the present application, in order to support emergency services, the core network will set the allocation and retention priority ARP value; the ARP value is used to perform differentiated functions in resource allocation and retention priority, and its main purpose is to decide whether to accept or reject the establishment or modification request of the bearer when resources are tight. At the same time, the ARP value is used to decide which bearer to discard when there are special resource restrictions (such as during switching). For example, in some scenarios, if resource congestion occurs and some low-priority resources need to be released, it is necessary to confirm who releases and who retains according to the setting of the ARP value.

[0075] As some optional embodiments of the present application, the above method also includes: the first base station centralized entity determines the target cell for providing emergency services and the form of providing emergency services based on the first message; at least includes: when at least one indication information of the IMS emergency service support indication, the IMS-based eCall emergency service support indication and the IMS emergency service support indication for SNPN is present in the information field of the serving cell, determining the target cell for providing emergency services and the form of providing emergency services based on the first message.

[0076] The first base station centralized entity receives the base station internal interface message. When the service cell emergency service support related information exists in the service cell information field, the first base station centralized entity can use the information to determine the target cell for subsequent emergency service provision and the form of emergency call provision.

[0077] The serving cell emergency service support related information exists in the serving cell information field, which means that at least one indication information among the IMS emergency service support indication, the IMS-based eCall emergency call support indication and the IMS emergency call support indication for SNPN exists in the serving cell information field.

[0078] In some optional embodiments of the present application, the terminal device determines the form of implementing the emergency service by the following method: the terminal device reads the emergency service related information supported by the serving cell from the broadcast message, wherein the broadcast message is generated by the first base station separation entity and sent to the terminal device; when the terminal device is in a normal state and in an SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN and determines whether the emergency service can be obtained through the SNPN; if the terminal device can register for the emergency service through the SNPN, it is determined that the emergency service is obtained through the SNPN; if the terminal device cannot search for a cell that can support emergency services in any available SNPN, The terminal device deactivates the SNPN access mode; when the terminal device is in a normal state and is not in the SNPN access mode, the terminal device reads the IMS-based eCall emergency service support indication and determines whether it can obtain eCall emergency services based on IMS; if the public land mobile network PLMN in a non-shared environment or all PLMNs in a shared environment support obtaining eCall emergency services based on IMS, the terminal device determines to obtain eCall emergency services based on IMS; if the PLMN in a non-shared environment or all PLMNs in a shared environment do not support obtaining eCall emergency services based on IMS, the terminal device determines to perform IMS emergency service registration.

[0079] In some other optional embodiments of the present application, the terminal device also determines the form of implementing the emergency service through the following method: when the terminal device is in an abnormal state and in the SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN and determines whether the emergency service can be obtained through the SNPN, wherein the terminal device being in an abnormal state includes: the terminal device is in a limited service state, or the terminal device resides normally in the cell but fails to successfully register with the network; if the terminal device can register for emergency services through the SNPN, it is determined that the emergency service is obtained through the SNPN; if the terminal device cannot search for a cell that supports emergency services in any available SNPN, the terminal device deactivates the SNPN access mode; when the terminal device is in an abnormal state and is not in the SNPN access mode, the terminal device Read the IMS-based eCall emergency service support indication and the IMS emergency service support indication; if the PLMN in the non-shared environment or all PLMNs in the shared environment support obtaining eCall emergency services based on IMS, the terminal device determines to obtain eCall emergency services based on IMS; if the PLMN in the non-shared environment or all PLMNs in the shared environment do not support obtaining eCall emergency services based on IMS, and the enumeration type corresponding to the IMS emergency service support indication is true, the terminal device determines to perform IMS emergency service registration; if the PLMN in the non-shared environment or all PLMNs in the shared environment do not support the terminal device in an abnormal state to perform IMS emergency service registration, trigger the execution of a fallback process, wherein the fallback process is used to execute emergency services from a 4G network or a network below the 4G network.

[0080] In the embodiment provided in the present application, the terminal device UE reads the emergency service support related information in the broadcast message, and determines the form of implementing the emergency service through the following steps:

[0081] Step 1: When the UE is in a normal state and in SNPN access mode, the UE reads the "IMS emergency service support indication for independent non-public networks" to determine whether emergency services can be obtained via SNPN; if emergency service registration can be performed through SNPN, emergency services are obtained through SNPN; if the UE cannot search for a cell that supports emergency services in any available SNPN network, the UE deactivates the SNPN access mode, regardless of the PLMN ID, and attempts to reside on any available PLMN cell that supports emergency calls, and executes step 2.

[0082] Step 2: When the UE is in a normal state and not in SNPN access mode, the UE only needs to read the IMS-based eCall emergency call support indication in the broadcast message to determine whether it can initiate an eCall emergency call based on IMS; if the serving cell PLMN in a non-shared environment or all PLMNs in a shared environment support IMS-based eCall emergency calls, subsequent operations are performed according to the terminal configuration information; if the serving cell does not support IMS-based eCall emergency calls, IMS emergency service registration is performed normally.

[0083] Step 3: When the UE is in an abnormal state and operates in the SNPN access mode, the UE reads the "Indication of IMS emergency service support for independent non-public networks" and attempts to reside on any SNPN-residable cell that supports emergency calls regardless of the SNPN ID or GIN; if the UE does not search for an SNPN-residable cell that supports IMS emergency services, the UE deactivates the SNPN access mode and executes step 4.

[0084] Step 4: When the UE is in an abnormal state and is not in SNPN access mode, the UE needs to read the IMS-based eCall emergency call support indication and the IMS emergency service support indication at the same time to determine whether the eCall emergency call can be initiated through the IMS; if the serving cell PLMN in a non-shared environment or all PLMNs in a shared environment support IMS-based eCall emergency calls, subsequent operations are performed according to the terminal configuration information; if the serving cell does not support IMS-based eCall emergency calls, but the IMS emergency service support indication is "True", the IMS emergency service registration is performed normally;

[0085] If the network of the cell does not support the IMS emergency service of the UE in the restricted service state, the UE supports the SNPN access mode but has not yet operated in the SNPN access mode, and no cell that can accept emergency call service can be found in any PLMN, the UE activates the SNPN access mode, reads the "Indication of Support for IMS Emergency Services for Independent Non-Public Networks", and resides in the SNPN campable cell that supports IMS emergency services to obtain emergency services;

[0086] If the network of the cell does not support the IMS emergency service of the UE in the restricted service state and the UE does not support the SNPN access mode, or the UE supports the SNPN access mode but has not searched for an SNPN resident cell that supports the IMS emergency service, the fallback process is triggered.

[0087] It can be understood that the UE in the abnormal state includes a UE in a limited service state, or a UE that normally resides in a cell but fails to successfully register with the network.

[0088] The above steps 1 to 4 describe three situations: a normal UE in a PLMN network, a normal UE in a SNPN network, and a UE in an abnormal state. The core is: a UE in a normal state can obtain IMS emergency services by default, while a UE in an abnormal state needs to judge one more indication. If the IMS emergency service cannot be obtained, the state must be dropped.

[0089] According to an optional embodiment of the present application, the broadcast message is generated by the first base station separation entity after determining that the cell supports emergency call services based on the configuration, wherein the configuration includes the configuration of the network management; the emergency call services include: at least one of IMS emergency calls, IMS-based eCall emergency calls and IMS emergency services for SNPN; the broadcast message is a SIB message, and the SIB message includes: at least one of IMS emergency service support indication, IMS-based eCall emergency service support indication and IMS emergency service support indication for SNPN.

[0090] In some optional embodiments of the present application, the broadcast message is a bit string of size 8, i.e., BIT STRING (SIZE (8)). According to the settings in the broadcast message, each position of the bit string indicates which type of emergency service the service cell is allowed to support. For example, the first position "1" indicates support for IMS emergency services, the second position "1" indicates support for IMS-based eCall emergency calls, and the third position "1" indicates support for IMS emergency calls for SNPN.

[0091] In the New Radio (NR), SIB1 (System Information Block #1) carries key information required for UE access, defines the scheduling of other system information, and provides common wireless resource configuration information for UE. SIB1 is also called Remaining Minimum System Information (RMSI). In the CU-DU separated base station architecture, DU is responsible for encoding and generating the contents of MIB and SIB1. The CU and DU are connected through the F1 interface. The DU uses the F1 Setup Request or DU configuration update message in the F1AP to transmit MIB and SIB1 messages to the CU.

[0092] In the limited service state, for emergency services other than eCall on IMS, the UE will learn from the broadcast indication (ims-EmergencySupport) whether the cell supports emergency services on NG-RAN. The ims-EmergencySupport field is carried by SIB1, which indicates whether the cell supports IMS emergency bearer services for UEs in the limited service state.

[0093] According to some other optional embodiments of the present application, the first base station centralized entity receives the separation entity system information sent by the first base station separation entity through a first message, wherein the SIB message is encapsulated in the separation entity system information.

[0094] The base station separation entity sends the broadcast message to the UE and encapsulates the SIB message in the separation entity system information (gNB-DU System Information), and sends the separation entity system information to the base station centralized entity through the base station interface message.

[0095] As an optional embodiment of the present application, the existence of the emergency service support related information of the serving cell is used to indicate that the emergency service support related information is broadcast to the terminal device in the broadcast message of the corresponding cell.

[0096] According to some optional embodiments of the present application, the first base station centralized entity sends a request message for establishing a terminal device context and a third message instructing the first base station separated entity to establish a session bearer to the first base station separated entity, wherein the request message carries an ARP value.

[0097] In this step, the first base station centralized entity sends a UE context establishment request message to the first base station separation entity, wherein the request establishment message carries the ARP value of the session and instructs the base station separation entity to set up a PDU session bearer.

[0098] In some optional embodiments of the present application, the first base station sends the emergency service support related information of the service cell to the second base station through the XN interface, wherein the second base station is any base station different from the first base station; the emergency service support related information of the service cell is used to provide emergency services for the terminal device in the second base station after the terminal device is switched.

[0099] The XN interface can provide interconnection for NG-RAN equipment from different equipment manufacturers.

[0100] The technical solution provided in this application is mainly aimed at the emergency call codes (ECC) of voice over New Radio (VoNR), that is, to directly establish an emergency PDU session on the NR network, and then complete the IMS ECC through the emergency PDU session; the network side sets the EMC indicator to True in 5GMMRegistrationAccept. For UEs in normal service status, during the registration phase, the service AMF will carry an indication in the registration acceptance message to indicate whether the 5GC network supports emergency services, and at the same time indicate whether the UE can establish an emergency PDU session to obtain emergency services. If the network supports emergency services, the UE can obtain emergency services by establishing an emergency PDU session; if the network does not support it, 5GC will send an emergency services fallback capability indication to indicate whether it supports allowing the UE to fall back to other RATs to obtain emergency services.

[0101] The technical solution provided by this application has the following advantages:

[0102] 1) The solution described in the present application solves the problem that the control unit in the base station separation architecture does not decode the RRC message from the separated entity, and the centralized entity cannot determine whether the current cell supports the emergency call service. By sending key information in the interface message within the base station, the centralized entity can report the cell capabilities to the core network in a timely manner, thereby ensuring the normal implementation of the terminal's emergency call service.

[0103] 2) The solution described in this application enables the centralized entity to obtain service cell information in a timely manner. When the cell does not support emergency services, the core network can quickly configure the emergency service fallback process, so that the terminal emergency registration can be completed quickly to establish an emergency PDU session, thereby reducing the delay in providing emergency services.

[0104] 3) The solution described in this application is a software evolution solution on the network side, which has no special requirements on the terminal side and facilitates the deployment and implementation of emergency call services in the wireless base station separation architecture.

[0105] Figure 3 FIG. 1 is a flowchart of another method for implementing a communication base station supporting emergency services according to an embodiment of the present application. Figure 3 As shown, the method comprises the following steps:

[0106] In step S302, the first base station separation entity sends the emergency service support related information of the service cell to the first base station centralized entity through a first message, wherein the emergency service support related information of the service cell includes: at least one of: an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN.

[0107] Step S304: the first base station separation entity receives a third message sent by the first base station concentration entity, wherein the third message is used to instruct the first base station separation entity to establish a session bearer for an emergency service.

[0108] Step S306: The first base station separation entity establishes a session bearer in response to the third message.

[0109] It should be noted that Figure 3 The preferred implementation of the illustrated embodiment can be found in Figure 2 The relevant description of the illustrated embodiment will not be repeated here.

[0110] According to an optional embodiment of the present application, the first message is an intra-base station interface message, and the intra-base station interface message includes at least one of the following: an F1 interface establishment request message and an update configuration message of the first base station separation entity, wherein the F1 interface is a connection interface between the first base station centralized entity and the first base station separation entity.

[0111] According to another optional embodiment of the present application, the first base station separation entity generates a broadcast message after determining that the cell supports emergency call service according to the configuration, and sends the broadcast message to the terminal device, wherein the configuration includes the configuration of the network management; the emergency call service includes: at least one of IMS emergency call, IMS-based eCall emergency call and IMS emergency service for SNPN; the broadcast message is a SIB message, and the SIB message includes: at least one of IMS emergency service support indication, IMS-based eCall emergency service support indication and IMS emergency service support indication for SNPN.

[0112] In some optional embodiments of the present application, the first base station separation entity sends separation entity system information to the first base station centralized entity through a first message, wherein the SIB message is encapsulated in the separation entity system information.

[0113] In other optional embodiments of the present application, the first base station separates the first base station entity and receives a request message for the terminal device context sent by the centralized entity, wherein the request message carries an allocation and retention priority ARP value; the first base station separates the entity and establishes a terminal device context in response to the request message; the first base station separates the entity and compares the pre-configured ARP value with the ARP value carried in the request message, and if the two are consistent, determines that the session bearer is an emergency service bearer.

[0114] The first base station centralized entity sends a UE context establishment request message to the first base station separation entity, wherein the request establishment message carries an ARP value and instructs the first base station separation entity to set up a PDU session bearer.

[0115] The first base station separation entity determines whether the user's bearer is an emergency service bearer based on the pre-configured ARP value and the ARP value of the session. The pre-configured ARP value and the ARP value of the session can be compared. If the two are consistent, the above PDU session bearer can be determined to be a service-only bearer.

[0116] The first base station separation entity completes the response to the base station concentration entity through a UE context establishment response message. It should be noted that the network side does not set a security context for an unauthenticated UE, so the UE needs to complete registration in the core network.

[0117] As an optional embodiment of the present application, the first base station separation entity receives a registration completion message sent by the terminal device, wherein the registration completion message is sent by the terminal device after completing registration in the core network.

[0118] After completing registration in the core network, the UE sends a registration completion message to the base station separation entity.

[0119] Figure 4 FIG. 1 is a flowchart of another method for implementing a communication base station supporting emergency services according to an embodiment of the present application. Figure 4 As shown, the method comprises the following steps:

[0120] In step S402, the terminal device receives a broadcast message sent by the first base station separation entity, wherein the broadcast message includes information related to emergency service support of the service cell, and the information related to emergency service support of the service cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN.

[0121] Step S404: The terminal device reads the emergency service support related information of the serving cell from the broadcast message.

[0122] Step S406: The terminal device determines the form of implementing the emergency service according to the emergency service support related information of the serving cell.

[0123] According to an optional embodiment of the present application, the terminal device determines the form of implementing the emergency service based on the emergency service support related information of the service cell in step S406, including the following steps: when the terminal device is in a normal state and in an SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN and determines whether the emergency service can be obtained through the SNPN; if the terminal device can register for emergency services through the SNPN, it is determined to obtain the emergency service through the SNPN; if the terminal device cannot search for a cell that can support emergency services in any available SNPN, the terminal device deactivates the SNPN access mode; when the terminal device is in a normal state and is not in an SNPN access mode, the terminal device reads the IMS-based eCall emergency service support indication and determines whether the eCall emergency service can be obtained based on the IMS; if the public land mobile network PLMN in a non-shared environment or all PLMNs in a shared environment support obtaining eCall emergency services based on the IMS, the terminal device determines to obtain the eCall emergency service based on the IMS; if the PLMN in the non-shared environment or all PLMNs in the shared environment do not support obtaining eCall emergency services based on the IMS, the terminal device determines to perform IMS emergency service registration.

[0124] According to another optional embodiment of the present application, the terminal device determines the form of implementing the emergency service according to the emergency service support related information of the serving cell in step S406, and also includes the following steps: when the terminal device is in an abnormal state and in the SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN, and determines whether the emergency service can be obtained through the SNPN, wherein the terminal device is in an abnormal state including: the terminal device is in a limited service state, or the terminal device resides normally in the cell but fails to successfully register with the network; if the terminal device can register for emergency services through the SNPN, it is determined that the emergency service is obtained through the SNPN; if the terminal device cannot search for a cell that supports emergency services in any available SNPN, the terminal device deactivates the SNPN access mode; when the terminal device is in an abnormal state and is not in the SNPN In access mode, the terminal device reads the IMS-based eCall emergency service support indication and the IMS emergency service support indication; if the PLMN in the non-shared environment or all PLMNs in the shared environment support obtaining eCall emergency services based on IMS, the terminal device determines to obtain eCall emergency services based on IMS; if the PLMN in the non-shared environment or all PLMNs in the shared environment do not support obtaining eCall emergency services based on IMS, and the enumeration type corresponding to the IMS emergency service support indication is true, the terminal device determines to perform IMS emergency service registration; if the PLMN in the non-shared environment or all PLMNs in the shared environment do not support the terminal device in an abnormal state to perform IMS emergency service registration, a fallback process is triggered, wherein the fallback process is used to execute emergency services from a 4G network or a network below the 4G network.

[0125] In some optional embodiments, the terminal device sends a radio resource control RRC message to the first base station centralized entity, wherein the RRC message includes a cause value, and the cause value is used to indicate whether the RRC message is associated with a session of an emergency service in the emergency service.

[0126] As an optional embodiment of the present application, the terminal device sends a registration completion message to the first base station separation entity after completing registration in the core network.

[0127] It should be noted that Figure 4 The preferred implementation of the illustrated embodiment can be found in Figure 2 The relevant description of the illustrated embodiment will not be repeated here.

[0128] Figure 5 FIG. 1 is a flowchart of another method for implementing a communication base station supporting emergency services according to an embodiment of the present application. Figure 5 As shown, the method comprises the following steps:

[0129] In step S502, the core network receives the emergency service support related information of the service cell sent by the first base station centralized entity, wherein the emergency service support related information of the service cell includes: at least one of: IP Multimedia Subsystem IMS emergency service support indication, IMS-based eCall emergency service support indication and IMS emergency service support indication for an independent non-public network SNPN.

[0130] Step S504: The core network sends a core network message to the first base station centralized entity, wherein the core network message is used to instruct the base station to establish a session for emergency services.

[0131] According to an optional embodiment of the present application, the above core network message also includes allocation and reservation priority ARP values.

[0132] It should be noted that Figure 5 The preferred implementation of the illustrated embodiment can be found in Figure 2 The relevant description of the illustrated embodiment will not be repeated here.

[0133] Figure 6 is a schematic diagram of the structure of a communication base station according to an embodiment of the present application, such as Figure 6 As shown, the communication base station includes: a plurality of separate entities 60 and a centralized entity 62, wherein the plurality of separate entities 60 are connected to the centralized entity 62, wherein the centralized entity 62 is configured to perform Figure 2 The communication base station in the embodiment shown supports the implementation method of emergency services; any one of the multiple separation entities 60 is configured to perform Figure 3 The communication base station in the illustrated embodiment supports an implementation method of emergency services.

[0134] Figure 7 is a structural diagram of a system for implementing a communication base station supporting emergency services according to an embodiment of the present application, such as Figure 7 As shown, the system includes: a communication base station 70, a terminal device 72 and a core network device 74, wherein:

[0135] The communication base station 70 includes Figure 6 The communication base station in the illustrated embodiment;

[0136] The terminal device 72 is connected to the communication base station 70 and the core network device 74 respectively, and is configured to execute Figure 4 The implementation method of the communication base station supporting emergency services in the illustrated embodiment;

[0137] The core network device 74 is configured to execute Figure 5 The communication base station in the illustrated embodiment supports an implementation method of emergency services.

[0138] An embodiment of the present application further provides a non-volatile storage medium, in which a program is stored, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the above-mentioned method for implementing the communication base station supporting emergency services.

[0139] The above-mentioned non-volatile storage medium is used to store programs that perform the following functions: the first base station centralized entity receives the emergency service support related information of the service cell sent by the first base station separation entity through the first message, wherein the emergency service support related information of the service cell includes: at least one of the IP Multimedia Subsystem IMS emergency service support indication, the IMS-based eCall emergency service support indication and the IMS emergency service support indication for the independent non-public network SNPN; the first base station centralized entity determines whether the RRC establishment of the terminal device is associated with an emergency call session based on the cause value carried in the radio resource control RRC message sent by the terminal device; the first base station centralized entity determines whether the session is used for emergency services based on the second message sent by the core network.

[0140] The above-mentioned non-volatile storage medium is also used to store programs that perform the following functions: the first base station separation entity sends the emergency service support related information of the service cell to the first base station centralized entity through a first message, wherein the emergency service support related information of the service cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; the first base station separation entity receives a third message sent by the first base station centralized entity, wherein the third message is used to instruct the first base station separation entity to establish a session bearer for emergency services; the first base station separation entity establishes a session bearer in response to the third message.

[0141] The above-mentioned non-volatile storage medium is also used to store programs that perform the following functions: the terminal device receives a broadcast message sent by the first base station separation entity, wherein the broadcast message includes emergency service support related information of the service cell, and the emergency service support related information of the service cell includes: at least one of an IP multimedia subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; the terminal device reads the emergency service support related information of the service cell from the broadcast message; the terminal device determines the form of implementing the emergency service based on the emergency service support related information of the service cell.

[0142] The above-mentioned non-volatile storage medium is also used to store programs that perform the following functions: the core network receives emergency service support related information of the service cell sent by the first base station centralized entity, wherein the emergency service support related information of the service cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; the core network sends a core network message to the first base station centralized entity, wherein the core network message is used to instruct the base station to establish a session for emergency services.

[0143] The application embodiment also provides an electronic device, including: a memory and a processor, the processor is used to run a program stored in the memory, wherein the above communication base station supports emergency services when the program is running.

[0144] The above-mentioned processor is used to run a program that performs the following functions: the first base station centralized entity receives the emergency service support related information of the service cell sent by the first base station separation entity through the first message, wherein the emergency service support related information of the service cell includes: at least one of the IP Multimedia Subsystem IMS emergency service support indication, the IMS-based eCall emergency service support indication and the IMS emergency service support indication for the independent non-public network SNPN; the first base station centralized entity determines whether the RRC establishment of the terminal device is associated with an emergency call session based on the cause value carried in the radio resource control RRC message sent by the terminal device; the first base station centralized entity determines whether the session is used for emergency services based on the second message sent by the core network.

[0145] The above-mentioned processor is used to run a program that performs the following functions: the first base station separation entity sends the emergency service support related information of the service cell to the first base station centralized entity through a first message, wherein the emergency service support related information of the service cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; the first base station separation entity receives a third message sent by the first base station centralized entity, wherein the third message is used to instruct the first base station separation entity to establish a session bearer for emergency services; the first base station separation entity establishes a session bearer in response to the third message.

[0146] The above-mentioned processor is used to run a program that performs the following functions: the terminal device receives a broadcast message sent by the first base station separation entity, wherein the broadcast message includes emergency service support related information of the service cell, and the emergency service support related information of the service cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; the terminal device reads the emergency service support related information of the service cell from the broadcast message; the terminal device determines the form of implementing the emergency service based on the emergency service support related information of the service cell.

[0147] The above-mentioned processor is used to run a program that performs the following functions: the core network receives the emergency service support related information of the service cell sent by the first base station centralized entity, wherein the emergency service support related information of the service cell includes: at least one of the IP Multimedia Subsystem IMS emergency service support indication, the IMS-based eCall emergency service support indication and the IMS emergency service support indication for the independent non-public network SNPN; the core network sends a core network message to the first base station centralized entity, wherein the core network message is used to instruct the base station to establish a session for emergency services.

[0148] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0149] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0150] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

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

[0152] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0153] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0154] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for implementing a communication base station supporting emergency services, characterized in that: include: The first base station centralized entity receives the emergency service support related information of the service cell sent by the first base station separation entity through the first message, wherein the emergency service support related information of the service cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; The first base station centralized entity determines whether the RRC establishment of the terminal device is associated with an emergency call session based on a cause value carried in a radio resource control RRC message sent by the terminal device; The first base station centralized entity determines whether the session is used for emergency services according to a second message sent by the core network.

2. The method according to claim 1, characterized in that The first message is an intra-base station interface message, and the intra-base station interface message includes at least one of the following: an F1 interface establishment request message and an update configuration message of the first base station separation entity, wherein the F1 interface is a connection interface between the first base station centralized entity and the first base station separation entity.

3. The method according to claim 1, characterized in that The second message is a core network message sent by the core network, and the first message may be an indication for establishing an emergency call, including the configuration of allocating and retaining priority ARP values; the first base station centralized entity determines whether the session is used for an emergency call based on the ARP value configured in the core network, and the ARP value indicates the usage of the emergency service to the first base station.

4. The method according to claim 1, characterized in that: The method further comprises: The first base station centralized entity determines, according to the first message, a target cell for providing emergency services and a form of providing the emergency services; At least it includes: when at least one indication information among the IMS emergency service support indication, the IMS-based eCall emergency service support indication and the IMS emergency service support indication for SNPN exists in the information field of the service cell, determining the target cell for providing the emergency service and the form of providing the emergency service according to the first message.

5. The method according to claim 1, characterized in that The terminal device determines the form of implementing the emergency service by the following method: The terminal device reads the emergency service related information supported by the serving cell from the broadcast message, wherein the broadcast message is generated by the first base station separation entity and then sent to the terminal device; When the terminal device is in a normal state and in an SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN and determines whether emergency services can be obtained through the SNPN; If the terminal device is capable of registering for emergency services through the SNPN, determining to obtain emergency services through the SNPN; If the terminal device cannot search for a cell that can support emergency services in any available SNPN, the terminal device deactivates the SNPN access mode; When the terminal device is in a normal state and is not in the SNPN access mode, the terminal device reads the IMS-based eCall emergency service support indication and determines whether the eCall emergency service can be obtained based on the IMS; If the public land mobile network PLMN in the non-shared environment or all PLMNs in the shared environment support obtaining eCall emergency services based on IMS, the terminal device determines to obtain eCall emergency services based on IMS; If the PLMN in the non-shared environment or all PLMNs in the shared environment do not support obtaining eCall emergency services based on IMS, the terminal device determines to perform IMS emergency service registration.

6. The method according to claim 5, characterized in that The terminal device also determines the form of implementing the emergency service by the following method: When the terminal device is in an abnormal state and in an SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN and determines whether emergency services can be obtained through the SNPN, wherein the terminal device being in the abnormal state includes: the terminal device being in a limited service state, or the terminal device being normally resident in a cell but failing to successfully register with the network; If the terminal device is capable of registering for emergency services through the SNPN, determining to obtain emergency services through the SNPN; If the terminal device cannot search for a cell that can support emergency services in any available SNPN, the terminal device deactivates the SNPN access mode; When the terminal device is in an abnormal state and is not in the SNPN access mode, the terminal device reads the IMS-based eCall emergency service support indication and the IMS emergency service support indication; If the PLMN in the non-shared environment or all PLMNs in the shared environment support obtaining the eCall emergency service based on the IMS, the terminal device determines to obtain the eCall emergency service based on the IMS; If the PLMN in the non-shared environment or all PLMNs in the shared environment do not support obtaining eCall emergency services based on IMS, and the enumeration type corresponding to the IMS emergency service support indication is true, the terminal device determines to perform IMS emergency service registration; If the PLMN in the non-shared environment or all PLMNs in the shared environment do not support the terminal device in the abnormal state to perform IMS emergency service registration, a fallback process is triggered, wherein the fallback process is used to obtain the emergency service from a 4G network or a network below the 4G network.

7. The method according to claim 5, characterized in that The broadcast message is generated by the first base station separation entity after determining that the cell supports the emergency call service according to the configuration, wherein the configuration includes the configuration of the network management; the emergency call service includes: at least one of an IMS emergency call, an IMS-based eCall emergency call, and an IMS emergency service for SNPN; The broadcast message is a SIB message, and the SIB message includes: at least one of an IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for SNPN.

8. The method according to claim 7, characterized in that The method further comprises: The first base station centralized entity receives the separation entity system information sent by the first base station separation entity through the first message, wherein the SIB message is encapsulated in the separation entity system information.

9. The method according to claim 5, characterized in that The existence of the emergency service support related information of the serving cell is used to indicate that the emergency service support related information is broadcast to the terminal device in the broadcast message of the corresponding cell.

10. The method according to claim 3, characterized in that The method further comprises: The first base station centralized entity sends a request message for establishing a terminal device context and a third message instructing the first base station separated entity to establish a session bearer to the first base station separated entity, wherein the request message carries the ARP value.

11. The method according to claim 1, characterized in that: The method further comprises: The first base station sends the emergency service support related information of the serving cell to the second base station through the XN interface, wherein the second base station is any base station different from the first base station; The emergency service support related information of the service cell is used to provide emergency services for the terminal device in the second base station after the terminal device is switched.

12. A method for implementing a communication base station supporting emergency services, characterized in that: include: The first base station separation entity sends the emergency service support related information of the serving cell to the first base station centralized entity through a first message, wherein the emergency service support related information of the serving cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; The first base station separation entity receives a third message sent by the first base station centralized entity, wherein the third message is used to instruct the first base station separation entity to establish a session bearer for the emergency service; The first base station separation entity establishes the session bearer in response to the third message.

13. The method according to claim 12, characterized in that The first message is an intra-base station interface message, and the intra-base station interface message includes at least one of the following: an F1 interface establishment request message and an update configuration message of the first base station separation entity, wherein the F1 interface is a connection interface between the first base station centralized entity and the first base station separation entity.

14. The method according to claim 12, characterized in that The method further comprises: The first base station separation entity generates a broadcast message after determining that the cell supports the emergency call service according to the configuration, and sends the broadcast message to the terminal device, wherein the configuration includes the configuration of the network management; the emergency call service includes: at least one of an IMS emergency call, an IMS-based eCall emergency call, and an IMS emergency service for SNPN; The broadcast message is a SIB message, and the SIB message includes: at least one of an IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for SNPN.

15. The method according to claim 14, characterized in that The method further comprises: The first base station separation entity sends separation entity system information to the first base station centralization entity through the first message, wherein the SIB message is encapsulated in the separation entity system information.

16. The method according to claim 12, characterized in that The method further comprises: The first base station separation entity receives a request message for a terminal device context sent by the first base station concentration entity, wherein the request message carries an allocation and retention priority ARP value; The first base station separation entity establishes the terminal device context in response to the request message; The first base station separation entity compares a pre-configured ARP value with the ARP value carried in the request message, and if the two are consistent, determines that the session bearer is an emergency service bearer.

17. The method according to claim 12, characterized in that The method further comprises: The first base station separation entity receives a registration completion message sent by a terminal device, wherein the registration completion message is sent by the terminal device after completing registration in a core network.

18. A method for implementing a communication base station supporting emergency services, characterized in that: include: The terminal device receives a broadcast message sent by the first base station separation entity, wherein the broadcast message includes the emergency service support related information of the serving cell, and the emergency service support related information of the serving cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; The terminal device reads the emergency service support related information of the serving cell from the broadcast message; The terminal device determines the form of implementing the emergency service according to the emergency service support related information of the serving cell.

19. The method according to claim 18, characterized in that The terminal device determines, according to the emergency service support related information of the serving cell, a form of implementing the emergency service, including: When the terminal device is in a normal state and in an SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN and determines whether emergency services can be obtained through the SNPN; If the terminal device is capable of registering for emergency services through the SNPN, determining to obtain emergency services through the SNPN; If the terminal device cannot search for a cell that can support emergency services in any available SNPN, the terminal device deactivates the SNPN access mode; When the terminal device is in a normal state and is not in the SNPN access mode, the terminal device reads the IMS-based eCall emergency service support indication and determines whether the eCall emergency service can be obtained based on the IMS; If the public land mobile network PLMN in the non-shared environment or all PLMNs in the shared environment support obtaining eCall emergency services based on IMS, the terminal device determines to obtain eCall emergency services based on IMS; If the PLMN in the non-shared environment or all PLMNs in the shared environment do not support obtaining eCall emergency services based on IMS, the terminal device determines to perform IMS emergency service registration.

20. The method according to claim 19, characterized in that The terminal device determines the form of implementing the emergency service according to the emergency service support related information of the serving cell, further comprising: When the terminal device is in an abnormal state and in an SNPN access mode, the terminal device reads the IMS emergency service support indication for the SNPN and determines whether emergency services can be obtained through the SNPN, wherein the terminal device being in the abnormal state includes: the terminal device being in a limited service state, or the terminal device being normally resident in a cell but failing to successfully register with the network; If the terminal device is capable of registering for emergency services through the SNPN, determining to obtain emergency services through the SNPN; If the terminal device cannot search for a cell that can support emergency services in any available SNPN, the terminal device deactivates the SNPN access mode; When the terminal device is in an abnormal state and is not in the SNPN access mode, the terminal device reads the IMS-based eCall emergency service support indication and the IMS emergency service support indication; If the PLMN in the non-shared environment or all PLMNs in the shared environment support obtaining the eCall emergency service based on the IMS, the terminal device determines to obtain the eCall emergency service based on the IMS; If the PLMN in the non-shared environment or all PLMNs in the shared environment do not support obtaining eCall emergency services based on IMS, and the enumeration type corresponding to the IMS emergency service support indication is true, the terminal device determines to perform IMS emergency service registration; If the PLMN in the non-shared environment or all PLMNs in the shared environment do not support the terminal device in the abnormal state to perform IMS emergency service registration, a fallback process is triggered, wherein the fallback process is used to obtain the emergency service from a 4G network or a network below the 4G network.

21. The method according to claim 18, characterized in that The method further comprises: The terminal device sends a radio resource control RRC message to the first base station centralized entity, wherein the RRC message includes a cause value, and the cause value is used to indicate whether the RRC message is associated with a session of an emergency service among the emergency services.

22. The method according to claim 18, characterized in that The method further comprises: After completing registration in the core network, the terminal device sends a registration completion message to the first base station separation entity.

23. A method for implementing a communication base station supporting emergency services, characterized in that: include: The core network receives the emergency service support related information of the service cell sent by the first base station centralized entity, wherein the emergency service support related information of the service cell includes: at least one of an IP Multimedia Subsystem IMS emergency service support indication, an IMS-based eCall emergency service support indication, and an IMS emergency service support indication for an independent non-public network SNPN; The core network sends a core network message to the first base station centralized entity, wherein the core network message is used to instruct the base station to establish a session for the emergency service.

24. The method according to claim 23, characterized in that The core network message also includes allocation and reservation priority ARP values.

25. A communication base station, characterized in that: include: A plurality of separate entities and a centralized entity, wherein the plurality of separate entities are connected to the centralized entity, wherein: The centralized entity is configured to execute the method for implementing a communication base station supporting emergency services as described in any one of claims 1 to 11; Any one of the multiple separated entities is configured to execute the method for implementing the communication base station supporting emergency services as described in any one of claims 12 to 17.

26. A communication base station supporting emergency service implementation system, characterized in that: include: Communication base stations, terminal equipment and core network equipment, among which: The communication base station comprises the communication base station according to claim 25; The terminal device is respectively connected to the communication base station and the core network device for communication, and is configured to execute the method for implementing the communication base station supporting emergency services as described in any one of claims 18 to 22; The core network device is configured to execute the method for implementing the communication base station supporting emergency services as described in any one of claims 23 to 24.

27. A non-volatile storage medium, characterized in that: The non-volatile storage medium stores a program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the method for implementing the communication base station supporting emergency services as described in any one of claims 1 to 24.

28. An electronic device, characterized in that: include: A memory and a processor, wherein the processor is used to run a program stored in the memory, wherein when the program is run, the method for implementing a communication base station supporting emergency services as described in any one of claims 1 to 24 is executed.

Images