Communication methods, devices, storage media and computer program products

Abstract

Embodiments of this disclosure provide a communication method, apparatus, storage medium, and computer program product. In this method, a network device, in response to establishing a dedicated path for data transmission for a first connection instance, reports first location information of a terminal device associated with an emergency service. This dedicated path differs from a default path established prior to the dedicated path for the first connection instance, which is associated with the emergency service. Thus, in embodiments of this disclosure, implementing this method enables timely reporting of the latest location information of the terminal device during emergency calls, improving the accuracy and real-time nature of user location tracking, thereby enhancing the reliability and timeliness of emergency rescue services.

Description

Technical Field

[0001] This disclosure generally relates to the field of communications, and more specifically to a communication method, apparatus, computer-readable storage medium, and computer program product. Background Technology

[0002] In emergency situations, terminal devices can initiate emergency calls, and the communication network accordingly triggers a location process to report the user's location information to the emergency service center. After an emergency call ends, if the default evolved packet system (EPS) bearer or default quality of service (QoS) stream has not been released, the emergency call center may call back the user or the user may initiate the call. During this period, the user's location information may have changed, meaning the emergency service center will not receive the latest location information, which will affect subsequent rescue services. Summary of the Invention

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

[0004] Firstly, a communication method is provided. The method provided in this disclosure can be executed by a network device. In this embodiment, the network device can be a core network device or a component within a core network device (e.g., a module, circuit, chip, chip system, or processor). The core network device or the component within the core network device can implement the network functions of the core network. In this method, in response to establishing a dedicated path for data transmission for a first connection instance, the network device reports the first location information of a terminal device associated with an emergency service. The dedicated path differs from the default path previously established for the first connection instance, wherein the first connection instance is associated with an emergency service. In this way, the latest location information of the terminal device can be reported promptly in emergency service scenarios, improving the accuracy and real-time nature of user positioning, thereby enhancing 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 4G or 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 increasing emergency rescue efficiency.

[0006] In some implementations, the network device determines whether the first connection instance is associated with the emergency service based on the type information of the first connection instance stored in the user context. This ensures that user location information is reported in the event of an emergency service, thus meeting the accuracy requirements for user location in emergency scenarios.

[0007] In some implementations, the network device determines that an established path is a private path based on the value of a path identifier associated with the path for data transmission established for the first connection instance. This allows the establishment of private paths to be recognized, enabling the reporting of terminal device location information triggered by the establishment of a private path, thus improving the accuracy and real-time nature of user positioning.

[0008] In some implementations, the path identifier is set to 1. This allows for the determination of whether to initiate a user location process by recognizing the path identifier's value, ensuring timely updates 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 to trigger a first positioning procedure, wherein the value of the first information cell in the message indicates that the first positioning procedure is a modification of a second positioning procedure, which is triggered based on the establishment of a default path and is used to report the second location information of the terminal device. In this way, the recipient of the positioning request message can know the reason for triggering the first positioning procedure, thereby improving the targeting and efficiency of the positioning procedure processing.

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

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

[0012] Secondly, a communication device is provided, which has the function of implementing the behavior in the method example of the first aspect described above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described function. The description of the method of the first aspect also applies 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 to a component within the communication device (e.g., a processor, a chip, or a chip system). In one possible design, the communication device includes a unit that performs the method of the first aspect or its implementation. 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] Thirdly, an apparatus is provided, including a processor and a memory storing a computer program or instructions, which, when executed by the processor, cause the apparatus to perform any method according to the first aspect and its implementation.

[0014] Fourthly, a computer-readable storage medium is provided, which stores a computer program or instructions that, when executed by an electronic device, cause the electronic device to perform the methods described in the preceding aspects.

[0015] Fifthly, a computer program or computer program product is provided, the computer program or computer program product including computer program instructions, which, when executed by an electronic device, cause the electronic device to perform the methods in the above aspects.

[0016] Sixthly, embodiments of this disclosure provide a chip system including a processor for implementing the functions of the apparatus in the methods of the above aspects. In one possible design, the chip system further includes a memory for storing computer programs or instructions and / or data. The chip system may be composed of chips or may include chips and other discrete devices.

