Communication method and device, storage medium and computer program product

Abstract

The embodiment of the invention provides a communication method and device, a storage medium and a computer program product. In the method, a network device reports first location information of a terminal device associated with an emergency service in response to establishing a proprietary path for data transmission for a first connection instance, the proprietary path being different from a default path established for the first connection instance prior to the proprietary path, where the first connection instance is associated with the emergency service. Therefore, in the embodiment of the invention, the latest position information of the terminal equipment can be reported in time in the emergency call process by implementing the method, and the accuracy and the real-time performance of user positioning are improved, so that the reliability and the timeliness of emergency rescue service are improved.

Description

Technical Field

[0001] The present disclosure generally relates to the field of communications, and more particularly, to a communication method, apparatus, computer-readable storage medium, and computer program product. Background Art

[0002] In an emergency, a terminal device can initiate an emergency call. The communications network then triggers a positioning process to report the user's location to the emergency service center. After the emergency call ends, if the default evolved packet system (EPS) bearer or default quality of service (QoS) flow is not released, the emergency call center will call back the user or the original caller. During this time, the user's location may have changed. As a result, the user's location information obtained by the emergency service center may not be the latest, which will affect subsequent rescue services. Summary of the Invention

[0003] The embodiments of the present disclosure provide a communication method, apparatus, computer-readable storage medium, and computer program product, which can enable timely reporting of the latest location information of terminal devices in emergency service scenarios, improve the accuracy and real-time performance of user positioning, and thus enhance the reliability and timeliness of emergency rescue services.

[0004] In the first aspect, a communication method is provided. The execution subject of the method provided in the first aspect may be a network device. The network device in the embodiment of the present disclosure may be a core network device or a component (such as a module, a module, a circuit or a chip, a chip system or a processor) in the core network device. The core network device or the component in the core network device may implement the network function of the core network. In this method, the network device reports the first location information of the terminal device associated with the emergency service in response to establishing a dedicated path for data transmission for the first connection instance. The dedicated path is different from the default path established for the first connection instance before the dedicated path, wherein the first connection instance is associated with the emergency service. In this way, the latest location information of the terminal device can be reported in a timely manner in the emergency service scenario, thereby improving the accuracy and real-time performance of user positioning, thereby improving the reliability and timeliness of emergency rescue services.

[0005] In some implementations, the first connection instance is a protocol data unit (PDU) session, the dedicated path is a dedicated QoS flow, and the default path is a default QoS flow. Alternatively, the first connection instance is a packet data network (PDN) connection, the dedicated path is a dedicated EPS bearer, and the default path is a default EPS bearer. In this way, for emergency service scenarios based on fourth-generation (4G) or fifth-generation (5G) networks, the latest user location information can be reported in a timely manner, improving the accuracy of user location data in the communication system and enhancing emergency rescue efficiency.

[0006] In some implementations, the network device determines that the first connection instance is associated with an emergency service based on the type information of the first connection instance stored in the user context. In this way, the user's location information is reported to the emergency service in the event of an emergency, thereby meeting the accuracy requirements for user positioning in emergency scenarios.

[0007] In some implementations, the network device determines that the established path is a dedicated path based on the value of a path identifier associated with the data transmission path established for the first connection instance. In this way, the establishment of a dedicated path can be identified, so that the location information of the terminal device is reported when the establishment of the dedicated path is triggered, thereby improving the accuracy and real-time performance of user positioning.

[0008] In some implementations, the value of the path identifier is 1. In this way, whether to initiate a user positioning process can be determined by identifying the value of the path identifier, thereby ensuring timely updating and reporting of user location information.

[0009] In some implementations, reporting the first location information of the terminal device includes: the network device sending a message for triggering a first positioning procedure, wherein the value of the first information element in the message indicates that the first positioning procedure is a modification of a second positioning procedure, the second positioning procedure being triggered based on the establishment of a default path and used to report the second location information of the terminal device. In this manner, the recipient of the positioning request message can be informed of the triggering reason for the first positioning procedure, thereby improving the relevance and efficiency of the positioning procedure processing.

[0010] In some implementations, the first positioning procedure is a network induced location request (NI-LR) positioning procedure, and the first information element is a location event information element.

[0011] In some implementations, the method of the first aspect is performed by an access and mobility management function (AMF) or a mobility management entity (MME).

[0012] In a second aspect, a communication device is provided, which has the function of implementing the behavior in the method example of the first aspect. The function can be implemented by hardware, or by hardware executing the corresponding software implementation. The hardware or software includes one or more modules corresponding to the above functions. The above description of the method of the first aspect is also applicable to the communication device of the second aspect, that is, the communication device of the second aspect can refer to the communication device itself, or it can refer to a component in the communication device (for example, a processor, a chip, or a chip system, etc.). In one possible design, the communication device includes a unit for executing the method of the first aspect or its implementation method. The beneficial effects of the communication device provided by the second aspect can be found in the description of the first aspect and will not be repeated here.

[0013] According to a third aspect, a device is provided, comprising a processor and a memory storing a computer program or instructions, wherein the computer program or instructions, when executed by the processor, causes the device to perform any method according to the first aspect and its implementation.

[0014] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are executed by an electronic device, the electronic device executes the methods in the above aspects.

[0015] In a fifth aspect, a computer program or a computer program product is provided. The computer program or the computer program product includes computer program instructions. When the computer instructions are executed by an electronic device, the electronic device executes the methods in the above aspects.

[0016] In a sixth aspect, embodiments of the present disclosure provide a chip system comprising a processor configured to implement the functions of the apparatus described in the methods of the aforementioned aspects. In one possible design, the chip system further comprises a memory configured to store computer programs, instructions, and / or data. The chip system may be comprised solely of a chip or may include a chip and other discrete components.

