Priority setting methods for emergency service, and apparatus, device and medium

WO2026232576A1PCT designated stage Publication Date: 2026-11-12GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/094058
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-12

Smart Images

  • Figure CN2025094058_12112026_PF_FP_ABST
    Figure CN2025094058_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the field of communications. Disclosed are priority setting methods for an emergency service, and an apparatus, a device and a medium. A priority setting method for an emergency service comprises: receiving a first message sent by a terminal device, wherein the first message is used for requesting an emergency service; and on the basis of the first message, sending a second message to an access network device, wherein the second message is used for indicating that the terminal device has requested the emergency service and is used for requesting that the access network device set a first priority for the terminal device, the first priority corresponding to the emergency service. The method provided in the present application helps set, when control plane optimization is applied, a first priority for a terminal device requesting an emergency service, thereby ensuring normal provision of emergency services.
Need to check novelty before this filing date? Find Prior Art

Description

Priority setting method, device and equipment for emergency service and medium TECHNICAL FIELD

[0001] The present application relates to the field of communication, in particular to a priority setting method, device and equipment for emergency service and medium. BACKGROUND

[0002] CP (Control Plane) CIoT (Cellular Internet of Things) EPS (Evolved Packet System) / 5GS (5G System) optimization refers to supporting transmission of user data through the control plane, for example, transmission of user data through NAS (Non-Access Stratum) messages. Without the need to transmit user data through the user plane after establishing a user plane connection, signaling overhead and power consumption can be reduced.

[0003] In related technologies, in the case of applying CP CIoT EPS / 5GS optimization, since the user plane connection is not established, the terminal device is not allocated ARP (Allocation and Retention Priority). This results in that the terminal device requesting emergency service cannot obtain resources for emergency service in priority. Emergency service is used to provide communication service for terminal devices in emergency situations.

[0004] Therefore, how to set priority for a terminal device requesting emergency service and applying CP CIoT EPS / 5GS optimization is a problem to be solved at present. SUMMARY

[0005] The embodiments of the present application provide a priority setting method, device and equipment for emergency service and medium, and the technical solution is as follows:

[0006] According to one aspect of the present application, a priority setting method for emergency service is provided, and the method is executed by a mobility management network element, and the method comprises the following steps:

[0007] Receiving a first message sent by a terminal device, the first message being used to request emergency service;

[0008] Based on the first message, a second message is sent to an access network device, the second message being used to indicate that the terminal device requests the emergency service, and being used to request the access network device to set a first priority for the terminal device, the first priority corresponding to the emergency service.

[0009] According to an aspect of the present application, a priority setting method for emergency service is provided, the method is performed by an access network device, and the method comprises the following steps:

[0010] receiving a second message sent by a mobility management network element, the second message being used for indicating that a terminal device requests an emergency service and requesting the access network device to set a first priority for the terminal device, the first priority corresponding to the emergency service;

[0011] setting the first priority for the terminal device based on the second message;

[0012] wherein the terminal device requests the emergency service from the mobility management network element through a first message.

[0013] According to an aspect of the present application, a mobility management network element is provided, and the mobility management network element comprises:

[0014] a first receiving module, configured to receive a first message sent by a terminal device, the first message being used for requesting an emergency service;

[0015] a first sending module, configured to send a second message to an access network device based on the first message, the second message being used for indicating that the terminal device requests the emergency service and requesting the access network device to set a first priority for the terminal device, the first priority corresponding to the emergency service.

[0016] According to an aspect of the present application, an access network device is provided, and the access network device comprises:

[0017] a second receiving module, configured to receive a second message sent by a mobility management network element, the second message being used for indicating that a terminal device requests an emergency service and requesting the access network device to set a first priority for the terminal device, the first priority corresponding to the emergency service;

[0018] a second processing module, configured to set the first priority for the terminal device based on the second message;

[0019] wherein the terminal device requests the emergency service from the mobility management network element through a first message.

[0020] According to an aspect of the present application, a terminal device is provided, and the terminal device comprises a processor and a transceiver connected to the processor; wherein the processor and / or the transceiver are configured to load and execute executable instructions to implement a priority setting method for emergency service.

[0021] According to an aspect of the present application, a network device is provided, comprising: a processor; a transceiver connected to the processor; wherein the processor and / or the transceiver are configured to load and execute the executable instructions to implement the priority setting method for emergency services.

[0022] According to an aspect of the present application, a computer readable storage medium is provided, wherein at least one program is stored in the computer readable storage medium, and the at least one program is loaded and executed by a processor and / or a transceiver to implement the priority setting method for emergency services.

[0023] According to an aspect of the present application, a chip is provided, comprising a programmable logic circuit and / or program instructions, when the chip is running on a terminal device, for implementing the above-mentioned priority setting method for emergency services.

[0024] According to an aspect of the present application, a chip is provided, comprising a programmable logic circuit and / or program instructions, when the chip is running on a network device, for implementing the above-mentioned priority setting method for emergency services.

[0025] According to an aspect of the present application, a computer program product is provided, comprising computer instructions stored in a computer readable storage medium, wherein a processor acquires the computer instructions from the computer readable storage medium, and the processor and / or a transceiver execute the computer instructions to implement the priority setting method for emergency services.

[0026] The technical solutions provided by the embodiments of the present application have at least the following beneficial effects:

[0027] It is shown that in the case that a terminal device requests emergency services, a mobility management network element sends a second message to an access network device according to a first message of the terminal device, to instruct the access network device to set a first priority for the terminal device, and the first priority corresponds to the emergency services. So that the access network device can set the priority for the terminal device. And then, fast and reliable emergency services are provided for the terminal device requesting emergency services. BRIEF DESCRIPTION OF DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative effort.

[0029] FIG. 1 shows a schematic diagram of a network architecture provided by an embodiment of the present application;

[0030] FIG. 2 shows an architecture diagram of an EPS system according to an example embodiment of the present application;

[0031] FIG. 3 shows a structure diagram of a mobile communication system according to an example embodiment of the present application;

[0032] FIG. 4 shows an architecture diagram of a 5GS system according to an example embodiment of the present application;

[0033] FIG. 5 shows a flowchart of a priority setting method for emergency services according to an example embodiment of the present application;

[0034] FIG. 6 shows a flowchart of a priority setting method for emergency services according to an example embodiment of the present application;

[0035] FIG. 7 shows a whole flowchart of a priority setting method for emergency services according to an example embodiment of the present application;

[0036] FIG. 8 shows a whole flowchart of a priority setting method for emergency services according to an example embodiment of the present application;

[0037] FIG. 9 shows a whole flowchart of a priority setting method for emergency services according to an example embodiment of the present application;

[0038] FIG. 10 shows a whole flowchart of a priority setting method for emergency services according to an example embodiment of the present application;

[0039] FIG. 11 shows a structure block diagram of a mobility management network element according to an example embodiment of the present application;

[0040] FIG. 12 shows a structure block diagram of an access network device according to an example embodiment of the present application;

[0041] FIG. 13 shows a structure diagram of a core network device according to an example embodiment of the present application;

[0042] FIG. 14 shows a structure diagram of an access network device according to an example embodiment of the present application. DETAILED DESCRIPTION

[0043] For the purpose of clarity, technical solutions and advantages of the present application will be further described in detail below with reference to the drawings. Hereinafter, exemplary embodiments will be described in detail with reference to the accompanying drawings. The exemplary embodiments are illustrated in the drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all the embodiments consistent with the present application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present application as detailed in the appended claims.

[0044] The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in the present application and the appended claims, the singular forms "a," "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0045] It should be understood that, although the terms first, second, third, etc. can be used herein to describe various information, the information should not be limited to these terms. These terms are only used to distinguish one piece of information from another. For example, a first information can also be termed a second information, and similarly, a second information can also be termed a first information without departing from the scope of the present application. Depending on the context, the word "if' as used herein can be interpreted as meaning "when" or "in response to determining" or "in response to ascertaining". In the present specification, when expressing the meaning of a Boolean value, it is expressed as '0' representing 'first meaning', '1' representing'second meaning', without loss of generality, it is understood by those skilled in the art that the representative meaning can be reversed, i.e., '1' representing 'first meaning', '0' representing'second meaning'.

[0046] The technical solutions described in some embodiments of the present application can be applied to various communication systems, for example: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolved system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th-Generation (5G) system, cellular Internet of Things system, cellular passive Internet of Things system, and can also be applied to the evolved system of 5G NR system, and can also be applied to 6G and subsequent evolved systems.

[0047] It should be understood that in some embodiments of this application, "5G" may also be referred to as "5G NR" or "NR". It should be understood that in the description of the embodiments of this application, the term "correspondence" may indicate a direct or indirect correspondence between two things, or an association between them, or a relationship of instruction and being instructed, configuration and being configured, etc. In the embodiments of this application, "predefined" can be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined may refer to what is defined in a protocol. In the embodiments of this application, "protocol" may refer to standard protocols in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0048] Figure 1 illustrates a schematic diagram of a network architecture provided in one embodiment of this application. The network architecture 100 may include: a terminal device 10, an access network device 20, and a core network device 30.

[0049] Terminal device 10 can refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent, or user device. Optionally, terminal device 10 can also be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal in a 5th Generation System (5GS), or terminal in a future Public Land Mobile Network (PLMN), etc., and this application embodiment is not limited in this respect. For ease of description, the devices mentioned above are collectively referred to as terminals. The number of terminal devices 10 is usually multiple, and one or more terminal devices 10 can be distributed within the cell managed by each access network device 20. In some embodiments, the terminal device in this application embodiment can be a CIoT terminal. CIoT terminals are characterized by low cost, simple functionality, low power consumption, and infrequent user data transmission. In other embodiments, the terminal device in this application may also be an NB-IoT (Narrowband Internet of Things) terminal.

[0050] Access network device 20 is a device deployed in an access network to provide wireless communication functionality to terminal device 10. Access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems employing different wireless access technologies, the name of the device with access network device functionality may differ. For example, in a 5GS system, it is called gNodeB or gNB (next generation Node B); in an EPS system, it is called eNodeB. As communication technologies evolve, the name "access network device" may change. For ease of description, in this embodiment, the aforementioned device providing wireless communication functionality to terminal device 10 is collectively referred to as access network device 20. Optionally, a communication relationship can be established between terminal device 10 and core network device 30 through access network device 20. For example, in an EPS system, access network device 20 can be one or more eNodeBs within an Evolved Universal Terrestrial Radio Access Network (EUTRAN); in a 5GS system, access network device 20 can be one or more gNBs within a Radio Access Network (RAN). In the embodiments of this application, unless otherwise specified, the network device referred to is access network device 20, such as a base station.

[0051] Core network device 30 is a device deployed in the core network. Core network device 30 refers to the device that can provide terminal device 10 with functions such as session management, mobility management, policy management, and security authentication. The core network device is the interface provided by the bearer network to the external network. In this embodiment, the core network device is responsible for the access management and mobility management of terminal device 10. Optionally, in a 5GS system, core network device 30 can be implemented as an AMF (Access and Mobility Management Function); in an EPS system, core network device 30 can be implemented as an MME (Mobility Management Entity).

[0052] In one example, access network device 20 and core network device 30 communicate with each other through some interface technology, such as the NG interface in a 5GS system, or the interface (also called a reference point, such as S1, S11, etc.) in an EPS system. Access network device 20 and terminal device 10 communicate with each other through some air interface technology, such as the Uu (cellular network communication interface) port.

[0053] Access network equipment 20 is the access device through which terminal equipment 10 wirelessly accesses the network architecture. It is mainly responsible for radio resource management, QoS (Quality of Service) management, data compression and encryption on the air interface side. Examples include: NodeB base stations, eNodeB base stations, base stations in 5G mobile communication systems or NR (New Radio) communication systems, and base stations in future mobile communication systems.

[0054] The core network equipment 30 includes core network elements with different functions. The division of core network elements in the 5GS system and the EPS system are somewhat different. For details, please refer to the following introduction to the architecture of 5GS and EPS.

[0055] The "5GS system" in this application embodiment can also be called a 5G NR system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in this application embodiment can be applied to LTE systems (or EPS systems), 5G NR systems, subsequent evolution systems of 5G NR systems, and other communication systems such as NB-IoT systems. This application does not limit these applications.

[0056] Figure 2 illustrates the architecture of an EPS system provided in an exemplary embodiment of this application. The EPS system may include: MME, HSS (Home Subscriber Server), S-GW (Serving Gateway), P-GW (Packet Data Network Gateway), PCRF (Policy and Charging Rules Function), SGSN (Serving GPRS Support Node), E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network), UTRAN (UMTS Terrestrial Radio Access Network), and GERAN (GSM EDGE Radio Access Network).

[0057] EUTRAN is a network comprising multiple eNodeBs used to implement radio physical layer functions, resource scheduling and radio resource management, radio access control, and mobility management. eNodeBs can connect via the X2 interface, which can be used to transmit data during X2-based handover. eNodeBs are connected to the S-GW via the user plane interface SI-U, using GTP-U (General Packet Radio System General Tunneling Protocol User Plane) to transmit user data; they are also connected to the MME via the control plane interface SI-MME. The MME is primarily responsible for all control plane functions related to user session management, including NAS (Non-Access-Stratum) signaling and security, tracking area management, P-GW selection, and S-GW selection. The SGW is primarily responsible for UE data transmission, forwarding, and routing handover, and serves as the local mobility anchor point for user equipment during handover between eNodeBs (only one SGW serves each user equipment at any given time). The P-GW, acting as the anchor point for PDN (Packet Data Network) connections, is responsible for UE Internet Protocol address allocation, terminal data packet filtering, rate control, and billing information generation. The SGSN serves as the access node for the 2G access network GERAN (GSM / EDGE Radio Access Network), the 3G access network UTRAN (Universal Terrestrial Radio Access Network), and the EPS core network EPC, responsible for establishing bearers and forwarding data from GERAN and UTRAN to the EPC. The HSS stores mobile user subscription data. The PCRF is responsible for billing management and policy control, including PCC (Policy and Charging Control) rules and QoS (Quality of Service) rules.

[0058] Furthermore, in the example shown in Figure 2, S1-MME is the reference point for the control plane protocol between E-UTRAN and MME.

[0059] S1-U is a reference point between E-UTRAN and S-GW, used for user plane tunneling for each bearer and for inter-base station path handover during the handover process.

[0060] S3 is a reference point between the MME and SGSN. It supports the exchange of user and bearer information during movement between 3GPP access networks, in both idle and / or active states. This reference point can be used within the same PLMN (Public Land Mobile Network) or between different PLMNs (e.g., during handover between different PLMNs).

[0061] S4 serves as the reference point between the S-GW and the SGSN. It provides relevant control and mobility support between the GPRS core network and the anchor function of the S-GW. Furthermore, it can provide user plane tunneling if a direct tunnel is not established.

[0062] S5 is the reference point between the S-GW and P-GW. It provides user plane tunneling and tunnel management functions between the S-GW and P-GW. It is used for serving gateway relocation due to UE movement, and when the S-GW needs to connect to a non-co-located P-GW to achieve the required PDN connection.

[0063] S6a serves as a reference point between the MME and HSS. It facilitates the transmission of subscription and authentication data between the MME and HSS, and is used for user access to the evolution system via an AAA interface.

[0064] Gx is used to provide QoS (Quality of Service) policy and charging rule transmission from PCRF to P-GW for PCEF (Policy and Charging Enforcement Function).

[0065] S10 is a reference point between MMEs, used for MME relocation and information transmission between MMEs. This reference point can be used within the same PLMN or between different PLMNs (e.g., when switching between different PLMNs).

[0066] S11 is the control plane reference point between the MME and S-GW. To support Control Plane CIoT EPS Optimisation, S11-U provides the user plane between the MME and S-GW, enabling the transmission of user data.

[0067] S12 serves as the user plane tunnel transmission reference point between the UTRAN and S-GW when establishing a direct tunnel. It is based on the Iu-u / Gn-u reference point and uses the GTP-U protocol defined between the SGSN and UTRAN or between the SGSN and GGSN. S12 is a configuration option for the operator.

[0068] SGi is the reference point between the P-GW and the packet data network. The packet data network can be a public or private packet data network outside the operator, or it can be an internal packet data network within the operator, such as one used to provide IMS (IP Multimedia Subsystem) services. This reference point corresponds to the Gi reference point for 3GPP access.

[0069] Rx is located between AF (Application Function) and PCRF.

[0070] Figure 3 illustrates a schematic diagram of the structure of a mobile communication system 200 provided in an exemplary embodiment of this application. As shown in Figure 3, the mobile communication system 200 may include a UE, a RAN (Radio Access Network), a Core, and a DN (Data Network). The UE, RAN, and Core are the main components of the architecture, logically divided into a user plane and a control plane. The control plane is responsible for the management of the mobile network, while the user plane is responsible for the transmission of service data. In Figure 3, the NG2 reference point is located between the RAN control plane and the Core control plane, the NG3 reference point is located between the RAN user plane and the Core user plane, and the NG6 reference point is located between the Core user plane and the data network.

[0071] UE (User Equipment): This is the entry point for mobile users to interact with the network. It provides basic computing and storage capabilities, displays service windows to the user, and accepts user input. The UE will use next-generation air interface technology to establish signal and data connections with the RAN (Radio Network Array), thereby transmitting control signals and service data to the mobile network.

[0072] RAN: Similar to a base station in a traditional network, it is deployed close to the UE (User Equipment) to provide network access for authorized users in a specific area. It can transmit user data using transmission tunnels of varying quality based on the user's level and service requirements. The RAN manages its own resources, utilizes them efficiently, and provides access services to the UE on demand, forwarding control signals and user data between the UE and the core network.

[0073] Core: Responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing UE with functions such as session management, mobility management, policy management, and security authentication. When the UE attaches, it provides network access authentication; when the UE has a service request, it allocates network resources for the UE; when the UE moves, it updates network resources for the UE; when the UE is idle, it provides a fast recovery mechanism for the UE; when the UE detaches, it releases network resources for the UE; when the UE has service data, it provides data routing functions, such as forwarding uplink data to the DN; or receiving downlink data from the UE from the DN, forwarding it to the RAN, and then sending it to the UE.