[0017] In a seventh aspect, embodiments of this disclosure also provide a communication system including a network device for performing the method of the first aspect. Attached Figure Description

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

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

[0020] Figure 3A , Figure 3B The combination illustrates a communication flow diagram according to some embodiments of this disclosure.

[0021] Figure 4A and Figure 4B The combination illustrates a communication flow diagram according to other embodiments of this disclosure.

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

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

[0024] Figure 7 This is a schematic diagram of the structure of an apparatus according to some embodiments of the present disclosure. Detailed Implementation

[0025] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that embodiments of this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0026] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "an 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 emergency service scenarios, terminal devices can initiate emergency calls, and the communication network accordingly triggers a location process to report the user's location information to the emergency service center. In some solutions, the AMF initiates the NI-LR location process during the establishment of the Emergency Protocol Data Unit (PDU) session. When the user plane function (UPF) reports that the PDU session is inactive within a specified time, the session management function (SMF) initiates the release of the emergency PDU session. In scenarios where a user's emergency call ends and the default bearer is not released, if the emergency call center calls back the user or the user initiates a call, the SMF initiates a PDU session modification process to establish a dedicated bearer. In this case, the AMF does not trigger the NI-LR location process and fails to report the user's latest location information in a timely manner. Based on the above analysis, the above solutions cannot report the user's latest location information in a timely manner in emergency service scenarios, which may affect subsequent emergency rescue services.

[0028] Therefore, this disclosure provides a communication method that enables timely reporting or updating of the user's latest location information in emergency service scenarios, improves the accuracy of user positioning, ensures the smooth progress of emergency service-related rescue work, and improves service efficiency.

[0029] Figure 1 A schematic diagram of a system architecture to which embodiments of this disclosure may be applied is shown. Figure 1 The communication system 100 shown, 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 the service area 130 of the access network device 120. The communication system 100 may also include a core network 140, which may include several 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 this embodiment may also be collectively referred to as network devices. In some examples, the location information of the terminal device 110 can be obtained through interaction between the access network device 120 and one or more core network devices. The core network devices in the communication system 100 can report the location information of the terminal device 110 to a third-party system, such as an emergency service center in emergency services. An 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 this 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. Specifically, it can 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. Terminal device 110 can also be a satellite phone, cellular phone, smartphone, wireless data card, wireless modem, machine-type communication device, 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, in-vehicle device or wearable device, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, terminal device 110 in 5G network or future communication network, etc. Terminal equipment 110 can also be a communication module, satellite phone, or a component thereof with satellite communication capabilities, 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, a vehicle-mounted or airborne satellite communication terminal, etc. It should be understood that a satellite communication terminal can serve as a micro base station to further provide data interfaces to accessed user equipment.

[0031] The access network device 120 mentioned in this disclosure embodiment can also be referred to as a radio access network (RAN) node, etc. The access network device 120 can be a device with base station functionality, such as an evolved NodeB (eNodeB), a transmitting and receiving point (TRP), a transmitting 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 can 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 types of macro base stations, micro base stations (also known as small cells) 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, transmitting and receiving points (TRPs), transmitting points (TPs), mobile switching centers, etc., or it can be the antenna panel of a base station. The control node can connect to multiple base stations and configure resources for multiple terminals covered by multiple base stations. Access network equipment 120 can also be a satellite (or satellite base station), a high-altitude platform station (HAPS), or 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 (or geosynchronous orbit satellite) or a non-geostationary earth orbit (NGEO) satellite. 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. There are no restrictions here. The access network equipment 120 may also be a gateway station (or ground station, earth station, signaling station, gateway, or gateway station), etc. In systems employing different wireless access technologies, the names of equipment with base station functions may differ. For example, it could be a gNB in ​​5G, or an access network device 120 in a network after 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 vehicle-to-everything (V2X) communication. This application does not limit the specific name of the access network device 120. The access network device 120 can also be an open radio access network (O-RAN or ORAN), a baseband unit pool (BBU pool) under a cloud radio access network (CRAN), or an RRU, etc.

