Communication methods and communication devices

Abstract

Provided are communication methods and communication devices. A method comprises: a terminal device determining first information, wherein the first information is used for determining a waiting duration for a callback for an emergency call after the terminal device completes the emergency call.

Description

Communication method and communication device TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, and more particularly, to a communication method and a communication device. BACKGROUND

[0002] The emergency call (eCall) system of a vehicle is gradually becoming an important tool for ensuring road safety. The eCall system can automatically or manually trigger by the driver after an accident occurs, quickly establish contact with a public safety answering point (PSAP), and provide accurate accident information, thereby significantly improving the speed of rescue response and the efficiency of life rescue, by integrating mobile communication technology and satellite positioning.

[0003] Currently, the Comité Européen de Normalisation / European Committee for Standardization (CEN) has proposed new requirements for the 3rd generation partnership project (3GPP) specification, which requires waiting for a callback from the PSAP after the completion of the eCall.

[0004] SUMMARY

[0005] The present application provides a communication method and a communication device. Each aspect of the present application is described below.

[0006] In a first aspect, a communication method is provided, comprising: determining, by a terminal device, first information, the first information being used to determine a waiting time length of a callback of an emergency call after the terminal device completes the emergency call.

[0007] In a second aspect, a communication method is provided, comprising: sending, by a first device, first information to a terminal device, the first information being used to determine a waiting time length of a callback of an emergency call after the terminal device completes the emergency call.

[0008] In a third aspect, a communication device is provided, the communication device being a terminal device, and the communication device comprising: a determining module configured to determine first information, the first information being used to determine a waiting time length of a callback of an emergency call after the terminal device completes the emergency call.

[0009] In a fourth aspect, a communication device is provided, the communication device being a first device, the communication device comprising a communication module configured to send first information to a terminal device, the first information being used to determine a waiting time for a callback of an emergency call after the terminal device completes the emergency call.

[0010] In a fifth aspect, a communication device is provided, comprising a transceiver, a memory and a processor, the memory being configured to store a program, the processor being configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the communication device performs the method according to the first aspect or the second aspect.

[0011] In a sixth aspect, an apparatus is provided, comprising a processor configured to invoke a program from a memory, so that the apparatus performs the method according to the first aspect or the second aspect.

[0012] In a seventh aspect, a chip is provided, comprising a processor configured to invoke a program from a memory, so that a device installed with the chip performs the method according to the first aspect or the second aspect.

[0013] In an eighth aspect, a computer readable storage medium is provided, the computer readable storage medium storing a program, the program causing a computer to perform the method according to the first aspect or the second aspect.

[0014] In a ninth aspect, a computer program product is provided, the computer program product comprising a program, the program causing a computer to perform the method according to the first aspect or the second aspect.

[0015] In a tenth aspect, a computer program is provided, the computer program causing a computer to perform the method according to the first aspect or the second aspect.

[0016] Embodiments of the present application introduce the first information. According to the first information, the terminal device can determine the waiting time for the callback of the emergency call, thereby helping to meet the requirements of CEN on the emergency call process, and further improving the reliability of the emergency call process. BRIEF DESCRIPTION OF DRAWINGS

[0017] FIG. 1 is an example diagram of a system architecture of a wireless communication system to which embodiments of the present application can be applied.

[0018] FIG. 2 is an example diagram of a structure of an eCall system.

[0019] FIG. 3 is an example diagram of a specific structure of the eCall system shown in FIG. 2.

[0020] FIG. 4 is a flow diagram of a communication method according to an embodiment of the present application.

[0021] FIG. 5 is a flow diagram of a communication method according to another embodiment of the present application.

[0022] FIG. 6 is an example diagram of a definition manner of a timer according to an embodiment of the present application.

[0023] FIG. 7 is a structural diagram of a communication device according to an embodiment of the present application.

[0024] FIG. 8 is a structural diagram of a communication device according to another embodiment of the present application.

[0025] FIG. 9 is a schematic diagram of an apparatus to which embodiments of the present application can be applied. DETAILED DESCRIPTION

[0026] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0027] Wireless communication system

[0028] FIG. 1 is an example diagram of a system architecture of a wireless communication system 100 to which embodiments of the present application can be applied. The wireless communication system 100 can include a network device 110 and a terminal device 120. The network device 110 can be a device that communicates with the terminal device 120. The network device 110 can provide network coverage for a specific geographic area and can communicate with the terminal device 120 located in the coverage area. The terminal device 120 can access a network (such as a wireless network) through the network device 110. Optionally, the wireless communication system 100 can also include a network controller, a mobile management entity, and other network entities, which are not limited by embodiments of the present application.

[0029] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: 5G system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided by the present application can also be applied to future communication systems, such as the sixth generation mobile communication system, such as satellite communication system, etc.

[0030] The terminal device in the embodiments of the present application can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user apparatus. The terminal device in the embodiments of the present application can refer to a device providing voice and / or data connectivity for a user, and can be used to connect people, things and machines, such as handheld devices with wireless connection function, vehicle-mounted devices, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity, which provides sidelink signals between terminal devices in vehicle to everything (V2X) or device to device (D2D), etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and the smart home device communicate with each other without relaying the communication signals through the base station.