[0017] In a seventh aspect, an embodiment of the present disclosure further provides a communication system, comprising a network device for executing the method of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A schematic diagram of a system architecture to which the embodiments of the present disclosure may be applied is shown.

[0019] Figure 2 A communication flow diagram according to some embodiments of the present disclosure is shown.

[0020] Figure 3A 、 Figure 3B The combination of is a schematic diagram of a communication process according to some embodiments of the present disclosure.

[0021] Figure 4A and Figure 4B The combination of is a schematic diagram of a communication process according to some other embodiments of the present disclosure.

[0022] Figure 5 A schematic diagram showing an example process implemented in a communication device according to an embodiment of the present disclosure is shown.

[0023] Figure 6 is a block diagram of a device that can be used to implement some embodiments of the present disclosure.

[0024] Figure 7 is a schematic structural diagram of an apparatus according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0025] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the embodiments of the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Instead, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0026] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to." The term "based on" should be understood as "based at least in part on." The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment." The terms "first," "second," etc. may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0027] In the emergency service scenario, the terminal device can initiate an emergency call, and the communication network will trigger the positioning process accordingly to report the user's location information to the emergency service center. In some solutions, the AMF initiates the NI-LR positioning process in the emergency protocol data unit PDU session establishment process. When the user plane function (UPF) reports that the PDU session is inactive within the specified time, the session management function (SMF) initiates the release of the emergency PDU session. In the scenario where the user's emergency call ends and the default bearer is not released, the emergency call center calls back the user or the user initiates the call, the SMF initiates the PDU session modification process and establishes a dedicated bearer. At this time, the AMF does not trigger the NI-LR positioning process and does not report the user's latest location information in a timely manner. Based on the above analysis, the above solution cannot report the user's latest location information in a timely manner in the emergency service scenario, which may affect subsequent emergency rescue services.

[0028] To this end, the embodiments of the present disclosure provide a communication method, which can ensure the timely reporting or updating of the user's latest location information in emergency service scenarios, improve the accuracy of user positioning, ensure the smooth implementation of emergency service-related rescue work, and improve service efficiency.

[0029] Figure 1 A schematic diagram of a system architecture to which the present disclosure embodiment can be applied is shown. Figure 1 The illustrated communication system 100, such as a 4G communication system, a 5G communication system, or a future communication system, may include a terminal device 110 and an access network device 120. The terminal device 110 may be located within a service area 130 of the access network device 120. The communication system 100 may also include a core network 140, which may include a number of core network devices (or core network nodes, or core network elements, or network functions). The access network device 120 and core network devices mentioned in the embodiments of the present disclosure may also be collectively referred to as network devices. In some examples, the location information of the terminal device 110 may be obtained through interaction between the access network device 120 and one or more core network devices. The core network device in the communication system 100 may report the location information of the terminal device 110 to a third-party system. For example, in emergency services, the third-party system may be an emergency service center. The emergency service center is, for example, a service platform that provides emergency communication and dispatch services to users.

[0030] The terminal device 110 mentioned in the embodiments of the present disclosure includes various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication functions, and can specifically refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device 110 may also be a satellite phone, a cellular phone, a smartphone, a wireless data card, a wireless modem, a machine type communication device, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device or a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a terminal device 110 in a 5G network or a future communication network, etc. The terminal device 110 may also be a communication module with satellite communication capabilities, a satellite phone, or a component thereof, or a satellite communication terminal, such as a very small aperture terminal (VSAT) (commonly referred to as a VSAT terminal), a portable station, a fixed station, or a vehicle-mounted or aircraft-mounted satellite communication terminal. It should be understood that a satellite communication terminal may function as a micro base station to further provide a data interface to connected user equipment.

[0031] The access network device 120 mentioned in the embodiments of the present disclosure may also be referred to as a radio access network (RAN) node, etc. The access network device 120 may be a device with base station functions, such as an evolved NodeB (eNodeB), a transmission and receiving point (TRP), a transmission point (TP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an integrated access and backhaul (IAB) node. The access network device 120 may be a transmission reception point (TRP), a base station, or various forms of control nodes, such as a network controller or a wireless controller. Specifically, the access network device 120 can be various forms of macro base stations, micro base stations (also known as small stations) in heterogeneous network (HetNet) scenarios, relay stations, access points (APs), radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved node Bs or home node Bs, HNBs), baseband units (BBUs) and remote radio units (RRUs) in distributed base station scenarios, transmission points (TRPs), transmitting points (TPs), mobile switching centers, etc. It can also be a base station antenna panel. The control node can connect to multiple base stations and configure resources for multiple terminals covered by the multiple base stations. The access network device 120 may also be a satellite (or satellite base station), a high altitude platform station (HAPS), an unmanned aerial vehicle (UAV), or a base station device mounted on a satellite / HAPS / UAV.The satellite may include at least one of the following: a geostationary Earth orbit (GEO) satellite (also known as a geosynchronous orbit satellite) or a non-geostationary Earth orbit (NGEO). A non-geostationary Earth orbit satellite may include at least one of the following: a medium Earth orbit (MEO) satellite or a low Earth orbit (LEO) satellite. This is not a limitation. The access network device 120 may also be a gateway (also known as a ground station, earth station, gateway, or gateway station). In systems using different wireless access technologies, the name of the device with base station functionality may vary. For example, it may be a gNB in ​​5G, or an access network device 120 in a network beyond 5G, or a device in a future-evolved public land mobile network (PLMN), or a device that performs base station functions in device-to-device (D2D) communication, machine-to-machine (M2M) communication, or Internet of Vehicles communication. This application does not limit the specific name of the access network device 120. The access network device 120 may also be a baseband pool (BBU pool) and RRU in an open radio access network (open RAN, or ORAN) or a cloud radio access network (CRAN).