[0032] The core network 140, as the bearer network, provides an interface to the data network, offering user equipment (UE) communication connections, authentication, management, policy control, and data service delivery. The core network equipment mentioned in this embodiment can be used to provide core network services to access network equipment 120 and terminal equipment 110. The core network equipment can correspond to different devices in different systems. For example, in third-generation (3G) networks, the core network equipment can correspond to a Serving GPRS Support Node (SGSN) and / or a Gateway GPRS Support Node (GGSN), etc. In 4G, core network equipment can correspond to 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 can correspond to AMF, Session Management Function (SMF), Policy Control Function (PCF), User Plane Function (UPF), Unified Data Management (UDM), SBC / P-CSCF, Location Management Function (LMF), and GMLC. The AMF element manages the access and mobility of terminal equipment (e.g., UE), primarily responsible for UE authentication, UE mobility management, and UE paging functions.

[0033] Access network device 120 may also include, but is not limited to: evolved node B (eNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or transmission reception point (TRP) in a wireless fidelity (WIFI) system. 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, access network device 120 may also be a network node constituting a gNB or TP, such as a BBU, or a distributed unit (DU). Alternatively, access network device 120 may also be a device performing network-side functions in a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT) communication system, a vehicle-to-everything (V2X) communication system, or other communication systems.

[0034] The methods provided in this disclosure can be applied to various communication systems, such as wireless local area network (WLAN) systems, Internet of Things (IoT) systems, narrowband Internet of Things (NB-IoT) systems, long term evolution (LTE) systems, 5G communication systems, new radio (NR) systems, or new communication systems emerging in future communication developments. These methods can also be applied to satellite communication systems, high altitude platform station (HAPS) communication, and non-terrestrial network (NTN) systems such as unmanned aerial vehicles (UAVs), including integrated communication and navigation (ICAN) systems, Global Navigation Satellite Systems (GNSS), and ultra-dense low-Earth orbit (LEO) satellite communication systems. NTN systems can be integrated with traditional mobile communication systems. For example, mobile communication systems can be 4G communication systems (e.g., LTE systems), worldwide interoperability for microwave access (WiMAX) communication systems, 5G communication systems (e.g., NR systems), and future mobile communication systems such as NR NTN, IoT NTN, etc.

[0035] Embodiments of this disclosure may be implemented according to any suitable communication protocol, including but not limited to 3G, 4G, 5G, or future cellular communication protocols, wireless LAN communication protocols such as IEEE 802.11, and / or any other protocols currently known or to be developed in the future. The technical solutions of the embodiments disclosed herein are applicable to communication systems that follow any suitable communication protocol, such as: GPRS, Global System for Mobile Communications (GSM), Enhanced Data Rate for GSM Evolution (EDGE), Universal Mobile Telecommunications Service (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), 5G or NR, and other future generations of communication systems, etc.

[0036] Figure 2 A schematic diagram of a communication flow according to some embodiments of this disclosure is shown. For example... Figure 2 As shown, process 200 involves network device 210 and first device 220. In some examples, network device 210 may be a core network device; for example, network device 210 may be an AMF (Advanced Management Function). First device 220 may be another core network device that interacts with network device 210. In emergency service scenarios, this other core network device may be used to further report the location information of the terminal device reported by network device 210 to the emergency service provider, such as an emergency call center. Process 200 may also involve... Figure 2 One or more other core network devices not shown. In some examples, network device 210 and first device 220 may interact via one or more other core network devices. Reference Figure 1The core network equipment can be located in the core network 140. In some examples, process 200 may also involve access network equipment (not shown) (see reference). Figure 1 Access network device 120). An example of a terminal device could be... Figure 1 The terminal device 110, such as a UE, is used. In various examples of this disclosure, the core network device can be replaced by a core network element, a core network node, or a core network function. This disclosure mainly describes 4G or 5G communication scenarios. For example, in a 4G communication scenario, an example of network device 210 can be an AMF. In a 5G communication scenario, an example of network device 210 can be an MME. An example of the first device 220 in a 4G or 5G communication scenario can be a GMLC. It should be noted that this disclosure can also be applied to communication scenarios of future networks (e.g., 6G or above). In future network (e.g., 6G or above) communication scenarios, the names of the corresponding network elements and the message names interacting between network elements can be adaptively changed, and all such changes fall within the protection scope of this disclosure.