[0031] The network device in the embodiments of the present application can be a device for communicating with a terminal device. The network device may, for example, be an access network device or a radio access network device. For example, the network device can be a base station. The base station can broadly cover various names in the following or replace the following names: Node B (Node B), evolved Node B (eNB), next generation Node B (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof.

[0032] In a conventional communication system (such as a conventional NR system), a network device periodically transmits system information (such as system information block (SIB) 1). The system information is very important for a terminal device in an idle state, because the terminal device in the idle state can access a cell based on the system information.

[0033] However, some information in the periodically transmitted system information is wasted (for example, at a certain moment, the network device transmits the system information, but at this moment, there is no terminal device that needs to acquire the system information). In addition, because the network device needs to always maintain the system information, the network device cannot enter a deep sleep mode to save power consumption. According to the statistics of operators, power consumption is one of the main sources of the operating costs of operators. Therefore, if the power consumption of the network device can be reduced, it will not only help to better operate future cellular systems, but also help the ecosystem (such as reducing carbon emissions, thereby slowing down the speed of global warming).

[0034] However, if the network device directly deletes the system information, it will cause the terminal device in the idle state to be unable to access the cell. Therefore, an ideal way is that the terminal device requests the system information of the cell on demand, and the network device only transmits the system information to the terminal device in the case of needing to transmit the system information.

[0035] Therefore, embodiments of the present application are concerned with how to effectively communicate with a cell while considering network energy saving. The scheme can be applied to a communication system provided by related technologies, such as an NR system, and can also be applied to a future communication system, such as a sixth generation (6G) communication system.

[0036] eCall system

[0037] FIG. 2 shows an eCall system architecture to which embodiments of the present application are applied. The eCall system includes a vehicle terminal device 120, a network 130, and a public safety answering point (PSAP) 140, wherein the vehicle terminal device 120 includes an in-vehicle system (IVS), and initiates an eCall when the IVS in the vehicle terminal device detects a traffic accident. Voice data is sent to the PSAP through a voice channel 100, and the current global positioning system (GPS) positioning coordinates of the vehicle, the time of the accident, and the related information such as the description of the vehicle are sent to the PSAP in the form of minimum set of data (MSD) data through a data channel 110. It should be noted that the PSAP can be implemented through a server.

[0038] In particular, as shown in FIG. 3, the IVS in the in-vehicle terminal device 120 can include one or more of an MSD information source, an IVS data modem, a GPS receiver, a microphone & speaker, a speech codec, and a radio modem. The network 130 can include a public land mobile network (PLMN) and a public switched telephone network (PSTN) / global switched telephone network (GSTN), in which one or more of a base station controller (BTS), a transcoding and rate adaptation unit (TRAU), and a mobile switching center (MCS) can be included. The PSAP 140 can include a PSAP data modem, an MSD display, and a speaker. The PSAP data modem, the MSD display, and the speaker can be integrated in the same device or can be separate physical entities. When an accident occurs in a vehicle, the terminal device initiates an eCall to the PSAP through the network and transmits voice data and MSD-formatted data of the eCall to the PSAP.

[0039] CEN requirements for eCall system

[0040] On 12 March 2024, CEN sent a liaison statement (LS) to the 3GPP technical specification group (TSG) system architecture (SA) and 3GPP TSG core network and terminals (CT) to inform the 3GPP organization Europe about new regulations or standards for eCall and internet protocol multimedia subsystem (IMS)-eCall in CEN member countries (see CP-241245). These regulations specify requirements for PSAPs, vehicles, and IVSs in CEN member countries.

[0041] Currently, CEN member countries include all member countries of the European Union; three member countries of the European Free Trade Association: Iceland, Norway, and Switzerland; and other countries such as the United Kingdom, North Macedonia, Turkey, and Serbia.

[0042] In addition, the current CEN member countries include Albania, Armenia, Azerbaijan, Belarus, Bosnia and Herzegovina, Egypt, Georgia, Israel, Jordan, Lebanon, Moldova, Montenegro, Morocco, Tunisia, and Ukraine.

[0043] In addition, the current CEN partner standardization organizations include Australia, Canada, Mongolia, and Kazakhstan.

[0044] In the LS (CP-241245), CEN requested 3GPP TSG to meet the new requirements for emergency systems proposed by CEN by modifying 3GPP specifications. The 3GPP specifications mentioned here mainly refer to 3GPP TS 24.229 (within the scope of responsibility of 3GPP CT1 working group) and 3GPP TS 23.167 (within the scope of responsibility of 3GPP SA2 working group).

[0045] In response to the LS from CEN, 3GPP TSG CT and SA also issued a liaison statement. The statement requires the 3GPP CT1 working group (WG) to take the lead in studying the differences between the requirements proposed by CEN and the provisions in 3GPP specifications (3GPP TS 24.229). See LS from 3GPP TSG CT (CP-241307) and LS from 3GPP TSG SA (SP-240973).

[0046] In LS (CP-241245), CEN raised the following inconsistency between CEN current requirements and 3GPP specifications for next generation (NG) IMS-eCall:

[0047] If the IVS is not in a limited service state, the IVS shall remain in a registered state and shall wait for a possible callback initiated by the PSAP. Currently, 3GPP TS 24.229 specifies different behaviors for the IVS. For example, 3GPP TS 24.229 states that if a circuit switch (CS) domain is available, the IVS shall immediately attempt to re-initiate the eCall in the CS domain, or the IVS shall immediately attempt to re-initiate the eCall through another packet switch (PS) radio access technology (RAT) or another public land mobile network (PLMN). However, 3GPP TS 24.229 does not specify that the IVS needs to wait for a callback from the PSAP.

[0048] To solve the inconsistency, the following can be specified in 3GPP specifications: a terminal device supporting an emergency call function, such as an IVS, needs to wait for a callback after completing an emergency call. How to set the waiting time for the callback if the terminal device needs to wait for the callback is a problem to be solved.

[0049] To solve the above problem, an embodiment of the present application introduces first information. The first information can be used to determine the waiting time for a callback of an emergency call after the terminal device completes the emergency call (or after the emergency call fails, that is, the terminal device completes the emergency call can be due to the emergency call failure). That is, after completing the emergency call, the terminal device can determine the waiting time for the callback of the emergency call according to the first information. Then, the terminal device can remain in a registered state for the waiting time to wait for the callback.

[0050] Further, in some implementations, if the callback is still not received after the callback waiting duration, the terminal device can attempt to reinitiate the emergency call through other manners. For example, if the emergency call that has been completed is an emergency call initiated in a packet switch (PS) domain, the terminal device can attempt to reinitiate the emergency call in a circuit switch (CS) domain. Or, the terminal device can reinitiate the emergency call using another PS radio access technology (RAT) or another public land mobile network (PLMN).

[0051] In some implementations, as shown in FIG. 4, the terminal device can first determine the first information (see step S410). The “determine” mentioned here can mean “obtain”. For example, the terminal device can obtain the first information from preconfigured information of the terminal device. Or, the “determine” mentioned here can also mean “receive”. For example, as shown in FIG. 5, the terminal device can receive the first information from a first device (see step S510). The first device can be any type of device capable of configuring the first information for the terminal device, such as a network device (e.g., a core network device) or a server.

[0052] The embodiments of the present application do not make specific limitations on the content of the first information, which can be any type of information that is helpful for determining the callback waiting duration. In some implementations, the first information can be used to directly indicate the waiting duration (or the maximum waiting duration) of the callback. For example, the first information can include a first timer. The first timer is used to determine the waiting duration of the callback (the timing duration of the first timer can be equal to the waiting duration or the maximum waiting duration of the callback). After the terminal device completes the emergency call, the terminal device can start the first timer; before the first timer expires, the terminal device remains in a registered state to wait for the callback. If the callback is still not received after the first timer expires, the terminal device can attempt to reinitiate the emergency call through other manners. For example, if the emergency call that has been completed is an emergency call initiated in a PS domain, the terminal device can attempt to reinitiate the emergency call in a CS domain. Or, the terminal device can reinitiate the emergency call using another PS RAT or another PLMN.

[0053] In addition to directly indicating the waiting duration of the callback, the first information can also indicate a minimum waiting duration (e.g., 3 minutes or 5 minutes) of the callback. If the first information indicates the minimum waiting duration of the callback, the terminal device can determine an actual callback waiting duration according to the implementation of the terminal device, as long as the actual callback waiting duration is greater than or equal to the minimum waiting duration.

[0054] Alternatively, in some implementations, the first information can include an indication of the waiting time length for the callback (e.g., the first timer mentioned above) and an indication of the minimum waiting time length for the callback. The two indications can be transmitted via the same signaling or message, or can be transmitted via different messages or signaling. Alternatively, the indication of the waiting time length for the callback can be transmitted via signaling or a message, and the indication of the minimum waiting time length for the callback can be predefined by the protocol. If the terminal device receives the indication of the waiting time length for the callback, the terminal device can determine the waiting time length for the callback based on the indication. If the terminal device does not receive the indication for some reason, the terminal device can determine the waiting time length for the callback according to the implementation of the terminal device, as long as the determined waiting time length is greater than or equal to the minimum waiting time length for the callback.

[0055] It can be understood that even within the member countries of the CEN, different countries can have different views on how the waiting time length for the callback should be set. Therefore, the waiting time length for the callback mentioned above can be a configurable time length (e.g., a timer with a configurable time length). For example, the waiting time length for the callback can have a value range of 0-60 seconds, and can be configured according to different requirements of the member countries of the CEN. A possible revision of 3GPP TS 24.229 is given below to define the waiting time length for the callback in the 3GPP specification.

[0056] Section 5.1.6.11.2 of 3GPP TS 24.229 (Initial INVITE request) contains the following content:

[0057] 5.1.6.11.2 Initial INVITE request

[0058] If the upper layers request establishment of an IMS emergency call of the automatically initiated eCall type of emergency service or of the manually initiated eCall type of emergency service and if allowed by IP-CAN specific annex, the UE shall send an INVITE request as specified in the procedures in subclause 5.1.6.8 with the following additions:

[0059] 1) the UE shall set the Request-URI to "urn:service:sos.ecall.automatic" or "urn:service:sos.ecall.manual"; and