[0074] DN: This is the data network that provides services to users. Generally, the client is located at the UE (User Equipment), and the server is located in the data network. The data network can be a private network, such as a local area network (LAN), an external network not controlled by the operator, such as the Internet, or a dedicated network jointly deployed by the operator, such as for configuring IMS services.

[0075] Figure 4 shows the detailed architecture defined based on Figure 3. The core network user plane includes the UPF (User Plane Function); the core network control plane includes the AUSF (Authentication Server Function), AMF (Access and Mobility Management Function), SMF (Session Management Function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (NF Repository Function), UDM (Unified Data Management), PCF (Policy Control Function), SF (Sensing Function), AF (Application Function), and GMSC (Gateway Mobile Sensing Center). The functions of these entities are as follows:

[0076] UPF: Performs user packet forwarding according to the routing rules of SMF;

[0077] AUSF: Performs security authentication for the UE;

[0078] AMF: UE Access Management and Mobility Management;

[0079] SMF: UE Session Management;

[0080] NSSF: Select network slices for the UE;

[0081] NEF: To expose network functions to third parties via API interfaces;

[0082] NRF: Provides storage and selection functions for network function entity information for other network elements;

[0083] UDM: Management of user subscription context;

[0084] PCF: User Policy Management;

[0085] SF: Sensing function, responsible for processing sensing data and generating sensing results;

[0086] AF (located in the data network): User application management;

[0087] GMSC: Used to handle functions related to scene perception.

[0088] In some embodiments, GMSC may also be referred to as GMSF (Gateway Mobile Sensing Function).

[0089] In the architecture shown in Figure 4, the N1 interface is the reference point between the UE and the AMF; the N2 interface is the reference point between the RAN and the AMF, used for sending NAS (Non-Access Stratum) messages, etc.; the N3 interface is the reference point between the RAN and the UPF, used for transmitting user plane data, etc.; the N4 interface is the reference point between the SMF and the UPF, used for transmitting information such as tunnel identification information for N3 connection, data buffer indication information, and downlink data notification messages, etc.; and the N6 interface is the reference point between the UPF and the DN, used for transmitting user plane data, etc.

[0090] The UE connects to the (R)AN (Access Network) via the Uu interface to establish an access layer connection, exchanging access layer messages and radio data. The UE connects to the AMF (Asynchronous Access Management Function) via the N1 interface to exchange NAS messages. The AMF is the mobility management function in the core network, and the SMF is the session management function. In addition to managing the UE's mobility, the AMF is responsible for forwarding session management-related messages between the UE and the SMF. The PCF is the policy management function in the core network, responsible for formulating policies related to UE mobility management, session management, and charging. The PCF transmits data with the AF (Automatic Front-End) via the N5 interface. The UPF (User Plane Function) is the user plane function in the core network, transmitting data with the DN (Digital Network) via the N6 interface and with the AN (Anchor Network) via the N3 interface.

[0091] It should be noted that the interface names between the network elements in Figures 3 and 4 are merely examples, and the interface names in actual implementations may be different. This application embodiment does not impose specific limitations on these names. Similarly, the names of the network elements (such as SMF, AF, UPF, etc.) included in Figures 3 and 4 are also merely examples and do not limit the functionality of the network elements themselves. In 5GS and other future networks, the aforementioned network elements may also have other names, and this application embodiment does not impose specific limitations on these names. For example, in 6G networks, some or all of the aforementioned network elements may use the terminology from 5G, or they may use other names, etc. This is explained uniformly here and will not be elaborated further below. Furthermore, it should be understood that the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not limit the functionality of the messages themselves.

[0092] Before introducing the technical solution of this application, some background technical knowledge involved in this application will be introduced and explained. The following related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0093] Emergency Services

[0094] Emergency services are used to support IMS emergency sessions. "Emergency services" refers to the functionality provided when the service network is configured to support emergency services. Emergency services are provided to normally registered UEs and UEs that are urgently registered; these UEs can be normally registered or in a limited service state. According to local regulations, receiving emergency services in a limited service state does not require a valid subscription. According to local regulations and operator policies, the network may allow or deny emergency service registration requests (i.e., emergency registration) from UEs identified as being in a limited service state. The four supported emergency service behaviors are as follows:

[0095] 1. Valid UE Only: UEs with limited service status are not supported in the network. Only UEs with valid subscriptions, authenticated and authorized at the attachment location are allowed. The UE should attach to the network and then perform a PDN connection request when an IMS emergency session is detected by the UE.

[0096] 2. Only Authenticated UEs: These UEs must have a valid IMSI (International Mobile Subscriber Identity). These UEs are authenticated and may be in a limited service state due to being in a restricted service location. Unauthenticated UEs will be rejected.

[0097] 3. IMSI required, authentication optional: These UEs must have an IMSI. If authentication fails, the UE will be granted access, and the unauthenticated IMSI will be retained in the network for record-keeping. The IMEI (International Mobile Equipment Identity) will be used as the UE identifier in the network. IMEI-only UEs will be rejected (e.g., UICCless UEs).

[0098] 4. Allow all UEs: This includes UEs with unauthenticated IMSIs and UEs with only IMEIs, in addition to authenticated UEs. If a UE provides an unauthenticated IMSI, the unauthenticated IMSI will be retained in the network for logging. The IMEI will be used to identify the UE in the network.

[0099] To provide emergency bearer services, the MME configures MME emergency configuration data, which applies to all emergency bearer services established by the MME in response to UE requests. The MME emergency configuration data includes an emergency APN for deriving the P-GW, or it may also include a P-GW statically configured for the emergency APN.

[0100] For satellite-access-based cellular IoT, if a UE in limited service status knows its location within a country, the UE should select the PLMN providing service for its country. The network can be configured to verify the location of UEs registering for emergency services.

[0101] A UE in limited service state will initiate an attach procedure, indicating that the attach will be used to receive emergency services. Additionally, UEs that have already attached for normal service but have not established an emergency bearer, and are camped in a limited service state cell (e.g., due to limited tracking area or prohibition of closed user groups), should also initiate this attach procedure, indicating that the attach will be used to receive emergency services. Networks supporting emergency services for UEs in limited service state will provide emergency bearer services to these UEs, regardless of whether the UE can be authenticated, whether there are roaming or mobility restrictions, or whether it has a valid subscription (depending on local regulations). For emergency services other than eCall, UEs in limited service state determine whether the cell supports emergency services provided via E-UTRAN through broadcast indications in the AS. eCall emergency calls can only be made via IMS if the UE has a UICC (Universal Integrated Circuit Card).

[0102] A normally camped UE in the cell (i.e., without any conditions that would cause a service-limited state) will initiate a normal initial attach procedure if it is not already connected. A normally connected UE will initiate a "UE-Requested PDN Connection" procedure to receive emergency bearer service. During the attach and TAU procedures, a normally camped UE will learn from the emergency service support indicator that the PLMN supports providing emergency bearer service via E-UTRAN. The MME can be configured to indicate the emergency service support indicator for each HPLMN (Home Public Land Mobile Network). A normally camped UE can also use the emergency attach procedure under specified conditions, such as when the MM (Mobility Management) backoff timer is running.

[0103] When a UE uses NB-IoT, emergency bearer service is not supported. That is, for a UE using a RAT type access network equal to NB-IoT, the MME shall not use an emergency service support indicator to indicate support for emergency bearer service during attach and TAU (Tracking Area Update) processes, and the NB-IoT cell shall not indicate support for emergency service in any broadcast information in the AS (Access Stratum).

[0104] When emergency services are supported and local regulations require emergency sessions to be provided regardless of mobility or access restrictions, mobility restrictions do not apply to UEs receiving emergency services. When the E-RAB (Evolved Radio Access Bearer) for the emergency bearer is established, the ARP value of the emergency bearer service indicates the usage of emergency services in the E-UTRAN.

[0105] If local regulations require support for calls from unauthorized callers, the MME may not have subscribed data. Furthermore, the local network may wish to provide IMS emergency service support in a manner different from what the UE's subscription allows. Therefore, the initial QoS values ​​used to establish emergency bearer service are configured in the MME's "MME Emergency Configuration Data".

[0106] Dynamic PCC is used for UE to establish emergency services. When establishing an emergency bearer service with the P-GW, the PCRF provides QoS parameters to the P-GW, including ARP values ​​reserved for the emergency bearer, to determine the bearer priority during access control. Dynamic PCC should be used to manage IMS emergency sessions when the operator allows them.

[0107] PCRF ensures that emergency PDN connections are used only for IMS emergency sessions. If the AF (i.e., P-CSCF) does not provide an emergency indication to the PCRF, the PCRF will reject IMS sessions established via emergency PDN connections.

[0108] The default and dedicated EPS bearers of the PDN connection associated with the emergency APN should be dedicated to the IMS emergency session and should not allow any other type of traffic. The emergency bearer context must not be changed to a non-emergency bearer context, and vice versa. The P-GW should block any traffic not originating from or destined for the address of the network entity providing IMS emergency services (e.g., P-CSCF). Dynamic PCC should be deployed to support IMS emergency sessions. If an emergency P-GW connection already exists, the UE must not request another emergency PDN connection. The MME should reject any other emergency PDN connection requests. The UE must not request any bearer resource modifications for an emergency PDN connection. The P-GW should reject any bearer resource modifications requested by the UE for an emergency PDN connection. ARP reserved for emergency bearer services should only be allocated to the EPS bearer associated with the emergency PDN connection.

[0109] Control plane optimization

[0110] In NB-IoT's CIoT CP (Control Plane) optimization, data transmission is achieved by encapsulating user data within NAS (Non-Access Stratum) messages. User data is encapsulated in NAS messages and transmitted via UL NAS signaling messages or data carried within UL RRC (Radio Resource Control) container messages. Downlink user data is also transmitted via DL RRC container messages within DL NAS signaling or DL ​​NAS data. Data transmission does not require establishing additional user plane connections, further reducing latency and resource consumption.

[0111] CIoT CP optimization supports the transmission of IP, non-IP, and SMS data. For IP data, the UE and MME can perform header compression based on the ROHC framework. When the UE has user data to send, it initiates a Service Request procedure and transmits the user data by sending a Control Plane Service Request (CONTROL PLANE SERVICE REQUEST) message. If the UE has already established a PDN connection, it will include an ESM Data Transport message in the CONTROL PLANE SERVICE REQUEST message. CIoT CP optimization does not support the establishment of dedicated bearers.

[0112] It should be noted that the emergency services shown in the embodiments of this application generally refer to communication services provided to users in emergency situations. However, they can also be considered as communication services requiring first priority (or high priority), that is, emergency services can also be called priority services, leading services, first services, etc. The embodiments of this application do not limit this, but the scope of protection of the embodiments of this application is not limited thereto.

[0113] Figure 5 illustrates a flowchart of a priority setting method for emergency services provided in an exemplary embodiment of this application. The method is performed by a mobility management network element. The method includes:

[0114] Step 210: Receive the first message sent by the terminal device. The first message is used to request emergency services.

[0115] The first message is used to request emergency services, or in other words, the first message is used to instruct the terminal device to request emergency services, or in other words, the first message is used to instruct the terminal device to request the network device to provide emergency services.

[0116] In some embodiments, the first message is further used to indicate that the terminal device supports control plane optimization, or in other words, the first message is further used to indicate that the terminal device has applied control plane optimization. Control plane optimization refers to supporting the transmission of user data through the control plane, such as transmitting user data through NAS messages, without needing to transmit user data through the user plane after establishing a user plane connection. In some embodiments, control plane optimization may also be referred to as CP CIoT (Control Plane CIoT) optimization, or other equivalent names may be used.

[0117] In some embodiments, the first message is sent directly from the terminal device to the mobility management network element. Alternatively, the first message is sent from the terminal device to the access network device, which then forwards it to the mobility management network element; that is, the mobility management network element receives the first message forwarded by the access network device, which was originally sent by the terminal device to the access network device. Alternatively, the first message is sent from the terminal device to the first core network element, which then forwards it to the mobility management network element. In other words, the embodiments of this application do not limit the transmission path of the first message to the mobility management network element, but the scope of protection of the embodiments of this application is not limited thereto.

[0118] In some embodiments, emergency services may also be referred to as emergency operations or other equivalent names. Emergency services refer to communication services provided to terminal devices in emergency situations, such as emergency calls and emergency text messages. For example, an emergency call refers to a voice or video call initiated by a terminal device in an emergency. Emergency calls include dialing emergency numbers such as 112, 110, 119, and 120 to report an emergency or request for help. It should be understood that the aforementioned 112, 110, 119, and 120 can be referred to as emergency service numbers, which can be agreed upon by an agreement or stipulated by the regulations of different countries. Emergency text messages refer to information sent using a terminal device in an emergency. The target of emergency text messages is usually also an emergency service number. For details regarding emergency services, please refer to the above introduction to "emergency services," which will not be repeated here.

[0119] In some embodiments, the first message is used to request emergency services, which can be achieved by carrying a first instruction, a first flag, an emergency instruction, an emergency flag, an emergency service instruction, an emergency service flag, a request type, etc., in the first message. The first instruction and / or the first flag is used to indicate emergency services. Alternatively, the first message can be implemented using a first format, which is the message format corresponding to emergency services. Optionally, there may also be message formats corresponding to normal services (or ordinary services, non-emergency services, etc.). The first format is different from the second format. That is, this application does not limit the instruction method of the first message.

[0120] In some embodiments, the first message is used to indicate that the terminal device supports control plane optimization. This can be achieved by carrying a control plane optimization instruction, a second instruction, or other similar means in the first message; alternatively, the first message can use a third format, which is a message format that supports control plane optimization. Optionally, a fourth format, which is a message format that does not support control plane optimization, may also exist. The third and fourth formats are different.

[0121] In some alternative embodiments, the first message indicates the needs and / or capabilities of the terminal device through different indications, flags, etc. For example, the first message includes a request type and control plane optimization indication.

[0122] In some alternative embodiments, the first message indicates the terminal device's needs and / or capabilities through a message format. For example, there may be a message format that simultaneously indicates emergency service and support for control plane optimization, or a message format that simultaneously indicates emergency service and lack of support for control plane optimization, or a message format that simultaneously indicates normal service and support for control plane optimization, or a message format that simultaneously indicates normal service and lack of support for control plane optimization.

[0123] Step 220: Based on the first message, send a second message to the access network device. The second message is used to indicate that the terminal device has requested emergency services and to request the access network device to set a first priority for the terminal device. The first priority corresponds to the emergency services.

[0124] Based on the first message sent by the terminal device, the mobility management network element determines whether a second message needs to be sent to the access network device. For example, if the first message requests emergency service and instructs the terminal device to support control plane optimization, a second message is sent to the access network device.

[0125] Furthermore, the second message is used to instruct the terminal device to request emergency services and to request the access network device to set a first priority for the terminal device; or, in other words, the second message is used to instruct the terminal device to request emergency services, and the access network device should set the first priority corresponding to the emergency service for the terminal device; or, in still other words, the second message is used to request emergency services for the terminal device, and the access network device should set the first priority corresponding to the emergency service for the terminal device, thereby providing emergency services to the terminal device.

[0126] In some embodiments, the second message is used to indicate that the terminal device has requested emergency services, and / or, the second message is used to request the access network device to set a first priority for the terminal device. For example, the second message is used to indicate that the terminal device has requested emergency services; or, the second message is used to request the access network device to set a first priority for the terminal device; or, the second message is used to indicate that the terminal device has requested emergency services and to request the access network device to set a first priority for the terminal device.

[0127] In some embodiments, if the first message requests emergency service and indicates that the terminal device does not support control plane optimization, the second message is not sent to the access network device.

[0128] In some embodiments, if the first message does not request emergency service and indicates that the terminal device supports control plane optimization, the second message is not sent to the access network device. Alternatively, if the first message does not request emergency service and indicates that the terminal device supports control plane optimization, the second message is sent to the access network device.

[0129] In some embodiments, if the first message does not request emergency services and indicates that the terminal device does not support control plane optimization, a second message is not sent to the access network device.

[0130] In some embodiments, the mobility management network element determines whether it needs to send a second message to the access network device based on a first message sent by the terminal device and the capabilities of the mobility management network element. For example, if the first message requests emergency services and indicates that the terminal device supports control plane optimization, and the mobility management network element also supports control plane optimization, then the mobility management network element sends a second message to the access network device.

[0131] In some embodiments, the first priority is the highest priority. Alternatively, the first priority is a priority higher than a priority threshold; wherein the priority threshold is agreed upon by a protocol, or pre-agreed upon by the mobility management network element and the access network equipment, or pre-agreed upon by other core network elements and the access network equipment. Alternatively, the first priority is a priority within a first interval; wherein the first interval is agreed upon by a protocol, or pre-agreed upon by the mobility management network element and the access network equipment, or pre-agreed upon by other core network elements and the access network equipment; for example, the priority value range agreed upon by the protocol is 1-15, the first interval is 1-8, and the first interval is used for priority services, which include emergency services and other services. These priority services can be agreed upon by a protocol or set by the operator; this application embodiment does not limit this.

[0132] In some embodiments, the first priority is higher than the second priority, where the second priority is the priority corresponding to normal services, or in other words, the second priority is the priority corresponding to non-urgent services.

[0133] In summary, the method provided in this application illustrates that when a terminal device requests emergency services, a mobility management network element sends a second message to an access network device based on a first message from the terminal device, instructing the access network device to set a first priority for the terminal device, whereby the first priority corresponds to the emergency service. This enables the access network device to set a priority for the terminal device, thereby providing fast and reliable emergency services to the terminal device requesting emergency services.

[0134] Furthermore, with control plane optimization applied, the mobility management element determines and instructs the access network device to set a first priority for the terminal device requesting emergency service. This prevents the access network device from failing to prioritize the terminal device due to a lack of user plane connection established with it caused by control plane optimization, thus avoiding emergency service failure because the terminal device cannot obtain resources to transmit emergency services. In other words, by sending a second message to the access network device based on the terminal device's first message, the mobility management element ensures that the access network device can still set a priority for the terminal device even without a user plane connection. This guarantees that the access network device will allocate resources to the terminal device according to the first priority, allowing the terminal device's emergency service to be transmitted using the resources allocated by the access network device, improving the priority transmission and reliability of emergency services.