[0037] In process 200, at 201, network device 210, in response to establishing a dedicated path for data transmission for the first connection instance, reports location information (referred to as first location information) 212 of the terminal device associated with the emergency service, wherein the dedicated path differs from the 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, and a call initiated by the 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 the corresponding terms in the relevant network.

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

[0040] In some examples, network device 210 can determine that a 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 an establishment request for a first connection instance from a terminal device, network device 210 can store the type information of the request in the user context. This 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 in the first connection instance is established first. For example, in the 4G communication scenario of this disclosure embodiment, a default EPS bearer is established first. In the 5G communication scenario of this disclosure embodiment, a default QoS flow is established first. In some examples, after the default path for data transmission in the first connection instance is established, the network device 210 may trigger a location procedure (referred to as a second location procedure) to report the location information (referred to as second location information) of the terminal device associated with the emergency service. For example, in the case of an emergency call initiated by a terminal device, a default path is established. Based on the establishment of the default path, the network device 210 will trigger the second location procedure 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 this disclosure embodiment, a dedicated EPS bearer is established while the default EPS bearer is being established. In the 5G communication scenario of this disclosure embodiment, a dedicated QoS flow is established after the default QoS flow is being established. After the dedicated path for data transmission of the first connection instance is established, the network device 210 will trigger a positioning procedure again (referred to as the first positioning procedure) to report the latest location information of the terminal device (i.e., the first location information 212). For example, in a scenario where an emergency call initiated by the terminal device ends and the default path is not released, a dedicated path is established when the emergency call center calls back the terminal device or the terminal device initiates another call. Based on the establishment of the dedicated path, the network device 210 will trigger the first positioning procedure to report the first location information 212 of the terminal device at this time. Considering 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 devices indicated by the two may be different.

[0043] As described above, in response to the establishment of a dedicated path for data transmission in the first connection instance, network device 210 triggers a first location procedure. Before reporting the first location information 212 of the terminal device, network device 210 can first determine that the data transmission path established for the first connection instance is a dedicated path. For example, network device 210 can determine that the established path is a dedicated path based on the value of the path identifier associated with the data transmission path 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 the example where the first connection instance is a QoS flow, the path identifier is, for example, a 5th generation quality of service identifier (5QI), whose value of 1 indicates that the data transmission path is a dedicated path. The message carrying the 5QI could be a PDU Session Resource Modification Request (SRESOURCE MODIFYREQUEST), 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) is 1, it indicates that the path for data transmission is a private path. The message carrying the QCI can be a Create Bearer Request, which will be described in detail in process 300 below.

[0044] In some examples, during the reporting of the terminal device's first location information 212, the network device 210 sends a message to trigger a first positioning procedure, which includes a first information cell. In some examples, the value of the first information cell indicates that the first positioning procedure is a modification of a second positioning procedure, as described above, which is triggered based on the establishment of a default path and is used to report the terminal device's second location information. The first positioning procedure is used to report the terminal device's first location information 212. The first location information 212 is updated location information compared to the second location information, i.e., the latest location information.

[0045] In some examples, the first and second location procedures are NI-LR location procedures, and the first information element is a location event information element, such as a LocationEvent information element. Exemplarily, in the first triggered second location procedure, the value of the location event information element is, for example, EMERGENCY_CALL_ORIGINATION, indicating an initial NI-LR location procedure for an emergency call. In the subsequently triggered first location procedure, the value of the location event information element is, for example, EMERGENCY_CALL_MODIFICATION, indicating a modification of the initial NI-LR location procedure for the emergency call. Alternatively, in some examples, the first location procedure may reuse the value of the location event information element from the second location procedure; that is, the value of the location event information element in both the first and second location procedures is EMERGENCY_CALL_ORIGINATION.