[0032] The core network 140, as a bearer network, provides an interface to the data network, offering communication connectivity, authentication, management, policy control, and data service bearering for user equipment (UE). The core network devices mentioned in the embodiments of the present disclosure can be used to provide core network services for the access network device 120 and the terminal device 110. Core network devices can correspond to different devices in different systems. For example, in the third generation (3G) system, core network devices can correspond to the serving GPRS support node (SGSN) and / or the gateway GPRS support node (GGSN) of the general packet radio system (GPRS). In 4G, core network equipment may correspond to the MME, serving gateway (S-GW), policy and charging rules function (PCRF), packet data network gateway (P-GW), home subscriber server (HSS), session border controller / proxy-call session control function (SBC / P-CSCF), and gateway mobile location center (GMLC). In 5G, core network equipment may correspond to the AMF, session management function (SMF), policy control function (PCF), user plane function (UPF), unified data management function (UDM), SBC / P-CSCF, location management function (LMF), and GMLC. The AMF network element is used to manage the access and mobility of terminal devices 110 (e.g., UEs), and is primarily responsible for UE authentication, UE mobility management, UE paging, and other functions.

[0033] The access network device 120 may also include, but is not limited to, an evolved node B (eNB), a baseband unit (BBU), an access point (AP) in a wireless fidelity (WIFI) system, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission reception point (TRP). The access network device 120 may also be a gNB, TRP, or TP in a 5G system, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system. Furthermore, the access network device 120 may also be a network node that constitutes a gNB or TP, such as a BBU or a distributed unit (DU). Alternatively, the access network device 120 may be a device that performs network-side functions in a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT), an Internet of Vehicles (IoV) communication system, or other communication systems.

[0034] The methods provided in the embodiments of the present disclosure can be applied to various communication systems, such as wireless local area networks (WLANs), Internet of Things (IoT), narrowband Internet of Things (NB-IoT), long-term evolution (LTE), 5G, new radio (NR), or new communication systems emerging in future communications developments. The embodiments of the present disclosure can also be applied to non-terrestrial network (NTN) systems, such as satellite communication systems, high altitude platform station (HAPS) communications, and drones, including integrated communication and navigation (ICaN) systems, global navigation satellite systems (GNSS), and ultra-dense low-orbit satellite communication systems. NTN systems can be integrated with traditional mobile communication systems. For example, the mobile communication system may be a 4G communication system (e.g., LTE system), a worldwide interoperability for microwave access (WiMAX) communication system, a 5G communication system (e.g., NR system), and future mobile communication systems such as NR NTN and IoT NTN.

[0035] Embodiments of the present disclosure may be implemented in accordance with any suitable communication protocol, including but not limited to 3G, 4G, 5G, or future cellular communication protocols, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or developed in the future. The technical solutions of the embodiments of the present disclosure are applied to communication systems that comply with any appropriate communication protocols, such as: GPRS, global system for mobile communications (GSM), enhanced data rate for GSM evolution (EDGE), universal mobile telecommunications system (UMTS), LTE system, Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access 2000 (CDMA2000), Time Division-Synchronization Code Division Multiple Access (TD-SCDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), fifth generation system or NR, other generations of communication systems evolved in the future, and the like.