[0135] Figure 6 illustrates a flowchart of a priority setting method for emergency services provided in an exemplary embodiment of this application. The method is performed by an access network device. The method includes:

[0136] Step 310: Receive a second message sent by the mobility management network element. The second message is used to indicate that the terminal device has requested emergency services and requests the access network device to set a first priority for the terminal device. The first priority corresponds to the emergency services.

[0137] In this process, the terminal device requests emergency services from the mobility management network element via the first message.

[0138] The first message is used to request emergency services, or in other words, the first message is used to instruct the terminal device to request emergency services, or in other words, the first message is used to instruct the terminal device to request the network device to provide emergency services.

[0139] In some embodiments, the first message is further used to indicate that the terminal device supports control plane optimization, or in other words, the first message is further used to indicate that the terminal device has applied control plane optimization. Control plane optimization refers to supporting the transmission of user data through the control plane, such as transmitting user data through NAS messages, without needing to transmit user data through the user plane after establishing a user plane connection. In some embodiments, control plane optimization may also be referred to as CP CIoT (Control Plane CIoT) optimization, or other equivalent names may be used.

[0140] In some embodiments, the first message is used to request emergency services, and / or the first message is used to instruct the terminal device to support control plane optimization. For example, the first message is used to request emergency services; or, the first message is used to instruct the terminal device to support control plane optimization; or, the first message is used to instruct the request for emergency services and to instruct the terminal device to support control plane optimization.

[0141] In some embodiments, the first message is sent directly from the terminal device to the mobility management network element. Alternatively, the first message is sent from the terminal device to the access network device, which then forwards it to the mobility management network element; that is, the mobility management network element receives the first message forwarded by the access network device, which was originally sent by the terminal device to the access network device. Alternatively, the first message is sent from the terminal device to the first core network element, which then forwards it to the mobility management network element. In other words, the embodiments of this application do not limit the transmission path of the first message to the mobility management network element, but the scope of protection of the embodiments of this application is not limited thereto.

[0142] In some embodiments, emergency services may also be referred to as emergency operations or other equivalent names. Emergency services refer to communication services provided to terminal devices in emergency situations, such as emergency calls and emergency text messages. For example, an emergency call refers to a voice or video call initiated by a terminal device in an emergency. Emergency calls include dialing emergency numbers such as 112, 110, 119, and 120 to report an emergency or request for help. It should be understood that the aforementioned 112, 110, 119, and 120 can be referred to as emergency service numbers, which can be agreed upon by an agreement or stipulated by the regulations of different countries. Emergency text messages refer to information sent using a terminal device in an emergency. The target of emergency text messages is usually also an emergency service number. For details regarding emergency services, please refer to the above introduction to "emergency services," which will not be repeated here.

[0143] In some embodiments, the first message is used to request emergency services, which can be achieved by carrying a first instruction, a first flag, an emergency instruction, an emergency flag, an emergency service instruction, an emergency service flag, a request type, etc., in the first message. The first instruction and / or the first flag is used to indicate emergency services. Alternatively, the first message can be implemented using a first format, which is the message format corresponding to emergency services. Optionally, there may also be message formats corresponding to normal services (or ordinary services, non-emergency services, etc.). The first format is different from the second format. That is, this application does not limit the instruction method of the first message.

[0144] In some embodiments, the first message is used to indicate that the terminal device supports control plane optimization. This can be achieved by carrying a control plane optimization instruction, a second instruction, or other similar means in the first message; alternatively, the first message can use a third format, which is a message format that supports control plane optimization. Optionally, a fourth format, which is a message format that does not support control plane optimization, may also exist. The third and fourth formats are different.

[0145] In some alternative embodiments, the first message indicates the needs and / or capabilities of the terminal device through different indications, flags, etc. For example, the first message includes a request type and control plane optimization indication.

[0146] In some alternative embodiments, the first message indicates the terminal device's needs and / or capabilities through a message format. For example, there may be a message format that simultaneously indicates emergency service and support for control plane optimization, or a message format that simultaneously indicates emergency service and lack of support for control plane optimization, or a message format that simultaneously indicates normal service and support for control plane optimization, or a message format that simultaneously indicates normal service and lack of support for control plane optimization.

[0147] The second message is used to instruct the terminal device to request emergency services and to request the access network device to set a first priority for the terminal device; or, in other words, the second message is used to instruct the terminal device to request emergency services, and the access network device should set the first priority corresponding to the emergency service for the terminal device; or, in still others, the second message is used to request emergency services for the terminal device, and the access network device should set the first priority corresponding to the emergency service for the terminal device, thereby providing emergency services to the terminal device.

[0148] In some embodiments, the second message is used to indicate that the terminal device has requested emergency services, and / or, the second message is used to request the access network device to set a first priority for the terminal device. For example, the second message is used to indicate that the terminal device has requested emergency services; or, the second message is used to request the access network device to set a first priority for the terminal device; or, the second message is used to indicate that the terminal device has requested emergency services and to request the access network device to set a first priority for the terminal device.

[0149] Step 320: Based on the second message, set the first priority for the terminal device.

[0150] In some embodiments, the first priority is the highest priority. Alternatively, the first priority is a priority higher than a priority threshold; wherein the priority threshold is agreed upon by a protocol, or pre-agreed upon by the mobility management network element and the access network equipment, or pre-agreed upon by other core network elements and the access network equipment. Alternatively, the first priority is a priority within a first interval; wherein the first interval is agreed upon by a protocol, or pre-agreed upon by the mobility management network element and the access network equipment, or pre-agreed upon by other core network elements and the access network equipment; for example, the priority value range agreed upon by the protocol is 1-15, the first interval is 1-8, and the first interval is used for priority services, which include emergency services and other services. These priority services can be agreed upon by a protocol or set by the operator; this application embodiment does not limit this.

[0151] In some embodiments, the first priority is higher than the second priority, where the second priority is the priority corresponding to normal services, or in other words, the second priority is the priority corresponding to non-urgent services.

[0152] In summary, the method provided in this application embodiment illustrates that when a terminal device requests emergency services, the mobility management network element sends a second message to the access network device based on a first message from the terminal device, instructing the access network device to set a first priority for the terminal device, whereby the first priority corresponds to the emergency service. This enables the access network device to set a priority for the terminal device.

[0153] Furthermore, with control plane optimization applied, the mobility management element determines and instructs the access network device to set a first priority for the terminal device requesting emergency service. This prevents the access network device from failing to prioritize the terminal device due to a lack of user plane connection established with it caused by control plane optimization, thus avoiding emergency service failure because the terminal device cannot obtain resources to transmit emergency services. In other words, by sending a second message to the access network device based on the terminal device's first message, the mobility management element ensures that the access network device can still set a priority for the terminal device even without a user plane connection. This guarantees that the access network device will allocate resources to the terminal device according to the first priority, allowing the terminal device's emergency service to be transmitted using the resources allocated by the access network device, improving the priority transmission and reliability of emergency services.

[0154] The first and second messages shown above will be described in detail below.

[0155] 1. First News

[0156] In some embodiments, the first message includes one or more of the following messages: Attach Request; Service Request; Control Plane Service Request; TAU Request; Registration Request; PDU (Protocol Data Unit) Session Establishment Request; PDU Session Modification Request; PDN Connection Establishment Request; PDN Connection Modification Request.

[0157] In some embodiments, the first message is used to instruct a terminal device that supports control plane optimization to request emergency services.

[0158] In some embodiments, the first message may be referred to as an emergency service request message, an emergency service message, or other equivalent names.

[0159] In some embodiments, the first message includes a control plane service request; the control plane service request includes the following parameters: service type, which is used to indicate that the terminal device requests emergency services.

[0160] In some embodiments, the service type includes one or more of emergency service, emergency service fallback, high-priority access, signaling service, data service, and mobile terminal service. In the embodiments of this application, the first message is used to request emergency service; therefore, the service type is typically emergency service. However, in other embodiments, an additional service type can be set for scenarios where application control plane optimization is applied and emergency service is requested. This attached type is used to instruct the terminal device applying control plane optimization to request emergency service, or to instruct emergency service under control plane optimization scenarios.

[0161] In some embodiments, the first message includes an attach request; the attach request includes one or more of the following parameters: terminal device identifier; attach type, which indicates that the terminal device requests emergency services; support for control plane optimization, which indicates that the terminal device supports control plane optimization; and SM (Session Management) container, which indicates that a PDN connection is established for the terminal device.

[0162] In some embodiments, the attachment type includes one or more of the following: initial attachment, mobility registration update, periodic registration update, emergency attachment, and SNPN (Stand-alone Non-Public Network) network entry attachment. In the embodiments of this application, the first message, i.e., the attachment request, is used to request emergency services; therefore, the attachment type is typically emergency attachment. However, in other embodiments, an additional attachment type can be set for scenarios where control plane optimization is applied and emergency services are requested. This attachment type is used to indicate that the terminal device applying control plane optimization is requesting emergency services, or to indicate emergency services under control plane optimization scenarios. The embodiments of this application do not limit this, but the scope of protection of the embodiments of this application is not limited thereto.

[0163] In some embodiments, the support for control plane optimization is used to indicate whether the terminal device supports control plane optimization. In this application embodiment, the support for control plane optimization parameter in the first message is used to indicate that the terminal device supports control plane optimization. For example, the value of the support for control plane optimization parameter is either "0" or "1". For instance, the protocol stipulates that when the value of the support for control plane optimization parameter is "1", it indicates that the terminal device supports control plane optimization; when the value of the support for control plane optimization parameter is "0", it indicates that the terminal device does not support control plane optimization. It should be noted that this application embodiment does not limit the relationship between the values ​​of each parameter and their specific meanings, but the protection scope of this application embodiment is not limited thereto. Taking the support for control plane optimization parameter as an example, for the support for control plane optimization parameter, it is also possible that when the value of the control plane optimization parameter is "1", it indicates that the terminal device does not support control plane optimization; and when the value of the control plane optimization parameter is "0", it indicates that the terminal device supports control plane optimization.

[0164] In some embodiments, the SM container may be called an SM message container, an ESM (EPS Session Management) container, or an ESM message container, or other equivalent names. The SM container is used to indicate the establishment of a PDN connection for the terminal device, or in other words, the SM container carries configuration information for establishing a PDN connection, or it can be said that the SM container carries configuration information related to the PDN connection. In an EPS network, the Mobility Management Element (MME) is responsible not only for the terminal device's attach procedure but also for the terminal device's session establishment and modification procedures. That is, the terminal device can carry the SM container in the first message (i.e., the attach request), so that after receiving the attach request, the Mobility Management Element, in addition to completing the attach procedure, must also complete the PDN establishment procedure. In other embodiments, the SM container may not be carried in the attach request; instead, after sending the attach request and completing the attach procedure, a PDN establishment request is sent to establish a PDN connection.

[0165] In some embodiments, the SM container includes one or more of the following parameters: request type, which indicates that the type of request from the terminal device is an emergency service; PDN type; encryption option transmission flag, which indicates that encryption options are transmitted, including APN.

[0166] In some embodiments, the request type includes a request type corresponding to an emergency service, such as a request type value of "emergency service" or "instruction information corresponding to an emergency service." It should be understood that the request type here can also be an additional request type, i.e., used to instruct emergency services in control plane optimization scenarios. This application embodiment does not limit this.

[0167] In some embodiments, the PDN type includes one or more of IPv4, IPv6, IPv4v6, Non-IP, and Ethernet.

[0168] In some embodiments, the Ciphered Options Transfer Flag is used to indicate whether encrypted options are transmitted. Encrypted options include APN. Optionally, encrypted options also include PCO (Protocol Configuration Options). When a terminal device expects to transmit encrypted options to a mobility management network element, the terminal device should set the Ciphered Options Transfer Flag to transmit encrypted options in the SM container; the mobility management network element can then determine, based on this Ciphered Options Transfer Flag, whether it should set the encrypted options itself or obtain the encrypted options from the terminal device while ensuring network security. Network security includes authentication and NAS security settings for the terminal device already completed in the core network.

[0169] In summary, the method illustrated in the embodiments of this application demonstrates relevant information for a first message used to request emergency services. The first message can be an attach request, registration request, service request, control plane service request, etc., meaning it supports emergency service requests from terminal devices with control plane optimization in various scenarios, ensuring the comprehensiveness of application scenarios for terminal devices requesting emergency services and guaranteeing the provision of emergency services to terminal devices in different scenarios.

[0170] 2. Determining APN / DNN

[0171] When the first message is another message, such as a registration request, service request, control plane service request, PDU establishment request, or PDU modification request, the encryption option also includes a DNN. Here, the APN is used to identify the PDN, and the DNN is used to identify the DN; that is, both the APN and DNN are used to identify the external data network (relative to the operator), such as the Internet or a private enterprise network. The DNN is also used to select the SMF and UPF and determine the policy applied to that data network. If the terminal device wishes to use its own provided APN or DNN instead of being selected by the mobility management element (MLE), it should instruct the MLE so that the MLE can obtain the encryption option from the terminal device while ensuring network security. However, in some embodiments, the MLE may select the APN or DNN for the terminal device based on some configuration information. After determining the APN or DNN, a connection with the PDN or a PDU session can be established, thereby enabling information exchange between the UE and the external data network. The details are as follows.

[0172] In some embodiments, encryption options refer to parameters that need to be transmitted encrypted. Encryption options include APN and / or DNN.

[0173] In some embodiments, the method further includes: the mobility management network element determining an APN or DNN based on a first configuration, wherein the APN or DNN is used for emergency services; and / or, upon meeting a first condition, obtaining an APN or DNN from a terminal device, wherein the APN or DNN is used for emergency services; wherein the first condition includes one or more of the following conditions: authentication completed; NAS security settings completed.

[0174] In some embodiments, the mobility management network element determines an APN or a DNN based on a first configuration; it can also be understood that the mobility management network element determines an APN or a DNN for emergency services based on the first configuration; further, it can be understood that the mobility management network element determines an emergency APN or an emergency DNN based on the first configuration. Alternatively, the mobility management network element determines a network access identifier based on the first configuration, the network access identifier being used to identify an external data network. The network access identifier includes an APN and / or a DNN; it can also be understood that the mobility management network element determines a network access identifier for emergency services based on the first configuration; further, it can be understood that the mobility management network element determines an emergency network access identifier based on the first configuration. It should be understood that the determination of the aforementioned APN for emergency services, DNN for emergency services, emergency APN, emergency DNN, network access identifier for emergency services, and emergency network access identifier, etc., is all for the purpose of establishing corresponding emergency PDN connections or emergency PDU sessions, thereby enabling the provision of emergency services to terminal devices.

[0175] In some embodiments, the first configuration includes one or more of MME Emergency Configuration Data and AMF Emergency Configuration Data. For example, when the Mobility Management Network (MMN) determines the APN, the first configuration may be MME Emergency Configuration Data; when the MMN determines the DNN, the first configuration may be AMF Emergency Configuration Data. The aforementioned MME Emergency Configuration Data and / or AMF Emergency Configuration Data can be collectively referred to as emergency configuration data. The specific information contained therein may be agreed upon by a protocol or set by the operator according to specific regulations; this application embodiment does not limit this.

[0176] In some embodiments, when the first configuration indicates multiple APNs or DNNs, the mobility management network element selects the APN or DNN with the highest priority from the multiple APNs or DNNs indicated by the first configuration, such as the first APN or the first DNN. When the access network device needs to obtain QoS parameters, the QoS parameters corresponding to the first APN or the first DNN are sent to the access network device.

[0177] In some embodiments, the mobility management network element obtains an APN or DNN from the terminal device when a first condition is met; it can also be understood that the mobility management network element obtains an APN or DNN for emergency services from the terminal device when the first condition is met; further, it can be understood that the mobility management network element obtains an emergency APN or emergency DNN from the terminal device when the first condition is met. Alternatively, the mobility management network element obtains a network access identifier from the terminal device when the first condition is met, the network access identifier including an APN and / or DNN; it can also be understood that the mobility management network element obtains a network access identifier for emergency services from the terminal device when the first condition is met; further, it can be understood that the mobility management network element obtains an emergency network access identifier from the terminal device when the first condition is met.

[0178] In some embodiments, the first condition includes authentication completion; or, the first condition includes NAS security setup completion; or, the first condition includes both authentication completion and NAS security setup completion.

[0179] For example, the mobility management network element obtains the APN or DNN from the terminal device after authentication and NAS security settings are completed; it can also be understood that the mobility management network element obtains the APN or DNN for emergency services from the terminal device after authentication and NAS security settings are completed; and it can also be understood that the mobility management network element obtains the emergency APN or emergency DNN from the terminal device after authentication and NAS security settings are completed.

[0180] In some embodiments, obtaining the APN or DNN from the terminal device can be achieved by the mobility management network element sending a request or notification to the terminal device to inform the terminal device to report the APN or DNN; alternatively, the mobility management network element can send a notification to the terminal device after confirming that authentication and / or NAS security settings are complete. This notification indicates that authentication and / or NAS security settings are complete, and the terminal device reports the APN or DNN upon confirming that a first condition is met. The terminal device can report the APN or DNN using a separate message for reporting the APN or DNN, or it can include information elements indicating the APN or DNN in a message, as is common in related technologies, such as in a PDU session establishment request. This application does not limit the method by which the mobility management network element obtains the APN or DNN from the terminal device, but the scope of protection of this application is not limited thereto.

[0181] In summary, the method provided in this application embodiment illustrates the determination of APN and / or DNN, namely, that the mobility management network element determines or obtains the APN and / or DNN from the terminal device according to the first configuration, thereby ensuring the acquisition of APN and / or DNN for emergency services, and thus realizing the establishment of emergency PDN connection and / or emergency PDU session.

[0182] 3. Second message