[0060] 2) if the IP-CAN indicates the eCall support indication, the UE shall:

[0061] a) insert a multipart / mixed body containing an "application / EmergencyCallData.eCall.MSD" MIME body part as defined in RFC 8147

[0244] , containing the MSD not exceeding 140 bytes and encoded in binary ASN.1 PER as specified in CEN EN 15722:2015

[0245] and include a Content-Disposition header field with a "handling" header field parameter with an "optional" value, as described in RFC 3261

[0026] ;

[0062] b) insert an Accept header field indicating the UE is willing to accept an "application / EmergencyCallData.Control+xml" MIME type as defined in RFC 8147

[0244] ; and

[0063] c) insert a Recv-Info header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147

[0244] .

[0064] NOTE: Further content for the INVITE is as defined in RFC 8147

[0244] .

[0065] Then the UE shall proceed as follows:

[0066] 1) if the UE receives a 200(OK) response to the INVITE request not containing:

[0067] a) a multipart / mixed body containing an "application / EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147

[0244] with an "ack" element containing:

[0068] i) a "received" attribute set to "true"; and

[0069] ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

[0070] then the UE shall send the MSD using audio media stream encoded as described in 3GPP TS 26.267[9C];

[0071] 2) if the UE receives a 200(OK) response to the INVITE request containing:

[0072] a) a multipart / mixed body containing an "application / EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147

[0244] with an "ack" element containing:

[0073] i) a "received" attribute set to "true"; and

[0074] ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

[0075] then the UE shall consider the initial MSD transmission as successful;

[0076] 3) if the UE receives a 486(Busy Here), 600(Busy Everywhere) or 603(Decline) response to the INVITE request containing:

[0077] a) a multipart / mixed body containing an "application / EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147

[0244] with an "ack" element containing:

[0078] i) a "received" attribute set to "true"; and

[0079] ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

[0080] then the UE shall consider the initial MSD transmission as successful and shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167[4B]; and

[0081] 4) in all other cases, the UE shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167[4B].

[0082] The last paragraph of the 3) point in the above content can be replaced with the following content to reflect the callback of the emergency call and the callback waiting time:

[0083] then the UE shall consider the initial MSD transmission as successful. Depending on the national requirements the UE shall either perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B], or shall remain registered in the mobile network and shall wait for a PSAP operator to call back, unless the UE is in a limited service state, as required in the CEN countries. To enable PSAP callback, the UE shall support a configurable wait timer 'emerg-callback', see clause 7.8. (then the UE shall consider the initial MSD transmission as successful. Depending on the national requirements the UE shall either perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B], or shall remain registered in the mobile network and shall wait for a PSAP operator to call back, unless the UE is in a limited service state, as required in the CEN countries. To enable PSAP callback, the UE shall support a configurable wait timer 'emerg-callback', see clause 7.8.)

[0084] Compared with the content before replacement, the content after replacement adds: in the case where CEN requirements apply, the procedure that the UE needs to perform after completing the emergency call, i.e., remaining registered in the mobile network and waiting for a PSAP operator to call back. "If CEN requirements apply" refers to the new requirements for emergency calls proposed by CEN, such as CEN requiring that the emergency call does not interfere with the services provided by the PSAP. Whether CEN requirements apply can depend on whether the UE is in a CEN member country. The specific judgment method is described below in relation to the description of the second information. The "configurable wait timer" in the content after replacement is one possible implementation of the first timer mentioned in the foregoing. By introducing the timer, the UE's callback waiting time can be clearly defined, thereby improving the reliability of communication.

[0085] Then, a new timer (i.e. the waiting timer 'emerging-callback') can be added in the timers defined in Table 7.8.1 of section 7.8 of 3GPP TS 24.229, for configuring the waiting duration of the callback from the PSAP, as follows:

[0086] Table 7.8.1: IM CN subsystem timers

[0087] The above describes the content of the first information in detail, and the following illustrates the carrying manner of the first information in detail.

[0088] The first information can be sent to the terminal device through any type of message or signaling. In some implementations, the first information can be carried in non-access stratum (NAS) signaling. For example, a new information element (IE) can be carried in the NAS signaling, and the first information can be carried through the new IE. Alternatively, a new field can be added in an existing IE of the NAS signaling, and the first information can be carried through the new field. The NAS signaling mentioned herein can be carried in one or more of the following, for example: a registration accept message (REGISTRATION ACCEPT), a downlink NAS transport message (DL NAS TRANSPORT), a service accept message (SERVICE ACCEPT), or other types of messages defined in 3GPP TS 24.501 clause 8 (3GPP TS 24.501, clause 8) that are sent by the network to the terminal device. Alternatively, the NAS signaling can be carried in the NAS message defined in 3GPP TS 24.301 or 3GPP TS 24.008.

[0089] In some implementations, the first information can be carried in session initialization protocol (SIP) signaling. The SIP signaling can be, for example, the SIP signaling defined in 3GPP TS 24.229 that is sent by the network to the terminal device.

[0090] In some implementations, the first information can be carried in an application layer message. Alternatively, the first information can be transmitted through application-to-application signaling. As an example, the first information can be transmitted based on over the top technology.

[0091] In some implementations, the first information can be transmitted based on a subscriber identity module (SIM) toolkit (STK) technology. The implementation of the STK technology can be referred to 3GPP TS 31.115.

[0092] In some implementations, the first information can be carried in a management object (MO) (MO defined in 3GPP specification).

[0093] Further, in some implementations, the first information can be carried in an IMS MO (refer to 3GPP TS 24.167). For example, a leaf node can be added in the IMS MO to define the first information (or the first timer).

[0094] For example, section 4 of 3GPP TS 24.167 (e.g., v18.1.0) introduces the 3GPP IMS MO, as follows:

[0095] The 3GPP IMS MO is used to manage the settings of the UE for the IMS CN subsystem protocols. The management object covers generic parameters for the IM CN subsystem. The MO allows management of these settings on behalf of the end user.

[0096] Further, section 4 introduces the nodes in the IMS MO, as shown in FIG. 6. In this example, a timer (corresponding to the first timer described above) is added in the penultimate leaf node in FIG. 6, i.e., "Timer_eCall_Wait_PSAP_Callback?". The timer can be used to define the callback waiting duration after the emergency call is completed.

[0097] Then, the leaf node corresponding to the timer can be further defined in the subsequent sections of 3GPP TS 24.167. The definition can be, for example, as follows:

[0098] 5.x / <x> / Timer_eCall_Wait_PSAP_Callback

[0099] The optional Timer_eCall_Wait_PSAP_Callback leaf defines the time the UE (Electronic User Equipment) needs to wait for a PSAP callback after completing an eCall.

[0100] -Occurrence:ZeroOrOne (This node appears 0 or 1 times in the model)

[0101] -Format:int(Format: Integer)

[0102] -Access Types:Get,Replace

[0103] -Values:<The maximum time UE waits for a PSAP callback upon completion of eCall> (Value: The maximum duration for the UE to wait for a PSAP callback after completing the eCall).

[0104] The "PSAP callback waiting timer (Timer_eCall_Wait_PSAP_Callback)" mentioned above is the first timer mentioned earlier. By introducing this timer, the callback waiting time of the UE can be clearly defined, thereby improving the reliability of communication.

[0105] Of course, in addition to defining the first information in the IMS MO, in some implementations, the first information can also be defined in the NAS MO (see 3GPP TS 24.368).

[0106] In some implementations, the first information can be transmitted based on a roaming guidance mechanism (see 3GPP TS 23.122 Annex C for details). For example, the first information can be carried in roaming guidance information and transmitted to the terminal device through the roaming guidance information.

[0107] In some embodiments, the first information can be determined based on protocol predefined information. In other words, the value of the first information can be specified by 3GPP protocol. For example, the first information can be used to indicate the minimum duration of the callback. The minimum duration of the callback can be defined by 3GPP protocol.

[0108] In some embodiments, the first information can be recorded or configured in a SIM card (e.g., universal subscriber identity module (USIM)) of the terminal device.

[0109] In some embodiments, the first information can be determined by a combination of the above-mentioned manners. For example, the first information can be transmitted to the terminal device multiple times by different messages. Alternatively, part of the first information can be transmitted by one of the above-mentioned signals (e.g., NAS signaling message), and another part of the first information can be transmitted by another of the above-mentioned signals (e.g., SIP signaling).

[0110] It should be understood that the new requirements on emergency call proposed by CEN in LS (CP-241245) only apply to IVS, that is, CEN only expects 3GPP specification to define the emergency call behavior of IVS to meet the requirements of CEN. However, it can be seen from the provisions of 3GPP TS 22.101 that not only IVS supports the emergency call feature. For example, Annex A.27.1 of 3GPP TS 22.101 contains the following description: "An IVS, or other UE designed to support eCall functionality, shall include in the emergency call set-up an indication that the present call is either a Manually Initiated eCall (MIeC) or an Automatically Initiated eCall (AIeC)". It can be seen from the above description that the terminal device supporting the emergency call function can be of other types in addition to IVS. Therefore, the callback waiting related content mentioned in the embodiments of the present application can not only be applicable to IVS (or vehicle terminal device), but also be applicable to other terminal devices supporting the emergency call function.

[0111] It is to be noted that the emergency call mentioned above is initiated by the terminal device to a handling node of the emergency call. The callback can be initiated by the handling node to the terminal device. The handling node can be, for example, the PSAP mentioned above.

[0112] It is to be further noted that the emergency call mentioned above can be a normal emergency call or an IMS-based emergency call, i.e. IMS-eCall.

