Communication methods, device, system, and storage medium
Patent Information
- Application Number
- PCT/CN2025/089681
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-04-17
- Publication Date
- 2026-10-22
Smart Images

Figure CN2025089681_22102026_PF_FP_ABST
Abstract
Description
Communication methods, devices, systems and storage media Technical Field
[0001] This disclosure relates to the field of communication technology, and more specifically, to a communication method, device, system, and storage medium. Background Technology
[0002] Emergency services refer to services that provide emergency assistance in critical situations where personal or public health, safety, life, or property are endangered. In mobile communications, even if the user equipment (UE) cannot initiate normal services, it can still initiate emergency services in a timely manner, such as dialing emergency numbers 110 (police), 120 (ambulance), or 119 (fire) when there is no SIM card. Summary of the Invention
[0003] This disclosure provides a communication method, device, system, and storage medium.
[0004] A first aspect of this disclosure provides a communication method, executed by a first node, the method comprising:
[0005] The first network is determined to support emergency services for terminals accessed through the first access network based on at least one of the following:
[0006] The terminal accesses the network via the first access network;
[0007] The first network supports emergency services through the first access network;
[0008] Regulations or operational policies support the terminal in carrying out emergency services through the first access network at its location;
[0009] The emergency service configuration on the first node supports emergency services to be carried out through the first access network.
[0010] The first network is the network where the first node is located.
[0011] A second aspect of this disclosure provides a communication method, executed by a terminal, the method comprising:
[0012] The system receives first information sent by a first node, the first information being used to indicate that a first network supports emergency services of the terminal accessed through a first access network, wherein the first network is the network where the first node is located.
[0013] A third aspect of this disclosure provides a terminal, including:
[0014] The first transceiver module is used to receive first information sent by the first node. The first information is used to indicate that the first network supports emergency services of the terminal accessed through the first access network, wherein the first network is the network where the first node is located.
[0015] A fourth aspect of this disclosure provides a first node, including:
[0016] The second processing module is configured to determine, based on at least one of the following, the emergency services supported by the first network for terminals accessing through the first access network:
[0017] The terminal accesses the network via the first access network;
[0018] The first network supports emergency services through the first access network;
[0019] Regulations or operational policies support the terminal in carrying out emergency services through the first access network at its location;
[0020] The emergency service configuration on the first node supports emergency services to be carried out through the first access network.
[0021] The first network is the network where the first node is located.
[0022] A fifth aspect of this disclosure provides a terminal, including:
[0023] One or more processors;
[0024] The terminal is used to execute an optional implementation of the second aspect described above.
[0025] A sixth aspect of this disclosure provides a first node, including:
[0026] One or more processors;
[0027] The network device is used to perform an optional implementation of the first aspect described above.
[0028] A seventh aspect of this disclosure provides a communication system including a terminal and a first node, wherein the terminal is configured to implement the method described in an optional embodiment of the second aspect, and the first node is configured to implement the method described in an optional embodiment of the first aspect.
[0029] According to an eighth aspect of the present disclosure, a computer-readable storage medium is provided that stores executable instructions which are loaded and executed by the processor to implement the method described in the optional embodiments of the first or second aspect.
[0030] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0031] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0032] Figure 1 is a schematic diagram of a wireless communication system according to an exemplary embodiment;
[0033] Figure 2 is a flowchart illustrating a communication method according to an exemplary embodiment;
[0034] Figure 3a is a flowchart illustrating the communication method according to an embodiment of this disclosure;
[0035] Figure 3b is a flowchart illustrating the communication method according to an embodiment of this disclosure;
[0036] Figure 3c is a flowchart illustrating the communication method according to an embodiment of this disclosure;
[0037] Figure 4a is a flowchart illustrating the communication method according to an embodiment of this disclosure;
[0038] Figure 4b is a flowchart illustrating the communication method according to an embodiment of this disclosure;
[0039] Figure 5a is a flowchart illustrating the communication method according to an embodiment of this disclosure;
[0040] Figure 5b is a flowchart illustrating the communication method according to an embodiment of this disclosure;
[0041] Figure 5c is a flowchart illustrating the communication method according to an embodiment of this disclosure;
[0042] Figure 6a is a schematic diagram of the structure of the terminal proposed in an embodiment of this disclosure;
[0043] Figure 6b is a schematic diagram of the structure of the first node proposed in an embodiment of this disclosure;
[0044] Figure 7a is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure;
[0045] Figure 7b is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation
[0046] This disclosure provides communication methods, devices, communication systems, and storage media.
[0047] In a first aspect, embodiments of this disclosure propose a communication method, which is executed by a first node, the method comprising:
[0048] The first network is determined to support emergency services for terminals accessed through the first access network based on at least one of the following:
[0049] The terminal accesses the network via the first access network;
[0050] The first network supports emergency services through the first access network;
[0051] Regulations or operational policies support the terminal in carrying out emergency services through the first access network at its location;
[0052] The emergency service configuration on the first node supports emergency services to be carried out through the first access network.
[0053] The first network is the network where the first node is located.
[0054] In the above embodiments, the first node determines that the first network it is in supports the emergency services of the terminal accessed through the first access network according to different conditions, so as to better apply to different application scenarios and achieve the purpose of the first network providing emergency service to the terminal accessed through the first access network and improving communication performance.
[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:
[0056] Send a first message to the terminal, the first message being used to instruct the first network to support emergency services of the terminal accessed through the first access network.
[0057] In the above embodiments, the first node indicates to the terminal that its first network supports the emergency services of the terminal accessing through the first access network, thereby enabling the first network to provide emergency service to the terminal accessing through the first access network and improving communication performance.
[0058] In conjunction with some embodiments of the first aspect, in some embodiments, before determining that the first network supports emergency services of a terminal accessed through the first access network, the method further includes: receiving second information sent by the terminal, the second information being used to initiate a network attachment process for the emergency service.
[0059] In the above embodiments, after receiving the network attach procedure information sent by the terminal for initiating an emergency service, the first node can determine whether its own first network supports the emergency service of the terminal accessed through the first access network. When it is determined that its own first network supports the emergency service of the terminal accessed through the first access network, the first node instructs the terminal that its own first network supports the emergency service of the terminal accessed through the first access network, thereby enabling the first node to support the emergency service of the terminal accessed through the first access network.
[0060] In conjunction with some embodiments of the first aspect, in some embodiments, before determining that the first network supports emergency services of a terminal accessed through the first access network, the method further includes: receiving second information sent by the terminal, the second information being used to initiate a normal network attach process.
[0061] In the above embodiments, after receiving the information sent by the terminal for initiating a normal network attach process, the first node can determine whether its first network supports the emergency services of the terminal accessed through the first access network. When it is determined that its first network supports the emergency services of the terminal accessed through the first access network, the first node instructs the terminal that its first network supports the emergency services of the terminal accessed through the first access network, thereby enabling the first node to support the emergency services of the terminal accessed through the first access network.
[0062] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:
[0063] The terminal sends a third message, which is used to request the establishment of a packet data network (PDN) connection for the emergency service.
[0064] In the above embodiments, when a terminal learns that the first node supports the emergency services of the terminal accessed through the first access network, it can send a request to the first node to establish a PDN connection for the emergency services, thereby enabling the first node to support the emergency services of the terminal accessed through the first access network.
[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the third information is sent based on the first information.
[0066] In conjunction with some embodiments of the first aspect, in some embodiments, the third information includes access information related to the emergency service.
[0067] In the above embodiments, for a normal network attach process initiated by a terminal, the first node needs to establish a PDN connection for the emergency service based on the access information related to the emergency service included in the received third information, so as to establish an emergency PDN connection more accurately.
[0068] In conjunction with some embodiments of the first aspect, in some embodiments, the second information is sent by the terminal based on fourth information, which is received by the terminal from the network device of the first access network, and the fourth information is used to indicate that the serving cell of the network device supports the emergency service.
[0069] In conjunction with some embodiments of the first aspect, in some embodiments, the first access network includes narrowband Internet of Things (NB-IoT).
[0070] In the above embodiments, the first node improves communication performance by sending an instruction to the terminal that the first network it is in supports the emergency services of the terminal accessed via NB-IoT.
[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the emergency service includes the IP Multimedia Subsystem (IMS) emergency service.
[0072] Secondly, embodiments of this disclosure propose a communication method, which is executed by a terminal, the method comprising:
[0073] The system receives first information sent by a first node, which is used to indicate that the first network supports emergency services of terminals accessed through a first access network, wherein the first network is the network where the first node is located.
[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the emergency services supported by the first network for terminals accessed through the first access network are determined based on at least one of the following:
[0075] The terminal accesses the network via the first access network;
[0076] The first network supports emergency services through the first access network;
[0077] Regulations or operational policies support the terminal in carrying out emergency services through the first access network at its location;
[0078] The emergency service configuration on the first node supports emergency services to be carried out through the first access network.
[0079] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:
[0080] Send a second message to the first node, the second message being used to initiate the network attachment process for the emergency service.
[0081] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:
[0082] Send a second message to the first node, the second message being used to initiate a normal network attach process.
[0083] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:
[0084] A third message is sent to the first node, the third message being used to request the establishment of a packet data network (PDN) connection for the emergency service.
[0085] In conjunction with some embodiments of the second aspect, in some embodiments, the third information is sent based on the first information.
[0086] In conjunction with some embodiments of the second aspect, in some embodiments, the third information includes access information related to the emergency service.
[0087] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:
[0088] The system receives a fourth message sent by a network device located in the first access network, the fourth message being used to indicate that the cell served by the network device supports the emergency service;
[0089] Sending the second information to the first node includes:
[0090] Based on the fourth information, the second information is sent to the first node.
[0091] In conjunction with some embodiments of the second aspect, in some embodiments, the first access network includes narrowband Internet of Things (NB-IoT).
[0092] In conjunction with some embodiments of the second aspect, in some embodiments, the emergency service includes the IP Multimedia Subsystem (IMS) emergency service.
[0093] Thirdly, embodiments of this disclosure provide a terminal, including:
[0094] The first transceiver module is used to receive first information sent by the first node. The first information is used to indicate that the first network supports emergency services of the terminal accessed through the first access network, wherein the first network is the network where the first node is located.
[0095] Fourthly, embodiments of this disclosure provide a first node, comprising:
[0096] The second transceiver module is used to send first information to the terminal. The first information is used to indicate that the first network supports the emergency services of the terminal accessed through the first access network, wherein the first network is the network where the first node is located.
[0097] Fifthly, embodiments of this disclosure provide a terminal, including:
[0098] One or more processors;
[0099] The terminal executes the method described in the optional implementation of the second aspect.
[0100] According to a sixth aspect of the embodiments of this disclosure, a first node is provided, comprising:
[0101] One or more processors;
[0102] The network device executes the method described in the optional implementation of the first aspect.
[0103] In a seventh aspect, embodiments of this disclosure provide a communication system including a terminal and a first node, wherein the terminal is used to implement the method described in the optional implementation of the second aspect, and the first node is used to implement the method described in the optional implementation of the first aspect.
[0104] Eighthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in the optional embodiments of the first or second aspect.
[0105] Ninthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in the optional implementation of the first or second aspect.
[0106] In a tenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in an optional implementation of the first or second aspect.
[0107] Eleventhly, embodiments of this disclosure provide a chip or chip system including processing circuitry for performing the method described in an optional implementation of the first or second aspect above.
[0108] Understandably, the aforementioned devices, communication equipment, communication systems, storage media, program products, and computer programs for random access are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here. The communication equipment can be a terminal or a network device.
[0109] This disclosure provides communication methods, apparatus, devices, systems, and storage media.
[0110] In some embodiments, terms such as information processing system and communication system may be used interchangeably.
[0111] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of the embodiments disclosed. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
[0112] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0113] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the embodiments of this disclosure.
[0114] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.
[0115] In the embodiments disclosed herein, "multiple" refers to two or more.
[0116] In some embodiments, the terms “at least one of”, “at least one of”, “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0117] The descriptions in this disclosure, such as "at least one of A, B, C..." or "A and / or B and / or C...", include the case where any one of A, B, C... exists alone, as well as the case where any combination of any of A, B, C... exists alone. Each case can exist alone. For example, "at least one of A, B, C" includes the cases of A alone, B alone, C alone, A and B combination, A and C combination, B and C combination, and A and B and C combination. For example, A and / or B includes the cases of A alone, B alone, and A and B combination.
[0118] In some embodiments, the notation "in one case A, in another case B" or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: A is executed regardless of B, i.e., A is executed in some embodiments; B is executed regardless of A, i.e., B is executed in some embodiments; A and B are selectively executed, i.e., A and B are selected for execution in some embodiments; A and B are both executed, i.e., A and B are executed in some embodiments. The same applies when there are more branches such as A, B, and C.
[0119] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. As another example, if the object being described is "information", then "first configuration" and "second configuration" can be the same information or different information, and their content can be the same or different.
[0120] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0121] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.
[0122] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.
[0123] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.
[0124] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.
[0125] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.
[0126] In some embodiments, the access network device, core network device, or network device can be replaced by a terminal. For example, various embodiments of this disclosure can also be applied to structures that replace communication between the access network device, core network device, or network device and the terminal with communication between multiple terminals (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal can also be configured to have all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "side").
[0127] For example, uplink channels and downlink channels can be replaced with side channels, and uplink links and downlink links can be replaced with side links.
[0128] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".
[0129] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.
[0130] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".
[0131] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values (e.g., a comparison with a predetermined value), but is not limited thereto.
[0132] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0133] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0134] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0135] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
[0136] As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.
[0137] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.
[0138] In some embodiments, network device 102 may include at least one of access network device and core network device.
[0139] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a wireless fidelity (WiFi) system.
[0140] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.
[0141] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.
[0142] In some embodiments, the access network device may be a single device, multiple devices, or a group of devices, including all or part of a first network element, a second network element, etc. Network elements may be virtual or physical. Network devices may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).
[0143] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).
[0144] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.
[0145] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. The number and form of each main body are arbitrary. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.
[0146] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, utilizing other systems for random access, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0147] The Evolved Universal Terrestrial Radio Access Network (E-UTRAN) provides an emergency bearer service to support emergency sessions for the Internet Protocol (IP) Multimedia Subsystem (IMS). When the network supports emergency services, the emergency bearer service is provided by the Serving Public Land Mobile Network (PLMN). Terminals performing normal attach, terminals performing emergency attach, or UEs in a limited service state can use the emergency bearer service.
[0148] A UE in a restricted service state initiates an attach procedure and instructs that the attach be used to receive emergency services. Regardless of whether the UE is network-authenticated, roaming, subject to mobility restrictions, or has a valid subscription, as long as the network supports providing emergency services to a UE in a restricted service state, the network provides emergency bearer services to the UE.
[0149] UEs that have successfully attached via normal procedures receive emergency bearer services by initiating a Packet Data Network (PDN) connection for emergency services. During the attach or Tracking Area Update (TAU) process, UEs normally camped on the cell are notified that the PLMN supports emergency bearer services via E-UTRAN.
[0150] To provide emergency bearer services, the Mobility Management Entity (MME) is configured with emergency configuration data (including an emergency Access Point Name (APN), which is used to obtain the Packet Data Network Gateway (P-GW) for emergency services, or includes the P-GW configured for the emergency APN). This emergency configuration data is applied to all emergency bearer services established by the MME based on UE requests.
[0151] However, when a UE uses Narrow Band Internet of Things (NB-IoT) access, the aforementioned emergency bearer service is not supported. Specifically, during the attach or TAU process of a UE using NB-IoT access, the MME will not provide the UE with an Emergency Service Support indicator, and the cell belonging to the NB-IoT access will not broadcast support for IMS emergency services to the UE. However, it is currently necessary to support IMS emergency services through NB-IoT access, especially NB-IoT non-terrestrial communication (NTN) access, and there is currently no solution to this problem.
[0152] Based on the aforementioned wireless communication system, various embodiments of the communication method proposed in this disclosure will be described in detail below.
[0153] Figure 2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2, the communication method is used in a communication system 100, and the method includes:
[0154] S200, The first node determines that the first network supports emergency services of terminals accessed through the first access network.
[0155] Optionally, the first network is the network where the first node is located.
[0156] In some embodiments, the first node may be a core network node, such as a Mobility Management Entity (MME). Optionally, the first network may be the core network where the MME resides.
[0157] In some embodiments, the first access network includes narrowband Internet of Things (NB-IoT). Optionally, the first access network may include an NB-IoT Terrestrial Network (TN) and an NB-IoT Non-Terrestrial Network (NTN). The NB-IoT NTN may also include GEO-based NB-IoT access.
[0158] In some embodiments, emergency services may include IP multimedia subsystem (IMS) emergency services. Optionally, IMS emergency services may include, but are not limited to, IMS emergency voice call services.
[0159] In some embodiments, the first node may determine the emergency services supported by the first network for terminals accessing through the first access network based on at least one of the following:
[0160] The terminal accesses the network through the first access network;
[0161] The first network supports emergency services through the first access network;
[0162] Regulations or operational strategies may support the terminal in carrying out emergency services through the primary access network at its location;
[0163] Emergency service configuration on the first node supports emergency services to be carried out through the first access network.
[0164] In some embodiments, if a terminal accesses a first network where a first node is located via a first access network, then the first network supports the terminal's emergency services.
[0165] Optionally, if the terminal accesses the first network where the first node is located through the first access network, the first network can provide emergency service to the terminal accessing through the first access network.
[0166] In some embodiments, if the first network where the first node is located supports emergency services through the first access network, then when the terminal accesses the first network through the first access network, the first network supports the terminal's emergency services.
[0167] Optionally, if the first network where the first node is located supports emergency services through the first access network, then the first network can provide emergency service to terminals accessed through the first access network.
[0168] In some embodiments, if regulations or operational policies support a terminal to conduct emergency services through a first access network at its location, then when the terminal accesses the first access network, the first network supports the terminal's emergency services.
[0169] In some embodiments, the regulations can be understood as the regulations of the location where the first network is deployed. Optionally, if the regulations of the location where the first network is deployed support the first network in providing emergency service to terminals accessed through the first access network, then the terminals can conduct emergency services through the first access network in that location.
[0170] In some embodiments, the operating strategy can be understood as the operating strategy of the first network deployment location. Optionally, if the operating strategy of the first network deployment location supports the first network in providing emergency service to terminals accessed through the first access network, then the terminals can carry out emergency services through the first access network in the first network deployment location.
[0171] In some embodiments, if the first network where the first node is located supports the terminal to carry out emergency services through the first access network, and the operation policies and / or regulations of the deployment location of the first network support the terminal to carry out emergency services through the first access network in that deployment location, then the terminal can carry out emergency services through the first access network in that deployment location (or it can be described as: when the terminal accesses the first network through the first access network in the deployment location of the first network, the first network can provide emergency service to the terminal).
[0172] In some embodiments, if the emergency service configuration on the first node supports emergency services through the first access network, then when the terminal accesses the first network where the first node is located through the first access network, the first network supports the terminal's emergency services. Optionally, the emergency service configuration on the first node can be MME Emergency Configuration Data, but is not limited to this.
[0173] Optionally, if the emergency configuration data of the MME supports emergency services through the first access network, the core network where the MME is located can provide emergency service to terminals accessing through the first access network.
[0174] In some embodiments, if the emergency service configuration on the first node and the first network where the first node is located support the terminal to carry out emergency services through the first access network, then when the terminal accesses the first network through the first access network, the first network can provide emergency service to the terminal.
[0175] In some embodiments, if the emergency service configuration on the first node and the first network where the first node is located support the terminal to carry out emergency services through the first access network, and the operation policy and / or regulations of the deployment location of the first network support the terminal to carry out emergency services through the first access network in that deployment location, then the terminal can carry out emergency services through the first access network in the deployment location of the first network (or it can be described as: when the terminal accesses the first network through the first access network in the deployment location of the first network, the first network can provide emergency service to the terminal).
[0176] S201, The first node sends the first information to the terminal.
[0177] In some embodiments, the first information is used to indicate that the first network supports emergency services of terminals accessed through the first access network.
[0178] In some embodiments, after a first node determines that its first network supports emergency services for a terminal accessing through the first access network, it may send first information to the terminal so that the terminal knows that the first network where the first node is located can provide emergency service to the terminal accessing through the first access network.
[0179] In some embodiments, the first node can be an MME, and the first network in which it resides can be a core network.
[0180] In some embodiments, the first access network may be NB-IoT, and the emergency service may be IMS emergency service.
[0181] Optionally, the MME can notify the terminal that the core network to which the MME resides supports the IMS emergency service of the terminal accessed via NB-IoT.
[0182] S202, The terminal sends the third information to the first node.
[0183] In some embodiments, the third information is used to request the establishment of a packet data network (PDN) connection for emergency services.
[0184] In some embodiments, the terminal may send a message to the first node requesting the first node to establish a PDN connection for emergency services.
[0185] In some embodiments, the terminal may send third information to the first node based on the first information.
[0186] In some embodiments, if a terminal learns that the network where the first node is located supports the terminal's emergency services accessed through the first access network, it can send a message to the first node requesting it to establish a PDN connection for the emergency services.
[0187] S203. The first node establishes a PDN connection for emergency services.
[0188] In some embodiments, after receiving a request from a terminal to establish a PDN connection for emergency services, the first node establishes the PDN connection for emergency services. It should be noted that the process of the first node establishing the PDN connection for emergency services can be implemented with reference to existing related technologies, and will not be elaborated upon here for the sake of brevity.
[0189] In some embodiments, prior to step S200, the following may also be included:
[0190] S204. The terminal sends the second information to the first node.
[0191] In some embodiments, the second information is used to initiate a network attach procedure for emergency services. Optionally, the second information can be an attach request message indicating an emergency attach. Optionally, the attach request message sent by the terminal to the first node indicates an emergency attach to initiate the emergency attach procedure.
[0192] In some embodiments, the second information is used to send a normal network attach procedure. Optionally, the second information may be a normal attach request message, which does not carry any indication. Optionally, the terminal sends an attach request message to the first node to initiate the attach procedure.
[0193] Optionally, a 1-bit information field in a certain information element of the attach request message can be used to indicate whether the attach request message is used to initiate an emergency attach procedure.
[0194] For example, if the value of a 1-bit information field in a certain information element of an attach request message is 1, it indicates that the attach request message is used to initiate an emergency attach procedure. If the value of a 1-bit information field in a certain information element of an attach request message is 0 or empty, it indicates that the attach request message is used to initiate a normal attach procedure.
[0195] For example, if the value of a 1-bit information field in a certain information element of an attach request message is 0, it indicates that the attach request message is used to initiate an emergency attach procedure. If the value of a 1-bit information field in a certain information element of an attach request message is 1 or empty, it indicates that the attach request message is used to initiate a normal attach procedure.
[0196] In some embodiments, if the second information is used to initiate the network attachment process for emergency services, the third information in step S202 above can be an emergency PDN connection established request message.
[0197] In some embodiments, if the second information is used to initiate a normal network attach process, the third information in step S202 above can be a PDN connection established request message, which may include access information related to emergency services. Optionally, the access information may include, but is not limited to, the Access Point Name (APN).
[0198] Optionally, if the terminal initiates a normal network attach procedure to the first node, and the terminal learns that the network where the first node is located supports the terminal's emergency services accessed through the first access network, it can send a PDN connection establishment request message to the first node, carrying an APN (emergency APN) related to the emergency service in the message to request the establishment of a PDN connection for that emergency service. For example, the message may carry an APN related to the IMS emergency voice service to request the establishment of a PDN connection for the IMS emergency voice service.
[0199] In some embodiments, after receiving information from the terminal regarding initiating an emergency service network attachment process, or information regarding initiating a normal network attachment process, the first node can determine whether the first network to which the first node resides supports the terminal's emergency service accessed through the first access network. If it is determined that the first network supports the terminal's emergency service accessed through the first access network, the first node can send first information to the terminal.
[0200] In some embodiments, prior to step S204, the following may also be included:
[0201] S205. The terminal receives the fourth information sent by the network device.
[0202] In some embodiments, the terminal may receive fourth information from a network device in the first access network. Optionally, the fourth information may be used to indicate that the serving cell of the network device supports emergency services.
[0203] In some embodiments, the fourth information may be a broadcast message. Optionally, the network device of the first access network may broadcast to the terminal that its serving cell supports emergency services.
[0204] In some embodiments, the terminal may send the second information to the first node based on the fourth information.
[0205] In some embodiments, after a terminal learns from a network device in a first access network that the serving cell of that network device supports emergency services, it can send information to a first node for initiating a network attach procedure for emergency services, or send information to a first node for initiating a normal network attach procedure, in order to initiate a PDN connection for emergency services.
[0206] In some embodiments, the names of information, etc., are not limited to those described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", and "data" can be used interchangeably.
[0207] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0208] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.
[0209] In some embodiments, terms such as “in the case of,” “when,” “when,” “if,” “if,” etc., can be used interchangeably.
[0210] The method involved in the embodiments of this disclosure may include at least one of steps S200 to S205. For example, step S201 can be implemented as an independent embodiment, steps S201 and S202 can be implemented as independent embodiments, steps S201, S202, and S203 can be implemented as independent embodiments, steps S201, S204, and S205 can be implemented as independent embodiments, steps S201, S202, S204, and S205 can be implemented as independent embodiments, and steps S201, S202, S203, S204, and S205 can be implemented as independent embodiments. Steps S200, S201, S202, S203, S204, and S205 can be implemented as independent embodiments, but are not limited thereto.
[0211] In some embodiments, step S202 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0212] In some embodiments, step S203 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0213] In some embodiments, step S204 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0214] In some embodiments, step S205 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0215] Figure 3a is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3a, the communication method can be executed by a first node, and the method includes:
[0216] S301. Determine that the first network supports emergency services of terminals accessed through the first access network.
[0217] In some embodiments, the first node can determine whether its first network supports emergency services of a terminal accessed through the first access network. Optionally, the first node can be a core network node, such as an MME.
[0218] In some embodiments, the first node may determine the emergency services supported by the first network for terminals accessing through the first access network based on at least one of the following:
[0219] The terminal accesses the network through the first access network;
[0220] The first network supports emergency services through the first access network;
[0221] Regulations or operational strategies may support the terminal in carrying out emergency services through the primary access network at its location;
[0222] Emergency service configuration on the first node supports emergency services to be carried out through the first access network.
[0223] The optional implementation of step S301 can be found in the optional implementation of step S200 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0224] S302, Send the first message.
[0225] In some embodiments, the first node may send first information to the terminal. Optionally, the first information is used to indicate that the first network supports emergency services of the terminal accessed through the first access network.
[0226] In some embodiments, after a first node determines that its first network supports emergency services of a terminal accessing through a first access network, it may send first information to the terminal so that the terminal knows that the first network supports its emergency services when it accesses the first network through the first access network.
[0227] The optional implementation of step S302 can be found in the optional implementation of step S201 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0228] The method involved in the embodiments of this disclosure may include at least one of steps S301 to S302. For example, step S302 may be implemented as a separate embodiment, but is not limited thereto.
[0229] In some embodiments, step S301 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0230] Figure 3b is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3b, the communication method can be executed by a first node, and the method includes:
[0231] S311, Obtain the second information.
[0232] In some embodiments, acquiring can be understood as receiving. Optionally, the first node receives second information sent by the terminal.
[0233] In some embodiments, the second information is used to initiate a network attachment process for emergency services. Optionally, the first node may receive the second information sent by the terminal for initiating a network attachment process for emergency services.
[0234] In some embodiments, the second information is used to send a normal network attach procedure. Optionally, the first node may receive the second information sent by the terminal for initiating a normal network attach procedure.
[0235] The optional implementation of step S311 can be found in the optional implementation of step S204 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0236] S312. Determine that the first network supports emergency services for terminals accessed through the first access network.
[0237] In some embodiments, after receiving information from the terminal regarding initiating an emergency service network attachment procedure, or information regarding initiating a normal network attachment procedure, the first node can determine that the first network supports emergency services for terminals accessing through the first access network based on at least one of the following:
[0238] The terminal accesses the network through the first access network;
[0239] The first network supports emergency services through the first access network;
[0240] Regulations or operational strategies may support the terminal in carrying out emergency services through the primary access network at its location;
[0241] Emergency service configuration on the first node supports emergency services to be carried out through the first access network.
[0242] The optional implementation of step S312 can be found in the optional implementation of step S200 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0243] S313, Send the first message.
[0244] In some embodiments, the first node may send first information to the terminal. Optionally, the first information is used to indicate that the first network supports emergency services of the terminal accessed through the first access network.
[0245] The optional implementation of step S313 can be found in the optional implementation of step S201 in Figure 2, the optional implementation of step S302 in Figure 3a, and other related parts in the embodiments involved in Figures 2 and 3a, which will not be repeated here.
[0246] S314. Obtain third-party information.
[0247] In some embodiments, acquiring can be understood as receiving. Optionally, the first node receives third information sent by the terminal.
[0248] In some embodiments, the third information is used to request the establishment of a PDN connection for emergency services.
[0249] In some embodiments, the third information is sent based on the first information. Optionally, if the terminal learns that the network where the first node is located supports the terminal's emergency services accessed through the first access network, it can send third information to the first node requesting it to establish a PDN connection for the emergency services.
[0250] In some embodiments, if the second information in step S311 is used to send a normal network attach procedure, the third information may include access information related to emergency services, such as the access point name related to emergency services.
[0251] The optional implementation of step S314 can be found in the optional implementation of step S202 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0252] The method involved in the embodiments of this disclosure may include at least one of steps S311 to S314. For example, step S312 may be implemented as an independent embodiment, steps S311 and S312 may be implemented as independent embodiments, steps S312 and S313 may be implemented as independent embodiments, steps S311, S312 and S313 may be implemented as independent embodiments, and steps S312, S313 and S314 may be implemented as independent embodiments, but are not limited thereto.
[0253] In some embodiments, step S311 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0254] In some embodiments, step S313 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0255] In some embodiments, step S314 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0256] Figure 3c is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3c, the communication method can be executed by a first node, and the method includes:
[0257] S321. Determine that the first network supports emergency services for terminals accessed through the first access network.
[0258] The optional implementation of step S321 can be found in the optional implementation of step S200 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0259] In some embodiments, it is determined that the first network supports emergency services for terminals accessed through the first access network based on at least one of the following:
[0260] The terminal accesses the network through the first access network;
[0261] The first network supports emergency services through the first access network;
[0262] Regulations or operational strategies may support the terminal in carrying out emergency services through the primary access network at its location;
[0263] Emergency service configuration on the first node supports emergency services to be carried out through the first access network.
[0264] In some embodiments, the above method may further include: sending first information.
[0265] In some embodiments, the first node sends first information to the terminal.
[0266] In some embodiments, the first information is used to indicate that the first network supports emergency services for terminals accessed through the first access network. Optionally, the first network is the network where the first node is located. Optionally, the first node can be a core network node, such as an MME.
[0267] The above-mentioned optional implementation methods can be found in the optional implementation methods of step S201 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0268] In some embodiments, before step S321, the method may further include: receiving second information sent by the terminal.
[0269] Optionally, the second information is used to initiate the network attachment process for emergency services.
[0270] Optionally, the second information is used to initiate the normal network attach process.
[0271] In some embodiments, the second information is sent by the terminal based on the fourth information, which is received by the terminal from the network device of the first access network. The fourth information is used to indicate that the serving cell of the network device supports emergency services.
[0272] The above-mentioned optional implementation methods can be found in the optional implementation methods of steps S204 and S205 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0273] In some embodiments, the method may further include receiving third information sent by a terminal. Optionally, the third information is used to request the establishment of a packet data network (PDN) connection for emergency services.
[0274] In some embodiments, the third information is sent based on the first information.
[0275] In some embodiments, the third information includes access information related to emergency services.
[0276] The above-mentioned optional implementation methods can be found in the optional implementation methods of step S202 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0277] In the above embodiments, the first access network may include narrowband Internet of Things (NB-IoT). Optionally, the first access network may include: an NB-IoT Terrestrial Network (TN) and an NB-IoT Non-Terrestrial Network (NTN).
[0278] In the above embodiments, emergency services may include IP Multimedia Subsystem (IMS) emergency services. Optionally, IMS emergency services may include IMS emergency voice call services.
[0279] Figure 4a is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4a, the method involved in this embodiment is executed by a terminal, and the method includes:
[0280] S401, Send the second message.
[0281] In some embodiments, the terminal may send second information to the first node.
[0282] In some embodiments, the second information is used to initiate a network attachment process for emergency services. Optionally, the terminal may send the second information for initiating a network attachment process for emergency services to the first node.
[0283] In some embodiments, the second information is used to send a normal network attach procedure. Optionally, the terminal may send the second information to the first node to initiate a normal network attach procedure.
[0284] The optional implementation of step S401 can be found in the optional implementation of step S204 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0285] S402, Obtain first information.
[0286] In some embodiments, acquiring can be understood as receiving. Optionally, the terminal receives the first information sent by the first node.
[0287] In some embodiments, the first information is used to indicate that the first network where the first node is located supports emergency services of terminals accessed through the first access network.
[0288] In some embodiments, after receiving information from the terminal regarding initiating an emergency service network attachment process, or information regarding initiating a normal network attachment process, the first node can determine whether the first network to which the first node resides supports the terminal's emergency service accessed through the first access network. If it is determined that the first network supports the terminal's emergency service accessed through the first access network, the first node can send first information to the terminal.
[0289] The optional implementation of step S402 can be found in the optional implementation of step S201 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0290] S403, Send third information.
[0291] In some embodiments, the terminal may send third information to the first node.
[0292] In some embodiments, the third information is used to request the establishment of a PDN connection for emergency services.
[0293] In some embodiments, the third information is sent based on the first information. Optionally, if the terminal learns that the network where the first node is located supports the terminal's emergency services accessed through the first access network, it can send third information to the first node requesting it to establish a PDN connection for the emergency services.
[0294] The optional implementation of step S403 can be found in the optional implementation of step S202 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0295] In some embodiments, if the second information in step S311 is used to send a normal network attach procedure, the third information may include access information related to emergency services, such as the access point name related to emergency services.
[0296] The method involved in the embodiments of this disclosure may include at least one of steps S401 to S403. For example, step S402 may be implemented as a separate embodiment, steps S401 and S402 may be implemented as separate embodiments, and steps S402 and S403 may be implemented as separate embodiments, but are not limited thereto.
[0297] In some embodiments, step S401 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0298] In some embodiments, step S403 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0299] Figure 4b is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4b, the method involved in this embodiment is executed by a terminal, and the method includes:
[0300] S411, Obtain first information.
[0301] In some embodiments, acquiring can be understood as receiving. Optionally, the terminal receives the first information sent by the first node.
[0302] In some embodiments, the first information is used to indicate that the first network supports emergency services for terminals accessed through the first access network. Optionally, the first network is the network where the first node is located. Optionally, the first node can be a core network node, such as an MME.
[0303] The optional implementation of step S411 can be found in the optional implementation of step S201 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0304] In some embodiments, the emergency services supported by the first network for terminals accessed through the first access network are determined based on at least one of the following:
[0305] The terminal accesses the network through the first access network;
[0306] The first network supports emergency services through the first access network;
[0307] Regulations or operational strategies may support the terminal in carrying out emergency services through the primary access network at its location;
[0308] Emergency service configuration on the first node supports emergency services to be carried out through the first access network.
[0309] In some embodiments, the above method may further include: sending second information to the first node.
[0310] In some embodiments, the second information is used to initiate the network attachment process for emergency services.
[0311] In some embodiments, the second information is used to initiate a normal network attach process.
[0312] The above-mentioned optional implementation methods can be found in the optional implementation methods of step S204 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0313] In some embodiments, the method may further include: sending third information to the first node. Optionally, the third information is used to request the establishment of a packet data network (PDN) connection for emergency services.
[0314] In some embodiments, the third information is sent based on the first information.
[0315] In some embodiments, the third information includes access information related to emergency services.
[0316] The above-mentioned optional implementation methods can be found in the optional implementation methods of step S202 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0317] In some embodiments, the method may further include receiving fourth information sent by a network device located in a first access network. Optionally, the fourth information is used to indicate that the cell served by the network device supports emergency services.
[0318] In this embodiment, sending the second information to the first node may include: sending the second information to the first node based on the fourth information.
[0319] The above-mentioned optional implementation methods can be found in the optional implementation methods of step S205 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0320] In the above embodiments, the first access network may include narrowband Internet of Things (NB-IoT). Optionally, the first access network may include: an NB-IoT Terrestrial Network (TN) and an NB-IoT Non-Terrestrial Network (NTN).
[0321] In the above embodiments, emergency services may include IP Multimedia Subsystem (IMS) emergency services. Optionally, IMS emergency services may include IMS emergency voice call services.
[0322] This disclosure also provides an optional implementation, as shown in FIG5a, including:
[0323] S51 and MME (which may correspond to the first node above) determine, based on at least one of the following information, that the terminal supports IMS emergency services via NB-IoT:
[0324] The terminal connects via NB-IoT;
[0325] The network where the MME is located supports IMS emergency services via NB-IoT;
[0326] The regulations or operational policies at the location of the terminal support IMS emergency services via NB-IoT;
[0327] Emergency service configuration data on the MME supports emergency services via NB-IoT.
[0328] S52 and MME send the first information to the terminal.
[0329] Optionally, the first information indication supports IMS emergency services via NB-IoT.
[0330] In some embodiments, prior to step S52, the following may also be included:
[0331] S50a, The terminal sends an emergency registration request to the MME (which may correspond to the second information above).
[0332] Optionally, an emergency registration request is used to request network attachment for IMS emergency services.
[0333] In some embodiments, prior to step S50a, the following may also be included:
[0334] S50b: The terminal receives broadcast information (which may correspond to the fourth information mentioned above) sent by a network device located in the NB-IoT network. Optionally, the broadcast information indicates that the broadcasting cell supports IMS emergency services.
[0335] In some embodiments, based on broadcast information, the terminal may perform at least one of the following:
[0336] Initiate an emergency registration request;
[0337] Initiate a PDN connection establishment request for emergency operations.
[0338] It should be noted that steps S50a and S50b can be before or after step S51, and this embodiment does not limit this.
[0339] In some embodiments, after step S52, the following may also be included:
[0340] S53. The terminal initiates a PDN connection establishment request for emergency services based on the first information (which may correspond to the third information mentioned above).
[0341] In the above embodiments, NB-IoT access includes, but is not limited to, NB-IoT Terrestrial Network (TN) access and NB-IoT Non-Terrestrial Network (NTN) access. Optionally, NB-IoT NTN access includes NB-IoT Geosynchronous Earth Orbit (GEO) access.
[0342] In the above embodiments, IMS emergency services include, but are not limited to, IMS emergency voice call services.
[0343] The method involved in the embodiments of this disclosure may include at least one of steps S50a to S53. For example, steps S51 and S52 may be implemented as independent embodiments, steps S51, S52 and S53 may be implemented as independent embodiments, steps S50a, S51 and S52 may be implemented as independent embodiments, steps S50a, S51, S52 and S53 may be implemented as independent embodiments, steps S50a, S50b, S51 and S52 may be implemented as independent embodiments, and steps S50a, S50b, S51, S52 and S53 may be implemented as independent embodiments, but are not limited thereto.
[0344] In some embodiments, step S50a is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0345] In some embodiments, step S50b is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0346] In some embodiments, step S53 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0347] Example 1:
[0348] This disclosure provides an optional implementation scheme, as shown in FIG5b, including:
[0349] S501, A UE located in the coverage area of an NB-IoT eNodeB (which may correspond to the network mentioned above) receives broadcast information from the eNodeB.
[0350] Optionally, the eNodeB can broadcast in a system message whether the cell supports emergency calls from UEs in a limited service state.
[0351] Optionally, the broadcast message indicates that the eNodeB's cell supports IMS emergency calls.
[0352] Optionally, NB-IoT access is NB-IoT access based on GEO satellites, using GEO to provide network coverage.
[0353] S502. If the UE needs to use the IMS emergency call service, it should camp on the cell of the eNodeB.
[0354] S503. Before using the IMS emergency call service, the UE needs to initiate the emergency attach procedure using an attach request message. This message indicates that the attach is for receiving emergency services.
[0355] S504. When the MME receives an attach request indicated as an emergency attach, if the MME has the capability to support emergency services, and if local regulations support emergency services via NB-IoT access or NB-IoT-GEO access, then the MME accepts the attach for the emergency service. The process is not affected by whether the UE is authenticated, whether it is roaming, whether it is under mobility restrictions, or whether it has a valid subscription.
[0356] S505, MME sends an attach accept to UE.
[0357] S506. During the process of attaching emergency services, a PDN connection for emergency services can also be established.
[0358] In some embodiments, it may also include: establishing an emergency bearer for PDN connections for emergency services.
[0359] Optionally, the UE can initiate an IMS emergency call through the emergency bearer.
[0360] Example 2:
[0361] This disclosure provides an optional implementation scheme, as shown in FIG5c, including:
[0362] S511. The UE located in the coverage area of the NB-IoT eNodeB receives broadcast information from the eNodeB.
[0363] Optionally, the broadcast information is used to indicate that the cell of the eNodeB supports IMS emergency call.
[0364] Optionally, NB-IoT access is NB-IoT access based on GEO satellites, using GEO to provide network coverage.
[0365] S512, regardless of whether the UE needs to use emergency services, it remains camped on the cell of the eNodeB.
[0366] S513. The UE initiates a normal attach process by using an attach request. The normal attach process is the initial attach process. Other data services, including emergency services, can be carried out through the attach process.
[0367] S514. When the MME receives an attach request, if the network where the MME is located has the capability to support emergency services, and if local regulations support emergency services via NB-IoT access, then the MME determines that it supports IMS emergency services via NB-IoT access, wherein the NB-IoT access includes terrestrial NB-IoT access (NB-IoT TN) or non-terrestrial NB-IoT access (NB-IoT NTN); the IMS emergency services include IMS emergency voice services or IMS emergency calls.
[0368] S515 and MME send an attach accept message to the UE, which can indicate support for IMS emergency calls via NB-IoT NTN.
[0369] S516. The UE sends a PDN connection request message to the MME. This message contains an APN related to emergency services, which is used to indicate that the PDN connection is used for emergency services.
[0370] Optionally, based on the IMS emergency call indication received in step S515 that supports IMS emergency calls via NB-IoT NTN, if a normally attached UE wants to use IMS emergency calls, a PDN connection for the emergency service needs to be established before using the IMS emergency service.
[0371] S517. Based on emergency configuration data, the MME can authorize the establishment of a PDN connection for emergency services for the UE.
[0372] S518, MME sends a Create Session Request message to S-GW / P-GW. After establishing the emergency bearer, S-GW / P-GW sends a Create Session response message to MME.
[0373] Optionally, the session creation request message may include an emergency APN. Optionally, the emergency APN is used to select a dedicated P-GW that supports IMS emergency services.
[0374] S519, MME sends an emergency PDN connection response message to UE for emergency services.
[0375] S5110. Establish an emergency bearer for a normally attached UE to use for emergency services via a PDN connection. Optionally, the PDN connection for emergency services can also be described as an "emergency PDN connection".
[0376] Optionally, the UE can initiate an IMS emergency call via the emergency bearer of the emergency PDN connection, which can also be described as "IMS emergency voice service".
[0377] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.
[0378] Figure 6a is a schematic diagram of the structure of a terminal proposed in an embodiment of this disclosure. As shown in Figure 6a, the terminal may include at least one of a first transceiver module 611, a first processing module 612, etc.
[0379] In some embodiments, the first transceiver module 611 is used to receive first information sent by the first node, the first information being used to indicate that the first network supports emergency services of the terminal accessed through the first access network, wherein the first network is the network where the first node is located.
[0380] Optionally, the first transceiver module 611 is also used to perform the steps related to sending and receiving signaling or communicating performed by the terminal in any of the above methods, such as at least one of steps S202, S204, and S205 shown in Figure 2, which will not be described in detail here.
[0381] Figure 6b is a schematic diagram of the structure of the first node proposed in an embodiment of this disclosure. As shown in Figure 6b, the first node includes at least one of a second transceiver module 621, a second processing module 622, etc.
[0382] In some embodiments, the second processing module 622 is configured to determine, based on at least one of the following, that the first network supports emergency services for terminals accessing through the first access network:
[0383] The terminal accesses the network via the first access network;
[0384] The first network supports emergency services through the first access network;
[0385] Regulations or operational policies support the terminal in carrying out emergency services through the first access network at its location;
[0386] The emergency service configuration on the first node supports emergency services through the first access network; wherein, the first network is the network where the first node is located.
[0387] Optionally, the second processing module 622 is also used to execute the information processing-related steps performed by the first node in any of the above methods, such as step S203 shown in Figure 2, which will not be described in detail here.
[0388] Optionally, the second transceiver module 621 is also used to perform the steps related to sending and receiving signaling or communicating executed by the first node in any of the above methods, such as at least one of steps S201, S202, and S204 shown in Figure 2, which will not be described in detail here.
[0389] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functions of some or all of the units or modules can be achieved through the design of the hardware circuits. The aforementioned hardware circuits can be understood as one or more processors. For example, in one implementation, the aforementioned hardware circuit is an application-specific integrated circuit (ASIC). The functions of some or all of the aforementioned units or modules are achieved through the design of the logical relationships between the components within the circuit. As another example, in another implementation, the aforementioned hardware circuit can be implemented through a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functions of some or all of the aforementioned units or modules.
[0390] All units or modules of the above devices can be implemented entirely through processor-invoked software, entirely through hardware circuits, or partially through processor-invoked software with the remainder implemented through hardware circuits. In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. These logical relationships are fixed or reconfigurable. For example, the processor may be a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be hardware circuits designed for artificial intelligence, which can be understood as ASICs, such as Neural Network Processing Units (NPUs), Tensor Processing Units (TPUs), and Deep Learning Processing Units (DPUs).
[0391] Figure 7a is a schematic diagram of the structure of the communication device 7100 proposed in an embodiment of this disclosure. The communication device 7100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 7100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0392] As shown in Figure 7a, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. The processor 7101 is used to invoke instructions to cause the communication device 7100 to execute any of the above methods.
[0393] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the transceiver 7103 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., at least one of steps S201, S202, S204, and S205 shown in FIG. 2, but not limited thereto), and the processor 7101 performs at least one of other steps (e.g., at least one of steps S200 and S203 shown in FIG. 2, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0394] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may be located outside the communication device 7100.
[0395] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.
[0396] Optionally, the communication device 7100 further includes one or more interface circuits 7104, which are connected to the memory 7102. The interface circuits 7104 can be used to receive signals from the memory 7102 or other devices, and can be used to send signals to the memory 7102 or other devices. For example, the interface circuits 7104 can read instructions stored in the memory 7102 and send the instructions to the processor 7101.
[0397] The communication device 7100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 7100 described in this disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7a. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0398] Figure 7b is a schematic diagram of the structure of the chip 7200 proposed in an embodiment of this disclosure. For cases where the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the chip 7200 shown in Figure 7b, but it is not limited thereto.
[0399] Chip 7200 includes one or more processors 7201. Chip 7200 is used to perform any of the above methods.
[0400] In some embodiments, chip 7200 further includes one or more interface circuits 7202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 7200 further includes one or more memories 7203 for storing data. Optionally, all or part of the memories 7203 may be located outside of chip 7200. Optionally, interface circuit 7202 is connected to memory 7203, and interface circuit 7202 can be used to receive data from memory 7203 or other devices, and interface circuit 7202 can be used to send data to memory 7203 or other devices. For example, interface circuit 7202 can read data stored in memory 7203 and send the data to processor 7201.
[0401] In some embodiments, the interface circuit 7202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., at least one of steps S201, S202, S204, and S205 shown in FIG. 2, but not limited thereto). The interface circuit 7202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 7202 performing data interaction between the processor 7201, the chip 7200, the memory 7203, or the transceiver device. In some embodiments, the processor 7201 performs at least one of other steps (e.g., at least one of steps S200 and S203 shown in FIG. 2, but not limited thereto).
[0402] This disclosure also provides a program product that, when executed by the communication device 7100, causes the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.
[0403] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
[0404] The technical solutions described in the embodiments of this disclosure can be combined arbitrarily without conflict.
[0405] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.
[0406] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.
Claims
1. A communication method, characterized in that, The method is executed by the first node, and the method includes: The first network is determined to support emergency services for terminals accessing the first access network based on at least one of the following: The terminal accesses the network via the first access network; The first network supports emergency services through the first access network; Regulations or operational policies support the terminal in carrying out emergency services through the first access network at its location; The emergency service configuration on the first node supports emergency services to be carried out through the first access network. The first network is the network where the first node is located.
2. The method according to claim 1, characterized in that, The method further includes: Send first information to the terminal, the first information being used to indicate that the first network supports emergency services of the terminal accessed through the first access network.
3. The method according to claim 1 or 2, characterized in that, Before determining that the first network supports emergency services of terminals accessed through the first access network, the method further includes: The terminal sends a second message, which is used to initiate the network attachment process for the emergency service.
4. The method according to claim 1 or 2, characterized in that, Before determining that the first network supports emergency services of terminals accessed through the first access network, the method further includes: The terminal sends a second message, which is used to initiate a normal network attach process.
5. The method according to any one of claims 1-4, characterized in that, The method further includes: The terminal sends a third message, which is used to request the establishment of a packet data network (PDN) connection for the emergency service.
6. The method according to claim 5, characterized in that, The third information is sent based on the first information.
7. The method according to claim 5 or 6, characterized in that, The third piece of information includes access information related to the emergency service.
8. The method according to any one of claims 3-7, characterized in that, The second information is sent by the terminal based on the fourth information, which is received by the terminal from the network device of the first access network. The fourth information is used to indicate that the serving cell of the network device supports the emergency service.
9. The method according to any one of claims 1-8, characterized in that, The first access network includes narrowband Internet of Things (NB-IoT).
10. The method according to any one of claims 1-9, characterized in that, The emergency services include the IP Multimedia Subsystem (IMS) emergency services.
11. A communication method, characterized in that, The method is executed by a terminal, and the method includes: The system receives first information sent by a first node, which is used to indicate that the first network supports emergency services of terminals accessed through a first access network, wherein the first network is the network where the first node is located.
12. The method according to claim 11, characterized in that, The emergency services supported by the first network for terminals accessing through the first access network are determined based on at least one of the following: The terminal accesses the network via the first access network; The first network supports emergency services through the first access network; Regulations or operational policies support the terminal in carrying out emergency services through the first access network at its location; The emergency service configuration on the first node supports emergency services to be carried out through the first access network.
13. The method according to claim 11 or 12, characterized in that, The method further includes: Send a second message to the first node, the second message being used to initiate the network attachment process for the emergency service.
14. The method according to claim 11 or 12, characterized in that, The method further includes: Send a second message to the first node, the second message being used to initiate a normal network attach process.
15. The method according to any one of claims 11-14, characterized in that, The method further includes: A third message is sent to the first node, the third message being used to request the establishment of a packet data network (PDN) connection for the emergency service.
16. The method according to claim 15, characterized in that, The third information is sent based on the first information.
17. The method according to claim 15 or 16, characterized in that, The third piece of information includes access information related to the emergency service.
18. The method according to any one of claims 13-17, characterized in that, The method further includes: The system receives a fourth message sent by a network device located in the first access network, the fourth message being used to instruct the serving cell of the network device to support the emergency service; Sending the second information to the first node includes: Based on the fourth information, the second information is sent to the first node.
19. The method according to any one of claims 11-18, characterized in that, The first access network includes narrowband Internet of Things (NB-IoT).
20. The method according to any one of claims 11-19, characterized in that, The emergency services include the IP Multimedia Subsystem (IMS) emergency services.
21. A communication device, characterized in that, The communication device is used to perform the method of any one of claims 1-10, or any one of claims 11-20.
22. A communication system, characterized in that, include: A terminal and a first node, wherein the terminal is used to implement the method of any one of claims 11-20, and the network device is used to implement the method of any one of claims 1-10.
23. A computer storage medium, characterized in that, The computer-readable storage medium stores executable instructions that are loaded and executed by a processor to implement the method of any one of claims 1-10 or any one of claims 11-20.
24. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements any one of claims 1-10, or any one of claims 11-20.