[0046] Based on the examples of the above processes, network device 210 can promptly report the latest location information of terminal devices in emergency service scenarios, improving the accuracy and real-time nature 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 this disclosure embodiment in a 4G communication scenario is illustrated in combination, wherein Figure 3B yes Figure 3A The continuation, Figure 3A and Figure 3B Each step of process 300 is included, and the two combined constitute the complete process 300. Process 300 involves terminal device 301, eNodeB 302, MME 303, S-GW 304, PCRF 305, P-GW 306, HSS 307, SBC / P-CSCF 308, and GMLC 309. Terminal device 301 can be an example of terminal device 110. eNodeB 302 can be an example of access network device 120 or an access network device mentioned in process 200. MME 303 can be an example of network device 210. GMLC 309 can be an example of first device 220. (See reference) Figure 1MME 303, S-GW 304, PCRF 305, P-GW306, HSS 307, SBC / P-CSCF 308, and GMLC 309 can be located in 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 user data between the base station and the core network; PCRF 305 can be used for policy control, responsible for the formulation and distribution of policies and charging rules; P-GW 306 can be used for data egress gateway, responsible for IP address allocation, data forwarding, and interoperability with external packet data networks; HSS 307 can be used for home subscriber subscription data management, responsible for storing and providing 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 mobility positioning, responsible for interfacing with external applications and reporting location information to emergency service centers, etc.

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

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

[0050] In step 315, the default EPS bearer is established. The establishment of the default EPS bearer involves the interaction of multiple network elements, including but not limited to several network elements such as terminal device 301, eNodeB 302, MME 303, S-GW 304, PCRF 305, P-GW 306, HSS 307, and SBC / P-CSCF 308. The specific establishment of the default EPS bearer can adopt the conventional establishment process for default EPS bearers in 4G, which will not be described in detail in this invention. Alternatively, steps 313 and 315 can be executed simultaneously.