[0183] In some embodiments, the second message is used to instruct the access network device to reserve resources for emergency services of the terminal device; or, the second message is used to instruct the access network device to prioritize the allocation of resources to the terminal device for the transmission of emergency service data. Alternatively, the first priority is used to instruct the access network device to reserve resources for emergency services of the terminal device; or, the first priority is used to instruct the access network device to prioritize the allocation of resources to the terminal device for the transmission of emergency service data.

[0184] In some embodiments, the second message is a priority allocation message, a priority setting message, a priority indication message, a priority allocation message for emergency services, a priority setting message for emergency services, a priority indication message for emergency services, or other equivalent names.

[0185] In some embodiments, the access network device selects a first terminal device from at least two terminal devices based on a second message to allocate resources preferentially. The first terminal device is the terminal device requesting emergency service indicated by the second message. That is, the access network device allocates resources among at least two terminal devices according to the priority of each terminal device.

[0186] For example, when the access network device sets the terminal device to have the highest priority, the access network device will prioritize establishing an SRB for the terminal device. The SRB is used by the terminal device to transmit user data.

[0187] In some embodiments, the second message includes one or more of the following messages: Initial Context Setup Request; UE Information Transfer message. In other embodiments, the second message may also be other messages, such as messages for providing QoS parameters or priorities or other priority-related parameters, and this application embodiment does not limit this.

[0188] In some embodiments, the second message includes one or more of the following parameters: QoS parameters, used to indicate the QoS parameters of emergency services; a first indication, used to indicate that the terminal device has requested emergency services; a priority, used to indicate that the priority assigned to the terminal device by the mobility management network element is the first priority; an ARP, used to indicate the ARP of the emergency service; an EPS bearer identifier, used to identify the EPS bearer of the terminal device; a terminal device identifier; an RRC connection hold indication, used to indicate that the access network device should maintain the RRC connection for the terminal device; a timer, used to indicate the hold time of the RRC connection; a control plane only indication, used to indicate that the terminal device and / or the mobility management network element only apply control plane optimization; and support for control plane optimization, used to indicate that the terminal device and / or the mobility management network element support for control plane optimization.

[0189] In some embodiments, QoS parameters may also be referred to as UE-level QoS parameters, or other equivalent names. Optionally, QoS parameters are used to determine the priority of the terminal device.

[0190] In some embodiments, QoS parameters include one or more of the following parameters: CQI (QoS Class Identifier); ARP.

[0191] In some embodiments, the first instruction may be referred to as an emergency instruction, an emergency service instruction, or other equivalent names.

[0192] In some embodiments, the priority is used to indicate the priority assigned by the mobility management network element to the terminal device. The priority in the second message is the first priority, that is, the second message is used to instruct the mobility management network element to request the access network device to set the priority of the terminal device to the first priority; or, the second message is used to instruct the mobility management network element to request the access network device to set the ARP of the terminal device to the first ARP corresponding to the first priority, for example, the first priority corresponds to the priority level in the first ARP.

[0193] In some embodiments, the ARP is used to indicate the ARP for emergency services. This ARP may be reserved by the mobility management network element for emergency services, such as when the mobility management network element reserves at least one ARP for emergency services (or priority services), and the second message carries one of these at least one ARPs. Alternatively, the ARP may be agreed upon by a protocol, such as when the protocol stipulates that at least one ARP is used for emergency services (or priority services).

[0194] In some embodiments, the EPS bearer identifier is used to identify the EPS bearer of the terminal device.

[0195] In some embodiments, the terminal device identifier is used to identify the terminal device.

[0196] In some embodiments, the terminal device identifier includes one or more of the following parameters: IMSI; GUTI (Globally Unique Temporary Identity); IMEI; 5G-GUTI; SUCI (Subscription Concealed Identifier); SUPI (Subscription Identifier).

[0197] In some embodiments, the RRC connection hold indication is used to indicate that the access network device should maintain the RRC connection for the terminal device.

[0198] In some embodiments, the timer is used to indicate the hold time of the RRC connection. It can also be understood that the access network device ensures that it is in an RRC connection state with the terminal device before the timer expires. After the timer expires, the RRC connection state can be modified according to the network conditions.

[0199] In some embodiments, the second message is an initial context request. The initial context request includes one or more of the following parameters: QoS parameters, used to indicate the QoS parameters for emergency services; a first indication, used to indicate that the terminal device has requested emergency services; a priority, used to indicate that the mobility management network element has assigned the terminal device a first priority; an ARP, used to indicate the ARP for emergency services; an EPS bearer identifier, used to identify the EPS bearer of the terminal device; a terminal device identifier; an RRC connection hold indication, used to indicate that the access network device should maintain an RRC connection for the terminal device; a timer, used to indicate the hold time for the RRC connection; a control plane only indication, used to indicate that the terminal device and / or the mobility management network element only apply control plane optimization; and support for control plane optimization, used to indicate that the terminal device and / or the mobility management network element support for control plane optimization.

[0200] In some embodiments, the second message is a UE information transmission. The UE information transmission includes one or more of the following parameters: message type; QoS parameters, which are used to indicate the QoS parameters of emergency services; UE radio capabilities; NB-IoT UE priority; subscription-based UE differentiation information; pending data indication; and IMEISV (International Mobile Equipment Identity and Software Version Number) mask.

[0201] In summary, the method provided in this application embodiment illustrates relevant information about the second message. The second message is used by the mobility management network element to allocate a first priority to the terminal device from the access network device. This enables the access network device to prioritize allocating resources to terminal devices requesting emergency services to ensure the normal transmission of emergency services. Furthermore, due to the application of control plane optimization—that is, the transmission of emergency service data does not need to go through the user plane but can be directly transmitted through the control plane—signaling resources for establishing the user plane and energy consumption for the terminal device to establish the user plane are saved, allowing the terminal device to use emergency services with lower energy consumption.

[0202] In some embodiments, after the access network device completes the priority setting for the terminal device, it can notify the mobility management network element via a message. The specifics are as follows.

[0203] 4. Other news

[0204] In some embodiments, the method further includes: a mobility management network element receiving a third message sent by an access network device, the third message being used to instruct the access network device to set a first priority for emergency services for the terminal device.

[0205] In some embodiments, the method further includes: the access network device sending a third message to the mobility management network element, the third message being used to instruct the access network device to set a first priority for emergency services for the terminal device.

[0206] In some embodiments, the third message is a response to the second message. For example, the second message is an initial context establishment request, and the third message is an initial context establishment response. Alternatively, the second message may be a UE information transmission, and the third message may be a UE information transmission response.

[0207] In some embodiments, the third message is a priority allocation completion message, a priority setting completion message, a priority allocation completion message for emergency services, a priority setting completion message for emergency services, or other equivalent names.

[0208] In this method, a third message is used to indicate to the access network device that the terminal device has been set to the first priority, thereby ensuring the normal transmission of emergency service data for subsequent emergency services.

[0209] In addition, after the emergency service ends, the mobility management network element should also notify the access network equipment to adjust the priority of the terminal equipment, as shown below.

[0210] In some embodiments, the method further includes: a mobility management network element sending a fourth message to an access network device, the fourth message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

[0211] In some embodiments, the method further includes: the access network device receiving a fourth message sent by a mobility management network element, the fourth message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

[0212] In some embodiments, the mobility management network element sends a fourth message to the access network device when the emergency service ends or becomes inactive. For example, the mobility management network element determines whether the emergency service has ended or is no longer active based on one or more of O&M Intervention, User Inactivity, and NAS messages sent by the terminal device.

[0213] In some embodiments, the fourth message is further used to indicate the release of a transmission interface, where the transmission interface refers to the interface between the mobility management network element and the access network equipment. In some embodiments, when the fourth message indicates that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active, the fourth message may be an emergency service termination message, an emergency service suspension message, an emergency service inactive message, an termination message, an inactive message, or other equivalent names. Furthermore, when the fourth message indicates the release of a transmission interface, the fourth message may be referred to as a release message, a transmission interface release message, an S1 release message, an S1 interface release message, an NG release message, or an NG interface release message, at least one of these.

[0214] In some embodiments, the transmission interface includes: an S1 interface; and / or an NG interface.

[0215] In some embodiments, the fourth message is a context release command; the context release command includes a reason value; wherein the reason value is used to indicate that the emergency service has ended, or, the reason value is used to indicate that the emergency service is no longer active, or, the reason value is used to indicate that the user is no longer active.

[0216] In some embodiments, the fourth message includes indication information indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

[0217] In some embodiments, the access network device performs one or more of the following operations based on the fourth message: adjusts the priority of the terminal device; no longer prioritizes allocating resources to the terminal device; no longer keeps the terminal device in a connected state; and releases the RRC connection with the terminal device.

[0218] For example, adjusting the priority of a terminal device could involve changing its first priority to a second priority, where the second priority is lower than the first priority. In other words, it would lower the priority of the terminal device.

[0219] In some embodiments, the method further includes: a mobility management network element sending a fifth message, the fifth message indicating the establishment of a session, the fifth message including a control plane-only connection indication, the control plane-only connection indication indicating that the established connection uses control plane optimization.

[0220] For example, the fifth message is a session creation request. A session creation request is used to indicate the establishment of a PDN connection or PDU session. A control plane-only connection indication may also be called a control plane-only indication, control plane indication, second indication, or other equivalent names. This control plane-only connection indication is used for indication.

[0221] In some embodiments, the fifth message is a session creation message, a session creation request message, a transport connection establishment message, or other equivalent names.

[0222] For example, the MME sends a session creation request to the SGW.

[0223] In some embodiments, the method further includes: a mobility management network element sending a sixth message to a terminal device, the sixth message being used to instruct the mobility management network element to accept a first message from the terminal device; wherein the sixth message includes one or more of the following: a control plane only indicator (CP ONLY indicator), which instructs the mobility management network element to use control plane transmission; an emergency service support indicator, which instructs the mobility management network element to support emergency services; and an emergency service support for CP indicator, which instructs the mobility management network element to support emergency services on the control plane.

[0224] In some embodiments, the sixth message is a connection indication message, a control plane connection indication message, a control plane indication message, a feedback message, a feedback message of the first message, a transmission indication message, or other equivalent names.

[0225] In some embodiments, the emergency service support instruction is used to instruct mobility management network elements to support emergency services in control plane optimization scenarios.

[0226] In other embodiments, the emergency service support indication is used to instruct the mobility management network element to support emergency services. The control plane only indication is used to instruct the mobility management network element to support control plane transport. The mobility management network element may carry both the control plane only indication and emergency service support in the sixth message to instruct the network side to support emergency services in control plane optimized scenarios. Alternatively, the sixth message may carry an emergency service indication supporting the control plane to instruct the network side to support emergency services in control plane optimized scenarios.

[0227] In the context of control plane optimization, emergency services can be understood as transmitting emergency service data through the control plane, or providing emergency services through the control plane, or other equivalent descriptions. This application embodiment does not limit this interpretation. It should be understood that the various parameter names shown in this application embodiment, such as "control plane only indication," "emergency service support indication," "emergency service indication supporting the control plane," "first indication," etc., are all illustrative examples. These parameter names can be changed in actual application scenarios, and this application embodiment does not limit this interpretation.

[0228] In some embodiments, after completing the above process, i.e., setting a first priority for the terminal device, emergency service data can be transmitted via NAS messages. For example, the mobility management network element receives emergency service data sent by the terminal device, and the emergency service data is sent via NAS messages.

[0229] For example, the mobility management network element sends emergency service data to the terminal device, and the emergency service data is sent via downlink DL NAS messages.

[0230] In summary, the method illustrated in this application demonstrates several related messages in different processes. For example, the third message responds to the second message, enabling the mobility management network element to determine whether the first priority setting has been completed, thus allowing subsequent process triggering to continue. The fourth message, when detecting that the emergency service of the terminal device is inactive or has ended, instructs the access network device to adjust the priority of the terminal device, discontinue maintaining the RRC connection, etc., so that the access network device does not need to prioritize resource allocation for terminal devices that no longer require emergency service, ensuring the effective and reasonable allocation of resources by the access network device. The fifth message indicates the established session; when control plane optimization is applied, the fifth message carries a control plane-only connection indication, ensuring that the established session only supports control plane optimization, guaranteeing the classification of various sessions in the network environment, and simplifying the transmission between various network elements in the core network device and the access network device. The sixth message instructs the mobility management network element to accept the first message from the terminal device, indicating that the network-side process is basically complete. This sixth message carries relevant information about this process, such as the control plane-only indication and the emergency service support indication, used to identify transmission-related parameters of different terminal devices.

[0231] It should be noted that the "1. First Message", "2. Determination of APN / DNN", "3. Second Message", and "4. Other Messages" shown above can be implemented as independent embodiments or as combined embodiments. For example, "1. First Message" and "2. Determination of APN / DNN" can be implemented as combined embodiments; or, "1. First Message" and "3. Second Message" can be implemented as combined embodiments; or, "1. First Message" and "4. Other Messages" can be implemented as combined embodiments; or, "2. Determination of APN / DNN" and "3. Second Message" can be implemented as combined embodiments; or, "2. Determination of APN / DNN" and "4. Other Messages" can be implemented as combined embodiments; or, "3. Second Message" and "4. Other Messages" can be implemented as combined embodiments; in addition to the pairwise combinations shown above, combinations of three or four are also possible. For example, “1. First Message”, “2. Determination of APN / DNN”, and “3. Second Message” can be implemented in combination; or, “1. First Message”, “2. Determination of APN / DNN”, and “4. Other Messages” can be implemented in combination; or, “1. First Message”, “3. Second Message”, and “4. Other Messages” can be implemented in combination; or, “2. Determination of APN / DNN”, “3. Second Message”, and “4. Other Messages” can be implemented in combination; or, “1. First Message”, “2. Determination of APN / DNN”, “3. Second Message”, and “4. Other Messages” can be implemented in combination.

[0232] In some embodiments, the first message from the terminal device requesting emergency services may have multiple message types, and the second message from the mobility management network element triggering the access network device to set priorities may also have multiple message types. Therefore, the priority setting method for emergency services shown in this application embodiment has multiple combinations. The following shows some combinations of some message types. For other combinations of other message types, refer to the combinations shown below; they will not be elaborated further here.

[0233] Example 1: The first message is an attach request, the second message is an initial context request, and the mobility management element is the MME.

[0234] During the attach process, the UE requests the emergency service desk and instructs the UE to support CP CIoT optimization. After establishing a session for emergency services, the MME instructs the access network device to set the highest priority for the UE requesting emergency services. As shown in Figure 7, a UE supporting CP IoT optimization can request to establish a PDN connection for emergency services in its attach request. After establishing the session, the MME instructs the access network device to allocate high priority to this UE, so that the access network device will prioritize allocating resources to the UE requesting emergency services during admission control.

[0235] Step 601: The UE initiates an attach request.

[0236] In some embodiments, the attach request includes one or more of the following information: UE identifier, IMSI or GUTI; Attach type: Emergency, indicating that the attach type is emergency service; Support of Control Plane CIoT EPS / 5GS optimization, indicating that the UE supports CP CIoT UE; ESM container, also known as SM message container.

[0237] When the attach request includes an SM message container, it indicates that a PDN connection is being established for the UE during the attach process. The SM message container contains one or more of the following parameters: Request type: Emergency, indicating that the request type is emergency service; PDN type, indicating the requested PDN type, such as IPv4, IPv6, etc.

[0238] Step 602: The access network device forwards the attach request to the MME.

[0239] In some embodiments, the access network device selects an MME that supports emergency services and CP CIoT optimization and forwards the attach request message to the MME.

[0240] Step 603: The MME and HSS exchange a location update request / confirmation.

[0241] In some embodiments, the MME obtains the UE's subscription message from the HSS.

[0242] In some embodiments, step 603 is an optional step, meaning that an update location request / confirmation may not be performed during the attachment process.

[0243] Step 604: The MME sends a session creation request message to the SGW.

[0244] In some embodiments, the MME establishes configuration parameters for the emergency bearer based on the MME emergency configuration data.

[0245] The session creation request includes one or more of the following parameters:

[0246] -UE identifier, IMSI.

[0247] - MME Tunnel Endpoint Identifier for Control Plane; A TEID (Tunnel Endpoint Identifier) ​​is used to identify the MME in the control plane. It is typically used with the S11 interface to establish and manage tunnel PDN GW addresses between the MME and other network nodes (such as S-GW).

[0248] - PDN address, used to identify the UE's connection in the PDN, and can include an IPv4 address, an IPv6 interface identifier, or both. The MME includes this parameter in the message when the UE's subscription message includes the subscribed PDN address.

[0249] -APN; APN is used to identify an access point in a mobile network. In this embodiment, it is an emergency APN, used to select the PDN GW (Packet Data Network Gateway) that supports emergency calls.

[0250] -EPS Bearer Identity; The EPS Bearer Identity is a parameter used to uniquely identify the EPS bearer of a UE.

[0251] - QoS of the default EPS bearer; QoS parameters assigned to the default EPS, including CQI and ARP.

[0252] If control plane CIOT EPS optimization is applicable, the MME should also instruct the S11-U tunnel NAS user data and send its own S11-U IP address and MME DL TEID for the SGW to forward DL data.

[0253] -S11-U IP address; In the control plane CIoT EPS optimization, the IP address used to transmit user data between the MME and S-GW.

[0254] -MME DL TEID; is the identifier of the MME at the downlink tunnel endpoint.

[0255] - Control Plane Only PDN Connection Indicator: Indicates that the current PDN connection only applies CP CIoT optimization.

[0256] Step 605: The SGW sends a session creation request message to the PGW.

[0257] In some embodiments, the message includes one or more of the following parameters: UE identifier, IMSI; APN; Serving GW TEID of the control plane; Tunnel endpoint identifier of the Serving GW for the control plane; Default EPS Bearer QoS; PDN Type; PDN Address; EPS Bearer Identity; Control Plane Only PDN Connection Indicator.

[0258] Step 606: PCEF initiates an IP connection to the access network.

[0259] In some embodiments, if a PCC supporting emergency services is configured and a dynamic PCC is deployed, the PCRF sets the ARP in the PCC rule to the value configured for emergency services based on the emergency APN.

[0260] Step 607: PGW returns a session creation response message to SGW.