[0036] Figure 2 FIG. 1 shows a communication flow diagram according to some embodiments of the present disclosure. Figure 2 As shown, process 200 involves a network device 210 and a first device 220. In some examples, the network device 210 may be a core network device, and illustratively, the network device 210 may be an AMF. The first device 220 may be another core network device that interacts with the network device 210. In an emergency service scenario, the other core network device may be used to further report the location information of the terminal device reported by the network device 210 to an emergency service provider, such as an emergency call center. Process 200 may also involve Figure 2 In some examples, the network device 210 and the first device 220 may interact via one or more other core network devices. Figure 1, the core network device may be located in the core network 140. In some examples, the process 200 may also involve an access network device (see Figure 1 An example of a terminal device may be an access network device 120. Figure 1 The terminal device 110, such as UE. In each example of the embodiment of the present disclosure, the core network device can be replaced by a core network network element, a core network node, or a network function of the core network. The embodiment of the present disclosure is mainly described by taking the 4G or 5G communication scenario as an example. For example, in the 4G communication scenario, an example of the network device 210 can be an AMF. In the 5G communication scenario, an example of the network device 210 can be an MME. An example of the first device 220 in the 4G or 5G communication scenario can be a GMLC. It should be noted that the embodiment of the present disclosure can also be applied to the communication scenarios of future networks (such as 6G or above). In the communication scenarios of future networks (such as 6G or above), the names of the corresponding network elements and the names of the messages exchanged between network elements can be adaptively changed, and various changes fall within the protection scope of the embodiment of the present disclosure.

[0037] In process 200, at 201, network device 210 reports location information 212 of a terminal device associated with an emergency service (referred to as first location information) in response to establishing a dedicated path for data transmission for a first connection instance. The dedicated path is different from a default path previously established for the first connection instance, and the first connection instance is associated with the emergency service. In some examples, the emergency service may include various services related to emergency rescue or other emergency situations. A call initiated by a terminal device in an emergency service scenario may be referred to as an emergency call.

[0038] In some examples, the first connection instance is a PDU session, the dedicated path is a dedicated QoS flow, and the default path is a default QoS flow. Such examples can be applied to 5G communication scenarios. In other examples, the first connection instance is a PDN connection, the dedicated path is a dedicated EPS bearer, and the default path is a default EPS bearer. Such examples can be applied to 4G communication scenarios. For communication scenarios in future networks (e.g., 6G or above), the first connection instance, dedicated path, and default path can be replaced with corresponding terms in the corresponding network.

[0039] The first connection instance can be established after the terminal device sends a request to establish the first connection instance to the network device 210. The establishment process of the first connection instance involves interaction between multiple network elements or network functions of the core network, for example, referring to the conventional establishment process of the PDN connection in 4G, or the conventional establishment process of the PDU session in 5G. The embodiment of the present disclosure does not provide specific explanations.

[0040] In some examples, network device 210 may determine that the first connection instance is associated with an emergency service based on type information of the first connection instance stored in the user context. For example, after receiving a request from a terminal device to establish a first connection instance, network device 210 may store the type information of the request in the user context. The type information indicates that the first connection instance is a connection instance associated with an emergency service.

[0041] In some examples, a default path for data transmission of the first connection instance is established first. For example, in the 4G communication scenario of the embodiment of the present disclosure, a default EPS bearer is established first. In the 5G communication scenario of the embodiment of the present disclosure, a default QoS flow is established first. In some examples, after the default path for data transmission of the first connection instance is established, the network device 210 can trigger a positioning process (referred to as a second positioning process) to report the location information of the terminal device associated with the emergency service (referred to as the second location information). For example, in the case where the terminal device initiates an emergency call, the default path is established. Based on the establishment of the default path, the network device 210 will trigger the second positioning process to report the second location information of the terminal device at this time.

[0042] In some examples, a dedicated path is established after the default path. For example, in the 4G communication scenario of the embodiment of the present disclosure, a dedicated EPS bearer is established when the default EPS bearer is established. In the 5G communication scenario of the embodiment of the present disclosure, a dedicated QoS flow is established after the default QoS flow is established. After the dedicated path for data transmission of the first connection instance is established, the network device 210 will also trigger the positioning process (referred to as the first positioning process) again to report the latest location information of the terminal device (i.e., the first location information 212). For example, in a scenario where the emergency call initiated by the terminal device ends and the default path is not released, when the emergency call center calls back the terminal device or the terminal device initiates a call again, the dedicated path is established. Based on the establishment of the dedicated path, the network device 210 will trigger the first positioning process to report the first location information 212 of the terminal device at this time. Taking into account the movement of the terminal device or other situations, the first location information 212 is the latest location information of the terminal device relative to the second location information, and the locations of the terminal device indicated by the two may be different.

[0043] As described above, in response to the establishment of a dedicated path for data transmission of the first connection instance, the network device 210 triggers the first positioning process. Therefore, before reporting the first location information 212 of the terminal device, the network device 210 may first determine that the path for data transmission established for the first connection instance is a dedicated path. For example, the network device 210 may determine that the established path is a dedicated path based on the value of a path identifier associated with the path for data transmission established for the first connection instance. In some examples, the established path is determined to be a dedicated path when the value of the path identifier is 1. For example, in an example where the first connection instance is a QoS flow, the path identifier is, for example, a 5G quality of service identifier (5QI), which, when set to 1, indicates that the path for data transmission is a dedicated path. The message carrying the 5QI may be a PDU session resource modification request (SESSION RESOURCE MODIFY REQUEST), which will be described in detail in process 400 below. In the example where the first connection instance is an EPS bearer, when the quality of service class identifier (QCI) has a value of 1, it indicates that the path for data transmission is a dedicated path. The message carrying the QCI may be a Create Bearer Request, which will be described in detail in process 300 below.

[0044] In some examples, when reporting the first location information 212 of the terminal device, the network device 210 sends a message for triggering a first positioning procedure, the message including a first information element. In some examples, the value of the first information element indicates that the first positioning procedure is a modification of a second positioning procedure. As described above, the second positioning procedure is triggered based on the establishment of a default path and is used to report the second location information of the terminal device. The first positioning procedure is used to report the first location information 212 of the terminal device. The first location information 212 is updated location information of the second location information, i.e., the latest location information.

[0045] In some examples, the first positioning procedure and the second positioning procedure are NI-LR positioning procedures, and the first information element is a location event information element, such as a location event (LocationEvent) information element. For example, in the second positioning procedure that is triggered first, the value of the location event information element is, for example, emergency call initiation (EMERGENCY_CALL_ORIGINATION), which indicates the initial NI-LR positioning procedure for the emergency call. In the first positioning procedure that is triggered later, the value of the location event information element is, for example, emergency call modification (EMERGENCY_CALL_MODIFICATION), which indicates a modification of the initial NI-LR positioning procedure for the emergency call. Alternatively, in some examples, the first positioning procedure can reuse the value of the location event information element of the second positioning procedure, that is, the value of the location event information element in both the first positioning procedure and the second positioning procedure is EMERGENCY_CALL_ORIGINATION.

[0046] Based on the various examples of the above process, network device 210 can promptly report the latest location information of the terminal device in an emergency service scenario, improving the accuracy and real-time performance of user positioning, thereby enhancing the reliability and timeliness of emergency rescue services. This avoids reduced rescue efficiency due to untimely location information updates, and improves the reliability and timeliness of emergency assistance services.

[0047] Figure 3A and Figure 3B The processing flow of the embodiment of the present disclosure in the 4G communication scenario is shown in combination, wherein Figure 3B yes Figure 3A The continuation of Figure 3A and Figure 3B Each of the steps includes part of the steps of process 300, and the two together constitute the complete process 300. Process 300 involves a terminal device 301, an eNodeB 302, an MME 303, an S-GW 304, a PCRF 305, a P-GW 306, an HSS 307, an SBC / P-CSCF 308, and a GMLC 309. The terminal device 301 may be an example of the terminal device 110. The eNodeB 302 may be an example of the access network device 120 or an example of the access network device mentioned in process 200. The MME 303 may be an example of the network device 210. The GMLC 309 may be an example of the first device 220. Figure 1, MME 303 , S-GW 304 , PCRF 305 , P-GW 306 , HSS 307 , SBC / P-CSCF 308 , and GMLC 309 may be located in the core network 140 . In some examples, MME 303 can be used for access and mobility management, responsible for user access control, authentication and mobility management; S-GW 304 can be used for user plane data forwarding, responsible for forwarding and caching of user data between the base station and the core network; PCRF 305 can be used for policy control, responsible for the formulation and issuance of policies and charging rules; P-GW 306 can be used for data export gateway, responsible for IP address allocation, data forwarding and intercommunication with external packet data networks for user data; HSS 307 can be used for home user subscription data management, responsible for the storage and provision of user identity information, authentication information and service subscription data; SBC / P-CSCF 308 can be used for session control, responsible for signaling control and security management of IMS services such as voice; GMLC 309 can be used for gateway mobile positioning, responsible for connecting to external applications and reporting location information to emergency service centers, etc.

[0048] In process 300, at step 311, terminal device 301 sends a PDN connection establishment request message 312 to MME 303. The message includes type information. The type information may include request type information indicating that the PDN connection establishment request message is an initial emergency request. Alternatively, the type information may include PDN connection type information. The PDN connection is hereinafter referred to as an emergency PDN connection. MME 303 receives PDN connection establishment request message 312.

[0049] In 313 , the MME 303 stores the type information. For example, the type information is stored in the user context. The type information is associated with the identifier of the emergency PDN connection, and the identifier of the emergency PDN connection indicates that the emergency PDN connection is associated with emergency services.

[0050] At 315, a default EPS bearer is established. The process of establishing a default EPS bearer involves the interaction of multiple network elements, including, but not limited to, terminal device 301, eNodeB 302, MME 303, S-GW 304, PCRF 305, P-GW 306, HSS 307, and SBC / P-CSCF 308. The specific process of establishing a default EPS bearer can follow the conventional process of establishing a default EPS bearer in 4G, which is not described in detail in this invention. Alternatively, 313 and 315 can be performed simultaneously.

[0051] At 317, MME 303 triggers a positioning procedure, such as a NI-LR procedure (an example of a second positioning procedure), to report the location information of terminal device 301 to GMLC 309. The specific implementation of MME 303 obtaining the location information of terminal device 301 can be referenced to the conventional implementation of MME 303 obtaining the location of a terminal device during an emergency call, and is not described in detail in this embodiment. In some examples, MME 303 may report the location information of terminal device 301 to GMLC 309 via one or more other core network elements. Accordingly, GMLC 309 receives the location information of terminal device 301 from MME 303. During the NI-LR procedure in this step, MME 303 sends a second Subscriber Location Report message 322 to GMLC 309 to notify the user of the current location information. Second Subscriber Location Report message 322 includes a Location Event Information Element (LOIIE), and the value of the LOCIE is EMERGENCY_CALL_ORIGINATION.

[0052] At 319, a first dedicated EPS bearer is established. When terminal device 301 hangs up the call, the first dedicated EPS bearer is released, as shown in 321. The network elements involved in executing operations 319 and 321 may include terminal device 301, eNodeB 302, MME 303, S-GW 304, PCRF 305, P-GW 306, HSS 307, and SBC / P-CSCF 308. For details, reference may be made to conventional methods for establishing a dedicated bearer based on a default bearer and releasing a dedicated EPS bearer in 4G scenarios, which will not be described in detail in the present invention.

[0053] After 321, SBC / P-CSCF 308 sends an authentication authorization response (AAR) to PCRF 305, and PCRF 305 receives the AAR response returned by SBC / P-CSCF 308. Figure 3A Not shown. Figure 3B At 323 , PCRF 305 sends a re-authentication request (RAR) 332 to P-GW 306 to trigger dedicated bearer establishment.

[0054] At 325 , P-GW 306 sends a Create Bearer Request message 342 to S-GW 304 to notify the establishment of a dedicated bearer. At 327 , Create Bearer Request message 342 is further sent to MME 303 , which receives the Bearer Request message 342 sent by S-GW 304 .

[0055] At 329, MME 303 identifies the current PDN connection as an emergency PDN connection and determines that the currently established EPS bearer is a dedicated EPS bearer. Specifically, MME 303 combines Create Bearer Request message 342 (e.g., the EPS bearer identifier (eps-bearer-id) information element therein) with type information stored in the user context (e.g., request type information or PDN connection type information) to determine that the current PDN connection is an emergency PDN connection. If Create Bearer Request message 342 indicates that the QCI is 1, MME 303 identifies the process as a dedicated bearer establishment procedure.

[0056] At 331, MME 303 triggers the NI-LR procedure (an example of the first positioning procedure) and sends a first Subscriber Location Report message 352 to GMLC 309 to notify the user of the current location information. This first Subscriber Location Report message 352 includes a Location Event Information Unit (LOU) with a newly added enumeration value, specifically EMERGENCY_CALL_MODIFICATION, to distinguish it from the previously existing EMERGENCY_CALL_ORIGINATION. EMERGENCY_CALL_MODIFICATION identifies the NI-LR procedure currently triggered in 331 as a modification of the NI-LR procedure triggered in step 317. Because the first positioning procedure is based on a modification of the second positioning procedure, some of the existing parameters, configurations, or information in the second positioning procedure can also be applied to the first positioning procedure, saving the overhead of establishing a new positioning procedure.

[0057] Process 300 may also include subsequent steps (not shown). For example, MME 303 may send a Bearer Setup Request message to eNodeB 302, instructing eNodeB 302 to establish voice E-RAB resources. eNodeB 302 may send a Bearer Setup Response message to MME 303 to confirm that the bearer has been activated. MME 303 may then send a Create Bearer Response message to S-GW 304 to confirm the bearer activation. S-GW 304 may further send a Create Bearer Response message to P-GW 306 to confirm the bearer activation.

[0058] Combine Figure 3A and Figure 3B In the illustrated process 300, after the first dedicated EPS bearer is released, if the default EPS bearer corresponding to the first emergency PDN connection is not released, if the terminal device 301 is called back or the terminal device 301 initiates a call again, the establishment of the dedicated EPS bearer corresponding to the first emergency PDN connection will be triggered again, and the MME 303 can initiate the positioning process again to report the location information of the terminal device 301 again. Since there is usually a certain time interval between the establishment of two dedicated EPS bearers, the location of the terminal device 301 changes during this period. The latest location information of the terminal device 301 can be reported in a timely manner, thereby enabling the dynamic update of the location information of the terminal device 301 during the emergency call process, thereby improving the accuracy and real-time performance of user positioning, and further improving the reliability and timeliness of emergency rescue services.

[0059] Figure 4A 、 Figure 4B The combined process of FIG. 1 and FIG. 2 shows the processing flow in the 5G communication scenario according to the present disclosure. Figure 4A and 4B As shown, Figure 4A and 4BEach of the two steps includes partial steps of process 400, and the two together constitute the complete process 400. Process 400 involves terminal device 401, next generation radio access network (NG-RAN) 402, AMF 403, SMF 404, PCF 405, UPF 406, UDM 407, SBC / P-CSCF 408, LMF 409, and GMLC 410. Terminal device 401 may be an example of terminal device 110. NG-RAN 402 may be an example of access network device 120 or the access network device mentioned in process 200. AMF 403, SMF 404, PCF 405, UPF 406, UDM 407, SBC / P-CSCF 408, LMF 409, and GMLC 410 may be located in core network 140. Among them, AMF 403 is used for access and mobility management, responsible for user access, registration and mobility control; SMF 404 is used for session management, responsible for session establishment, modification and release; PCF405 is used for policy control, responsible for policy-based resource allocation and QoS management; UPF 406 is used for user plane data forwarding, responsible for forwarding and processing data packets; UDM 407 is used for unified data management, responsible for the storage and management of user subscription data and authentication information; SBC / P-CSCF 408 is used for session control, responsible for signaling control and security management of voice and other services; LMF 409 is used for positioning management, responsible for obtaining and processing terminal locations; GMLC 410 has the same functions as GMLC 309.

[0060] In process 400, at 411, terminal device 401 sends a PDU session establishment request message 412 to AMF 403. Accordingly, AMF 403 receives PDU session establishment request message 412 from terminal device 401. PDU session establishment request message 412 carries type information, which may be request type information indicating that the PDU session establishment request is an initial emergency request. Alternatively, the type information may be PDU session type information. This PDU session is an emergency PDU session.

[0061] In 413, AMF 403 stores the type information. The type information is stored in the user context, for example, and the type information is associated with the identifier of the emergency PDU session, and the identifier of the emergency PDU session indicates that the PDU session is associated with the emergency service.

[0062] At 415, a default QoS flow is established. This process involves the interaction of multiple network elements, including, but not limited to, terminal device 401, NG-RAN 402, AMF 403, SMF 404, PCF 405, UPF 406, UDM 407, and SBC / P-CSCF 408. The establishment of the default QoS flow can follow the conventional process for establishing a default QoS flow in 5G, which will not be described in detail in this disclosure. Alternatively, 413 and 415 can be performed simultaneously.

[0063] After the default QoS flow establishment process for the emergency PDU session is completed, AMF 403 initiates an emergency location procedure (e.g., the NI-LR process, an example of a second location procedure) based on local configuration at 417. AMF 403 sends a Location Event Notification (Namf_Location_EventNotify) message (referred to as second Location Notification message 422) to GMLC 410 to notify terminal device 401 of its current location information (i.e., second location information). Second Location Notification message 422 includes a Location Event Information Element (IE), whose value is EMERGENCY_CALL_ORIGINATION. The specific implementation of AMF 403 obtaining terminal device 401's location information can be referenced to the conventional implementation of AMF 403 obtaining terminal device location during an emergency call, and is not described in detail in this embodiment. In some examples, AMF 403 may report terminal device 401's location information to GMLC 410 via one or more other core network elements. Accordingly, GMLC 410 receives the location information of terminal device 401 from AMF 403.

[0064] At 419, a first dedicated QoS flow is established. When terminal device 401 hangs up the call, the first dedicated QoS flow is released, as shown in 421. The network elements involved in executing operations 319 and 321 may include several network elements in terminal device 401, NG-RAN 402, AMF 403, SMF 404, PCF 405, UPF 406, UDM 407, and SBC / P-CSCF 408. For details, please refer to the conventional method of establishing and releasing dedicated QoS flows in 5G scenarios, which will not be described in detail in this invention.

[0065] In the scenario where the emergency call center calls back terminal device 401 or terminal device 401 initiates a call, SBC / P-CSCF 408 initiates a request to PCF 405 to establish a dedicated QoS flow. For example, at 423, SBC / P-CSCF 408 sends a second dedicated QoS flow establishment request message 432 to PCF 405. At 425, PCF 405 sends a session management policy control update notification request (e.g., Npcf_SMPolicyControl_UpdateNotify request) 442 to SMF 404 to notify SMF 404 to create a voice-dedicated QoS flow.

[0066] At 427, SMF 404 sends a first message 452 (eg, Namf_Communication_N1N2MessageTransfer request message) including a PDU session identifier (pduSessionId) information element to AMF 403. AMF 403 receives the first message 452. The pduSessionId information element indicates the PDU session ID.

[0067] At 429, AMF 403 combines the pduSessionId information element in the first message 452 (e.g., Namf_Communication_N1N2MessageTransfer request message) and the type information saved in the user context (e.g., request type information or PDU session type information) to determine that the current PDU session is an emergency PDU session, and parses the PDU session resource modification request (PDU SESSION RESOURCE MODIFY REQUEST) content carried in the first message 452. If the 5QI obtained from the parsing result is equal to 1, the current QoS flow is identified as a dedicated bearer establishment process.

[0068] At 431, the AMF 403 triggers the NI-LR procedure (an example of the first positioning procedure). For example, the AMF 403 sends a first location event notification (Namf_Location_EventNotify) message (referred to as the first location notification message 462) to the GMLC 410 to notify the terminal device 401 of its current location information (the first location information). Specifically, the first location notification message 462 includes a location event information element. The value of the location event information element is newly added with the enumeration value EMERGENCY_CALL_MODIFICATION (used to indicate that the current NI-LR procedure is a modification of the NI-LR procedure in step 417), to distinguish it from the location event information element enumeration value EMERGENCY_CALL_ORIGINATION in the second location notification message 422 sent in the second positioning procedure in step 417. The first location information reported in the first positioning procedure updates the second location information reported in the second positioning procedure.

[0069] Process 400 may also include subsequent steps (not shown), such as AMF 403 sending a PDU Session Resource Modification Request message to NG RAN 402 to notify the NG RAN to establish voice QoS flow resources (step 11). NG RAN 402 sends a PDU Session Resource Modification Response (PDUSession Resource Modification Response) to AMF 403, which contains N2 session management (N2 SM) information confirming the PDU session resource modification result. AMF 403 sends an Nsmf_PDUSession_UpdateSMContext request to SMF 404, which carries the N2 SM information sent by NG RAN 402 (step 13).

[0070] Combine Figure 4A and Figure 4BIn the process shown, after the first dedicated QoS flow is released, if the default QoS flow corresponding to the first emergency PDU session is not released, if the terminal device 401 is called back or the terminal device 401 initiates a call again, the establishment of the dedicated QoS flow corresponding to the emergency PDU session will be triggered again. The AMF 403 of the embodiment of the present disclosure can initiate the positioning process again to report the location information of the terminal device 401 again. Since there is usually a certain time interval between the establishment of two dedicated QoS flows, the location of the terminal device 401 changes during this period. The latest location information of the terminal device 401 can be reported in a timely manner, thereby achieving dynamic update of the location information of the terminal device 401 during the emergency call process. This ensures that in the emergency service scenario, the party that needs to know the location information of the terminal device 401 (such as the emergency call center) obtains the latest location of the terminal device 401, thereby improving the accuracy and real-time performance of user positioning, and further improving the reliability and timeliness of emergency rescue services.

[0071] Figure 5 A schematic diagram of an example process implemented at a communication device according to an embodiment of the present disclosure is shown. As shown in Figure 5, process 500 can be executed by a communication device. In some embodiments, the communication device that executes process 500 can be a network device 210, an AMF 403, or an MME 303. In box 510, the communication device reports the first location information of the terminal device associated with the emergency service in response to establishing a dedicated path for data transmission for the first connection instance, and the dedicated path is different from the default path established for the first connection instance before the dedicated path, wherein the first connection instance is associated with the emergency service. In some embodiments, process 500 may also include combining the embodiment of the present disclosure with the default path. Figure 2 、 Figure 3A 、 Figure 3B 、 Figure 4A 、 Figure 4B Other operations performed at a network device, AMF, or MME as described in one or some examples.

[0072] Figure 66 is a block diagram of a device 600 that can be used to implement some embodiments of the present disclosure. In some embodiments, the device 600 can be an element of a communication network infrastructure, such as a base station (e.g., NodeB, evolved NodeB (eNodeB or eNB), next generation NodeB (sometimes referred to as next generation NodeB, gNodeB or gNB), a home subscriber server (HSS), a gateway (GW), such as a packet gateway (PGW) or a serving gateway (SGW), or various other nodes or functions within a core network (CN, which can communicate with UEs through base stations) or a public land mobile network (PLMN). In other embodiments, the device 600 can be a device connected to the network infrastructure via a wireless interface, such as a mobile phone, a smart phone, or other such device that can be classified as a user equipment (UE). In some embodiments, the device 600 can be a machine type communication (MTC) device. In some embodiments, the device 600 may be a road side unit (RSU), a vehicle UE (V-UE), a pedestrian UE (P-UE), or an infrastructure UE (I-UE). In some scenarios, the device 600 may also be referred to as a mobile device, which term is intended to reflect a device that is connected to a mobile network, regardless of whether the device itself is designed for or capable of movement. A specific device may utilize all of the components shown or only a subset of the components, and the level of integration may vary from device to device. In addition, the device 600 may include multiple instances of components, such as multiple processors, memories, transmitters, receivers, and the like.

[0073] Device 600 generally includes a processor 602, such as a central processing unit (CPU), and may further include a special-purpose processor, such as a graphics processing unit (GPU) or other such processor, memory 604, a network interface 606, and a bus 608 to connect the components of device 600. Optionally, device 600 may also include components such as mass storage 610, a video adapter 612, and an I / O interface 616 (shown in dashed lines).

[0074] Memory 604 may include any type of non-transitory system memory readable by processor 602, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or a combination thereof. In one embodiment, memory 604 may include more than one type of memory, such as ROM used at boot time and DRAM used for program and data storage during program execution. Bus 608 may be one or more of any type of bus architecture, including a memory bus or memory controller, a peripheral bus, or a video bus. In some examples, memory 604 and processor 602 may be separate devices. In other examples, memory 604 may be integrated with processor 602 as a single device.

[0075] The device 600 may also include one or more network interfaces 606, which may include at least one of a wired network interface and a wireless network interface. Figure 6 As shown, network interface 606 may include a wired network interface for connecting to network 622 and may also include a wireless access network interface 620 for connecting to other devices via wireless links. When device 600 is a network infrastructure element, wireless access network interface 620 may be omitted for nodes or functions that are elements of the PLMN rather than elements at the wireless edge. When device 600 is infrastructure at the wireless edge of a network, both wired and wireless network interfaces may be included. When device 600 is a wirelessly connected device, such as a user device, wireless access network interface 620 may be present and may be supplemented by other wireless interfaces, such as a Wi-Fi network interface. Network interface 606 allows device 600 to communicate with remote entities, such as those connected to network 622.

[0076] The mass storage 610 may include any type of non-transitory storage device configured to store data, programs, and other information and make the data, programs, and other information accessible via the bus 608. The mass storage 610 may include, for example, one or more of a solid-state drive, a hard disk drive, a magnetic disk drive, or an optical disk drive. In some embodiments, the mass storage 610 may be remote from the device 600 and may be accessed using a network interface such as the interface 606. In the illustrated embodiment, the mass storage 610 is different from the memory 604 comprising it, and the mass storage 610 may typically perform storage tasks compatible with higher latency, but may typically provide less or no fluctuation. In some embodiments, the mass storage 610 may be integrated with the memory 604.

[0077] An optional video adapter 612 and an I / O interface 616 (shown in dashed lines) provide interfaces for coupling device 600 to external input and output devices. Examples of input and output devices include a display 614 coupled to video adapter 612 and an I / O device 618, such as a touch screen, coupled to I / O interface 616. Other devices may be coupled to device 600, and additional or fewer interfaces may be utilized. For example, a serial interface such as a Universal Serial Bus (USB) (not shown) may be used to provide an interface for external devices. Those skilled in the art will appreciate that in embodiments where device 600 is part of a data center, I / O interface 616 and video adapter 612 may be virtualized and provided via network interface 606.

[0078] Figure 7 FIG. 7 is a schematic diagram of the structure of the device 700 according to some embodiments of the present application. Figure 7 As shown, the apparatus 700 includes a reporting unit 702. The apparatus 700 can be applied to Figure 1The communication scenario shown in the figure can implement the methods provided in the above embodiments, such as method 500. Optionally, the physical form of the device 700 can be a communication device, such as a network device. The network device can be a core network device or a network function of the core network. Alternatively, the device 700 can be a device suitable for implementing the corresponding network function in the core network device, such as a module, processor or chip. Specifically, the device 700 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC). It can also be a logical node, logic module or software that can implement all or part of the functions of the communication device.

[0079] In some embodiments, the reporting unit 702 can be configured to report the first location information of the terminal device associated with the emergency service in response to establishing a dedicated path for data transmission for the first connection instance, where the dedicated path is different from the default path established for the first connection instance before the dedicated path, wherein the first connection instance is associated with the emergency service.

[0080] In some other embodiments, the apparatus 700 may include various other units or modules, which may be configured to perform various operations or functions described in relation to the aforementioned method embodiments. Specific details may be obtained by referring to the detailed description of the aforementioned method embodiments, which will not be repeated herein.

[0081] In some other embodiments, the apparatus 700 may include various other units or modules, which may be configured to perform various operations or functions described in relation to the aforementioned method embodiments. Specific details may be obtained by referring to the detailed description of the aforementioned method embodiments, which will not be repeated herein.

[0082] It should be noted that the division of modules in the above embodiments of the present disclosure is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or may exist physically as separate units, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0083] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can essentially or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0084] Based on the above embodiments, an embodiment of the present disclosure further provides a computer program, which, when executed on a computer, enables the computer to execute any of the methods provided in the above embodiments.