[0113] If the scheme provided by the embodiments of the present application is adopted by the 3GPP specification, some sections in the 3GPP specification need to be adjusted (see the foregoing description for details) to adapt to the new requirements proposed by CEN. It is to be noted that the requirements specified by the 3GPP specification need to be adopted by all countries deploying the mobile system. However, the new requirements proposed by CEN are not universally adopted worldwide. For example, in the case of emergency call failure, some countries can hope that the terminal device immediately selects another access point or domain to retry the emergency call, or some countries can not require the terminal device to wait for the callback of the PSAP. Therefore, the new requirements can only be adopted in the CEN member countries, and other countries do not need to comply with the new requirements. Therefore, the modification of the 3GPP specification needs to clearly indicate that the PLMN only applies to the CEN member countries (and can also apply to the allied countries or partners of CEN in the future), and should not force all member countries of 3GPP to comply with the requirements.

[0114] Before the requirements of CEN are applied, the terminal device can first determine whether it is in a CEN member country. A possible implementation is provided below.

[0115] In some embodiments, the terminal device can receive second information. The second information can be sent by a first device (such as a network device or a server) to the terminal device. The second information can be used to determine (or indicate) one or more of the following: whether the terminal device is in a CEN-associated country (or whether the terminal device is attached to, resides in, or is registered in a network of a CEN-associated country), whether the terminal device is required to perform an emergency call according to the emergency call requirements of CEN. In the case where the terminal device determines that it is in a CEN-associated country or is required to perform an emergency call according to the emergency call requirements of CEN, when the terminal device initiates an emergency call, the emergency call process should be performed according to the requirements of CEN for the emergency call. The introduction of the above-mentioned second information helps the terminal device to clearly determine whether to comply with the requirements proposed by CEN for the emergency call, thereby improving the robustness of the communication process.

[0116] In some implementations, the second information is used to determine (or indicate) whether the terminal device is in a CEN-associated country. The CEN-associated country mentioned in the embodiments of the present application can include CEN member countries. Further, in some implementations, the CEN-associated country can also include the alliance countries and / or partners of the CEN. There can be various ways for the second information to determine (or indicate) whether the terminal device is in a CEN-associated country. For example, the second information can indicate whether the PLMN in which the terminal device is currently registered belongs to the PLMN of the CEN-associated country. For another example, the second information can indicate the mobile country code (MCC) of the CEN-associated country, for example, the second information can include a list of MCCs of the CEN-associated country. The terminal device can compare the MCC in the currently registered PLMN with the MCC indicated by the second information, and if the MCC in the currently registered PLMN belongs to the MCC indicated by the second information, it can be determined that the terminal device is in a CEN-associated country.

[0117] In some implementations, the second information can be used to indicate whether the CEN corresponding emergency call requirement is applicable or not applicable. For example, the second information can directly indicate "the CEN corresponding emergency call requirement is applicable". As a more specific example, the second information can be a 1-bit, if the value of the 1-bit is 1, it indicates that the CEN corresponding emergency call requirement is applicable; if the value of the 1-bit is 0, it indicates that the CEN corresponding emergency call requirement is not applicable.

[0118] The content of the second information is introduced above. The carrying manner of the second information is described in detail below.

[0119] In some implementations, the second information is carried in the wireless signal or wireless channel provided by the wireless system. For example, the first device is an access network device, and the second information is carried in the broadcast channel or system information sent by the access network device. Illustratively, the access network device can broadcast the identification of the CEN member country. The identification can be carried in a bit field; or the identification can be man-machine readable text; or the identification can be other information that can be understood or used by the mobile system or terminal device.

[0120] In some implementations, the second information can be carried in IMS level signaling. For example, the second information can be carried in SIP signaling (SIP signaling used by 3GPP IMS system), such as carried in session description protocol (SDP) of SIP. As a more specific example, a list of MCCs of countries associated with CEN can be carried in SDP of SIP, or a string such as "CEN requirements apply" or having similar meaning can be carried. The second information can also be carried in SIP signaling defined in 3GPP TS 24.229.

[0121] In some implementations, the second information can be carried in NAS signaling. The NAS signaling can be carried in one or more of the following: REGISTRATION ACCEPT message, DL NAS TRANSPORT message, SERVICE ACCEPT message, or other messages defined in section 8 of 3GPP TS 24.501 sent by the network to the terminal device. In addition to the above NAS signaling, the second information can also be transmitted through NAS signaling defined in 3GPP TS 24.301 or 3GPP TS 24.008.

[0122] Further, in some implementations, the NAS signaling can include a network feature support information element, such as a 5GS network feature support information element. The network feature support information element can be used to indicate the second information. For example, the network feature support information element can include spare bits, which can be used to carry the second information. Taking the 5GS network feature support information element as an example, the 6th byte of the 5GS network feature support information element includes one or more spare bits, and some or all of the one or more spare bits can be used to carry the second information. As a specific example, the first bit (which can be any bit of the one or more spare bits, such as the 5th bit, the 6th bit, the 7th bit, or the lower 8 bits of the 6th byte of the 5GS network feature support information element) of the one or more spare bits in the network feature support information element can be used to carry the second information. If the first bit has a first value (such as 1), it can indicate that the requirements raised by CEN for emergency calls apply; if the first bit has a second value (such as 0), it can indicate that the requirements raised by CEN for emergency calls do not apply. The following illustrates the indication of the second information in more detail in conjunction with 3GPP TS 24.501.

[0123] For example, the content of section 9.11.3.5 of 3GPP TS 24.501 (e.g. in version 3GPP TS 24.501 v18.7.0) can be modified as follows (the underlined parts are the new additions):

[0124] 9.11.3.5 5GS network feature support

[0125] The purpose of the 5GS network feature support information element is to indicate whether certain features are supported by the network.

[0126] The 5GS network feature support information element is coded as shown in figure 9.11.3.5.1 and table 9.11.3.5.1.

[0127] The 5GS network feature support is a type 4 information element with a minimum length of 3 octets and a maximum length of 6 octets.

[0128] If:

[0129] - the length of 5GS network feature support contents field is set to one, then the UE shall interpret this as a receipt of an information element with all bits of octet 4, octet 5 and octet 6 coded as zero.

[0130] - the length of 5GS network feature support contents field is set to two, the UE shall interpret this as a receipt of an information element with all bits of octet 5 and octet 6 coded as zero.

[0131] - the length of 5GS network feature support contents field is set to three, the UE shall interpret this as a receipt of an information element with all bits of octet 6 coded as zero.

[0132] Table 9.11.3.5.1: 5GS network feature support information element