[0261] In some embodiments, the message includes one or more of the following parameters: PDN GW TEID of the control plane, the tunnel endpoint identifier of the PDN gateway on the control plane; PDN Type; PDN Address; EPS Bearer Identity; EPS Bearer QoS.

[0262] In step 608, the SGW returns a session creation response message to the MME.

[0263] In some embodiments, the message includes one or more of the following parameters: PDN Type; PDN Address; Serving GW TEID for control plane; EPS Bearer Identity; EPS Bearer QoS; and at the PDN GW, the following for uplink traffic: the PDN GW address and TEIDs corresponding to the S5 / S8 interface based on GTP, or the GRE key corresponding to the S5 / S8 interface based on PMIP.

[0264] In some embodiments, steps 604 to 608 are optional steps. For example, if the attach request does not carry an SM container, steps 604 to 608 are not executed; if the attach request carries an SM container, a session is established through steps 604 to 608.

[0265] Step 609: The MME sends an attach accept message to the access network device via downlink NAS transmission message.

[0266] In some embodiments, the attach accept message includes one or more of the following parameters: network support for CP CIoT optimization; the identifier GUTI assigned to the UE; the TAI list, the UE's registration area; a Session Management Request, including APN, PDN Type, PDN Address, EPS Bearer Identity, Protocol Configuration Options, Header Compression Configuration, Control Plane Only Indicator, and EPS Bearer QoS parameters (QCI, ARP).

[0267] In some embodiments, during the attach process initiated by the UE for emergency services, in addition to establishing a PDN connection for the emergency call, the MME also needs to instruct the access network device that the UE has requested emergency services. The access network device needs to prioritize allocating resources for emergency service transmission for this UE; therefore, the MME also needs to send an initial context establishment request to the access network device. This initial context establishment request includes one or more of the following information:

[0268] - Emergency indication is used to indicate that the current UE request is for an emergency service, such as an emergency call.

[0269] - Priority: The priority assigned to a UE, used to indicate the priority in allocating resources to this UE among multiple UEs to ensure that emergency services can be given priority in resource allocation by the access network equipment.

[0270] - ARP: The MME can also directly send ARP parameters reserved by the network for emergency services to the access network device. The access network device determines the priority of the services transmitted on the UE based on the ARP value.

[0271] -EPS bearer ID, used to identify the EPS bearer for emergency services (such as emergency calls).

[0272] -UE identifier, IMSI, GUIT and other UE identifiers.

[0273] -RRC Connection Keep Indicator: Indicates that the access network device needs to keep the UE connected to the RRC at all times, and the UE is always in the RRC connected state.

[0274] - Timer: The MME can also provide a timer to the access network device, which ensures that the access network device is in the RRC connected state with the UE before the timer expires.

[0275] - Control Plane Only Indicator: Indicates that the UE has only applied CP CIoT optimization.

[0276] - Supports control plane optimization: Indicates that the UE has applied CP CIoT optimization.

[0277] Step 610: The access network device sends the received attach accept message to the UE.

[0278] In some embodiments, the access network device sets a priority for the UE based on the indication of the received Initial Context Establishment Request, ensuring that resources are allocated to the UE to establish an SRB first, and ensuring that the UE remains connected and does not release the RRC connection with the UE before receiving a notification that the emergency service has ended, so that the service data of the emergency service can be delivered to the UE and the network in a timely manner.

[0279] Step 611: The access network device sends an initial context response message to the MME.

[0280] In some embodiments, the initial context response message is used to confirm that the access network device has configured the corresponding priority for emergency service transmission for the UE, and may also include the TEID and address information of the access network device.

[0281] Step 612: The UE sends an attach complete message to the access network device.

[0282] In some embodiments, the attach complete message includes one or more of the following information: EPS Bearer Identity; NAS sequence number: used to ensure the integrity, confidentiality and sequential delivery of NAS messages; NAS-MAC (Message Authentication Code for NAS) used to verify the integrity of NAS messages.

[0283] Step 613: The access network device forwards the attach complete message to the MME.

[0284] Subsequently, the UE can send emergency service data (NAS data PDU) to the MME via NAS messages. After the MME performs decryption and integrity protection verification, it sends the received data to the SGW, which then forwards it to the PGW. Downlink emergency service data is sent from the PGW to the SGW, which then sends it to the MME. The MME performs data encryption and integrity protection before sending it to the UE via DL NAS messages.

[0285] Example 2: The first message is a control plane service request, the second message is an initial context establishment request, and the mobility management element is the MME.

[0286] During the control plane service request process, the UE requests to establish a PDN connection corresponding to the emergency service. The MME instructs the eNB to set the highest priority for the UE requesting the emergency service. As shown in Figure 8, a UE with CP CIoT optimization can send a control plane service request to request the establishment of a connection for sending emergency services. The control plane service request can be initiated by the UE for a calling emergency call (MO emergency call) or initiated by the UE in response to a paging message for a called emergency call (MT emergency call).

[0287] Step 701: The UE sends a control plane service request to the access network device.

[0288] In some embodiments, the control plane service request message carries one or more of the following parameters:

[0289] - Service type: Emergency service, used to indicate that the control plane service request requests to establish a connection for emergency service.

[0290] -ESM message container.

[0291] In some embodiments, the ESM message container includes one or more of the following parameters: header compression configuration; Control Plane Only Indicator: the UE only applies CP CIoT optimization; ESM DATA TRANSPORT: carries user data.

[0292] Step 702: The access network device forwards the received control plane service request to the MME.

[0293] Step 703: The MME and UE perform authentication and security procedures.

[0294] In some embodiments, the MME determines whether emergency services and CP CIoT optimization are supported based on the UE subscription message and network capabilities. If supported, the MME indicates to the access network device that the UE has requested the transmission of emergency service data in the control plane, and that a higher priority needs to be set for it so that the base station can allocate resources for emergency services first. This instruction can be sent to the access network device in the initial context setup request message.

[0295] In some embodiments, step 703 is optional; that is, authentication and security procedures may or may not be performed.

[0296] Step 704: The MME sends an initial context establishment request to the access network device.

[0297] In some embodiments, the initial context establishment request specifically includes one or more of the following parameters:

[0298] -emergency service indication: Used to indicate that the current UE request is an emergency service, such as an emergency call.

[0299] -Priority, the priority assigned to the UE, is used to indicate the priority allocation of resources for this UE among multiple UEs to ensure that emergency services can be given priority in resource allocation by the access network equipment.

[0300] - ARP: The MME can also directly send the ARP parameters reserved by the network for emergency services to the access network device. The access network device determines the priority of the services transmitted on the UE based on the ARP value.

[0301] -EPS bearer ID, used to identify the EPS bearer for emergency services (emergency calls).

[0302] -UE identifier, IMSI, GUIT and other UE identifiers.

[0303] -RRC Connection Keep Indicator: Indicates that the access network device needs to keep the UE connected to the RRC at all times, and the UE is always in the RRC connected state.

[0304] -Timer: The MME can also provide a timer to the access network device, which will ensure that the access network device is in the RRC connected state with the UE before the timer expires.

[0305] -Control Plane Only Indicator: Indicates that only CP CIoT optimization has been applied to the UE.

[0306] - Support of CP CIoT optimization: Indicates that the UE has applied CP CIoT optimization.

[0307] Step 705: The MME sends a Modify Bearer Request to the SGW.

[0308] In some embodiments, if an S11-U is not established between the MME and the SGW, the MME sends a Modify Bearer Request to the SGW for each PDN connection that has applied CIoT CP optimization. The Modify Bearer Request includes one or more of the following parameters: MME address; MME TEID DL.

[0309] Step 706: The SGW sends a Modify Bearer Request to the PGW.

[0310] In some embodiments, if the RAT type or UE location changes, the SGW sends a Modify Bearer Request to the PGW, and the message includes the RAT type.

[0311] Step 707: PCEF initiates an IP connection to access the network.

[0312] If a PCC that supports emergency services is configured and a dynamic PCC is deployed, the PCRF will set the ARP in the PCC rule to the value configured for emergency services based on the emergency APN.

[0313] Step 708: PGW sends a modified bearer response to SGW.

[0314] Step 709: The SGW sends a modified bearer response to the MME.

[0315] In some embodiments, the modified bearer response message includes one or more of the Serving GW address and Serving GW TEID corresponding to S11-U for uplink data transmission.

[0316] Subsequently, the SGW can send the DL data to the MME, which performs integrity verification and encryption, and then sends the DL data to the UE in a downlink NAS message. The UE can then send a NAS PDU containing user data to the access network device in a subsequent UL RRC message. The access network device sends the NAS data PDU to the MME. The MME performs integrity verification and decryption, and then sends it to the SGW and PGW.

[0317] In some embodiments, steps 705 to 709 are optional steps. If S11-U between MME and SGW has been established, it is not necessary to perform steps 705 to 709 to modify the bearer.

[0318] Example 3: The first message is an attach request, the second message is UE information transmission, and the mobility management network element is the MME.

[0319] For example, as shown in Figure 9.

[0320] Step 801: The UE initiates an attach request.

[0321] If a UE needs to perform emergency services, it can initiate the attach procedure by sending an attach request message to the access network device. The UE will indicate its support for CP CIoT EPS optimization in its preferred network behavior. If the attach request includes an ESM message container, the UE should set the request type to "Emergency" in the attach request. If it does not include an ESM message container, steps 805 to 809 are not executed. That is, steps 805 to 809 below are optional.

[0322] Step 802: The access network device forwards the attach request to the MME.

[0323] For example, the access network device forwards the attach request message to the mobility management entity (MME) in accordance with Clause 5.3.2.1 of TS23.401[5].

[0324] Step 803: The MME and UE perform authentication and security procedures.

[0325] In some embodiments, the authentication and non-access stratum (NAS) security setup process is performed in accordance with Section 5.3.2.1 of TS23.401[5].

[0326] In some embodiments, step 803 above is an optional step, that is, authentication and security processes can be performed or not.

[0327] Step 804: The MME and HSS exchange a location update request / confirmation.

[0328] In some embodiments, the MME may obtain the UE's subscription context information from the HSS. If the MME is not configured to support emergency services, or if the MME only supports user plane CIoT EPS optimization functions, the MME should reject the attach request.

[0329] In some embodiments, step 804 is an optional step; that is, an update location request / acknowledgment may or may not be performed. In step 805, the MME sends a create session request message to the SGW.

[0330] In some embodiments, for emergency attach, the MME applies parameters from the MME Emergency Configuration Data (e.g., Emergency Access Point Name (APN), Emergency QoS Profile, Emergency PGW Identifier, etc.). To support control plane CIoT EPS optimization, the MME instructs the transmission of NAS user data through the S11-U tunnel and sends its own S11-U IP address and DL TEID so that the SGW can forward downlink data. The MME also includes a control plane PDN connection-only indication in the session creation request to indicate that the PDN connection used only for IMS emergency calls uses control plane CIoT EPS optimization only.

[0331] Step 806: SGW sends a session creation request message to PGW.

[0332] In some embodiments, the SGW creates a new entry in its EPS bearer table and sends a session creation request to the PGW indicated by the emergency PGW identifier. In the session creation request, the SGW informs the PGW of the received control-plane-only PDN connection indicator.

[0333] Step 807: PCEF initiates an IP connection to access the network.

[0334] If the PCC is configured to support emergency services and a dynamic PCC is deployed, the PCRF sets the ARP for the PCC rule to a value reserved for emergency services, based on the emergency APN. If a dynamic PCC is not deployed, the PGW uses the ARP of the default emergency EPS bearer. The PGW determines if there is an emergency service request based on the emergency APN received in the session creation request message.

[0335] In step 808, the PGW returns a session creation response to the SGW.

[0336] Step 809: SGW returns a session creation response to MME.

[0337] In some embodiments, the SGW includes the SGW IP address and TEID for S11-U in the session creation response to support control plane CIoT EPS optimization functionality.

[0338] Step 810: The MME sends an attach accept message to the access network device via downlink NAS transmission message.

[0339] In some embodiments, the MME sends an attach accept message to the eNB in ​​the S1-AP downlink NAS transmission message. The MME indicates its acceptance of CIoT EPS optimization features in the supported network behavior and includes a control plane-only indicator and an emergency service support indicator in the attach accept message, thereby indicating support for emergency services in control plane optimization scenarios; or, the attach accept message includes an emergency service support indicator for control plane, which is used to indicate that the mobility management network element supports emergency services on the control plane.

[0340] In addition, the MME indicates to the eNB that the UE is performing an emergency service, such as an IMS emergency call, so that the eNB can prioritize resources for the UE requesting the emergency service. The MME provides the eNB with a negotiated QoS profile in accordance with Clause 4.7.8 of TS23.401[5]. This QoS profile includes QoS parameters reserved for emergency services (e.g., QCI, ARP). If more than one EPS bearer is established (e.g., one for IMS-related signaling and another for IMS data), the MME sends the QoS profile of only one EPS bearer to the eNB. In this case, the MME uses local configuration (e.g., the MME selects the EPS bearer with the QCI corresponding to the highest priority) to determine which EPS bearer's QoS to send to the eNB. The eNB may also keep the UE in the RRC_CONNECTED state to prevent potential interference with IMS emergency calls.

[0341] Step 811: The access network device sends the received attach accept message to the UE.

[0342] In some embodiments, the access network device forwards the attach accept message to the UE in the RRC direct transmission message.

[0343] Step 812: The UE sends an attach complete message to the access network device.

[0344] In some embodiments, the UE sends a direct transmission message to the access network device, which includes an attach complete message.

[0345] Step 813: The access network device forwards the attach complete message to the MME.

[0346] In some embodiments, the access network device forwards the attach complete message to the MME in the Uplink NAS Transport message.

[0347] Step 814: When emergency services are needed and the emergency PDN connection is not activated, the UE requests to establish a PDN connection for emergency services.

[0348] In some embodiments, if emergency services are required and an emergency PDN connection is not yet active (e.g., when the UE has "Support Attach without PDN connection" set in preferred network behavior), the UE requests a PDN connection for emergency services. Alternatively, the UE does not set an ESM message container in the attach request.

[0349] Step 815: The MME sends a UE information transmission message to the access network equipment.

[0350] For example, as shown in step 810, the MME provides the access network device with a QoS profile that includes ARP values ​​reserved for emergency services in the UE information transmission message.

[0351] In some embodiments, steps 814 to 815 and steps 805 to 809 described above are not executed simultaneously; and steps 814 to 815 are optional steps. That is, the SM container can be included in the attach request to establish a connection in the attach process, or a connection can be established separately as in steps 814 to 815, and a QoS profile for emergency services can be obtained.

[0352] Step 816a: The emergency PDN connection is released.

[0353] Step 816: The MME sends a UE information transmission message to the access network device.

[0354] In some embodiments, step 816a is a prerequisite step for step 816, meaning that step 816 is executed only after step 816a occurs. If the MME determines that the PDN connection for emergency services has been released (e.g., upon receiving a Delete Bearer Request message), the MME provides the eNB with updated QoS parameters for the NB-IoT UE using the control plane CIoT EPS optimization function by sending a UE INFORMATION TRANSFER message. The eNB can then adjust resource priority decisions accordingly.

[0355] In some embodiments, steps 816a and 816 can be implemented as independent embodiments, that is, after the emergency PDN is released, the QoS is updated by transmitting a UE information transmission message.

[0356] The MME can release the S11-U bearer used for CP CIoT optimization when emergency service is inactive or when an emergency call ends, and notify the access network device that it no longer needs to maintain RRC-connected. The access network device can release the RRC connection with the UE based on local resource occupancy, UE activity, and network indications. The MME indicates emergency service inactivity or termination through a fourth message, as shown in Figure 10.

[0357] Example 4: Releasing the RRC connection via the fourth message instruction

[0358] Step 901: MME releases the S11-U bearer optimized by the control plane.

[0359] In some embodiments, the MME determines that it no longer needs to maintain the current PDN connection based on O&M Intervention, User Inactivity, NAS messages sent by the UE, etc. The MME sends a Release Access Bearers Request to release the S11-U bearer used for CP CIoT optimization between the MME and the SGW. The SGW releases the MME address and MME TEID, as well as Control Plane CIoT EPS Optimization related information, and returns a Release Access Bearers Response message to the MME.

[0360] Step 902: The MME sends an emergency service inactivity notification to the access network equipment.

[0361] In some embodiments, the MME notifies the access network device that the emergency service has ended, and the access network device does not need to maintain the high priority of the corresponding UE, nor does it need to keep the UE in a connected state. The MME can notify the access network device via an S1 message. If the MME determines to release the S1 interface, it can send an S1 UE context release command message to the UE. The S1 UE context release command message contains a reason value to indicate that the emergency service requested by the UE has ended. Alternatively, an existing user inactivity reason value can be reused to indicate the reason for releasing S1.

[0362] If the S1 interface is not released, notification messages can be sent to access network devices via S1. These notification messages can include an indication that emergency services have ended or that the user's emergency services are no longer active.

[0363] Step 903: The access network device releases the RRC connection.

[0364] In some embodiments, after receiving a cause value or indication information, the access network device can adjust the priority of the corresponding UE. For example, it can lower the priority, no longer prioritize resource allocation for it, and does not need to ensure that the UE is in a connected state. It can release the RRC connection with the UE at any time based on the UE's activity level and local resource occupancy. If the message received by the eNB is an S1 UE context release command message, the access network device can send an RRC Connection Release to the UE and delete the UE context after receiving an acknowledgment message from the UE.

[0365] Step 904: The access network device sends an S1 UE context release complete message to the MME.

[0366] In some embodiments, if the message received by the access network device is an S1 UE context release command message, after the RRC connection is released, the access network device can send an S1 UE context release complete message to the MME to confirm that the connection established between the MME and the access network device for the UE has been released.

[0367] Figure 11 shows a structural block diagram of a mobility management network element provided in an exemplary embodiment of this application. The mobility management network element includes: a first receiving module 1010 and a first transmitting module 1020.

[0368] The first receiving module 1010 is used to receive a first message sent by the terminal device, which is used to request emergency services.