[0085] Based on the above embodiments, the embodiments of the present disclosure further provide a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a computer, the computer performs any of the methods provided in the above embodiments. The storage medium can be any available medium that can be accessed by a computer. By way of example but not limitation, the computer-readable medium may include RAM, ROM, Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disk storage, magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0086] Based on the above embodiments, an embodiment of the present disclosure further provides a chip, which is used to read a computer program stored in a memory and implement any of the methods provided in the above embodiments.

[0087] Based on the above embodiments, embodiments of the present disclosure provide a chip system that includes a processor for supporting a computer device in implementing the functions involved in each communication device in the above embodiments. In one possible design, the chip system also includes a memory for storing the necessary programs and data for the computer device. The chip system can be composed of a chip alone or can include a chip and other discrete devices.

[0088] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0089] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0090] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0091] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

Claims

1. A communication method, characterized in that: include: In response to establishing a dedicated path for data transmission for the first connection instance, reporting first location information of a terminal device associated with the emergency service, the dedicated path being different from a default path established for the first connection instance before the dedicated path, The first connection instance is associated with the emergency service.

2. The method according to claim 1, characterized in that The first connection instance is a protocol data unit (PDU) session, the dedicated path is a dedicated quality of service (QoS) flow, and the default path is a default QoS flow; or The first connection instance is a packet data network PDN connection, the dedicated path is a proprietary evolved packet system EPS bearer, and the default path is a default EPS bearer.