[0133] In the above example, a new element "CEN eCall applicablity" is added in the 5GS network feature support information element, which indicates whether the requirements of CEN for emergency call are applicable. This element can be used to indicate whether the requirements of CEN for emergency call are applicable. Table 9.11.3.5.1 explains "CEN eCall applicablity", i.e. if the bit corresponding to "CEN eCall applicablity" is 0, it means that the requirements of CEN for emergency call are not applicable, and if the bit corresponding to "CEN eCall applicablity" is 1, it means that the requirements of CEN for emergency call are applicable.

[0134] In some implementations, the second information can be carried in an MO (MO defined in 3GPP specification). The MO can be an IMS MO (see 3GPP TS 24.167) or a NAS MO (see 3GPP TS 24.368).

[0135] In some implementations, the second information can be provided to the terminal device by a home PLMN (HPLMN) operator when activating, e.g., a universal subscriber identity module (USIM). Alternatively, the second information can also be downloaded remotely after using the USIM.

[0136] In some implementations, the second information can be transmitted based on a roaming guidance manner. For example, the second information can be transmitted based on the roaming guidance manner as described in 3GPP TS 23.122, Appendix C.

[0137] In some implementations, the second information can be transmitted based on an STK technology. The implementation of the STK technology can be found in 3GPP TS 31.115 (Security data structure for (U)SIM tool application).

[0138] In some implementations, the second information can be carried in an application layer message. Alternatively, the second information can be transmitted through application-to-application signaling. As an example, the second information can be transmitted based on an over the top technology.

[0139] The method embodiments of the present application are described in detail above in combination with FIG. 1 to FIG. 6. The apparatus embodiments of the present application are described in detail below in combination with FIG. 7 to FIG. 9. It should be understood that the description of the method embodiments and the description of the apparatus embodiments correspond to each other, and thus, the parts not described in detail can be referred to the method embodiments described above.

[0140] FIG. 7 is a structural schematic diagram of a communication device according to an embodiment of the present application. The communication device 700 described in FIG. 7 can be the terminal device described above. The communication device 700 includes a determination module 710. The determination module 710 is configured to determine first information, the first information being used to determine a waiting time length of a callback of an emergency call after the terminal device completes the emergency call.

[0141] In some implementations, the terminal device is in a registered state during the waiting of the callback by the terminal device.

[0142] In some implementations, the first information includes a first timer, the first timer being used to determine the waiting time length of the callback.

[0143] In some implementations, the first information is carried in a non-access stratum (NAS) signaling.

[0144] In some embodiments, the NAS signaling is carried in one or more of the following: a registration accept message; a downlink NAS transport message; a service accept message.

[0145] In some embodiments, the first information is carried in an MO.

[0146] In some embodiments, the MO is an IMS MO or a NAS MO.

[0147] In some embodiments, the first information is carried in session initiation protocol (SIP) signaling; or, the first information is carried in an application layer message; or, the first information is transmitted based on STK technology; or, the first information is transmitted based on a roaming guide manner; or, the first information is determined based on protocol predefined information; or, the first information is recorded in a SIM card of the terminal device.

[0148] In some embodiments, the first information is used to indicate one or more of the following: a waiting time length of the callback; a maximum waiting time length of the callback; a minimum waiting time length of the callback.

[0149] In some embodiments, the communication device 700 further includes a communication module, configured to receive second information, the second information being used to determine one or more of the following: whether the terminal device is in a country associated with a CEN; whether the terminal device is suitable for making an emergency call according to an emergency call requirement corresponding to the CEN.

[0150] In some embodiments, the second information indicates an MCC of the country associated with the CEN.

[0151] In some embodiments, the second information indicates whether the emergency call requirement corresponding to the CEN is suitable or unsuitable.

[0152] In some embodiments, the terminal device is an in-vehicle system.

[0153] In some embodiments, the emergency call is an IMS-based emergency call.

[0154] In some embodiments, the callback is a callback of the emergency call by a PSAP.

[0155] FIG. 8 is a structural schematic diagram of a communication device according to an embodiment of the present application. The communication device 800 shown in FIG. 8 can be the first device mentioned above. The communication device 800 includes a communication module 810. The communication module 810 is configured to send first information to a terminal device, the first information being used to determine a waiting time length of a callback of an emergency call after the terminal device completes the emergency call.

[0156] In some embodiments, the terminal device is in a registered state during the process that the terminal device waits for the callback.

[0157] In some embodiments, the first information comprises a first timer, and the first timer is used to determine a waiting duration of the callback.

[0158] In some embodiments, the first information is carried in NAS signaling.

[0159] In some embodiments, the NAS signaling is carried in one or more of the following: a registration accept message; a downlink NAS transport message; a service accept message.

[0160] In some embodiments, the first information is carried in an MO.

[0161] In some embodiments, the MO is an IMS MO or a NAS MO.

[0162] In some embodiments, the first information is carried in session initiation protocol (SIP) signaling; or, the first information is carried in an application layer message; or, the first information is transmitted based on STK technology; or, the first information is transmitted based on a roaming guide manner.

[0163] In some embodiments, the first information is used to indicate one or more of the following: a waiting duration of the callback; a maximum waiting duration of the callback; a minimum waiting duration of the callback.

[0164] In some embodiments, the communication module 810 is further configured to: send second information to the terminal device, and the second information is used to determine one or more of the following: whether the terminal device is in a country associated with the CEN; whether the terminal device is suitable for making an emergency call according to an emergency call requirement corresponding to the CEN.

[0165] In some embodiments, the second information indicates an MCC of the country associated with the CEN.

[0166] In some embodiments, the second information indicates whether the emergency call requirement corresponding to the CEN is suitable or not suitable.

[0167] In some embodiments, the terminal device is an in-vehicle system.

[0168] In some embodiments, the emergency call is an IMS-based emergency call.

[0169] In some embodiments, the callback is a callback of the emergency call by a PSAP.

[0170] FIG. 9 is a schematic structural diagram of a communication device to which embodiments of the present application can be applied. The dashed line in FIG. 9 indicates that the unit or module is optional. The device 900 can be used to implement the methods described in the above method embodiments. The device 900 can be a chip, a terminal device, or a network device.

[0171] The device 900 can include one or more processors 910. The processor 910 can support the device 900 to implement the methods described in the above method embodiments. The processor 910 can be a general purpose processor or a dedicated processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, etc. The general purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0172] The device 900 can also include one or more memories 920. The memory 920 stores a program that can be executed by the processor 910, so that the processor 910 performs the methods described in the above method embodiments. The memory 920 can be independent of the processor 910 or integrated in the processor 910.