[0051] At step 317, MME 303 triggers a location procedure, such as the NI-LR procedure (an example of the second location 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 found in the conventional implementation scheme for MME 303 obtaining the location of terminal devices in emergency calls, and will not be described in detail in this disclosure. 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. In the NI-LR procedure of this step, MME 303 sends a second Subscriber Location Report message 322 to GMLC 309 to notify the user of the current location information. The second Subscriber Location Report message 322 includes a location event element, the value of which is EMERGENCY_CALL_ORIGINATION.

[0052] In step 319, a first dedicated EPS bearer is established. After the terminal device 301 hangs up the call, as shown in step 321, the first dedicated EPS bearer is released. The network elements involved in the operations of steps 319 and 321 may include several network elements among the terminal device 301, eNodeB 302, MME 303, S-GW 304, PCRF 305, P-GW 306, HSS 307, and SBC / P-CSCF 308. For details, refer to the conventional methods of establishing dedicated bearers based on default bearers and releasing dedicated EPS bearers in 4G scenarios; this invention will not provide a detailed description.

[0053] Following step 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. This step is... Figure 3A Not shown in the image. (See reference.) Figure 3B At 323, PCRF 305 sends a re-authentication request (RAR) 332 to P-GW 306 to trigger the establishment of a dedicated bearer.

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

[0055] In step 329, MME 303 identifies the current PDN connection as an urgent PDN connection and determines that the currently established EPS bearer is a dedicated EPS bearer. Specifically, MME 303 combines the Create Bearer Request message 342 (e.g., the EPS bearer identifier (eps-bearer-id) information element therein) and the 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 urgent PDN connection. If the Create Bearer Request message 342 indicates that QCI equals 1, then MME 303 identifies it as a dedicated bearer establishment process.

[0056] In step 331, MME 303 triggers the NI-LR procedure (an example of the first positioning procedure), sending a first Subscriber Location Report message 352 to GMLC 309 to notify the user of their current location information. The first Subscriber Location Report message 352 includes a location event element, which adds a new enumeration value, specifically EMERGENCY_CALL_MODIFICATION, to distinguish it from the previously existing enumeration EMERGENCY_CALL_ORIGINATION. EMERGENCY_CALL_MODIFICATION identifies that the NI-LR procedure triggered in step 331 is a modified version of the NI-LR procedure triggered in step 317. Since the first positioning procedure is based on a modification of the second positioning procedure, some parameters, configurations, or information already existing in the second positioning procedure can still be applied to the first positioning procedure, saving the overhead of creating a new positioning procedure.

[0057] Process 300 may also include subsequent steps (not shown), such as the MME 303 sending a Bearer Setup Request message to the eNodeB 302 to notify the eNodeB 302 to establish voice E-RAB resources. The eNodeB 302 may send a Bearer Setup Response message to the MME 303 to confirm that the bearer is active. Then, the MME 303 may send a Create Bearer Response message to the S-GW 304 to confirm the bearer is active. The S-GW 304 may further send a Create Bearer Response message to the P-GW 306 to confirm the bearer is active.

[0058] Combination Figure 3A and Figure 3B As shown in process 300, if the terminal device 301 is called back or initiates another call after the first dedicated EPS bearer is released, and the default EPS bearer corresponding to the first emergency PDN connection is not released, the establishment of the dedicated EPS bearer corresponding to the first emergency PDN connection will be triggered again. The MME 303 can then initiate the location process again to report the location information of the terminal device 301. Since there is usually a certain time interval between the establishment of the dedicated EPS bearer, during which the location of the terminal device 301 may change, the latest location information of the terminal device 301 can be reported in a timely manner. This enables dynamic updates of the location information of the terminal device 301 during emergency calls, thereby improving the accuracy and real-time nature of user positioning and further enhancing the reliability and timeliness of emergency rescue services.

[0059] Figure 4A , Figure 4B The processing flow in a 5G communication scenario according to this disclosure is illustrated in combination. Figure 4A and 4B As shown, Figure 4A and 4BEach step of process 400 is included, 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 can be an example of terminal device 110. NG-RAN 402 can be an example of access network device 120 or an 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 can 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 packet forwarding and processing; 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 location management, responsible for terminal location acquisition and processing; GMLC 410 has the same function as GMLC 309.

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

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

[0062] In step 415, a default QoS flow is established. The establishment of the default QoS flow involves the interaction of multiple network elements, including but not limited to several network elements such as 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 adopt the conventional establishment process for default QoS flows in 5G, which will not be described in detail in this invention. Alternatively, steps 413 and 415 can be executed simultaneously.

[0063] After the default QoS flow establishment process of the emergency PDU session is completed, at 417, AMF 403 initiates an emergency location process (e.g., the NI-LR process, an example of the second location process) according to its local configuration. AMF 403 sends a location event notification (Namf_Location_EventNotify) message (referred to as the second location notification message 422) to GMLC 410 to notify terminal device 401 of its current location information (i.e., the second location information). The second location notification message 422 includes a location event element, the value of which is EMERGENCY_CALL_ORIGINATION. The specific implementation of AMF 403 obtaining the location information of terminal device 401 can be found in the conventional implementation scheme for AMF 403 obtaining the location of terminal devices in emergency calls, and will not be described in detail in this embodiment. In some examples, AMF 403 may report the location information of terminal device 401 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] In step 419, a first dedicated QoS flow is established. After the terminal device 401 hangs up the call, as shown in step 421, the first dedicated QoS flow is released. The network elements involved in performing operations 319 and 321 may include several network elements among terminal device 401, NG-RAN 402, AMF 403, SMF 404, PCF 405, UPF 406, UDM 407, and SBC / P-CSCF 408. For details, refer to the conventional methods for establishing and releasing dedicated QoS flows in 5G scenarios; this invention will not provide further details.

[0065] In scenarios where an emergency call center callback terminal 401 or a terminal 401 initiates a call, the SBC / P-CSCF 408 sends a request to the PCF 405 to establish a dedicated QoS flow. For example, at 423, the SBC / P-CSCF 408 sends a second dedicated QoS flow establishment request message 432 to the PCF 405. At 425, the PCF 405 sends a Session Management Policy Control Update Notification Request (e.g., an Npcf_SMPolicyControl_UpdateNotify request) 442 to the SMF 404 to notify the SMF 404 to create a voice dedicated QoS flow.

[0066] At 427, SMF 404 sends a first message 452 (e.g., a Namf_Communication_N1N2MessageTransfer request message) to AMF 403, which includes a PDU session identifier (pduSessionId) information cell. AMF 403 receives this first message 452. The pduSessionId information cell indicates the PDU session ID.

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