3. The method according to claim 1, characterized in that Also includes: Based on the type information of the first connection instance stored in the user context, it is determined that the first connection instance is associated with the emergency service.

4. The method according to claim 1, wherein Also includes: The established path is determined to be the dedicated path based on a value of a path identifier associated with a path for data transmission established for the first connection instance.

5. The method according to claim 4, characterized in that The value of the path identifier is 1.

6. The method according to claim 1, characterized in that Reporting the first location information of the terminal device includes: A message is sent to trigger a first positioning process, wherein the value of the first information element in the message indicates that the first positioning process is a modification of a second positioning process, and the second positioning process is triggered based on the establishment of the default path and is used to report the second location information of the terminal device.

7. The method according to claim 6, characterized in that The first positioning process is a network-triggered location request NI-LR positioning process, and the first information element is a location event information element.

8. The method according to claim 1, characterized in that The method is performed by an access and mobility management function AMF or a mobility management entity MME.

9. A communication device, characterized in that: include: A unit or module for performing the method according to any one of claims 1 to 8.

10. A communication device, characterized in that: include: A processor configured to execute the method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program or instructions, which, when executed, causes the method according to any one of claims 1 to 8 to be performed.

12. A computer program product, characterized in that The method comprises a computer program or instructions which, when executed, cause the method according to any one of claims 1 to 8 to be performed.

Images