[0369] The first message is used to request emergency services, or in other words, the first message is used to instruct the terminal device to request emergency services, or in other words, the first message is used to instruct the terminal device to request the network device to provide emergency services.

[0370] Furthermore, the first message is also used to indicate that the terminal device supports control plane optimization, or in other words, the first message is used to indicate that the terminal device has applied control plane optimization. Control plane optimization refers to supporting the transmission of user data through the control plane, such as transmitting user data through NAS messages, without needing to transmit user data through the user plane after establishing a user plane connection. In some embodiments, control plane optimization may also be referred to as CP CIoT (Control Plane CIoT) optimization, or other equivalent names may be used.

[0371] In some embodiments, the first message is sent directly from the terminal device to the mobility management network element. Alternatively, the first message is sent from the terminal device to the access network device, which then forwards it to the mobility management network element; that is, the mobility management network element receives the first message forwarded by the access network device, which was originally sent by the terminal device to the access network device. Alternatively, the first message is sent from the terminal device to the first core network element, which then forwards it to the mobility management network element. In other words, the embodiments of this application do not limit the transmission path of the first message to the mobility management network element, but the scope of protection of the embodiments of this application is not limited thereto.

[0372] In some embodiments, emergency services may also be referred to as emergency operations or other equivalent names. Emergency services refer to communication services provided to terminal devices in emergency situations, such as emergency calls and emergency text messages. For example, an emergency call refers to a voice or video call initiated by a terminal device in an emergency. Emergency calls include dialing emergency numbers such as 112, 110, 119, and 120 to report an emergency or request for help. It should be understood that the aforementioned 112, 110, 119, and 120 can be referred to as emergency service numbers, which can be agreed upon by an agreement or stipulated by the regulations of different countries. Emergency text messages refer to information sent using a terminal device in an emergency. The target of emergency text messages is usually also an emergency service number. For details regarding emergency services, please refer to the above introduction to "emergency services," which will not be repeated here.

[0373] In some embodiments, the first message is used to request emergency services, which can be achieved by carrying a first instruction, a first flag, an emergency instruction, an emergency flag, an emergency service instruction, an emergency service flag, a request type, etc., in the first message. The first instruction and / or the first flag is used to indicate emergency services. Alternatively, the first message can be implemented using a first format, which is the message format corresponding to emergency services. Optionally, there may also be message formats corresponding to normal services (or ordinary services, non-emergency services, etc.). The first format is different from the second format. That is, this application does not limit the instruction method of the first message.

[0374] In some embodiments, the first message is used to indicate that the terminal device supports control plane optimization. This can be achieved by carrying a control plane optimization instruction, a second instruction, or other similar means in the first message; alternatively, the first message can use a third format, which is a message format that supports control plane optimization. Optionally, a fourth format, which is a message format that does not support control plane optimization, may also exist. The third and fourth formats are different.

[0375] In some alternative embodiments, the first message indicates the needs and / or capabilities of the terminal device through different indications, flags, etc. For example, the first message includes a request type and control plane optimization indication.

[0376] In some alternative embodiments, the first message indicates the terminal device's needs and / or capabilities through a message format. For example, there may be a message format that simultaneously indicates emergency service and support for control plane optimization, or a message format that simultaneously indicates emergency service and lack of support for control plane optimization, or a message format that simultaneously indicates normal service and support for control plane optimization, or a message format that simultaneously indicates normal service and lack of support for control plane optimization.

[0377] The first sending module 1020 is used to send a second message to the access network device based on the first message. The second message is used to indicate that the terminal device has requested emergency service and to request the access network device to set a first priority for the terminal device. The first priority corresponds to the emergency service.

[0378] Based on the first message sent by the terminal device, the mobility management network element determines whether a second message needs to be sent to the access network device. For example, if the first message requests emergency service and instructs the terminal device to support control plane optimization, a second message is sent to the access network device.

[0379] Furthermore, the second message is used to instruct the terminal device to request emergency services and to request the access network device to set a first priority for the terminal device; or, in other words, the second message is used to instruct the terminal device to request emergency services, and the access network device should set the first priority corresponding to the emergency service for the terminal device; or, in still other words, the second message is used to request emergency services for the terminal device, and the access network device should set the first priority corresponding to the emergency service for the terminal device, thereby providing emergency services to the terminal device.

[0380] In some embodiments, if the first message requests emergency service and indicates that the terminal device does not support control plane optimization, the second message is not sent to the access network device.

[0381] In some embodiments, if the first message does not request emergency service and indicates that the terminal device supports control plane optimization, the second message is not sent to the access network device. Alternatively, if the first message does not request emergency service and indicates that the terminal device supports control plane optimization, the second message is sent to the access network device.

[0382] In some embodiments, if the first message does not request emergency services and indicates that the terminal device does not support control plane optimization, a second message is not sent to the access network device.

[0383] In some embodiments, the mobility management network element determines whether it needs to send a second message to the access network device based on a first message sent by the terminal device and the capabilities of the mobility management network element. For example, if the first message requests emergency services and indicates that the terminal device supports control plane optimization, and the mobility management network element also supports control plane optimization, then the mobility management network element sends a second message to the access network device.

[0384] In some embodiments, the first priority is the highest priority. Alternatively, the first priority is a priority higher than a priority threshold; wherein the priority threshold is agreed upon by a protocol, or pre-agreed upon by the mobility management network element and the access network equipment, or pre-agreed upon by other core network elements and the access network equipment. Alternatively, the first priority is a priority within a first interval; wherein the first interval is agreed upon by a protocol, or pre-agreed upon by the mobility management network element and the access network equipment, or pre-agreed upon by other core network elements and the access network equipment; for example, the priority value range agreed upon by the protocol is 1-15, the first interval is 1-8, and the first interval is used for priority services, which include emergency services and other services. These priority services can be agreed upon by a protocol or set by the operator; this application embodiment does not limit this.

[0385] In some embodiments, the first priority is higher than the second priority, where the second priority is the priority corresponding to normal services, or in other words, the second priority is the priority corresponding to non-urgent services.

[0386] In summary, the apparatus provided in this application embodiment illustrates that when a terminal device supports control plane optimization and requests emergency services, a mobility management network element sends a second message to an access network device based on a first message from the terminal device, instructing the access network device to set a first priority for the terminal device, whereby the first priority corresponds to emergency services. This enables the access network device to set a priority for terminal devices that support control plane optimization.

[0387] Furthermore, with control plane optimization applied, the mobility management element determines and instructs the access network device to set a first priority for the terminal device requesting emergency service. This prevents the access network device from failing to prioritize the terminal device due to a lack of user plane connection established with it caused by control plane optimization, thus avoiding emergency service failure because the terminal device cannot obtain resources to transmit emergency services. In other words, by sending a second message to the access network device based on the terminal device's first message, the mobility management element ensures that the access network device can still set a priority for the terminal device even without a user plane connection. This guarantees that the access network device will allocate resources to the terminal device according to the first priority, allowing the terminal device's emergency service to be transmitted using the resources allocated by the access network device, improving the priority transmission and reliability of emergency services.

[0388] Figure 12 shows a structural block diagram of an access network device provided in an exemplary embodiment of this application. The method includes:

[0389] The second receiving module 1110 is used to receive a second message sent by the mobility management network element. The second message is used to indicate that the terminal device has requested emergency services and requests the access network device to set a first priority for the terminal device. The first priority corresponds to the emergency services.

[0390] In this process, the terminal device requests emergency services from the mobility management network element via a first message, and the first message instructs the terminal device to support control plane optimization.

[0391] The first message is used to request emergency services, or in other words, the first message is used to instruct the terminal device to request emergency services, or in other words, the first message is used to instruct the terminal device to request the network device to provide emergency services.

[0392] Furthermore, the first message is also used to indicate that the terminal device supports control plane optimization, or in other words, the first message is used to indicate that the terminal device has applied control plane optimization. Control plane optimization refers to supporting the transmission of user data through the control plane, such as transmitting user data through NAS messages, without needing to transmit user data through the user plane after establishing a user plane connection. In some embodiments, control plane optimization may also be referred to as CP CIoT (Control Plane CIoT) optimization, or other equivalent names may be used.

[0393] In some embodiments, the first message is sent directly from the terminal device to the mobility management network element. Alternatively, the first message is sent from the terminal device to the access network device, which then forwards it to the mobility management network element; that is, the mobility management network element receives the first message forwarded by the access network device, which was originally sent by the terminal device to the access network device. Alternatively, the first message is sent from the terminal device to the first core network element, which then forwards it to the mobility management network element. In other words, the embodiments of this application do not limit the transmission path of the first message to the mobility management network element, but the scope of protection of the embodiments of this application is not limited thereto.

[0394] In some embodiments, emergency services may also be referred to as emergency operations or other equivalent names. Emergency services refer to communication services provided to terminal devices in emergency situations, such as emergency calls and emergency text messages. For example, an emergency call refers to a voice or video call initiated by a terminal device in an emergency. Emergency calls include dialing emergency numbers such as 112, 110, 119, and 120 to report an emergency or request for help. It should be understood that the aforementioned 112, 110, 119, and 120 can be referred to as emergency service numbers, which can be agreed upon by an agreement or stipulated by the regulations of different countries. Emergency text messages refer to information sent using a terminal device in an emergency. The target of emergency text messages is usually also an emergency service number. For details regarding emergency services, please refer to the above introduction to "emergency services," which will not be repeated here.

[0395] In some embodiments, the first message is used to request emergency services, which can be achieved by carrying a first instruction, a first flag, an emergency instruction, an emergency flag, an emergency service instruction, an emergency service flag, a request type, etc., in the first message. The first instruction and / or the first flag is used to indicate emergency services. Alternatively, the first message can be implemented using a first format, which is the message format corresponding to emergency services. Optionally, there may also be message formats corresponding to normal services (or ordinary services, non-emergency services, etc.). The first format is different from the second format. That is, this application does not limit the instruction method of the first message.

[0396] In some embodiments, the first message is used to indicate that the terminal device supports control plane optimization. This can be achieved by carrying a control plane optimization instruction, a second instruction, or other similar means in the first message; alternatively, the first message can use a third format, which is a message format that supports control plane optimization. Optionally, a fourth format, which is a message format that does not support control plane optimization, may also exist. The third and fourth formats are different.

[0397] In some alternative embodiments, the first message indicates the needs and / or capabilities of the terminal device through different indications, flags, etc. For example, the first message includes a request type and control plane optimization indication.

[0398] In some alternative embodiments, the first message indicates the terminal device's needs and / or capabilities through a message format. For example, there may be a message format that simultaneously indicates emergency service and support for control plane optimization, or a message format that simultaneously indicates emergency service and lack of support for control plane optimization, or a message format that simultaneously indicates normal service and support for control plane optimization, or a message format that simultaneously indicates normal service and lack of support for control plane optimization.

[0399] The second message is used to instruct the terminal device to request emergency services and to request the access network device to set a first priority for the terminal device; or, in other words, the second message is used to instruct the terminal device to request emergency services, and the access network device should set the first priority corresponding to the emergency service for the terminal device; or, in still others, the second message is used to request emergency services for the terminal device, and the access network device should set the first priority corresponding to the emergency service for the terminal device, thereby providing emergency services to the terminal device.

[0400] The second processing module 1120 is used to set a first priority for the terminal device based on the second message.

[0401] In some embodiments, the first priority is the highest priority. Alternatively, the first priority is a priority higher than a priority threshold; wherein the priority threshold is agreed upon by a protocol, or pre-agreed upon by the mobility management network element and the access network equipment, or pre-agreed upon by other core network elements and the access network equipment. Alternatively, the first priority is a priority within a first interval; wherein the first interval is agreed upon by a protocol, or pre-agreed upon by the mobility management network element and the access network equipment, or pre-agreed upon by other core network elements and the access network equipment; for example, the priority value range agreed upon by the protocol is 1-15, the first interval is 1-8, and the first interval is used for priority services, which include emergency services and other services. These priority services can be agreed upon by a protocol or set by the operator; this application embodiment does not limit this.

[0402] In some embodiments, the first priority is higher than the second priority, where the second priority is the priority corresponding to normal services, or in other words, the second priority is the priority corresponding to non-urgent services.

[0403] In summary, the apparatus provided in this application embodiment illustrates that when a terminal device supports control plane optimization and requests emergency services, a mobility management network element sends a second message to an access network device based on a first message from the terminal device, instructing the access network device to set a first priority for the terminal device, whereby the first priority corresponds to emergency services. This enables the access network device to set a priority for terminal devices that support control plane optimization.

[0404] Furthermore, with control plane optimization applied, the mobility management element determines and instructs the access network device to set a first priority for the terminal device requesting emergency service. This prevents the access network device from failing to prioritize the terminal device due to a lack of user plane connection established with it caused by control plane optimization, thus avoiding emergency service failure because the terminal device cannot obtain resources to transmit emergency services. In other words, by sending a second message to the access network device based on the terminal device's first message, the mobility management element ensures that the access network device can still set a priority for the terminal device even without a user plane connection. This guarantees that the access network device will allocate resources to the terminal device according to the first priority, allowing the terminal device's emergency service to be transmitted using the resources allocated by the access network device, improving the priority transmission and reliability of emergency services.

[0405] The first and second messages shown above will be described in detail below.

[0406] 1. First News

[0407] In some embodiments, the first message includes one or more of the following: Attach Request; Service Request; Control Plane Service Request; TAU Request; Registration Request; PDU Session Establishment Request; PDU Session Modification Request; PDN Connection Establishment Request; PDN Connection Modification Request.

[0408] In some embodiments, the first message is used to instruct a terminal device that supports control plane optimization to request emergency services.

[0409] In some embodiments, the first message includes a control plane service request; the control plane service request includes the following parameters: service type, which is used to indicate that the terminal device requests emergency services.

[0410] In some embodiments, the first message includes an attach request; the attach request includes one or more of the following parameters: terminal device identifier; attach type, which indicates that the terminal device requests emergency services; support for control plane optimization, which indicates that the terminal device supports control plane optimization; and SM (Session Management) container, which indicates that a PDN connection is established for the terminal device.

[0411] For details, please refer to "1. First Message" in the above method embodiment, which will not be repeated here.

[0412] 2. Determining APN / DNN

[0413] When the first message is another message, such as a registration request, service request, control plane service request, PDU establishment request, or PDU modification request, the encryption option also includes a DNN. Here, the APN is used to identify the PDN, and the DNN is used to identify the DN; that is, both the APN and DNN are used to identify the external data network (relative to the operator), such as the Internet or a private enterprise network. The DNN is also used to select the SMF and UPF and determine the policy applied to that data network. If the terminal device wishes to use its own provided APN or DNN instead of being selected by the mobility management element (MLE), it should instruct the MLE so that the MLE can obtain the encryption option from the terminal device while ensuring network security. However, in some embodiments, the MLE may select the APN or DNN for the terminal device based on some configuration information. After determining the APN or DNN, a connection with the PDN or a PDU session can be established, thereby enabling information exchange between the UE and the external data network. The details are as follows.

[0414] In some embodiments, the mobility management network element further includes a first processing module. The first processing module is configured to determine an APN or DNN based on a first configuration, wherein the APN or DNN is used for emergency services; and, if a first condition is met, obtain an APN or DNN from a terminal device, wherein the APN or DNN is used for emergency services; wherein the first condition includes one or more of the following: authentication completed; NAS security settings completed.

[0415] In some embodiments, the first processing module is configured to determine an APN or a DNN based on a first configuration; it can also be understood that the mobility management network element determines an APN or a DNN for emergency services based on the first configuration; further, it can be understood that the mobility management network element determines an emergency APN or an emergency DNN based on the first configuration. Alternatively, the mobility management network element determines a network access identifier based on the first configuration, the network access identifier being used to identify an external data network. The network access identifier includes one or more of the APN and DNN; it can also be understood that the mobility management network element determines a network access identifier for emergency services based on the first configuration; further, it can be understood that the mobility management network element determines an emergency network access identifier based on the first configuration. It should be understood that the determination of the aforementioned APN for emergency services, DNN for emergency services, emergency APN, emergency DNN, network access identifier for emergency services, and emergency network access identifier is all for the purpose of establishing corresponding emergency PDN connections or emergency PDU sessions, thereby enabling the provision of emergency services to terminal devices.

[0416] For details, please refer to "2. Determination of APN / DNN" in the above method embodiment, which will not be repeated here.

[0417] 3. Second message

[0418] In some embodiments, the second message is used to instruct the access network device to reserve resources for emergency services of the terminal device; or, the second message is used to instruct the access network device to prioritize the allocation of resources to the terminal device for the transmission of emergency service data. Alternatively, the first priority is used to instruct the access network device to reserve resources for emergency services of the terminal device; or, the first priority is used to instruct the access network device to prioritize the allocation of resources to the terminal device for the transmission of emergency service data.

[0419] In some embodiments, the second processing module 1120 is configured to select, based on the second message, a first terminal device to be given priority in resource allocation among at least two terminal devices. The first terminal device is the terminal device requesting emergency service indicated by the second message. That is, the access network device allocates resources among at least two terminal devices according to the priority of each terminal device.

[0420] For example, when the access network device sets the terminal device to have the highest priority, the access network device will prioritize establishing an SRB for the terminal device. The SRB is used by the terminal device to transmit user data.

[0421] In some embodiments, the second message includes one or more of the following: an Initial Context Setup Request; and a UE Information Transfer message. In other embodiments, the second message may also be other messages, such as messages for providing QoS parameters or priorities or other priority-related parameters, and this application embodiment does not limit this to such messages.

[0422] In some embodiments, the second message includes one or more of the following parameters: QoS parameters, used to indicate the QoS parameters of emergency services; a first indication, used to indicate that the terminal device has requested emergency services; a priority, used to indicate that the priority assigned to the terminal device by the mobility management network element is the first priority; an ARP, used to indicate the ARP of the emergency service; an EPS bearer identifier, used to identify the EPS bearer of the terminal device; a terminal device identifier; an RRC connection hold indication, used to indicate that the access network device should maintain the RRC connection for the terminal device; a timer, used to indicate the hold time of the RRC connection; a control plane only indication, used to indicate that the terminal device and / or the mobility management network element only apply control plane optimization; and support for control plane optimization, used to indicate that the terminal device and / or the mobility management network element support for control plane optimization.