[0173] The device 900 can also include a transceiver 930. The processor 910 can communicate with other devices or chips through the transceiver 930. For example, the processor 910 can perform data transmission and reception with other devices or chips through the transceiver 930.

[0174] Embodiments of the present application also provide a computer readable storage medium for storing a program. The computer readable storage medium can be applied in the terminal device or network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the communication device in the various embodiments of the present application.

[0175] Embodiments of the present application also provide a computer program product. The computer program product includes a program. The computer program product can be applied in the terminal device or network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the communication device in the various embodiments of the present application.

[0176] The embodiment of the present application further provides a computer program. The computer program can be applied to the terminal device or the network device provided by the embodiment of the present application, and the computer program enables a computer to execute the method performed by the communication device in the embodiments of the present application.

[0177] It should be understood that the terms "system" and "network" can be used interchangeably in the present application. In addition, the terms used in the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third", and "fourth" and the like in the specification and claims of the present application and the drawings are used to distinguish different objects, and are not used to describe a particular order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0178] In the embodiments of the present application, the "indication" mentioned can be direct indication, or indirect indication, or can represent an associated relationship. For example, A indicates B, which can mean that B can be obtained by A; or A indirectly indicates B, for example, A indicates C, and B can be obtained by C; or A and B have an associated relationship.

[0179] In the embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information.

[0180] In the embodiments of the present application, the term "corresponding" can represent a direct or indirect corresponding relationship between the two, or can represent an associated relationship between the two, or can represent an indication and being indicated, configuration and being configured, and the like.

[0181] In the embodiments of the present application, "predefined" or "preconfigured" can be implemented by pre-saving corresponding codes, tables or other information that can be used to indicate related information in devices (for example, including terminal devices and network devices), and the present application does not limit the specific implementation manner. For example, predefinition can refer to definition in a protocol.

[0182] In the embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field, for example, can include an LTE protocol, an NR protocol, and a related protocol applied to a future communication system, and the present application does not limit this.

[0183] The term "and / or" in the embodiments of the present application is only used to describe the associated relationship of associated objects, which means that there can be three relationships, for example, A and / or B can represent the three cases of A alone, A and B together, and B alone. In addition, the character " / " in this paper generally represents that the associated objects before and after are a "or" relationship.

[0184] In various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0185] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other ways. For example, the device embodiments described above are only schematic, and the division of the units is only a logical function division, and there can be another division way in actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0186] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on multiple network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiment scheme.

[0187] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit.

[0188] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server, data center and the like integrated with one or more available media sets. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, digital video disc (DVD)) or semiconductor media (for example, solid state disk (SSD)) and the like.

[0189] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.< / x>

Claims

1. A communication method characterized by comprising: Comprising: A terminal device determines first information, the first information being used to determine a waiting time length of a callback of an emergency call after the terminal device completes the emergency call.

2. The method of claim 1, wherein, The terminal device is in a registered state during a process in which the terminal device waits for the callback.

3. The method according to claim 1 or 2, characterized in that, The first information comprises a first timer, the first timer being used to determine the waiting time length of the callback.

4. The method according to any one of claims 1 to 3, characterized in that, The first information is carried in a non-access stratum (NAS) signaling.

5. The method of claim 4, wherein, The NAS signaling is carried in one or more of the following: a registration accept message; a downlink NAS transport message; a service accept message.

6. The method according to any one of claims 1 to 3, characterized in that, The first information is carried in a management object (MO).

7. The method of claim 6, wherein, The MO is an Internet Protocol Multimedia Subsystem (IMS) MO or a NAS MO.

8. The method of claim 1 or 2, wherein: the first information is carried in a session initiation protocol (SIP) signaling; or the first information is carried in an application layer message; or the first information is transmitted based on a subscriber identity module toolkit (STK) technology; or the first information is transmitted based on a roaming steering manner; or the first information is determined based on protocol predefinition information; or the first information is recorded in a SIM card of the terminal device.

9. The method according to any one of claims 1 to 8, characterized in that, The first information is used to indicate one or more of the following: the waiting time length of the callback; a maximum waiting time length of the callback; or a minimum waiting time length of the callback.

10. The method according to any one of claims 1 to 9, characterized in that, The method further comprises: The terminal device receives second information, the second information being used to determine one or more of the following: whether the terminal device is in a European Committee for Standardization (CEN) associated country; or whether the terminal device is applicable to an emergency call requirement corresponding to the CEN for the emergency call.

11. The method of claim 10, wherein, The second information indicates a mobile country code (MCC) of the CEN associated country.

12. The method according to claim 10 or 11, characterized in that, The second information indicates that the CEN corresponding emergency call requirement is applicable or not applicable.

13. The method according to any one of claims 1 to 12, characterized in that, The terminal device is an in-vehicle system.

14. The method according to any one of claims 1 to 13, characterized in that, The emergency call is an IMS based emergency call.

15. The method according to any one of claims 1 to 14, characterized in that, The callback is a callback of the emergency call by a public safety answering point (PSAP).

16. A method of communication, comprising: Comprising: A first device sends first information to a terminal device, the first information being used to determine a waiting time length of a callback of an emergency call after the terminal device completes the emergency call.

17. The method of claim 16, wherein, The terminal device is in a registered state during a process in which the terminal device waits for the callback.

18. The method according to claim 16 or 17, characterized in that The first information comprises a first timer, the first timer being used to determine the waiting time length of the callback.

19. The method of any one of claims 16-18, wherein, The first information is carried in a non-access stratum (NAS) signaling.

20. The method of claim 19, wherein, The NAS signaling is carried in one or more of the following: a registration accept message; a downlink NAS transport message; a service accept message.

21. The method of any one of claims 16-18, wherein, The first information is carried in a management object (MO).

22. The method of claim 21, wherein, The MO is an Internet Protocol Multimedia Subsystem (IMS) MO or a NAS MO.

23. The method of claim 16 or 17, wherein: the first information is carried in a session initiation protocol (SIP) signaling; or the first information is carried in an application layer message; or the first information is transmitted based on a subscriber identity module toolkit (STK) technology; or the first information is transmitted based on a roaming steering manner; or the first information is determined based on protocol predefinition information; or the first information is recorded in a SIM card of the terminal device. The first information is transmitted based on a roaming guide manner.