[0068] At step 431, AMF 403 triggers the NI-LR procedure (an example of the first positioning procedure). For instance, AMF 403 sends a first location event notification (Namf_Location_EventNotify) message (referred to as first location notification message 462) to GMLC 410 to notify terminal device 401 of its current location information (first location information). Specifically, the first location notification message 462 includes a location event element, which has a newly added enumerated value EMERGENCY_CALL_MODIFICATION (used to identify that the current NI-LR procedure is a modification of the NI-LR procedure in step 417), distinguishing it from the location event 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 by the first positioning procedure is an update to the second location information reported by 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 NG RAN to establish voice QoS stream resources (step 11). NG RAN 402 sends a PDU Session Resource Modification Response to AMF 403, which includes N2 session management (N2 SM) information used to confirm the PDU session resource modification result. AMF 403 sends an Nsmf_PDUSession_UpdateSMContext request to SMF 404, carrying the N2 SM information sent by NG RAN 402 (step 13).

[0070] Combination Figure 4A and Figure 4BThe illustrated process, after the first dedicated QoS flow is released, if the default QoS flow corresponding to the first emergency PDU session is not released, and the terminal device 401 is called back or initiates another call, the establishment of the dedicated QoS flow corresponding to the emergency PDU session will be triggered again. In this embodiment, the AMF 403 can initiate the location process again to report the location information of the terminal device 401. Since there is usually a certain time interval between the establishment of the two dedicated QoS flows, during which the location of the terminal device 401 changes, the latest location information of the terminal device 401 can be reported in a timely manner. This enables dynamic updating of the location information of the terminal device 401 during emergency calls, ensuring that in emergency service scenarios, the party needing to know the location information of the terminal device 401 (e.g., the emergency call center) receives the latest location of the terminal device 401. This improves the accuracy and real-time nature of user location and further enhances the reliability and timeliness of emergency rescue services.

[0071] Figure 5 A schematic diagram of an example flow implemented at a communication device according to an embodiment of this disclosure is shown. As shown in Figure 5, flow 500 can be executed by the communication device. In some embodiments, the communication device executing flow 500 may be a network device 210, an AMF 403, or an MME 303. In block 510, in response to establishing a dedicated path for data transmission for a first connection instance, the communication device reports first location information of a terminal device associated with an emergency service, the dedicated path being different from the default path established prior to the dedicated path for the first connection instance, wherein the first connection instance is associated with an emergency service. In some embodiments, flow 500 may further include elements combined with embodiments of this disclosure. Figure 2 , Figure 3A , Figure 3B , Figure 4A , Figure 4B One or more examples describe other operations performed at a network device, AMF, or MME.

[0072] Figure 6This is a block diagram of a device 600 that can be used to implement some embodiments of the present disclosure. In some embodiments, device 600 may be an element of a communication network infrastructure, such as a base station (e.g., a NodeB, an evolved NodeB (eNodeB or eNB), a next-generation NodeB (sometimes called a 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 a core network (CN, which can communicate with the UE via a base station) or a Public Land Mobility Network (PLMN) and various other nodes or functions within it. In other embodiments, device 600 may be a device connected to the network infrastructure via a wireless interface, such as a mobile phone, a smartphone, or other such device that can be classified as User Equipment (UE). In some embodiments, device 600 may be a machine-type communication device. Type Communications (MTC) devices (also known as machine-to-machine (M2M) devices), or other devices that, although not providing direct service to users, can be classified as UEs. In some embodiments, device 600 may be a roadside unit (RSU), a vehicle UE (V-UE), a pedestrian UE (P-UE), or an infrastructure UE (I-UE). In some scenarios, device 600 may also be referred to as a mobile device, a term intended to reflect a device connected to a mobile network, regardless of whether the device itself is designed for or capable of being mobile. A particular device may utilize all or only a subset of the components shown, and the level of integration may vary depending on the device. Furthermore, device 600 may contain multiple instances of components, such as multiple processors, memories, transmitters, receivers, etc.

[0073] Device 600 typically includes a processor 602, such as a central processing unit (CPU), and may further include a dedicated processor, such as a graphics processing unit (GPU) or other such processor, memory 604, a network interface 606, and a bus 608 for connecting 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 combinations 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 a plurality of bus architectures of any type, 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] Device 600 may also include one or more network interfaces 606, which may include at least one of wired network interfaces and wireless network interfaces. For example... 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 a wireless link. When device 600 is a network infrastructure element, the wireless access network interface 620 may be omitted for nodes or functions that are elements of a PLMN rather than elements at the wireless edge. When device 600 is infrastructure at the wireless edge of the network, it may include both wired and wireless network interfaces. When device 600 is a wirelessly connected device, such as a user equipment, the 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] 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 bus 608. Mass storage 610 may include, for example, one or more of a solid-state drive, hard disk drive, disk drive, or optical disk drive. In some embodiments, mass storage 610 may be located remotely from device 600 and may be accessed using a network interface such as interface 606. In the illustrated embodiment, mass storage 610 is distinct from memory 604, which includes it, and mass storage 610 typically performs storage tasks compatible with higher latency but typically provides low or no fluctuation. In some embodiments, mass storage 610 may be integrated with memory 604.