[0423] For details, please refer to "3. Second Message" in the above method embodiment, which will not be repeated here.

[0424] In some embodiments, after the access network device completes the priority setting for the terminal device, it can notify the mobility management network element via a message. The specifics are as follows.

[0425] 4. Other news

[0426] In some embodiments, the first receiving module 1010 is configured to receive a third message sent by the access network device, the third message being used to instruct the access network device to set a first priority for emergency services for the terminal device.

[0427] In some embodiments, the access network device further includes a second sending module. The second sending module is configured to send a third message to the mobility management network element, the third message instructing the access network device to set a first priority for emergency services for the terminal device.

[0428] In some embodiments, the first sending module 1020 is configured to send a fourth message to the access network device, the fourth message being used to indicate that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

[0429] In some embodiments, the second receiving module 1110 is configured to receive a fourth message sent by the mobility management network element, the fourth message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

[0430] In some embodiments, the second processing module 1120 is configured to perform one or more of the following operations based on the fourth message: adjust the priority of the terminal device; no longer prioritize resource allocation for the terminal device; no longer keep the terminal device in a connected state; release the RRC connection with the terminal device.

[0431] In some embodiments, the first sending module 1020 is configured to send a fifth message, the fifth message being used to indicate the establishment of a session, the fifth message including a control plane only connection indication, the control plane only connection indication being used to indicate that the established connection uses control plane optimization.

[0432] For example, the fifth message is a session creation request. A session creation request is used to indicate the establishment of a PDN connection or PDU session. A control plane-only connection indication may also be called a control plane-only indication, control plane indication, second indication, or other equivalent names. This control plane-only connection indication is used for indication.

[0433] For example, the MME sends a session creation request to the SGW.

[0434] In some embodiments, the first sending module 1020 is configured to send a sixth message to the terminal device, the sixth message being used to instruct the mobility management network element to accept the first message from the terminal device; wherein, the sixth message includes one or more of the following: a control plane only instruction, the control plane only instruction being used to instruct the mobility management network element to use control plane transmission; an emergency service support instruction, the emergency service support instruction being used to instruct the mobility management network element to support emergency services.

[0435] In some embodiments, after completing the above process, i.e., setting a first priority for the terminal device, emergency service data can be transmitted via NAS messages. For example, the first receiving module 1010 is used to receive emergency service data sent by the terminal device, and the emergency service data is sent via NAS messages.

[0436] For example, the first sending module 1020 is used to send emergency service data to the terminal device, and the emergency service data is sent through downlink DL NAS messages.

[0437] For details, please refer to "4. Other messages" in the above method embodiment, which will not be repeated here.

[0438] It should be noted that the device provided in the above embodiments is only an example of the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0439] Regarding the apparatus in this embodiment, the specific manner in which each module performs its operations has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0440] Figure 13 shows a schematic diagram of the core network device provided in an exemplary embodiment of this application. The core network device 1200 can be used to execute the method steps performed by the core network device in the above embodiments. The core network device 1200 may include: a processor 1201, a transceiver 1202, and a memory 1203. The processor 1201 can be used to control transmission and / or reception. The transceiver 1202 can be used to implement transmission and / or reception functions.

[0441] The processor 1201 includes one or more processing cores. The processor 1201 executes various functional applications and information processing by running software programs and modules.

[0442] Transceiver 1202 may include a receiver and a transmitter. For example, transceiver 1202 may include a wired communication component, which may include a wired communication chip and a wired interface (such as a fiber optic interface). Optionally, transceiver 1202 may also include a wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0443] The memory 1203 can be connected to the processor 1201 and the transceiver 1202.

[0444] The memory 1203 can be used to store a computer program executed by the processor, and the processor 1201 is used to execute the computer program to implement the various steps performed by the core network device in the above method embodiment.

[0445] Furthermore, the memory 1203 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static on-demand memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0446] In some embodiments, the processor 1201 and / or transceiver 1202 are configured to receive a first message sent by a terminal device, the first message being used to request emergency services and instructing the terminal device to support control plane optimization; based on the first message, send a second message to an access network device, the second message being used to instruct the terminal device to request the access network device to set a first priority for the terminal device, the first priority corresponding to the emergency service.

[0447] In some embodiments, processor 1201 and / or transceiver 1202 are configured to determine an APN or data network name (DNN) based on a first configuration, the APN or the DNN being used for the emergency service; and to obtain the APN or the DNN from the terminal device if a first condition is met, the APN or the DNN being used for the emergency service; wherein the first condition includes one or more of the following: authentication completed; NAS security settings completed.

[0448] In some embodiments, processor 1201 and / or transceiver 1202 are configured to receive a third message sent by the access network device, the third message being configured to instruct the access network device to set a first priority for emergency services for the terminal device.

[0449] In some embodiments, processor 1201 and / or transceiver 1202 are configured to send a fourth message to the access network device, the fourth message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

[0450] In some embodiments, processor 1201 and / or transceiver 1202 are configured to send a fifth message indicating the establishment of a session, the fifth message including a control plane-only connection indication indicating that the established connection uses the control plane optimization.

[0451] In some embodiments, processor 1201 and / or transceiver 1202 are configured to send a sixth message to the terminal device, the sixth message being used to instruct the mobility management network element to accept the first message from the terminal device; wherein the sixth message includes one or more of the following: a control plane only instruction, the control plane only instruction being used to instruct the mobility management network element to use the control plane for transmission; an emergency service support instruction, the emergency service support instruction being used to instruct the mobility management network element to support the emergency service.

[0452] For details not described in this embodiment, please refer to the embodiments above, which will not be repeated here.

[0453] Figure 14 shows a schematic diagram of an access network device provided in an exemplary embodiment of this application. The access network device 1300 can be used to execute the method steps performed by the access network device in the above embodiments. The access network device 1300 may include: a processor 1301, a transceiver 1302, and a memory 1303. The processor 1301 can be used to control transmission and / or reception. The transceiver 1302 can be used to implement transmission and / or reception functions.

[0454] The processor 1301 includes one or more processing cores. The processor 1301 executes various functional applications and information processing by running software programs and modules.

[0455] Transceiver 1302 may include a receiver and a transmitter. For example, transceiver 1302 may include a wired communication component, which may include a wired communication chip and a wired interface (such as a fiber optic interface). Optionally, transceiver 1302 may also include a wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0456] The memory 1303 can be connected to the processor 1301 and the transceiver 1302.

[0457] The memory 1303 can be used to store a computer program executed by the processor, and the processor 1301 is used to execute the computer program to implement the various steps performed by the access network device in the above method embodiment.

[0458] Furthermore, the memory 1303 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static on-demand memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0459] In some embodiments, the processor 1301 and / or transceiver 1302 are configured to receive a second message sent by a mobility management network element, the second message indicating that a terminal device has requested emergency services and requesting the access network device to set a first priority for the terminal device, the first priority corresponding to the emergency services; and set the first priority for the terminal device based on the second message; wherein the terminal device requests emergency services from the mobility management network element through a first message, and the first message indicates that the terminal device supports control plane optimization.

[0460] In some embodiments, processor 1301 and / or transceiver 1302 are configured to send a third message to the mobility management network element, the third message being configured to instruct the access network device to set a first priority for emergency services for the terminal device.

[0461] In some embodiments, processor 1301 and / or transceiver 1302 are configured to receive a fourth message sent by the mobility management network element, the fourth message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

[0462] In some embodiments, processor 1301 and / or transceiver 1302 are configured to perform one or more of the following operations based on the fourth message: adjust the priority of the terminal device; no longer prioritize resource allocation for the terminal device; no longer keep the terminal device in a connected state; release the RRC connection with the terminal device.

[0463] For details not described in this embodiment, please refer to the embodiments above, which will not be repeated here.

[0464] In one exemplary embodiment of this application, a computer-readable storage medium is also provided, storing at least one program segment. This program segment is loaded and executed by a processor and / or transceiver. The computer-readable storage medium implements the priority setting method for emergency services provided in the various method embodiments described above. In one exemplary embodiment of this application, a chip is also provided, including programmable logic circuits and / or program instructions. When the chip runs on a network device, it implements the priority setting method for emergency services provided in the various method embodiments described above. In one exemplary embodiment of this application, a chip is also provided, including programmable logic circuits and / or program instructions. When the chip runs on a terminal device, it implements the priority setting method for emergency services provided in the various method embodiments described above. In one exemplary embodiment of this application, a computer program product is also provided. When this computer program product runs on the processor and / or transceiver of a wireless device, it causes a core network device and / or an access network device to execute the aforementioned priority setting method for emergency services. In one exemplary embodiment of this application, a computer program is also provided, including computer instructions. The processor and / or transceiver of the wireless device executes the computer instructions, causing the core network device and / or access network device to execute the aforementioned priority setting method for emergency services. In one exemplary embodiment of this application, a chip is also provided. The chip is applied to a core network device or a mobility management network element. The chip is used to receive a first message sent by a terminal device. The first message requests emergency services and indicates that the terminal device supports control plane optimization. Based on the first message, the chip sends a second message to an access network device. The second message indicates that the terminal device has requested the emergency services and requests the access network device to set a first priority for the terminal device, where the first priority corresponds to the emergency services. In another exemplary embodiment of this application, a chip is also provided. The chip is applied to an access network device. The chip is used to receive a second message sent by a mobility management network element. The second message indicates that the terminal device has requested emergency services and requests the access network device to set a first priority for the terminal device, where the first priority corresponds to the emergency services. Based on the second message, the chip sets the first priority for the terminal device. The terminal device requests emergency services from the mobility management network element via the first message, and the first message indicates that the terminal device supports control plane optimization.

[0465] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of an association. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is an association between A and B. In the description of the embodiments of this application, the term "corresponding" can mean that there is a direct or indirect correspondence between two things, or that there is an association between two things, or it can mean an instruction and being instructed, a configuration and being configured, etc. The term "multiple" mentioned herein refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following associated objects are in an "or" relationship. The term "greater than or equal to" mentioned herein can mean greater than or equal to, or greater than; and "less than or equal to" can mean less than or equal to, or less than. Furthermore, the step numbers described herein are merely illustrative of one possible execution order among the steps. In some other embodiments, the steps may not be executed in the numerical order, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this. Those skilled in the art should recognize that the functions described in the above one or more examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transmission of computer programs from one place to another. Storage media can be any available medium accessible to general-purpose or special-purpose computers.

[0466] The above are merely exemplary embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application shall be included within the protection scope of this application.

Claims

1. A method for setting priority in emergency services, characterized in that, The method comprises a mobility management network element and includes: Receive a first message sent by the terminal device, the first message being used to request emergency services; Based on the first message, a second message is sent to the access network device. The second message is used to indicate that the terminal device has requested the emergency service and to request the access network device to set a first priority for the terminal device, the first priority corresponding to the emergency service.

2. The method according to claim 1, characterized in that, The second message is used to instruct the access network device to reserve resources for emergency services of the terminal device; or, the second message is used to instruct the access network device to prioritize the allocation of resources to the terminal device, the resources being used for the transmission of emergency service data.

3. The method according to claim 1 or 2, characterized in that, The second message includes one or more of the following messages: Initial Context Establishment Request; Terminal Equipment (UE) Information Transmission Message.

4. The method according to any one of claims 1 to 3, characterized in that, The second message includes one or more of the following parameters: Quality of Service (QoS) parameters, which are used to indicate the QoS parameters of the emergency service; and a first indication, which is used to indicate that the terminal device has requested the emergency service. Priority, wherein the priority is used to indicate that the mobility management network element assigns the first priority to the terminal device; The system includes: an allocation and reservation priority ARP, which indicates the ARP for the emergency service; an Evolved Packet System (EPS) bearer identifier, which identifies the EPS bearer of the terminal device; a terminal device identifier; a Radio Resource Control (RRC) connection hold-up indicator, which indicates that the access network device should maintain an RRC connection for the terminal device; a timer, which indicates the hold-up time for the RRC connection; and a control plane-only indicator, which indicates that the terminal device and / or the mobility management element should only apply control plane optimization. Support for control plane optimization, wherein the support for control plane optimization is used to instruct the terminal device and / or the mobility management network element to support the control plane optimization.

5. The method according to claim 4, characterized in that, The QoS parameters include one or more of the following parameters: Quality of Service Level Identifier (CQI); ARP.

6. The method according to any one of claims 1 to 5, characterized in that, The first message includes one or more of the following messages: attach request; service request; control plane service request; tracking area update (TAU) request; registration request; protocol data unit (PDU) session establishment request; and PDU session modification request.

7. The method according to claim 6, characterized in that, The first message includes the attach request; the attach request includes one or more of the following parameters: terminal device identifier; attach type, the attach type being used to indicate that the terminal device requests the emergency service; support for control plane optimization, the support for control plane optimization being used to indicate that the terminal device supports the control plane optimization; session management (SM) container, the SM container being used to indicate the establishment of a packet data network (PDN) connection for the terminal device.

8. The method according to claim 7, characterized in that, The SM container includes one or more of the following parameters: request type, which indicates that the type of request from the terminal device is the emergency service; PDN type; encryption option transmission flag, which indicates the transmission of encryption options, including the access point name (APN).

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Based on the first configuration, determine the APN or the data network name DNN, which is used for the emergency service; And / or, if a first condition is met, the APN or the DNN is obtained from the terminal device, the APN or the DNN being used for the emergency service; wherein the first condition includes one or more of the following conditions: authentication completed; NAS security settings completed.

10. The method according to claim 9, characterized in that, The first configuration includes one or more of the emergency configuration data of the Mobility Management Function Entity (MME) and the emergency configuration data of the Access and Mobility Management Function (AMF).

11. The method according to claim 6, characterized in that, The first message includes the control plane service request; the control plane service request includes the following parameter: service type, which is used to instruct the terminal device to request the emergency service.

12. The method according to claim 5 or 7, characterized in that, The terminal device identifier includes one or more of the following parameters: International Mobile Subscriber Identity (IMSI); Globally Unique Temporary Identifier (GUTI); International Mobile Equipment Identity (IMEI); 5G-GUTI; and Subtle User Identity (SUCI).

13. The method according to any one of claims 1 to 12, characterized in that, The method further includes: The access network device receives a third message, which instructs the access network device to set a first priority for emergency services for the terminal device.

14. The method according to claim 13, characterized in that, The method further includes: The system receives emergency service data sent by the terminal device, which is sent via a Non-Access Stratum (NAS) message.

15. The method according to claim 13 or 14, characterized in that, The method further includes: Emergency service data is sent to the terminal device via a downlink DL NAS message.

16. The method according to any one of claims 1 to 15, characterized in that, The method further includes: A fourth message is sent to the access network device, the fourth message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

17. The method according to claim 16, characterized in that, The fourth message is also used to indicate the release of the transmission interface, which refers to the interface between the mobility management network element and the access network device.

18. The method according to claim 17, characterized in that, The transmission interface includes: an S1 interface; and / or, a next-generation (NG) interface.

19. The method according to claim 17 or 18, characterized in that, The fourth message is a context release command; the context release command includes a reason value; wherein, the reason value is used to indicate that the emergency service has ended, or, the reason value is used to indicate that the emergency service is no longer active, or, the reason value is used to indicate that the user is no longer active.

20. The method according to claim 16, characterized in that, The fourth message includes an indication message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

21. The method according to any one of claims 16 to 20, characterized in that, The access network device performs one or more of the following operations based on the fourth message: adjusts the priority of the terminal device; no longer prioritizes allocating resources to the terminal device; no longer keeps the terminal device in a connected state; releases the RRC connection with the terminal device.

22. The method according to any one of claims 1 to 21, characterized in that, The method further includes: A fifth message is sent, which is used to indicate the establishment of a session. The fifth message includes a control plane-only connection indication, which is used to indicate that the established connection uses the control plane optimization.

23. The method according to any one of claims 1 to 22, characterized in that, The method further includes: A sixth message is sent to the terminal device, the sixth message being used to instruct the mobility management network element to accept the first message from the terminal device; wherein the sixth message includes one or more of the following parameters: control plane only indication, the control plane only indication being used to instruct the mobility management network element to use the control plane for transmission; emergency service support indication, the emergency service support indication being used to instruct the mobility management network element to support the emergency service; emergency service support indication for control plane, the emergency service support indication for control plane is used to instruct the mobility management network element to support emergency services on the control plane.

24. The method according to any one of claims 1 to 23, characterized in that, The control plane optimization includes: control plane EPS optimization; and / or, control plane 5G system 5GS optimization.

25. The method according to any one of claims 1 to 24, characterized in that, The mobility management network element is an MME; or, the mobility management network element is an AMF.

26. A method for setting priority in emergency services, characterized in that, The method is provided by an access network device, and the method includes: The device receives a second message from a mobility management network element, the second message indicating that the terminal device has requested emergency services and requesting the access network device to set a first priority for the terminal device, the first priority corresponding to the emergency services; Based on the second message, the first priority is set for the terminal device; The terminal device requests emergency services from the mobility management network element via a first message.

27. The method according to claim 26, characterized in that, The second message is used to request the access network device to reserve resources for the emergency service of the terminal device; or, the second message is used to request the access network device to prioritize the allocation of resources to the terminal device, the resources being used for the transmission of emergency service data.

28. The method according to claim 26 or 27, characterized in that, The second message includes one or more of the following messages: Initial Context Establishment Request; Terminal Equipment (UE) Information Transmission Message.

29. The method according to any one of claims 26 to 28, characterized in that, The second message includes one or more of the following parameters: Quality of Service (QoS) parameters, which are used to indicate the QoS parameters of the emergency service; and a first indication, which is used to indicate that the terminal device has requested the emergency service. Priority, wherein the priority is used to indicate that the mobility management network element assigns the first priority to the terminal device; The system includes: an allocation and reservation priority ARP, which indicates the ARP for the emergency service; an Evolved Packet System (EPS) bearer identifier, which identifies the EPS bearer of the terminal device; a terminal device identifier; an Unlimited Resource Control (RRC) connection hold-up indicator, which indicates that the access network device should maintain an RRC connection for the terminal device; a timer, which indicates the hold-up time for the RRC connection; and a control plane-only indicator, which indicates that the terminal device and / or the mobility management element should only apply control plane optimization. Support for control plane optimization, wherein the support for control plane optimization is used to instruct the terminal device and / or the mobility management network element to support the control plane optimization.