24. The method of any one of claims 16-23, wherein, The first information is used to indicate one or more of: a waiting time length of the callback; a maximum waiting time length of the callback; a minimum waiting time length of the callback.

25. The method of any one of claims 16-24, wherein, The method further comprises: The first device sends second information to the terminal device, and the second information is used to determine one or more of: whether the terminal device is in a country associated with the European Committee for Standardization (CEN); whether the terminal device makes an emergency call in accordance with an emergency call requirement corresponding to the CEN.

26. The method of claim 25, wherein, The second information indicates a mobile country code (MCC) of the country associated with the CEN.

27. The method of claim 25 or 26, wherein, The second information indicates whether the emergency call requirement corresponding to the CEN is applicable or not applicable.

28. The method of any one of claims 16-27, wherein, The terminal device is an in-vehicle system.

29. The method of any one of claims 16 to 28, wherein, The emergency call is an IMS-based emergency call.

30. The method of any one of claims 16-29, wherein, The callback is a callback of the emergency call by a public safety answering point (PSAP).

31. A communications device, characterized by The communication device is a terminal device, and the communication device comprises: a determining module configured to determine first information, the first information being used to determine a waiting time length of a callback of an emergency call after the terminal device completes the emergency call.

32. The communication device of claim 31, wherein, During a process in which the terminal device waits for the callback, the terminal device is in a registered state.

33. The communication device of claim 31 or 32, wherein, The first information comprises a first timer, and the first timer is used to determine the waiting time length of the callback.

34. The communication device of any one of claims 31 to 33, wherein, The first information is carried in non-access stratum (NAS) signaling.

35. The communication device of claim 34, wherein, The NAS signaling is carried in one or more of: a registration accept message; a downlink NAS transport message; a service accept message.

36. The communication device of any one of claims 31 to 33, wherein, The first information is carried in a management object (MO).

37. The communication device of claim 36, wherein, The MO is an Internet Protocol Multimedia Subsystem (IMS) MO or a NAS MO.

38. The communication device according to claim 31 or 32, wherein: the first information is carried in session initiation protocol (SIP) signaling; or the first information is carried in an application layer message; or the first information is transmitted based on a subscriber identity module toolkit (STK) technology; or the first information is transmitted based on a roaming guide manner; or the first information is determined based on protocol pre-defined information; or the first information is recorded in a SIM card of the terminal device.

39. The communication device according to any one of claims 31 to 38, characterized by, The first information is used to indicate one or more of: a waiting time length of the callback; a maximum waiting time length of the callback; a minimum waiting time length of the callback.

40. The communication device according to any one of claims 31 to 39, wherein, The communication device further comprises: a communication module configured to receive second information, the second information being used to determine one or more of: whether the terminal device is in a country associated with the European Committee for Standardization (CEN); whether the terminal device makes an emergency call in accordance with an emergency call requirement corresponding to the CEN.

41. The communication device of claim 40, wherein, The second information indicates a mobile country code (MCC) of the country associated with the CEN.

42. The communication device of claim 40 or 41, wherein, The second information indicates whether the emergency call requirement corresponding to the CEN is applicable or not applicable.

43. The communication device of any one of claims 31 to 42, wherein, The terminal device is an in-vehicle system.

44. The communication device of any one of claims 31 to 43, wherein, The emergency call is an IMS-based emergency call.

45. The communication device according to any one of claims 31 to 44, wherein, The callback is a callback of the emergency call by a public safety answering point (PSAP).

46. A communications device, characterized by The communication device is a first device, and the communication device comprises: The communication module is configured to send first information to the terminal device, the first information being used to determine a waiting time length of a callback of the emergency call after the terminal device completes the emergency call.

47. The communication device of claim 46, wherein, The terminal device is in a registered state during a process in which the terminal device waits for the callback.

48. The communication device of claim 46 or 47, wherein, The first information comprises a first timer, and the first timer is used to determine the waiting time length of the callback.

49. The communication device of any one of claims 46-48, wherein, The first information is carried in a non-access stratum (NAS) signaling.

50. The communication device of claim 49, wherein, The NAS signaling is carried in one or more of the following: a registration accept message; a downlink NAS transport message; a service accept message.

51. The communication device of any one of claims 46-48, wherein, The first information is carried in a management object (MO).

52. The communication device of claim 51, wherein, The MO is an Internet Protocol Multimedia Subsystem (IMS) MO or a NAS MO.

53. The communication device according to claim 46 or 47, wherein: the first information is carried in a session initiation protocol (SIP) signaling; or the first information is carried in an application layer message; or the first information is transmitted based on a subscriber identity module toolkit (STK) technology; or the first information is transmitted based on a roaming guide.

54. The communication device of any one of claims 46 to 53, wherein, The first information is used to indicate one or more of the following: the waiting time length of the callback; a maximum waiting time length of the callback; or a minimum waiting time length of the callback.

55. The communication device according to any one of claims 46-54, wherein, The communication module is further configured to: send second information to the terminal device, the second information being used to determine one or more of the following: whether the terminal device is in a country associated with the European Committee for Standardization (CEN); or whether the terminal device is suitable for making an emergency call according to a corresponding emergency call requirement of the CEN.

56. The communication device of claim 55, wherein, The second information indicates a mobile country code (MCC) of the country associated with the CEN.

57. The communication device of claim 55 or 56, wherein, The second information indicates whether the corresponding emergency call requirement of the CEN is applicable or not applicable.

58. The communication device of any one of claims 46 to 57, wherein, The terminal device is an in-vehicle system.

59. The communication device of any one of claims 46-58, wherein, The emergency call is an IMS-based emergency call.

60. The communication device of any one of claims 46 to 59, wherein, The callback is a callback of the emergency call by a public safety answering point (PSAP).

61. A communications device, characterized by A chip, comprising a transceiver, a memory and a processor, the memory being configured to store a program, the processor being configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the communication device executes the method according to any one of claims 1 to 30.

62. An apparatus, comprising: A device, comprising a processor configured to invoke a program from a memory, so that the device executes the method according to any one of claims 1 to 30.

63. A chip, comprising: A chip, comprising a processor configured to invoke a program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 30.

64. A computer-readable storage medium, characterized in that, A computer program product, having a program stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 30.

65. A computer program product, characterised in that, A computer program product, having a program stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 30.

66. A computer program characterised in that, The computer program product causes a computer to execute the method according to any one of claims 1 to 30.

Images