[0077] Optional video adapter 612 and 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 touchscreen, coupled to I / O interface 616. Other devices may be coupled to device 600 and may utilize additional or fewer interfaces. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide interfaces for external devices. Those skilled in the art will understand 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 This is a schematic diagram of the structure of device 700 according to some embodiments of this application. For example... Figure 7 As shown, the device 700 includes a reporting unit 702. The device 700 can be applied to applications such as... Figure 1The communication scenario shown can implement the methods provided in the preceding embodiments, such as method 500. Optionally, the physical manifestation of 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, device 700 can be a device suitable for implementing corresponding network functions in the core network device, such as a module, processor, or chip. Specifically, 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), etc. It can also be a logic node, logic module, or software that can implement all or part of the communication device functions.

[0079] In some embodiments, the reporting unit 702 may be configured to report first location information of a terminal device associated with an emergency service in response to establishing a dedicated path for data transmission for a first connection instance, wherein the dedicated path is different from the default path established for the first connection instance prior to the dedicated path, and 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 that can be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0081] In some other embodiments, the apparatus 700 may include various other units or modules that can be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0082] It should be noted that the module division in the above embodiments of this disclosure is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, exist as separate physical units, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0083] If the integrated unit is implemented as 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 this application, or all or part of it, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0084] Based on the above embodiments, this disclosure also provides a computer program that, when run on a computer, causes the computer to perform any of the methods provided in the above embodiments.

[0085] Based on the above embodiments, this disclosure also provides a computer-readable storage medium storing a computer program. When executed by a computer, the computer program causes the computer to perform 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 limited to, a computer-readable medium may include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code having the form of instructions or data structures and that can be accessed by a computer.

[0086] Based on the above embodiments, this disclosure also provides a chip for reading a computer program stored in a memory and implementing any of the methods provided in the above embodiments.

[0087] Based on the above embodiments, this disclosure provides a chip system including a processor for supporting a computer device in implementing the functions involved in the communication devices in the above embodiments. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete components.

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

[0089] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0090] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0091] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

Claims

1. A communication method, characterized in that, Applied to a network device, the method includes: In response to establishing a dedicated path for data transmission for a first connection instance, the first location information of the terminal device associated with the emergency service is reported, wherein the dedicated path is different from the default path established for the first connection instance prior to the dedicated path, and the dedicated path is established after the first dedicated path following the default path is released and the default path is not released. 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 Dedicated 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, characterized in that, Also includes: The established path is determined to be the private path based on the value of the path identifier associated with the 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, The first location information of the terminal device reported includes: A message is sent to trigger a first positioning process, wherein the value of a first information element in the message indicates that the first positioning process is a modification of a second positioning process, which 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 the Access and Mobility Management Function (AMF) or the Mobility Management Entity (MME).

9. A communication device, characterized in that, include: Units or modules used to perform the method according to any one of claims 1 to 8.

10. A communication device, characterized in that, include: The processor is configured to perform 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 that, when executed, cause the method according to any one of claims 1 to 8 to be performed.

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

Images