30. The method according to claim 29, characterized in that, The QoS parameters include one or more of the following parameters: Quality of Service Level Identifier (CQI); ARP.

31. The method according to any one of claims 26 to 30, characterized in that, The first message includes one or more of the following messages: attach request; service request; control plane service request; tracking area update (TAU) request; registration request; protocol data unit (PDU) session establishment request; and PDU session modification request.

32. The method according to claim 31, characterized in that, The first message includes the attach request; the attach request includes one or more of the following parameters: terminal device identifier; attach type, the attach type being used to indicate that the terminal device requests the emergency service; support for control plane optimization, the support for control plane optimization being used to indicate that the terminal device supports the control plane optimization; session management (SM) container, the SM container being used to indicate the establishment of a packet data network (PDN) connection for the terminal device.

33. The method according to claim 32, characterized in that, The SM container includes one or more of the following parameters: request type, which indicates that the type of request from the terminal device is the emergency service; PDN type; encryption option transmission flag, which indicates the transmission of encryption options, including the access point name (APN).

34. The method according to any one of claims 26 to 33, characterized in that, The mobility management network element determines an APN or a data network name (DNN) based on a first configuration, the APN or the DNN being used for the emergency service; and / or, the mobility management network element obtains an APN or a data network name (DNN) from the terminal device when a first condition is met, the APN or the DNN being used for the emergency service; wherein, the first condition includes one or more of the following conditions: authentication completed; NAS security settings completed.

35. The method according to claim 34, characterized in that, The first configuration includes one or more of the emergency configuration data of the Mobility Management Function Entity (MME) and the emergency configuration data of the Access and Mobility Management Function (AMF).

36. The method according to claim 31, characterized in that, The first message includes a control plane service request; the control plane service request includes the following parameter: service type, which is used to instruct the terminal device to request the emergency service.

37. The method according to claim 29 or 32, characterized in that, The terminal device identifier includes one or more of the following parameters: International Mobile Subscriber Identity (IMSI); Globally Unique Temporary Identifier (GUTI); International Mobile Equipment Identity (IMEI); 5G-GUTI; and Subtle User Identity (SUCI).

38. The method according to any one of claims 26 to 37, characterized in that, The method further includes: A third message is sent to the mobility management network element, the third message being used to instruct the access network device to set a first priority for the terminal device for emergency services.

39. The method according to claim 38, characterized in that, The mobility management network element receives emergency service data sent by the terminal device, and the emergency service data is sent via a non-access stratum (NAS) message.

40. The method according to claim 38 or 39, characterized in that, The mobility management network element sends emergency service data to the terminal device, and the emergency service data is sent via downlink DL NAS messages.

41. The method according to any one of claims 26 to 40, characterized in that, The method further includes: The system receives a fourth message from the mobility management network element, the fourth message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

42. The method according to claim 41, characterized in that, The fourth message is also used to indicate the release of the transmission interface, which refers to the interface between the mobility management network element and the access network device.

43. The method according to claim 42, characterized in that, The transmission interface includes: an S11 interface; and / or, a next-generation NG interface.

44. The method according to claim 42 or 43, characterized in that, The fourth message is a context release command; the context release command includes a reason value; wherein, the reason value is used to indicate that the emergency service has ended, or, the reason value is used to indicate that the emergency service is no longer active, or, the reason value is used to indicate that the user is no longer active.

45. The method according to claim 41, characterized in that, The fourth message includes an indication message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

46. ​​The method according to any one of claims 41 to 45, characterized in that, The method further includes: Based on the fourth message, perform one or more of the following operations: adjust the priority of the terminal device; no longer prioritize resource allocation for the terminal device; no longer keep the terminal device in a connected state; release the RRC connection with the terminal device.

47. The method according to any one of claims 26 to 46, characterized in that, The control plane optimization includes the following: control plane EPS optimization; and / or, control plane 5G system 5GS optimization.

48. The method according to any one of claims 26 to 47, characterized in that, The mobility management network element is an MME; or, the mobility management network element is an AMF.

49. A mobility management network element, characterized in that, The mobility management network element includes: The first receiving module is used to receive a first message sent by the terminal device. The first message is used to request emergency services and to instruct the terminal device to support control plane optimization. The first sending module is configured to send a second message to the access network device based on the first message. The second message is used to indicate that the terminal device has requested the emergency service and to request the access network device to set a first priority for the terminal device, the first priority corresponding to the emergency service.

50. The mobility management network element according to claim 49, characterized in that, The second message is used to instruct the access network device to reserve resources for emergency services of the terminal device; or, the second message is used to instruct the access network device to prioritize the allocation of resources to the terminal device, the resources being used for the transmission of emergency service data.

51. The mobility management network element according to claim 49 or 50, characterized in that, The second message includes one or more of the following messages: Initial Context Establishment Request; Terminal Equipment (UE) Information Transmission Message.

52. The mobility management network element according to any one of claims 49 to 51, characterized in that, The second message includes one or more of the following parameters: Quality of Service (QoS) parameters, which are used to indicate the QoS parameters of the emergency service; and a first indication, which is used to indicate that the terminal device has requested the emergency service. Priority, wherein the priority is used to indicate that the mobility management network element assigns the first priority to the terminal device; The system includes: an allocation and reservation priority ARP, which indicates the ARP for the emergency service; an Evolved Packet System (EPS) bearer identifier, which identifies the EPS bearer of the terminal device; a terminal device identifier; a Radio Resource Control (RRC) connection hold-up indicator, which indicates that the access network device should maintain an RRC connection for the terminal device; a timer, which indicates the hold-up time for the RRC connection; and a control plane-only indicator, which indicates that the terminal device and / or the mobility management element should only apply control plane optimization. Support for control plane optimization, wherein the support for control plane optimization is used to instruct the terminal device and / or the mobility management network element to support the control plane optimization.

53. The mobility management network element according to claim 52, characterized in that, The QoS parameters include one or more of the following parameters: Quality of Service Level Identifier (CQI); ARP.

54. The mobility management network element according to any one of claims 49 to 53, characterized in that, The first message includes one or more of the following messages: attach request; service request; control plane service request; tracking area update (TAU) request; registration request; protocol data unit (PDU) session establishment request; and PDU session modification request.

55. The mobility management network element according to claim 54, characterized in that, The first message includes the attach request; the attach request includes one or more of the following parameters: terminal device identifier; attach type, the attach type being used to indicate that the terminal device requests the emergency service; support for control plane optimization, the support for control plane optimization being used to indicate that the terminal device supports the control plane optimization; session management (SM) container, the SM container being used to indicate the establishment of a packet data network (PDN) connection for the terminal device.

56. The mobility management network element according to claim 55, characterized in that, The SM container includes one or more of the following parameters: request type, which indicates that the type of request from the terminal device is the emergency service; PDN type; encryption option transmission flag, which indicates the transmission of encryption options, including the access point name (APN).

57. The mobility management network element according to any one of claims 49 to 56, characterized in that, The mobility management network element also includes: A first processing module is configured to determine an APN or a Data Network Name (DNN) based on a first configuration, wherein the APN or the DNN is used for the emergency service; and / or, if a first condition is met, obtain the APN or the DNN from the terminal device, wherein the APN or the DNN is used for the emergency service; wherein the first condition includes one or more of the following conditions: authentication completed; NAS security settings completed.

58. The mobility management network element according to claim 57, characterized in that, The first configuration includes one or more of the emergency configuration data of the Mobility Management Function Entity (MME) and the emergency configuration data of the Access and Mobility Management Function (AMF).

59. The mobility management network element according to claim 54, characterized in that, The first message includes the control plane service request; the control plane service request includes the following parameter: service type, which is used to instruct the terminal device to request the emergency service.

60. The mobility management network element according to claim 52 or 55, characterized in that, The terminal device identifier includes one or more of the following parameters: International Mobile Subscriber Identity (IMSI); Globally Unique Temporary Identifier (GUTI); International Mobile Equipment Identity (IMEI); 5G-GUTI; and Subtle User Identity (SUCI).

61. The mobility management network element according to any one of claims 49 to 60, characterized in that, The first receiving module is further configured to receive a third message sent by the access network device, the third message being used to instruct the access network device to set a first priority for emergency services for the terminal device.

62. The mobility management network element according to claim 61, characterized in that, The first receiving module is further configured to receive emergency service data sent by the terminal device, the emergency service data being sent via a Non-Access Stratum (NAS) message.

63. The mobility management network element according to claim 61 or 62, characterized in that, The first sending module is further configured to send emergency service data to the terminal device, the emergency service data being sent via a downlink DL NAS message.

64. The mobility management network element according to any one of claims 49 to 63, characterized in that, The first sending module is further configured to send a fourth message to the access network device, the fourth message being used to indicate that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

65. The mobility management network element according to claim 64, characterized in that, The fourth message is also used to indicate the release of the transmission interface, which refers to the interface between the mobility management network element and the access network device.

66. The mobility management network element according to claim 65, characterized in that, The transmission interface includes: an S1 interface; and / or, a next-generation (NG) interface.

67. The mobility management network element according to claim 65 or 66, characterized in that, The fourth message is a context release command; the context release command includes a reason value; wherein, the reason value is used to indicate that the emergency service has ended, or, the reason value is used to indicate that the emergency service is no longer active, or, the reason value is used to indicate that the user is no longer active.

68. The mobility management network element according to claim 64, characterized in that, The fourth message includes an indication message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

69. The mobility management network element according to any one of claims 64 to 68, characterized in that, The access network device performs one or more of the following operations based on the fourth message: adjusts the priority of the terminal device; no longer prioritizes allocating resources to the terminal device; no longer keeps the terminal device in a connected state; releases the RRC connection with the terminal device.

70. The mobility management network element according to any one of claims 49 to 69, characterized in that, The first sending module is further configured to send a fifth message, the fifth message being used to indicate the establishment of a session, the fifth message including a control plane-only connection indication, the control plane-only connection indication being used to indicate that the established connection uses the control plane optimization.

71. The mobility management network element according to any one of claims 49 to 70, characterized in that, The first sending module is further configured to send a sixth message to the terminal device, the sixth message being used to instruct the mobility management network element to accept the first message from the terminal device; The sixth message includes one or more of the following parameters: control plane only indication, which instructs the mobility management network element to use the control plane for transmission; emergency service support indication, which instructs the mobility management network element to support the emergency service; and emergency service support indication, which instructs the mobility management network element to support emergency services on the control plane.

72. The mobility management network element according to any one of claims 49 to 71, characterized in that, The control plane optimization includes: control plane EPS optimization; and / or, control plane 5G system 5GS optimization.

73. The mobility management network element according to any one of claims 49 to 72, characterized in that, The mobility management network element is an MME; or, the mobility management network element is an AMF.

74. An access network device, characterized in that, The access network equipment includes: The second receiving module is used to receive a second message sent by the mobility management network element. The second message is used to indicate that the terminal device has requested emergency services and to request the access network device to set a first priority for the terminal device. The first priority corresponds to the emergency services. The second processing module is configured to set the first priority for the terminal device based on the second message; The terminal device requests emergency services from the mobility management network element via a first message, and the first message indicates that the terminal device supports control plane optimization.

75. The method according to claim 74, characterized in that, The second message is used to request the access network device to reserve resources for the emergency service of the terminal device; or, the second message is used to request the access network device to prioritize the allocation of resources to the terminal device, the resources being used for the transmission of emergency service data.

76. The access network equipment according to claim 74 or 75, characterized in that, The second message includes one or more of the following messages: Initial Context Establishment Request; Terminal Equipment (UE) Information Transmission Message.

77. The access network device according to any one of claims 74 to 76, characterized in that, The second message includes one or more of the following parameters: Quality of Service (QoS) parameters, which are used to indicate the QoS parameters of the emergency service; and a first indication, which is used to indicate that the terminal device has requested the emergency service. Priority, wherein the priority is used to indicate that the mobility management network element assigns the first priority to the terminal device; The system includes: an allocation and reservation priority ARP, which indicates the ARP for the emergency service; an Evolved Packet System (EPS) bearer identifier, which identifies the EPS bearer of the terminal device; a terminal device identifier; an Unlimited Resource Control (RRC) connection hold-up indicator, which indicates that the access network device should maintain an RRC connection for the terminal device; a timer, which indicates the hold-up time for the RRC connection; and a control plane-only indicator, which indicates that the terminal device and / or the mobility management element should only apply control plane optimization. Support for control plane optimization, wherein the support for control plane optimization is used to instruct the terminal device and / or the mobility management network element to support the control plane optimization.

78. The access network device according to claim 77, characterized in that, The QoS parameters include one or more of the following parameters: Quality of Service Level Identifier (CQI); ARP.

79. The access network device according to any one of claims 74 to 78, characterized in that, The first message includes one or more of the following messages: attach request; service request; control plane service request; tracking area update (TAU) request; registration request; protocol data unit (PDU) session establishment request; and PDU session modification request.

80. The access network device according to claim 79, characterized in that, The first message includes the attach request; the attach request includes one or more of the following parameters: terminal device identifier; attach type, the attach type being used to indicate that the terminal device requests the emergency service; support for control plane optimization, the support for control plane optimization being used to indicate that the terminal device supports the control plane optimization; session management (SM) container, the SM container being used to indicate the establishment of a packet data network (PDN) connection for the terminal device.

81. The access network device according to claim 80, characterized in that, The SM container includes one or more of the following parameters: request type, which indicates that the type of request from the terminal device is the emergency service; PDN type; encryption option transmission flag, which indicates the transmission of encryption options, including the access point name (APN).

82. The access network device according to any one of claims 74 to 81, characterized in that, The mobility management network element determines an APN or a data network name (DNN) based on a first configuration, the APN or the DNN being used for the emergency service; and / or, the mobility management network element obtains an APN or a data network name (DNN) from the terminal device when a first condition is met, the APN or the DNN being used for the emergency service; wherein, the first condition includes one or more of the following conditions: authentication completed; NAS security settings completed.

83. The access network device according to claim 72, characterized in that, The first configuration includes one or more of the emergency configuration data of the Mobility Management Function Entity (MME) and the emergency configuration data of the Access and Mobility Management Function (AMF).

84. The access network device according to claim 79, characterized in that, The first message includes a control plane service request; the control plane service request includes the following parameter: service type, which is used to instruct the terminal device to request the emergency service.

85. The access network equipment according to claim 77 or 80, characterized in that, The terminal device identifier includes one or more of the following parameters: International Mobile Subscriber Identity (IMSI); Globally Unique Temporary Identifier (GUTI); International Mobile Equipment Identity (IMEI); 5G-GUTI; and Subtle User Identity (SUCI).

86. The access network device according to any one of claims 74 to 85, characterized in that, The second sending module is used to send a third message to the mobility management network element, the third message being used to instruct the access network device to set a first priority for emergency services for the terminal device.

87. The access network device according to claim 86, characterized in that, The mobility management network element receives emergency service data sent by the terminal device, and the emergency service data is sent via a non-access stratum (NAS) message.

88. The access network equipment according to claim 86 or 87, characterized in that, The mobility management network element sends emergency service data to the terminal device, and the emergency service data is sent via downlink DL NAS messages.

89. The access network device according to any one of claims 74 to 88, characterized in that, The second receiving module is further configured to receive a fourth message sent by the mobility management network element, the fourth message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

90. The access network device according to claim 89, characterized in that, The fourth message is also used to indicate the release of the transmission interface, which refers to the interface between the mobility management network element and the access network device.

91. The access network device according to claim 90, characterized in that, The transmission interface includes: an S11 interface; and / or, a next-generation NG interface.

92. The access network equipment according to claim 90 or 91, characterized in that, The fourth message is a context release command; the context release command includes a reason value; wherein, the reason value is used to indicate that the emergency service has ended, or, the reason value is used to indicate that the emergency service is no longer active, or, the reason value is used to indicate that the user is no longer active.

93. The access network equipment according to claim 92, characterized in that, The fourth message includes an indication message indicating that the emergency service requested by the terminal device has ended, or that the emergency service is no longer active.

94. The access network device according to any one of claims 89 to 93, characterized in that, The second processing module is further configured to perform one or more of the following operations based on the fourth message: adjust the priority of the terminal device; no longer prioritize resource allocation for the terminal device; no longer keep the terminal device in a connected state; release the RRC connection with the terminal device.

95. The access network device according to any one of claims 74 to 94, characterized in that, The control plane optimization includes: control plane EPS optimization; and / or, control plane 5G system 5GS optimization.

96. The access network device according to any one of claims 74 to 95, characterized in that, The mobility management network element is an MME; or, the mobility management network element is an AMF.

97. A core network device, characterized in that, The core network device includes: a processor; a transceiver connected to the processor; wherein the processor and / or the transceiver is configured to load and execute the executable instructions to implement the priority setting method for emergency services as described in any one of claims 1 to 25.

98. An access network device, characterized in that, The access network device includes: a processor; a transceiver connected to the processor; wherein the processor and / or the transceiver are configured to load and execute the executable instructions to implement the priority setting method for emergency services as described in any one of claims 26 to 48.

99. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one program, which is loaded and executed by a processor and / or transceiver to implement the priority setting method for emergency services as described in any one of claims 1 to 48.

100. A chip, characterized in that, The chip includes programmable logic circuits and / or program instructions, and when the chip is running on the core network equipment, it is used to implement the priority setting method for emergency services as described in any one of claims 1 to 25.

101. A chip, characterized in that, The chip includes programmable logic circuits and / or program instructions, and when the chip is running on an access network device, it is used to implement the priority setting method for emergency services as described in any one of claims 26 to 48.

102. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium, from which a processor retrieves the computer instructions, and the processor and / or transceiver executes the computer instructions to implement the priority setting method for emergency services as described in any one of claims 1 to 48.