Communication method and device

Abstract

The embodiment of the invention provides a communication method and device, and the method comprises the steps: enabling a user to initiate an emergency service when terminal equipment executes a first process; the terminal device releases the communication link resource of the first process in the case of network congestion; first request information is sent to a network device, the first request information is used for requesting to process a target process, and the target process is triggered by the emergency service; and the terminal device receives first response information of the target flow from the network device. In the method, an emergency service is initiated at a terminal equipment side, if a current network is congested, the terminal equipment releases communication link resources of a flow which is being executed at present, and initiates new flow request information to a network side based on the emergency service; therefore, the network side can timely and effectively provide communication link resources for the process initiated by the emergency service, so that network connection failure caused by the fact that the emergency service is not processed due to timeout can be avoided.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0002] In the communication network, registration and services are sent serially on the terminal device side, that is, when the terminal device is executing the registration process, the service process will be cached, and the current protocol also clearly stipulates that the terminal device cannot initiate a new service request while executing the registration process or the service process.

[0003] In some scenarios, when the terminal device is executing a registration process or a business process, an emergency service (such as an emergency call) is initiated on the terminal device side. The emergency service will be cached and the terminal device can initiate a request for the emergency service only after the registration or business process is completed. If there is flow control processing or a large load on the core network side, it will choose not to reply to the terminal device, or even directly discard the registration request or business request initiated by the terminal device. In this case, the terminal device side can only wait until the timer of the current registration or business process times out before it can process the cached emergency service. However, the duration of the emergency service access attempt is usually relatively short, so the emergency service may not be cached yet, and the network connection fails due to an attempt timeout. Therefore, how to effectively avoid the failure of emergency services to connect to the network due to timeouts in network communications is one of the problems that urgently need to be solved. Summary of the invention

[0004] The present application proposes a communication method and device, which can effectively solve the problem of network connection failure due to timeout of emergency services in network communication.

[0005] In an embodiment of the present application, in order to effectively solve the problem of connection failure caused by timeout of emergency services in network communications, two solutions are provided. The first solution can refer to the contents of the following first aspect (terminal device side) and second aspect (network device side), and the second solution can refer to the contents of the following third aspect (terminal device side) and fourth aspect (network device side).

[0006] In the first aspect, the present application implements a communication method, which can be executed by a terminal device or by a chip or chip system corresponding to the terminal device, without limitation. The specific steps of the method may include: when executing the first process, the user initiates an emergency service; when network congestion occurs, the communication link resources of the first process are released; a first request message is sent to a network device, the first request message is used to request processing of a target process, the target process is triggered by the emergency service; and a first response message of the target process is received from the network device.

[0007] In the embodiment of the present application, the first process does not include the process of the emergency service, for example, the first process is a common registration process or a common service process.

[0008] The network devices involved in the embodiments of the present application may include access network devices and / or core network devices; the terminal device and the core network device may communicate through the access network device, for example, the terminal device transmits information to the core network device through the access network device. In addition, the communication between the terminal device and the network device may be a direct form of communication (i.e., terminal device to network device) or an indirect form of communication (for example, the terminal device and the network device may communicate through forwarding of one or more third-party communication devices or network elements). Furthermore, the embodiments of the present application do not limit the specific technology used for communication between the terminal device and the network device.

[0009] In the present application scheme, when an emergency service is initiated on the terminal device side while executing the first process, the terminal device releases the communication link resources of the first process when network congestion occurs, and initiates request information of the target process to the network device side based on the emergency service, so that the network device side can provide communication link resources for the target process initiated by the emergency service in a timely and effective manner, thereby avoiding the failure of the emergency service to connect to the network due to timeout and non-processing.

[0010] In a possible implementation, when the target process is an emergency registration or non-emergency registration process, the first request information is the emergency registration request information or the non-emergency registration request information, and the first response information is the emergency registration response information or the non-emergency registration response information.

[0011] In a possible implementation manner, the first request information includes first indication information, and the first indication information is used to indicate that the established communication link is not to be released after the emergency registration or the non-emergency registration process.

[0012] Exemplarily, if the first indication information is a follow on mark, then the follow on mark is used to indicate that information is further transmitted after the emergency registration or the non-emergency registration process, which is equivalent to instructing the network device side to keep the communication link from being released after establishing the communication link for the emergency registration or the non-emergency registration, so that the communication link can be used to transmit subsequent information and / or data sent by the terminal device and / or the network device.

[0013] If the first indication information is not a follow on mark, the first indication information may be carried in the first request information, or may not be carried in the first request information, but may be sent by the terminal device to the network device in other ways. For example, the first indication information may be independently located in the same message as the first request information and sent to the network device, or the first indication information may be sent to the network device separately, and this application does not make specific limitations on this.

[0014] Through this implementation, when the terminal device initiates an emergency registration or a non-emergency registration to the network device, the first request information is equivalent to the emergency registration request information or the non-emergency registration request information. Then, after receiving the first request information, the network device will establish a communication link for the emergency registration or the non-emergency registration; in addition, the terminal device also sends the first indication information to the network device. Therefore, after the network device establishes the communication link for the emergency registration or the non-emergency registration, it can keep the established communication link from being released based on the first indication information, so as to facilitate the subsequent transmission of information and / or data between the terminal device and the network device.

[0015] In addition, the first request information is carried in the first message, and the first message also carries first link establishment reason information, where the first link establishment reason information is used to indicate that the request to establish the communication link is for the emergency service.

[0016] Through this implementation, when the terminal device initiates an emergency registration process or a non-emergency registration process based on the emergency service, when the terminal device sends the corresponding registration request information to the network device, it also sends the link establishment reason information for indicating the emergency service, so that the network side determines that it is the emergency service that requests to establish a communication link based on the link establishment reason information, thereby providing the emergency service with communication link resources in a timely manner with high priority, so as to avoid the emergency service failing to connect to the network due to timeout.

[0017] In another possible implementation, when the target process is a business process, the first request information is business request information, the first request information includes business type information, and the business type information is used to indicate that the currently executed business type is the emergency business; the first response information is business response information.

[0018] In addition, the first request information is carried in the second message, and the second message also carries second link establishment reason information, where the second link establishment reason information is used to indicate that the request to establish the communication link is for the emergency service.

[0019] Through this implementation, when the terminal device initiates a service process based on the emergency service, the terminal device sends corresponding service request information to the network device, and the service request information carries service type information for indicating the emergency service. In addition, the terminal device also sends link establishment reason information to the network device, so that the network device side determines that it is the emergency service that requests to establish a link based on the link establishment reason, thereby providing communication link resources for the emergency service in a timely manner with high priority, so as to avoid the emergency service failing to connect to the network due to timeout.

[0020] In a possible implementation, the method further includes: when no network congestion occurs, the terminal device waits for the first process to end.

[0021] In this embodiment, the first request information sent by the terminal device to the network device is the request information of the emergency service, and the first request information includes service type information, and the service type information is used to indicate that the currently executed service type is the emergency service; the first response information is the response information of the emergency service.

[0022] Through this implementation, if there is no network congestion at present, the terminal device will promptly receive the response information of the first process fed back by the network device side. Therefore, the terminal device does not need to release the communication link resources of the first process, but waits for the first process to end, and reuses the communication link resources of the first process to send the request information of the emergency service to the network device. This can not only ensure the timely execution of the emergency service, but also avoid the additional resources and delay overhead generated by rebuilding the link.

[0023] In the second aspect, the present application provides a communication method, which can be executed by a network device or by a chip or chip system corresponding to the network device, without limitation. The specific steps of the method may include: receiving a first request message from a terminal device, the first request message is used to request processing of a target process, the target process is triggered by an emergency service of the terminal device; processing the target process based on the first request message; and sending a first response message of the target process to the terminal device.

[0024] In the embodiment of the present application, the first process refers to a non-urgent process, such as a normal registration process or a normal business process.

[0025] The network devices involved in the embodiments of the present application may include access network devices and / or core network devices; the terminal device and the core network device may communicate through the access network device, for example, the terminal device transmits information to the core network device through the access network device. In addition, the communication between the terminal device and the network device may be a direct form of communication (i.e., terminal device to network device) or an indirect form of communication (for example, the terminal device and the network device may communicate through forwarding of one or more third-party communication devices or network elements). Furthermore, the embodiments of the present application do not limit the specific technology used for communication between the terminal device and the network device.

[0026] In the present application scheme, when an emergency service is initiated on the terminal device side while executing the first process, the terminal device releases the communication link resources of the first process when determining that the current network is congested, and initiates request information of the target process to the network device side based on the emergency service, so that the network device side can provide communication link resources for the target process initiated by the emergency service in a timely and effective manner, thereby avoiding the failure of the emergency service to connect to the network due to timeout and failure to be processed.

[0027] In a possible implementation, when the target process is an emergency registration or non-emergency registration process, the first request information is the emergency registration request information or the non-emergency registration request information, and the first response information is the emergency registration response information or the non-emergency registration response information.

[0028] In a possible implementation manner, the first request information includes first indication information, and the first indication information is used to indicate that the established communication link is not to be released after the emergency registration or the non-emergency registration process.

[0029] Exemplarily, if the first indication information is a follow on mark, then the follow on mark is used to indicate that information is further transmitted after the emergency registration or the non-emergency registration process, which is equivalent to instructing the network device side to keep the communication link from being released after establishing the communication link for the emergency registration or the non-emergency registration, so that the communication link can be used to transmit subsequent information and / or data sent by the terminal device and / or the network device.

[0030] If the first indication information is not a follow on mark, the first indication information may be carried in the first request information, or may not be carried in the first request information, but may be sent by the terminal device to the network device in other ways. For example, the first indication information may be independently located in the same message as the first request information and sent to the network device, or the first indication information may be sent to the network device separately, and this application does not make specific limitations on this.

[0031] Through this implementation, when the terminal device initiates an emergency registration or a non-emergency registration to the network device, the first request information is equivalent to the emergency registration request information or the non-emergency registration request information. Then, after receiving the first request information, the network device will establish a communication link for the emergency registration or the non-emergency registration; in addition, the terminal device also sends the first indication information to the network device. Therefore, after the network device establishes the communication link for the emergency registration or the non-emergency registration, it can keep the established communication link from being released based on the first indication information, so as to facilitate the subsequent transmission of information and / or data between the terminal device and the network device.

[0032] In addition, the first request information is carried in the first message, and the first message also carries first link establishment reason information, where the first link establishment reason information is used to indicate that the request to establish the communication link is for the emergency service.

[0033] Through this implementation, when the terminal device initiates an emergency registration process or a non-emergency registration process based on the emergency service, when the terminal device sends the corresponding registration request information to the network device, it also sends the link establishment reason information for indicating the emergency service, so that the network device side determines that it is the emergency service that requests to establish a communication link based on the link establishment reason information, thereby providing communication link resources for the emergency service in a timely manner with high priority, so as to avoid the emergency service failing to connect to the network due to timeout.

[0034] In a possible implementation, when the target process is a business process, the first request information is business request information, the first request information includes business type information, and the business type information is used to indicate that the currently executed business type is the emergency business; the first response information is business response information.

[0035] In addition, the first request information is carried in the second message, and the second message also carries second link establishment reason information, where the second link establishment reason information is used to indicate that the request to establish the communication link is for the emergency service.

[0036] Through this implementation, when the terminal device initiates a service process based on the emergency service, the terminal device sends corresponding service request information to the network device, and the service request information carries service type information for indicating the emergency service. In addition, the terminal device also sends link establishment reason information to the network device, so that the network device side determines that it is the emergency service that requests to establish a communication link based on the link establishment reason, thereby providing communication link resources for the emergency service in a timely manner with high priority, so as to avoid the emergency service failing to connect to the network due to timeout.

[0037] On the third aspect, the present application implements a communication method, which can be executed by a terminal device or by a chip or chip system corresponding to the terminal device, without limitation. The specific steps of the method may include: when executing the first process, the user initiates an emergency service; if no response information of the first process is received within a preset first time period, a first request information is sent to a network device, and the first request information is used to request processing of a target process, which is triggered by the emergency service, and the target process uses the same communication link resources as the first process; and a first response information of the target process is received from the network device.

[0038] In the embodiment of the present application, the first process does not include the process of the emergency service, for example, the first process is a common registration process or a common service process.

[0039] The network devices involved in the embodiments of the present application may include access network devices and / or core network devices; the terminal device and the core network device may communicate through the access network device, for example, the terminal device transmits information to the core network device through the access network device. In addition, the communication between the terminal device and the network device may be a direct form of communication (i.e., terminal device to network device) or an indirect form of communication (for example, the terminal device and the network device may communicate through forwarding of one or more third-party communication devices or network elements). Furthermore, the embodiments of the present application do not limit the specific technology used for communication between the terminal device and the network device.

[0040] In the present application scheme, when the terminal device is executing the first process and the user initiates an emergency service, if no response information of the first process is received within the preset first time period, the communication link resources of the first process are reused in the connected state, and the first request information of the target process triggered by the emergency service is sent to the network device, so that the network device side can process the target process in a timely manner. This scheme can not only avoid the failure of the emergency service to connect to the network due to timeout, but also reduce the overhead of additional resources and delays generated by re-establishing the communication link.

[0041] In the embodiment of the present application, if the target process triggered by the emergency service is an emergency registration process or a non-emergency registration process, the following implementation methods may be included:

[0042] Implementation method 1: the first request information is the emergency registration request information; correspondingly, the first response information is the emergency registration response information.

[0043] It can be known from the implementation mode 1 that the terminal device initiates an emergency registration process to the network device side based on the emergency service to ensure that the network device side can process the emergency registration in time.

[0044] Implementation method 2: the first request information is the non-emergency registration request information, the first request information includes the identification information of the emergency service, and the identification information of the emergency service is used to indicate that the current non-emergency registration process is triggered by the emergency service; accordingly, the first response information is the non-emergency registration response information.

[0045] In the second embodiment, the first request information is carried in a first message, and the first message also carries first link reason information, where the first link reason information is used to indicate that the non-emergency registration process is triggered by the emergency service.

[0046] Through implementation mode 2, it can be known that the terminal device initiates a non-emergency registration (i.e., ordinary registration) process to the network device based on the emergency service. Then the non-emergency registration request information will carry the identifier of the emergency service, and the terminal device will also send link reason information to the network device side to indicate that the non-emergency registration is triggered by the emergency service, so that the network device side can process the non-emergency registration process in a timely manner with high priority based on the link reason information and the identifier of the emergency service.

[0047] In the embodiment of the present application, if the target process triggered by the emergency service is a business process, the following possible implementation methods may be included:

[0048] In a possible implementation, the first request information is service request information, and the first request information includes service type information, and the service type information is used to indicate that the service type currently being executed is the emergency service; accordingly, the first response information is service response information.

[0049] In this implementation, the first request information is carried in the second message, and the second message also carries second link reason information, where the second link reason information is used to indicate that the current service process is triggered by the emergency service.

[0050] Through this implementation, it can be seen that the terminal device sends service request information including service type information to the network device side based on the emergency service. In addition, it also sends link reason information to the network device to indicate that the service process is triggered by the emergency service, so that the network device side can process the service process in a timely manner with high priority based on the link reason information and the service request information.

[0051] In the fourth aspect, the present application implements a communication method, which can be executed by a network device or by a chip or chip system corresponding to the network device, without limitation. The specific steps of the method may include: receiving a first request message from a terminal device, the first request message is used to request processing of a target process, the target process is triggered by an emergency service of the terminal device, and the target process uses the same communication link resources as the currently executed first process; based on the first request message, processing the target process; sending a first response message of the target process to the terminal device.

[0052] In the embodiment of the present application, the first process does not include the process of the emergency service, for example, the first process is a common registration process or a common service process.

[0053] The network devices involved in the embodiments of the present application may include access network devices and / or core network devices; the terminal device and the core network device may communicate through the access network device, for example, the terminal device transmits information to the core network device through the access network device. In addition, the communication between the terminal device and the network device may be a direct form of communication (i.e., terminal device to network device) or an indirect form of communication (for example, the terminal device and the network device may communicate through forwarding of one or more third-party communication devices or network elements). Furthermore, the embodiments of the present application do not limit the specific technology used for communication between the terminal device and the network device.

[0054] In the present application scheme, when the terminal device is executing the first process, an emergency service is initiated. If the network device does not feed back the response information of the first process to the terminal device within the preset first time period, the network device will receive the first request information of the target process sent by the terminal device based on the emergency service; and then the network device side can process the target process in a timely manner based on the first request information. This scheme can not only avoid the emergency service from failing to connect to the network due to timeout, but also reduce the overhead of additional resources and delays generated by re-establishing the communication link.

[0055] In the embodiment of the present application, if the target process triggered by the emergency service on the terminal device side is an emergency registration process or a non-emergency registration process, the following implementation methods may be included:

[0056] Implementation method 1: the first request information is the emergency registration request information; correspondingly, the first response information is the emergency registration response information.

[0057] Through implementation mode 1, it can be known that the terminal device initiates an emergency registration process to the network device side based on the emergency service to ensure that the network device side can process the emergency registration in time.

[0058] Implementation method 2: the first request information is the non-emergency registration request information, the first request information includes the identification information of the emergency service, and the identification information of the emergency service is used to indicate that the current non-emergency registration process is triggered by the emergency service; accordingly, the first response information is the non-emergency registration response information.

[0059] In the second embodiment, the first request information is carried in a first message, and the first message also carries first link reason information, where the first link reason information is used to indicate that the non-emergency registration process is triggered by the emergency service.

[0060] Through implementation mode 2, it can be known that the terminal device initiates a non-emergency registration (i.e., ordinary registration) process to the network device based on the emergency service. Then the non-emergency registration request information will carry the identifier of the emergency service, and the terminal device will also send link reason information to the network device side to indicate that the non-emergency registration is triggered by the emergency service, so that the network device side can process the non-emergency registration process in a timely manner with high priority based on the link reason information and the identifier of the emergency service.

[0061] In the embodiment of the present application, if the target process triggered by the emergency service is a business process, the following possible implementation methods may be included:

[0062] In a possible implementation, the first request information is service request information, and the first request information includes service type information, and the service type information is used to indicate that the service type currently being executed is the emergency service; accordingly, the first response information is service response information.

[0063] In this implementation, the first request information is carried in the second message, and the second message also carries second link reason information, where the second link reason information is used to indicate that the current service process is triggered by the emergency service.

[0064] Through this implementation, it can be seen that the terminal device sends service request information including service type information to the network device side based on the emergency service. In addition, it also sends link reason information to the network device to indicate that the service process is triggered by the emergency service, so that the network device side can process the service process in a timely manner with high priority based on the link reason information and the service request information.

[0065] In the fifth aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the first aspect or the third aspect. The device may be a terminal device, or the device may be a component in the terminal device (for example, a chip, or a chip system, or a circuit), or may be a device that can be used in combination with the terminal device.

[0066] In one possible implementation, the device may include a module or unit corresponding to the method / operation / step / action described in the first aspect, and the module or unit may be a hardware circuit, or software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in the first aspect or any possible implementation of the first aspect; or the processing unit may be used to perform the method described in the third aspect or any possible implementation of the third aspect.

[0067] In the sixth aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the second aspect or the fourth aspect. The device may be a network device, or the device may be a component in the network device (for example, a chip, or a chip system, or a circuit), or may be a device that can be used in combination with the network device.

[0068] In one possible implementation, the device may include a module or unit corresponding to the method / operation / step / action described in the second aspect, and the module or unit may be a hardware circuit, or software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in the second aspect or any possible implementation of the second aspect; or the processing unit may be used to perform the method described in the fourth aspect or any possible implementation of the fourth aspect.

[0069] In the seventh aspect, an embodiment of the present application provides a device, which includes: at least one processor and a communication interface; wherein the communication interface is used to communicate with other devices; the processor is used to run a set of programs so that the device implements the method provided by the above-mentioned first aspect or any possible implementation method thereof, or enables the device to implement the method provided by the above-mentioned second aspect or any possible implementation method thereof.

[0070] In an eighth aspect, an embodiment of the present application provides a device, comprising: at least one processor and a communication interface; wherein the communication interface is used to communicate with other devices; the processor is used to run a set of programs so that the device implements the method provided in the third aspect or any possible implementation thereof, or implements the method provided in the fourth aspect or any possible implementation thereof.

[0071] In the ninth aspect, an embodiment of the present application also provides a computer storage medium, which stores a software program. When the software program is read and executed by one or more processors, it can implement the method provided by the first aspect or any possible implementation method thereof, or implement the method provided by the second aspect or any possible implementation method thereof, or implement the method provided by the third aspect or any possible implementation method thereof, or implement the method provided by the fourth aspect or any possible implementation method thereof.

[0072] In the tenth aspect, the embodiments of the present application also provide a computer program product comprising instructions, which, when executed on a computer, enables the method provided by the first aspect or any possible implementation thereof to be executed, or enables the method provided by the second aspect or any possible implementation thereof to be executed, or enables the method provided by the third aspect or any possible implementation thereof to be executed, or enables the method provided by the fourth aspect or any possible implementation thereof to be executed.

[0073] In an eleventh aspect, an embodiment of the present application provides a communication system, comprising a terminal device capable of implementing the method provided in the first aspect above, and a network device capable of implementing the method provided in the second aspect above.

[0074] In the twelfth aspect, an embodiment of the present application provides a communication system, including a terminal device capable of implementing the method provided in the third aspect above, and a network device capable of implementing the method provided in the fourth aspect above.

[0075] In the thirteenth aspect, an embodiment of the present application also provides a chip system, which includes a processor for supporting a terminal device to implement the functions involved in the first or third aspect above; or for supporting a network device to implement the functions involved in the second or fourth aspect above.

[0076] In a possible design, the chip system further includes a memory, which is used to store necessary program instructions and data executed by the loading device. The chip system can be composed of chips or include chips and other discrete devices.

[0077] It should be noted that the technical effects that can be achieved by any possible implementation method of the above-mentioned fifth to thirteenth aspects or the fifth to thirteenth aspects can be correspondingly referred to the technical effects that can be achieved by any possible implementation method of the above-mentioned first to fourth aspects or the first to fourth aspects; they will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] Figure 1AThis is one of the schematic diagrams of the architecture of the mobile communication system used in the embodiments of the present application;

[0079] Figure 1B The second schematic diagram of the architecture of the mobile communication system applied in the embodiment of the present application;

[0080] Figure 2 A flowchart of an emergency service in which a call fails due to an attempt timeout;

[0081] Figure 3A A flow chart of a communication method provided in an embodiment of the present application;

[0082] Figure 3B A flow chart of another communication method provided in an embodiment of the present application;

[0083] Figure 4 A specific flow chart of the first embodiment provided in the embodiments of the present application;

[0084] Figure 5 A specific flow chart of the second embodiment provided in the embodiments of the present application;

[0085] Figure 6 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0086] Figure 7 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;

[0087] Figure 8 A schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0088] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. The terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to be used as limitations on the present application. As used in the specification and the appended claims of the present application, the singular expressions "one", "a kind", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the embodiments of the present application, "one or more" refers to one, two or more; "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist; for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0089] References to "one embodiment" or "some embodiments" etc. described in this specification mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Thus, the statements "in one embodiment", "in some embodiments", "in other embodiments", etc. that appear in different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "include", "comprise", "have" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways. Words such as "exemplary" or "for example" are used to represent examples, illustrations or descriptions, and any embodiment or design described as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other embodiments or designs. The use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way for easy understanding.

[0090] The multiple involved in the embodiments of the present application refers to greater than or equal to two. It should be noted that in the description of the embodiments of the present application, the words "first", "second", etc. are only used to distinguish the purpose of description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order. In addition, the term "used for indication" mentioned in the description of the embodiments of the present application may include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used to indicate A, it may include that the indication information directly indicates A or indirectly indicates A, and it does not mean that the indication information must carry A.

[0091] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: Wideband Code Division Multiple Access (WCDMA) system, general packet radio service (GPRS), Long Term Evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system or future sixth generation communication system, etc.

[0092] Figure 1A is a schematic diagram of the architecture of a mobile communication system to which an embodiment of the present application is applied, Figure 1B It is a schematic diagram of the network structure corresponding to the communication system. The terminal device is connected to the access network device, and the access network device is connected to the core network device by wireless or wired means. The core network device and the access network device can be independent and different physical devices, or the functions of the core network device and the logical functions of the access network device can be integrated on the same physical device, or the functions of some core network devices and some access network devices can be integrated on one physical device. The terminal device can be fixed or movable. Figure 1A and Figure 1B This is just a schematic diagram, and the communication system may also include other network devices.

[0093] refer to Figure 1B The core network equipment includes session management network elements, access management network elements, user plane function network elements, etc.

[0094] Session management network element: mainly used for session management, allocation and management of Internet protocol (IP) addresses of terminal devices, selection of endpoints for manageable user equipment plane functions, policy control, or charging function interfaces, and downlink data notification. In 5G communications, the session management network element may be a session management function (SMF) network element. In future communications such as 6G communications, the session management function network element may still be an SMF network element, or have other names, which is not limited in this application. Nsmf is a service-based interface provided by SMF. SMF can communicate with other network functions through Nsmf.

[0095] Access management network element: mainly used for mobility management and access management, etc. For example, it can be the mobility management entity (MME) function in the 4G communication network or the access and management function (AMF) network element in the 5G network. In future communications such as 6G communications, the access management network element can still be an AMF network element, or have other names, which is not limited in this application. Namf is a service-based interface provided by AMF. AMF can communicate with other network functions through Namf.

[0096] User plane function network element: used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, etc. In 5G communication, the user plane network element may be a user plane function (UPF) network element. In future communications such as 6G communication, the user plane network element may still be a UPF network element, or have other names, which is not limited in this application.

[0097] Access network equipment: used to provide network access functions for authorized user devices in a specific area, and can use transmission tunnels of different qualities according to the level of user equipment, business requirements, etc.

[0098] Exemplarily, the access network device may be a wired access device or a wireless access device. The radio access network (RAN) device can manage wireless resources, provide access services for terminal devices, and then complete the forwarding of control signals and user equipment data between the terminal and the core network. For example, the radio access network device may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc.; it may also be a module or unit that completes part of the functions of a base station, for example, a centralized unit (CU) or a distributed unit (DU). The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device.

[0099] The terminal device may also be referred to as a terminal, user equipment (UE), a mobile station, a mobile terminal, etc. The terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality terminal device, an augmented reality terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in remote 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. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device.

[0100] The terminal device can be divided according to one or more layers as follows, for example, it can be specifically divided into a 5GS session management (5GS session management, 5GSM) layer and a 5GS mobility management (5GS mobility management, 5GMM) layer, a service quality flow control (QoS flow control, QFC) layer, a radio resource control (radio resource control, RRC) layer and a service data adaptation protocol (Service Data Adaptation Protocol SDAP) layer. Among them, the 5GSM layer is responsible for the session management of the terminal device. The 5GMM layer is responsible for the registration, deregistration, and mobility management of the UE. The QFC layer is responsible for notifying the 5GMM layer when uplink data needs to be sent and the radio resources have been released or suspended. The RRC layer is responsible for the management of radio resources. The RRC layer can also interact with the RAN to complete the establishment, modification, and release of the data radio bearer (DRB) of the protocol data unit (PDU) session. The SADP layer is responsible for completing the mapping of the quality of service (quality of service, QoS) flow and the DRB, the transmission of user plane data, etc.

[0101] When a terminal device wants to communicate with the 5G core network, it needs to establish a connection with the access and management function (AMF) because it is turned on for the first time or has been idle for a period of time, and the network has deleted resources to temporarily transmit data. This is called 5G connection management (5GCM). 5G connection management is used to establish and release control plane signaling connections between UE and AMF. Attributes include: connection management describes the UE status regarding its signaling with the AMF 5G core node, and 5G connection management is used to transmit NAS signaling messages, including two connections: 1) signaling connection between UE and AN; 2) N2 connection between AN and AMF. In an embodiment of the present application, 5G connection management may be responsible for initiating service link establishment and managing service connections for service requests.

[0102] The present application provides a communication method. In order to better understand the embodiment of the present application, the application scenarios and existing problems of the embodiment of the present application are first introduced below. It should be noted that the application scenario is to make the embodiment of the present application easier to understand and should not be regarded as a limitation on the scope of protection required by the present application.

[0103] In the communication network, registration and services are sent serially on the terminal device side, that is, when the terminal device is executing the registration process, the service process will be cached, and the current protocol also clearly stipulates that the terminal device cannot initiate a new service request while executing the registration process or the service process.

[0104] In some scenarios, when the terminal device is executing the registration process or service process, the terminal device initiates an emergency service (such as an emergency call). The emergency service will be cached and the terminal device can initiate the emergency service request only after the registration or service process is completed. If the UE is executing the registration process or the service process and receives an emergency service (such as an emergency call), according to the protocol, the emergency service will be cached first and the emergency service request can only be initiated after the registration process or service process is completed. Due to the flow control processing on the core network side or the excessive load, the core network can choose not to reply to any message on the UE side, or the core network directly discards the registration request and service request sent by the UE. The UE can only continue to process the emergency service in the cache after the timer of this registration process or service process expires. The actual time of the emergency service is usually short (less than 15s), which will cause the emergency call to fail due to the emergency attempt timeout of the upper layer IMSA before the emergency call is tried to be put into the cache.

[0105] For example, Figure 2 The process shown includes: step 1: the terminal equipment (UE) side initiates a normal registration request to the network side through 5GCM; step 2: 5GMM indicates to 5GCM that the service module is suspended (the service module cannot be used at this time); step 3: UE indicates to 5GCM that there is an emergency call (equivalent to an emergency service initiation) and an emergency PDU needs to be established, but the service module cannot be used; step 4: the call attempt on the local 5G is terminated due to the timeout of the call timer, that is, the emergency PDU activation process is terminated; if the core network side perceives that step 1 is a normal registration process, the registration request type sent by the UE to the network is: periodic registration, and the link establishment reason value is: MO-SIG; at the same time, the UE starts a timer T3510 (15s) to wait for the network to reply; if flow control or excessive load occurs on the core network side, the core network will choose not to reply to the UE side message or discard the registration request, then the emergency call on the UE side will be placed in the cache queue and cannot be processed; only when the T3510 timer on the UE side times out, the 5GMM on the UE side instructs the 5GCM to restore the service module, and then the emergency call in the cache can continue to be processed. However, emergency calls usually have their own timers. If no response is received for a long time, the call will time out, and then other access methods will be changed, such as trying to make an emergency call on LTE; or the emergency call may not have been added to the cache yet, and the call will fail and hang up due to the attempt timeout.

[0106] In view of the above problems, a communication method is provided in an embodiment of the present application, which can effectively solve the problem of network communication and effectively avoid the failure of emergency services to connect to the network due to timeout.

[0107] The technical solution of the present application is introduced below in conjunction with specific embodiments.

[0108] The present invention provides a communication method which is applicable to but not limited to Figure 1A-1B The communication system shown in the figure, and the method can be executed by a terminal device (which can also be a network device); or the method can be executed by a component (module, chip, etc.) corresponding to the terminal device (which can also be a network device); or the method can be executed by a device corresponding to the terminal device (which can also be a network device). The embodiments of the present application do not specifically limit the specific forms and corresponding quantities of the terminal device and the network device.

[0109] See also Figure 3A As shown, the specific process of this method is as follows:

[0110] S301A: When the terminal device is executing the first process, the user initiates an emergency service.

[0111] In the embodiment of the present application, the first process does not include the process of the emergency service, for example, the first process is a common registration process or a common service process.

[0112] Exemplarily, when the terminal device is performing a normal business process with the network device side (which may be referred to as the network side for short), the user makes an emergency call.

[0113] In the embodiment of the present application, the network device may include an access network device and / or a core network device. The terminal device may communicate with the core network device through the access network device, for example, the terminal device sends information of the terminal device to the core network through the base station. Therefore, in the embodiment of the present application, the devices on the network side including the access network device and / or the core network device are collectively referred to as network devices.

[0114] The embodiment of the present application takes the terminal device as the transmitting end and the network device as the receiving end as an example to describe the scheme of the present application. In actual applications, the transmitting end may not be limited to the terminal device, for example, it may also be executed by a chip or a component, and the receiving end may not be limited to the network device, for example, it may also be executed by a chip or a component. And the communication between the terminal device and the network device may be a direct form of communication (i.e., the terminal device to the network device) or an indirect form of communication (for example, the terminal device and the network device can communicate through one or more third-party communication devices or network element forwarding). In addition, the embodiment of the present application does not limit the specific technology used for the communication between the terminal device and the network device.

[0115] S302A: When network congestion occurs, the terminal device releases the communication link resources of the first process.

[0116] In a possible implementation, if there is no network congestion, the terminal device waits for the first process to end. In this implementation, if there is no network congestion, the terminal device will promptly receive a response message from the network device to confirm the end of the first process, so the terminal device can wait for the first process currently being executed to end before sending the first request information of the emergency service to the network device.

[0117] In an embodiment of the present application, the terminal device can determine (or detect) whether the current network is congested when initiating the first process, or determine (or detect) whether the current network is congested after initiating the first process, or determine (or detect) whether the current network is congested within a certain time when the user initiates an emergency service.

[0118] Exemplarily, after the UE sends a normal registration request message to the network device side (equivalent to the UE executing the first process), a timer with a set time (for example, 2s) can be started immediately (the type of timer is not limited, such as a retransmission timer); within the set time of the timer, if the UE receives information from the network device, then the UE determines that the current network is not congested; if the timer has timed out and the UE has not received any information from the network device, then the UE determines that the current network is congested.

[0119] After determining whether the current network is congested or not, the UE sets indication information or marking information for indicating whether the current network is congested. The UE and the network device are executing a normal registration process. When an emergency service is initiated, the UE can quickly determine whether the current network is congested based on the indication information or marking information; if the current network is congested, the UE can directly release (or disconnect) the current communication link (i.e., the communication link currently used by the normal registration process); if the current network is not congested, since the UE will promptly receive the response information fed back from the network device side, the UE does not need to release (or disconnect) the current communication link (i.e., the communication link currently used by the normal registration process), but waits for the normal registration process to end before initiating a request information to the network device side for the emergency service.

[0120] S303A: The terminal device sends a first request message to the network device, where the first request message is used to request processing of a target process, where the target process is triggered by the emergency service.

[0121] Correspondingly, the network device receives the first request information; and processes the target process based on the first request information.

[0122] In the embodiment of the present application, the target process triggered by the terminal device based on the emergency service may include the following situations:

[0123] Case 1: The target process is an emergency registration process or a non-emergency registration process.

[0124] If the emergency service triggers an emergency registration process, then the first request information sent by the terminal device to the network device is the emergency registration request information; accordingly, in the following step S304A, the first response information received by the terminal device from the network device is the emergency registration response information.

[0125] If the emergency service triggers a non-emergency registration process, then the first request information sent by the terminal device to the network device is the non-emergency registration request information; accordingly, in the following step S304A, the first response information received by the terminal device from the network device is the non-emergency registration response information.

[0126] Regardless of whether the target process triggered by the emergency service is an emergency registration process or a non-emergency registration process, the terminal device also sends a first indication message to the network device, and the first indication message is used to indicate that the established communication link will not be released after the emergency registration or the non-emergency registration process. In addition, the first request information can be carried in a first message, and the first message also carries first link establishment reason information, and the first link establishment reason information is used to indicate that the emergency service is requesting to establish a communication link.

[0127] Exemplarily, if the first indication information is a follow on mark, then the follow on mark is used to indicate that information is further transmitted after the emergency registration or the non-emergency registration process, which is equivalent to instructing the network device side to keep the communication link from being released after establishing the communication link for the emergency registration or the non-emergency registration, so that the communication link can be used to transmit subsequent information and / or data sent by the terminal device and / or the network device.

[0128] If the first indication information is not a follow on mark, the first indication information may be carried in the first request information, or may not be carried in the first request information, but may be sent by the terminal device to the network device in other ways. For example, the first indication information may be independently located in the same message as the first request information and sent to the network device, or the first indication information may be sent to the network device separately, and this application does not make specific limitations on this.

[0129] Through this implementation, when the terminal device initiates an emergency registration or a non-emergency registration to the network device, the first request information is equivalent to the emergency registration request information or the non-emergency registration request information. Then, after receiving the first request information, the network device will establish a communication link for the emergency registration or the non-emergency registration. In addition, the terminal device also sends the first indication information to the network device. Therefore, after the network device establishes the communication link for the emergency registration or the non-emergency registration, it can keep the established communication link from being released based on the first indication information, so as to effectively use it for the subsequent transmission of information and / or data between the terminal device and the network device.

[0130] In some embodiments, the terminal device sends a first request information (i.e., emergency registration request information or non-emergency registration request information) to a network device. The specific process may include: the terminal device first sends the first message to the access network device, and the first message includes the first request information (i.e., emergency registration request information or non-emergency registration request information) and the first link establishment reason information; after the access network device receives the first message, it can parse the first message and obtain the first request information (i.e., emergency registration request information or non-emergency registration request information) and the first link establishment reason information therein. The access network device can know based on the first link establishment reason information that the request to establish a communication link is for the emergency service; further, the access network device sends the first request information (i.e., emergency registration request information or non-emergency registration request information) to the core network device in a high priority manner, so that the core network device can process the emergency registration or non-emergency registration in a timely manner based on the first request information.

[0131] Case 2: The target process is a business process.

[0132] If the emergency service triggers a business process, then the first request information sent by the terminal device to the network device is a business request information, and the first request information includes business type information, and the business type information is used to indicate that the currently executed business type is the emergency service; accordingly, in the following step S304A, the first response information received by the terminal device from the network device is a business response information.

[0133] In addition, the first request information is carried in the second message, and the second message also carries second link establishment reason information, where the second link establishment reason information is used to indicate that the request to establish the communication link is for the emergency service.

[0134] In some embodiments, the terminal device sends a first request information (i.e., service request information) to a network device. The specific process may include: the terminal device first sends the second message to the access network device, and the second message includes the first request information (i.e., service request information, including service type information for indicating emergency services) and the second link establishment reason information; after receiving the second message, the access network device can parse the second message and obtain the first request information (i.e., the service request information) and the second link establishment reason information therein. The access network device can know, based on the second link establishment reason information, that the request to establish a communication link is for the emergency service; further, the access network device sends the first request information (i.e., service request information) to the core network device in a high priority manner, so that the core network device can process the emergency service in a timely manner.

[0135] Therefore, in an embodiment of the present application, the target process initiated (triggered) by the terminal device to the network device side for the emergency service may be a registration process or a service process. Specifically, the terminal device can determine it based on the current status information of the emergency service.

[0136] S304A: The network device sends the first response information of the target process to the terminal device. Correspondingly, the terminal device receives the first response information of the target process from the network device.

[0137] In summary, an embodiment of the present application proposes a communication method, which includes: when a terminal device is executing a first process, a user initiates an emergency service; when network congestion occurs, the terminal device releases the communication link resources of the first process; and then sends a first request message to the network device, the first request message is used to request processing of a target process, the target process is triggered by the emergency service; the terminal device receives a first response message of the target process from the network device. In this method, an emergency service is initiated on the terminal device side. If network congestion currently occurs, the terminal device releases the communication link resources of the currently executing process, and then initiates a new process request message to the network side based on the emergency service, so that the network side can promptly and effectively provide communication link resources for the process initiated by the emergency service, thereby avoiding the emergency service from failing to connect to the network due to timeout and not being processed.

[0138] The present application also provides another communication method, which can be applied to but not limited to the above Figure 1A-1BThe communication system shown in the figure, and the method can be executed by a terminal device (or a network device); or the method can be executed by a component (module, chip, etc.) corresponding to the terminal device (or a network device); or the method can be executed by a device corresponding to the terminal device (or a network device). The embodiments of the present application do not specifically limit the specific forms and corresponding quantities of the terminal device and the network device. Please refer to Figure 3B As shown, the specific process of this method is as follows:

[0139] S301B: When the terminal device is executing the first process, the user initiates an emergency service.

[0140] In the embodiment of the present application, the first process does not include the process of the emergency service. For example, the first process is a common registration process or a common service process.

[0141] Exemplarily, when the terminal device is performing a normal business process with the network device side (which may be referred to as the network side for short), the user initiates an emergency call.

[0142] In the embodiment of the present application, the network device may include an access network device and / or a core network device. The terminal device may communicate with the core network device through the access network device, for example, the terminal device sends information of the terminal device to the core network through the base station. Therefore, in the embodiment of the present application, the devices on the network side including the access network device and / or the core network device are collectively referred to as network devices.

[0143] The embodiment of the present application takes the terminal device as the transmitting end and the network device as the receiving end as an example to describe the scheme of the present application. In actual applications, the transmitting end may not be limited to the terminal device, for example, it may also be executed by a chip or a component, and the receiving end may not be limited to the network device, for example, it may also be executed by a chip or a component. And the communication between the terminal device and the network device may be a direct form of communication (i.e., the terminal device to the network device) or an indirect form of communication (for example, the terminal device and the network device can communicate through one or more third-party communication devices or network element forwarding). In addition, the embodiment of the present application does not limit the specific technology used for the communication between the terminal device and the network device.

[0144] S302B: If no response information of the first process is received within a preset first time period, the terminal device sends a first request information to the network device, and the first request information is used to request processing of a target process, which is triggered by the emergency service and uses the same communication link resources as the first process.

[0145] Correspondingly, the network device receives the first request information; and processes the target process based on the first request information.

[0146] Exemplarily, when the terminal device is executing the first process (such as a normal registration process or a normal business process) and an emergency service is initiated, the terminal device can preset a time (which can be a specific time later) or a duration (the start time of the duration is the time when the emergency service is initiated); when the preset time is reached, or the time the terminal device waits for feedback from the network device side reaches the preset time, if the terminal device has not received any downlink message (or downlink information) sent from the network device side, then the terminal device can, based on the emergency service, reuse the communication link currently used by the first process (in a connected state) to directly initiate a request for the target process to the network device side; or the terminal device does not consider whether it has received a downlink message (or downlink information) sent from the network device, as long as the preset time is reached or the waiting time reaches the preset time, it can use the communication link of the current first process (in a connected state) to initiate a request for the target process to the network device side.

[0147] In the embodiment of the present application, the target process triggered by the terminal device based on the emergency service may include the following situations:

[0148] Case 1: The target process is an emergency registration process or a non-emergency registration process.

[0149] If the emergency service triggers an emergency registration process, then the first request information sent by the terminal device to the network device is the emergency registration request information; accordingly, in the following step S303B, the first response information sent by the network device to the terminal device is the emergency registration response information.

[0150] If the emergency service triggers a non-emergency registration process, then the first request information sent by the terminal device to the network device is the non-emergency registration request information, and the first request information includes the identification information (or marking information) of the emergency service. The identification information (or marking information) of the emergency service is used to indicate that the current non-emergency registration process is triggered by the emergency service; accordingly, in the following step S303B, the first response information sent by the network device to the terminal device is the non-emergency registration response information.

[0151] In addition, the first request information is carried in the first message, and the first message also carries first link reason information, where the first link reason information is used to indicate that the non-emergency registration process is triggered by the emergency service.

[0152] In some embodiments, the terminal device sends a first request information (i.e., non-emergency registration request information, including marking information of the emergency service) to the network device. The specific process may include: the terminal device first sends the first message to the access network device (e.g., a base station), and the first message includes the first request information (i.e., the non-emergency registration request information, including marking information of the emergency service) and the first link reason information; after receiving the first message, the access network device can parse the first message and obtain the first request information (i.e., the non-emergency registration request information, including marking information of the emergency service) and the first link reason information therein, and the access network device can know based on the first link reason information that the non-emergency registration process is triggered by the emergency service; further, the access network device sends the first request information (i.e., the non-emergency registration request information, including marking information of the emergency service) to the core network device in a high priority manner, and finally, the core network device processes the non-emergency registration in a high priority manner based on the marking information of the emergency service contained in the first request information.

[0153] Case 2: The target process is a business process.

[0154] If the emergency service triggers a business process, then the first request information sent by the terminal device to the network device is a business request information, and the first request information includes business type information, and the business type information is used to indicate that the currently executed business type is the emergency service; accordingly, in the following step S303B, the first response information received by the terminal device from the network device is a business response information.

[0155] In addition, the first request information is carried in the second message, and the second message also carries second link reason information, where the second link reason information is used to indicate that the current service process is triggered by the emergency service.

[0156] In some embodiments, the terminal device sends a first request information (i.e., service request information) to the network device. The specific process may include: the terminal device first sends the second message to the access network device, and the second message includes the first request information (i.e., the service request information) and the second link reason information; after the access network device receives the second message, it can parse the second message and obtain the first request information (i.e., the service request information) and the second link reason information therein, and the access network device can know that the service process is triggered by the emergency service based on the second link reason information; further, the access network device sends the first request information (i.e., the service request information) to the core network device in a high priority manner, so that the core network device can process the emergency service in a timely manner.

[0157] S303B: The network device sends the first response information of the target process to the terminal device. Correspondingly, the terminal device receives the first response information of the target process from the network device.

[0158] In summary, the embodiment of the present application proposes another communication method, which includes: when the terminal device is executing the first process, the user initiates an emergency service; the terminal device does not receive the response information of the first process within a preset first time period, and sends a first request information to the network device, the first request information is used to request the processing of the target process, the target process is triggered by the emergency service, and the target process and the first process use the same communication link resources; the terminal device receives the first response information of the target process from the network device. In this method, when the terminal device side is executing the first process and an emergency service is initiated, if the terminal device does not receive the response information of the first process within the preset time period, it can initiate a request information of the target process to the network device side based on the emergency service in the connected state, so that the network side can promptly and effectively process the target process initiated by the emergency service, thereby avoiding the emergency service from failing to connect to the network due to timeout.

[0159] Based on the above Figure 3A-3B The communication method shown is further described in detail below through several specific embodiments.

[0160] Embodiment 1:

[0161] The first embodiment is based on the terminal device currently executing a normal registration or normal business process (in the above Figure 3A In the scenario where an emergency service occurs (collectively referred to as the first process in the above scheme), the above Figure 3A The present application scheme is described in detail. That is, in this embodiment 1, taking the 5G communication system as an example, when the terminal device (UE1) is currently executing a normal registration or normal service process, a user on the terminal device side makes an emergency call. The UE actively identifies (detects) whether the current network is congested, and effectively solves the process of initiating the emergency call. Figure 4 As shown, the process of this embodiment 1 is as follows:

[0162] S401: UE1 sends common registration / service request information to the network device.

[0163] For example, UE1 currently initiates a normal registration or normal service process (equivalent to the above Figure 3AThe first process in the described scheme), then the 5G mobility management (5GMM) module of UE1 sends a normal registration request message or a normal service request message (hereinafter referred to as the normal registration / service request message) to the core network device, and also sends a link establishment reason value of MO-SIG.

[0164] In the embodiment of the present application, the 5GMM module of the UE sends ordinary registration / service request information to the core network device, which is not limited to direct transmission, and may also be indirectly forwarded to the core network device through other devices (such as access network devices) or network elements. Exemplarily, UE1 first sends ordinary registration / service request information to the base station, and then the base station forwards the ordinary registration / service request information to the core network.

[0165] In this embodiment 1, it mainly involves UE1 sending registration / service request information to the network side, and receiving registration / service response information from the network side; as to the specific path through which the network side transmits the registration / service request information to the core network, and the specific path through which the registration / service response information sent by the core network is transmitted to UE1, this embodiment 1 does not make a detailed description and limitation, and thus the access network equipment and the core network equipment are collectively referred to as network equipment (or network equipment side).

[0166] After UE1 sends a normal registration / service request message to the network device, the service module on the UE1 side cannot continue to provide services to other registration / service processes of the UE. If a user on the UE side makes an emergency call (i.e., emergency service) at this time, the emergency call usually needs to be cached first, and the registration / service process of the emergency call can be initiated to the network device side only after the normal registration / service process is completed.

[0167] S402: UE1 determines whether the current network is congested.

[0168] Exemplarily, after the above-mentioned ordinary registration / service process is initiated, the UE enters the connected state. At this time, the UE side can set and start a 1s to 2s timer, which is used to detect whether the current network is congested.

[0169] If UE1 receives downlink NAS signaling from the network device within the time range of the timer, such as identity request, authentication request, security mode command, downlink transmission (DL Trans), configuration update command, etc., it means that the current network is not congested, so stop the timer and execute the following steps S403 to S406.

[0170] If UE1 does not receive any downlink NAS signaling from the network device within the time range of the timer, or the timer has timed out, it means that the current network is congested, and then the following steps S407 to S409 are executed.

[0171] S403: An emergency service occurs on the UE1 side, waiting for the normal registration / service process to be completed.

[0172] That is, when the current network is not congested, an emergency service (such as a user making an emergency call) occurs on the UE1 side, and the registration / service process of the emergency service can be initiated only after the above-mentioned ordinary registration / service process is completed.

[0173] S404: UE1 receives common registration / service response information from the network device.

[0174] The common registration / service response information is used to notify or indicate that the common registration / service process initiated by the UE1 side has been completed.

[0175] S405: UE1 sends registration / service request information of the emergency service to the network device.

[0176] Correspondingly, the network device receives the registration / service request information of the emergency service from UE1.

[0177] Exemplarily, UE1 sends registration / service request information of the emergency service to the core network device (ie, network device).

[0178] In an embodiment of the present application, UE1 can determine whether to initiate the registration process of the emergency service (corresponding UE1 should send registration request information) to the network device based on the status information of the emergency service, or to initiate the service process of the emergency service (corresponding UE1 should send service request information).

[0179] S406: UE1 receives registration / service response information of the emergency service from the network device.

[0180] The registration / service response information of the emergency service is used to indicate that the network device accepts to process the registration / service of the emergency service, or is used to indicate that the registration / service process of the emergency service is completed; or if UE1 receives the registration response information of the emergency service, then the registration response information is used to indicate that the registration process of the emergency service is completed; if UE1 receives the service response information of the emergency service, then the service response information is used to indicate that the network device accepts to process the service process of the emergency service; the embodiments of the present application do not make specific limitations on this.

[0181] S407: An emergency service occurs on the UE1 side, and the link of the current normal registration / service process is released.

[0182] That is, when the current network is already congested and an emergency service occurs on the UE1 side (for example, a user makes an emergency call), the UE1 can release (disconnect) the link of the current ordinary registration / service process.

[0183] S408: UE1 sends registration / service request information of the emergency service to the network device.

[0184] In some embodiments, UE1 determines to initiate a registration process for an emergency service to a network device, and UE1 sends a registration request message and a link establishment reason value for the emergency service to the network device, wherein the registration request message for the emergency service includes a signaling (follow on), and the signaling (follow on) is used to indicate that other signaling (i.e., used to establish a session link) is transmitted after the registration, and the link establishment reason value is an emergency reason value.

[0185] The UE1 side can send the registration information and link establishment reason value of the above emergency service to the network device (such as a base station) separately, or carry them in the same NAS message and send them to the network device (such as a base station), which is not limited in this application.

[0186] In other embodiments, UE1 determines a service process for initiating an emergency service to a network device, and then UE1 sends service request information and a link establishment reason value of the emergency service to the network device, wherein the service request information of the emergency service includes service type information, and the service type information is used to indicate that the service is an emergency service, and the link establishment reason value is an emergency reason value.

[0187] The UE1 side may send the emergency service request information and the link establishment reason value to the network device (eg, base station) separately, or may carry them in the same NAS message and send them to the network device (eg, base station), which is not limited in this application.

[0188] Exemplarily, Table 1 shows a mapping table of access identifier / access type and RRC establishment cause when accessing a 5GCN NAS signaling connection.

[0189] Table 1

[0190]

[0191] S409: The network device sends registration / service response information of the emergency service to UE1.

[0192] If in the above step S408, UE1 sends a registration request message for the emergency service to the network device; correspondingly, in the step S409, the network device will return the registration response message of the emergency service to UE1 to notify (or instruct) UE1 that the network side accepts the registration of the emergency service, or notify (or instruct) UE1 that the registration of the emergency service is completed.

[0193] If in the above step S408, UE1 sends service request information of the emergency service to the network device; correspondingly, in the step S409, the network device will return service response information of the emergency service to UE1 to notify (or instruct) UE1 that the network side accepts and processes the emergency service.

[0194] How to complete the registration process or service process of the emergency service between UE1 and the network device subsequently can be performed with reference to the existing technology and will not be described in detail here.

[0195] In this embodiment 1, if an emergency service occurs when the UE is executing a normal registration / service process, the UE can actively detect whether the current network is congested by, but not limited to, setting a timer; if the UE determines that there is no network congestion at present, then there is no need to release the communication link of the current normal registration / service process, and it can still be executed in the existing manner, that is, wait for the normal registration / service process to be completed, and then initiate the registration / service process of the emergency service; if the UE determines that there is network congestion at present, then the UE can actively release the communication link of the current normal registration / service process, and then initiate the registration / service process of the emergency service to the network side. Request information, and send a link establishment reason value (the link establishment reason value is set to emergency), so that the network side can effectively establish a corresponding session link for the registration / service process of the emergency service, and then effectively solve the problem of failure to initiate the emergency service due to timeout.

[0196] Embodiment 2:

[0197] The second embodiment is based on the fact that the terminal device is currently executing a normal registration or normal business process (in the above Figure 3B In the scenario where an emergency service occurs (collectively referred to as the first process in the above scheme), the above Figure 3B That is, in the second embodiment, taking the 5G communication system as an example, when the terminal device (UE1) is currently executing a normal registration or normal business process, a user on the terminal device side makes an emergency call. The UE can reuse the communication link of the current normal registration or normal business process to effectively solve the process of initiating an emergency call. Figure 5 As shown, the process of the second embodiment is as follows:

[0198] S501: UE1 sends a common registration / service request message 1 to a network device.

[0199] For example, UE1 currently initiates a normal registration or normal service process (equivalent to the above Figure 3B The first process in the described scheme), then the 5G mobility management (5GMM) module of UE1 sends a normal registration request message or a normal service request message 1 (hereinafter referred to as the normal registration / service request message) to the network device (base station, core network), and also sends a link establishment reason value of MO-SIG.

[0200] In an embodiment of the present application, the UE's 5GMM module sends a normal registration / service request message 1 to the base station, and the base station sends a normal registration / service request message 1 to the core network. This is not limited to direct transmission, but may also be indirectly forwarded through one or more communication devices or network elements.

[0201] After UE1 sends a common registration / service request message 1 to the network device, UE1 usually waits for a response message from the network.

[0202] S502: An emergency service occurs on the UE1 side, and it is determined to reuse the current ordinary registration / service communication link to initiate the registration / service process of the emergency service.

[0203] In one possible implementation, an emergency service occurs on the UE1 side. If UE1 does not receive any downlink information (or response information of the ordinary registration / service) fed back from the network device side within a preset time period, then the UE1 can directly use the current communication link of the ordinary registration / service to initiate the registration / service request information of the emergency service to the network device side.

[0204] Alternatively, as long as the waiting time meets the preset time, UE1 can use the currently executed ordinary registration / service communication link to initiate the registration / service request information of the emergency service to the network device side regardless of whether any downlink information fed back from the network device side is received.

[0205] In another possible implementation, an emergency service occurs on the UE1 side, and UE1 does not receive any downlink information (or response information of the ordinary registration / service) fed back from the network device at a preset time. Then, UE1 can use the current communication link of the ordinary registration / service to initiate the registration / service request information of the emergency service to the network device side.

[0206] Alternatively, as long as UE1 waits until a preset time, regardless of whether it receives any downlink information fed back from the network device side, it can use the current ordinary registration / service communication link to initiate the registration / service request information of the emergency service to the network device side.

[0207] While UE1 is waiting for a network response, UE1 cannot continue to initiate other registration / service processes; if an emergency service occurs on the UE1 side at this time, UE1 needs to re-initiate the registration / service process for the emergency service; specifically, UE1 determines that an emergency service has occurred and does not release the current ordinary registration / service communication link, but generates new ordinary registration / service request information based on the emergency service, that is, UE1 can re-fill in the content of the ordinary registration / service request information based on the emergency service to obtain registration / service request information 2.

[0208] S503: UE1 sends registration / service request information 2 and a multiplexing link cause value to the base station.

[0209] Correspondingly, the base station receives the registration / service request information 2 and the multiplexing link cause value.

[0210] In an embodiment of the present application, if UE1 sends a registration request message 2 to the base station, the registration request message 2 may include, in addition to some existing information (such as follow on), newly added registration mark information (i.e., indication information), and the registration mark information is used to indicate that this registration process is initiated (triggered) by an emergency service. Usually, when the UE is in a connected state, it will no longer send a multiplexing link cause value (i.e., RRC Cause) to the base station. However, in order to prevent the flow control and load influence of the base station, in an embodiment of the present application, UE1 needs to send an RRC cause (RRC Cause) to the base station, and the RRC Cause is set to an emergency type; accordingly, after the base station receives the RRC Cause and determines the emergency type, it will send the registration / service request message 2 to the core network with a high priority.

[0211] If UE1 sends a service request message 2 to the base station, the service request message 2 includes a service type, and the service type indicates that the service process initiated at this time is an emergency service type. As mentioned above, usually when the UE is in a connected state, it will no longer send a multiplexing link cause value (ie, RRC Cause) to the base station. However, in order to prevent the flow control and load influence of the base station, in the embodiment of the present application, UE1 needs to send RRCCause to the base station, and the RRC Cause is set to the emergency type; accordingly, after the base station receives the RRC Cause and determines the emergency type, it will send the service request message 2 to the core network with a high priority.

[0212] S504: The base station sends registration / service request information 2 to the core network.

[0213] Correspondingly, the core network receives the registration / service request information 2.

[0214] Exemplarily, if the base station sends registration request information 2 to the core network, the registration request information 2 includes newly added registration mark information (ie, indication information), and the registration mark information is used to indicate that this registration process is initiated (triggered) by an emergency service.

[0215] If the base station sends a service request message 2 to the core network, the service request message 2 includes a service type or newly added service tag information (i.e., indication information); the service type is used to indicate that the service process initiated this time is an emergency service type, and the service tag information is used to indicate that the service process is initiated (triggered) by an emergency service.

[0216] S505: The core network determines, based on the registration / service request information 2, that the registration or service process is triggered by an emergency service, and processes the registration / service process with a high priority.

[0217] S506: The core network sends registration / service response information to the base station.

[0218] S507: The base station sends registration / service response information to UE1.

[0219] Subsequently, UE1 initiates PDU activation of the emergency service to the network side, so that the network allocates resources for the emergency service to establish a link to implement the emergency service. The specific execution process can refer to the existing technology and will not be described in detail here.

[0220] In the second embodiment, if an emergency service occurs when the UE is executing a normal registration / service process, the UE does not release the communication link of the current normal registration / service process, but reuses the communication link of the current normal registration / service process, that is, in the connected state, the UE re-initiates the normal registration / service process to the network side. However, the second normal registration / service process initiated by the UE is triggered by the emergency service. The registration / service request information sent by the UE to the network side needs to carry a registration / service mark to indicate that the registration / service is initiated (triggered) by the emergency service. Then, after receiving the registration / service request information, the network side can identify that the second registration / service process is triggered by the emergency service, and then can process the second registration / service process with high priority, thereby effectively solving the problem of failure to initiate the emergency service due to timeout.

[0221] Regarding the above-mentioned Embodiment 1 and Embodiment 2, it should be noted that:

[0222] (1) The above-mentioned Embodiment 1 and Embodiment 2 can be implemented separately or in combination, and there is no specific limitation. For example, when an emergency service occurs on the UE1 side in Embodiment 2, UE1 reuses the communication link of the currently executed normal registration process or normal service process to request the network side to process the emergency service. This solution can be implemented separately or based on the situation in Embodiment 1 where UE1 determines that the current network is not congested. This embodiment of the present application does not limit this.

[0223] (2) The above description focuses on the differences between the first embodiment and the second embodiment. Except for the differences, the first embodiment and the second embodiment can refer to each other.

[0224] (3) The step numbers of the flowcharts described in Example 1 and Example 2 are only examples of the execution process and do not constitute a limitation on the order of execution of the steps. There is no strict execution order between the steps that have no temporal dependency relationship with each other in the embodiments of the present application. In addition, not all the steps shown in the flowcharts are steps that must be executed, and some steps can be added or deleted based on the actual needs of each flowchart.

[0225] In the embodiments provided by the present application, the methods provided by the embodiments of the present application are introduced from the perspective of interaction between various devices. In order to implement the functions in the methods provided by the embodiments of the present application, the terminal device or the network device may include a hardware structure and / or a software module to implement the functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether a function in the functions is performed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

[0226] The division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0227] Same as above idea, Figure 6 As shown, the embodiment of the present application also provides a communication device 600 for implementing the functions of the terminal device or network device in the above method. For example, the communication device 600 can be a software module or a chip system. In the embodiment of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices. The communication device 600 may include: a communication unit 601 and a processing unit 602.

[0228] In the embodiment of the present application, the communication unit 601 may also be referred to as a transceiver unit, and may include a sending unit and / or a receiving unit, which are respectively used to perform the steps of sending and receiving by the terminal device or the network device in the above method embodiment. The processing unit 602 may be used to read instructions and / or data in the storage module so that the communication device 600 implements the above method embodiment.

[0229] Optionally, the communication device 600 may further include a storage unit 603, which is equivalent to a storage module and can be used to store instructions and / or data.

[0230] The following, combined Figures 3A to 5 The communication device provided in the embodiment of the present application is described in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, so the contents not described in detail can be referred to the above Figure 3A-Figure 5 For the sake of brevity, the method embodiment will not be described in detail here.

[0231] The communication unit 601 may also be referred to as a transceiver, a transceiver, a transceiver device, etc. The processing unit may also be referred to as a processor, a processing board, a processing module, a processing device, etc. Optionally, the device used to implement the receiving function in the communication unit 601 may be regarded as a receiving unit, and the device used to implement the sending function in the communication unit 601 may be regarded as a sending unit, that is, the communication unit 601 includes a receiving unit and a sending unit. The communication unit may also be sometimes referred to as a transceiver, a transceiver, or a transceiver circuit, etc. The receiving unit may also be sometimes referred to as a receiver, a receiver, or a receiving circuit, etc. The sending unit may also be sometimes referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0232] When the communication device 600 executes the above embodiment Figure 3A In the terminal device in the process shown: the processing unit 602 is used to determine that the user initiates an emergency service when executing the first process; the processing unit 602 is also used to release the communication link resources of the first process if the current network is congested; the communication unit 601 is used to send a first request message to the network device, and the first request message is used to request processing of a target process, and the target process is triggered by the emergency service; the communication unit 601 is also used to receive a first response message of the target process from the network device.

[0233] When the communication device 600 executes the above embodiment Figure 3AIn the network device in the process shown: the communication unit 601 is used to receive a first request information from a terminal device, wherein the first request information is used to request processing of a target process, and the target process is triggered by an emergency service of the terminal device; the processing unit 602 is used to process the target process based on the first request information; the communication unit 601 is also used to send a first response information of the target process to the terminal device.

[0234] When the communication device 600 executes the above embodiment Figure 3B In the terminal device in the process shown: the processing unit 602 is used to determine that the user initiates an emergency service when executing the first process; the communication unit 601 is used to send a first request information to the network device when a preset time is reached, and the first request information is used to request processing of a target process, and the target process is triggered by the emergency service and the target process uses the same communication link resources as the first process; the communication unit 601 is also used to receive a first response information of the target process from the network device.

[0235] When the communication device 600 executes the above embodiment Figure 3B When the network device is in the process shown: the communication unit 601 is used to receive a first request information from a terminal device, the first request information is used to request processing of a target process, the target process is triggered by an emergency service of the terminal device and the target process uses the same communication link resources as the currently executed first process; the processing unit 602 is used to process the target process based on the first request information; the communication unit 601 is also used to send a first response information of the target process to the terminal device.

[0236] The above is just an example. The communication unit 601 and the processing unit 602 can also perform other functions. For more detailed description, please refer to Figure 3A-3B The relevant descriptions in the method embodiments are not repeated here.

[0237] like Figure 7 The figure shows a communication device 700 provided in an embodiment of the present application. Figure 7 The communication device shown can be Figure 6 The communication device 700 can be applied to the flowchart shown above to perform the functions of the terminal device or network device in the above method embodiment. For ease of description, Figure 7 Only the main components of the communication device are shown.

[0238] like Figure 7As shown, the communication device 700 includes a communication interface 701 and a processor 702. The communication interface 701 and the processor 702 are coupled to each other. It can be understood that the communication interface 701 can be a transceiver or an input-output interface, or an interface circuit such as a transceiver circuit. Optionally, the communication device 700 can also include a memory 703 for storing instructions executed by the processor 702 or storing input data required by the processor 702 to run the instructions or storing data generated after the processor 702 runs the instructions.

[0239] When the communication device 700 is used to implement Figure 6 In the method shown, the processor 702 is used to implement the functions of the above-mentioned processing unit 702, and the communication interface 701 is used to implement the functions of the above-mentioned receiving unit and / or sending unit.

[0240] The specific connection medium between the communication interface 701, the processor 702 and the memory 703 is not limited in the embodiment of the present application. Figure 7 In the embodiment, the memory 703, the processor 702 and the communication interface 701 are connected via a communication bus 704. Figure 7 The communication bus 704 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 7 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0241] When the communication device is a chip, Figure 8 A simplified schematic diagram of a chip device structure is shown, wherein the chip 800 includes an interface circuit 801 and one or more processors 802. Optionally, the chip 800 may also include a bus.

[0242] The processor 802 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above communication method can be completed by an integrated logic circuit of hardware in the processor 802 or an instruction in the form of software. The above processor 802 can be a general-purpose processor, a digital communicator (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The disclosed methods and steps in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0243] The interface circuit 801 can be used to send or receive data, instructions or information, and the processor 802 can use the data, instructions or other information received by the interface circuit 801 to process, and can send the processing completion information through the interface circuit 801. It can be understood that the interface circuit 801 can be used to output the execution result of the processor 802.

[0244] Optionally, the chip also includes a memory 803, which may include a read-only memory and a random access memory, and provides operation instructions and data to the processor. A portion of the memory 803 may also include a non-volatile random access memory (NVRAM). The memory stores executable software modules or data structures, and the processor can perform corresponding operations by calling the operation instructions stored in the memory (the operation instructions may be stored in the operating system).

[0245] It can be understood that the chip can be used in the terminal device or network device involved in the embodiments of the present application.

[0246] Regarding the communication method provided by one or more embodiments of the present application, reference may be made to the aforementioned embodiments, which will not be described in detail here.

[0247] It should be noted that the functions corresponding to the interface circuit 801 and the processor 802 can be implemented through hardware design, software design, or a combination of hardware and software, which is not limited here.

[0248] An embodiment of the present application also provides a computer-readable storage medium on which are stored computer instructions for implementing the method executed by a terminal device or a network device in the above method embodiment.

[0249] For example, when the computer program is executed by a computer, the computer can implement the method performed by the terminal device or the network device in the above method embodiment.

[0250] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method executed by a terminal device or a network device in the above method embodiment.

[0251] The embodiment of the present application also provides a chip, including a processor, which is used to call the computer program or computer instruction stored in the memory so that the processor executes the above Figure 3A-3B ,as well as Figure 4 and Figure 5 In one possible implementation, the chip input corresponds to the above Figure 3A-3B ,as well as Figure 4 and Figure 5In the receiving operation of the embodiment shown, the output of the chip corresponds to the above Figure 3A-3B ,as well as Figure 4 and Figure 5 The sending operation in the embodiment shown.

[0252] Optionally, the processor may be coupled to the memory via an interface. Alternatively, the chip further comprises a memory in which a computer program or a computer instruction is stored.

[0253] The processor mentioned in any of the above places can be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the above Figure 3A-3B ,as well as Figure 4 and Figure 5 An integrated circuit for executing a program of a communication method of the embodiment shown. The memory mentioned in any of the above places can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc.

[0254] It should be noted that, for the sake of convenience and brevity of description, the explanation of the relevant contents and beneficial effects in any of the communication devices provided above may refer to the corresponding communication method embodiments provided above, and will not be repeated here.

[0255] In the present application, the communication devices may also include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. Among them, the hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called main memory). The operating system of the operating system layer may be any one or more computer operating systems that implement business processing through processes, such as Linux operating system, Unix operating system, Android operating system, iOS operating system, or Windows operating system. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0256] The division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0257] Through the description of the above implementation mode, it can be clearly understood by those skilled in the art that the embodiments of the present application can be implemented by hardware, firmware, or a combination thereof. When software is used for implementation, the above functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein the communication media include any medium that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a computer can access. Taking this as an example but not limited to: a computer-readable medium can include RAM, ROM, electrically erasable programmable read only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer. In addition. Any connection can be appropriately a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the fixation of the medium. As used in the embodiments of the present application, disk and disc include compact disc (CD), laser disc, optical disc, digital video disc (DVD), floppy disk, and Blu-ray disc, where disks usually copy data magnetically and discs use lasers to copy data optically. The above combinations should also be included in the scope of protection of computer-readable media.

[0258] In short, the above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present application shall be included in the protection scope of the present application.

Claims

1. A communication method, characterized in that: The method is applied to a terminal device, comprising: When executing the first process, the user initiates an emergency service; In the event of network congestion, releasing the communication link resources of the first process; Sending first request information to a network device, wherein the first request information is used to request processing of a target process, wherein the target process is triggered by the emergency service; Receive first response information of the target process from the network device.

2. The method according to claim 1, characterized in that When the target process triggered by the emergency service is an emergency registration process or a non-emergency registration process, The first request information is the emergency registration request information or the non-emergency registration request information; the first response information is the emergency registration response information or the non-emergency registration response information.

3. The method according to claim 2, characterized in that The first request information includes first indication information, and the first indication information is used to indicate not to release the established communication link after the emergency registration or the non-emergency registration process.

4. The method according to claim 2 or 3, characterized in that: The first request information is carried in a first message. The first message also carries first link establishment reason information. The first link establishment reason information is used to indicate that the request to establish a communication link is for the emergency service.

5. The method according to claim 1, characterized in that: When the target process is a business process, the first request information is business request information, the first request information includes business type information, and the business type information is used to indicate that the currently executed business type is the emergency business; the first response information is business response information.

6. The method according to claim 5, characterized in that The first request information is carried in the second message, and the second message further carries second link establishment reason information, where the second link establishment reason information is used to indicate that the request to establish the communication link is for the emergency service.

7. The method according to claim 1, characterized in that The method further comprises: If there is no network congestion, wait for the first process to end.

8. The method according to claim 7, characterized in that The first request information is request information for the emergency service, the first request information includes service type information, and the service type information is used to indicate that the service type currently being executed is the emergency service; the first response information is response information for the emergency service.

9. The method according to any one of claims 1 to 8, characterized in that The first process does not include the process of the emergency service.

10. The method according to any one of claims 1 to 9, characterized in that The network equipment includes access network equipment and core network equipment.

11. A communication method, characterized in that: The method is applied to a network device, comprising: Receiving first request information from a terminal device, wherein the first request information is used to request processing of a target process, wherein the target process is triggered by an emergency service of the terminal device; Based on the first request information, processing the target process; Sending first response information of the target process to the terminal device.

12. The method according to claim 11, characterized in that When the target process is an emergency registration or non-emergency registration process, the first request information is the emergency registration request information or the non-emergency registration request information, and the first response information is the emergency registration response information or the non-emergency registration response information.

13. The method according to claim 12, characterized in that The first request information includes first indication information, and the first indication information is used to indicate not to release the established communication link after the emergency registration or the non-emergency registration process.

14. The method according to claim 12 or 13, characterized in that The first request information is carried in a first message. The first message also carries first link establishment reason information. The first link establishment reason information is used to indicate that the request to establish a communication link is for the emergency service.

15. The method according to claim 11, characterized in that When the target process is a business process, the first request information is business request information, the first request information includes business type information, and the business type information is used to indicate that the currently executed business type is the emergency business; the first response information is business response information.

16. The method according to claim 15, characterized in that The first request information is carried in the second message, and the second message further carries second link establishment reason information, where the second link establishment reason information is used to indicate that the request to establish the communication link is for the emergency service.

17. The method according to any one of claims 11 to 16, characterized in that The network equipment includes access network equipment and core network equipment.

18. A communication method, characterized in that: The method is applied to a terminal device, comprising: When executing the first process, the user initiates an emergency service; If no response information of the first process is received within a preset first time period, sending a first request information to the network device, wherein the first request information is used to request processing of a target process, the target process is triggered by the emergency service, and the target process and the first process use the same communication link resources; Receive first response information of the target process from the network device.

19. The method according to claim 18, characterized in that The target process is an emergency registration process or a non-emergency registration process.

20. The method according to claim 19, characterized in that The first request information is the emergency registration request information, and the first response information is the emergency registration response information.

21. The method according to claim 19, characterized in that The first request information is the non-emergency registration request information, the first request information includes the identification information of the emergency service, and the identification information of the emergency service is used to indicate that the current non-emergency registration process is triggered by the emergency service; the first response information is the non-emergency registration response information.

22. The method according to claim 21, characterized in that The first request information is carried in a first message. The first message also carries first link reason information. The first link reason information is used to indicate that the non-emergency registration process is triggered by the emergency service.

23. The method according to claim 18, characterized in that The target process is a business process.

24. The method according to claim 23, characterized in that The first request information is service request information, the first request information includes service type information, and the service type information is used to indicate that the type of service currently being executed is the emergency service; the first response information is service response information.

25. The method according to claim 24, characterized in that The first request information is carried in a second message, and the second message further carries second link reason information, where the second link reason information is used to indicate that the current service process is triggered by the emergency service.

26. The method according to any one of claims 18 to 25, characterized in that The first process does not include the process of the emergency service.

27. The method according to any one of claims 18 to 26, characterized in that The network equipment includes access network equipment and core network equipment.

28. A communication method, characterized in that: The method is applied to a network device, comprising: Receiving first request information from a terminal device, the first request information is used to request processing of a target process, the target process is triggered by an emergency service of the terminal device, and the target process uses the same communication link resources as a currently executed first process; Based on the first request information, processing the target process; Sending first response information of the target process to the terminal device.

29. The method according to claim 28, characterized in that The target process is an emergency registration process or a non-emergency registration process.

30. The method according to claim 29, characterized in that The first request information is the emergency registration request information, and the first response information is the emergency registration response information.

31. The method according to claim 29, characterized in that The first request information is the non-emergency registration request information, the first request information includes the identification information of the emergency service, and the identification information of the emergency service is used to indicate that the current non-emergency registration process is triggered by the emergency service; the first response information is the non-emergency registration response information.

32. The method according to claim 31, characterized in that The first request information is carried in a first message. The first message also carries first link reason information. The first link reason information is used to indicate that the non-emergency registration process is triggered by the emergency service.

33. The method according to claim 28, characterized in that The target process is a business process.

34. The method according to claim 33, characterized in that The first request information is service request information, the first request information includes service type information, and the service type information is used to indicate that the type of task currently being executed is the emergency service; the first response information is service response information.

35. The method according to claim 34, characterized in that The first request information is carried in a second message, and the second message further carries second link reason information, where the second link reason information is used to indicate that the service process is triggered by the emergency service.

36. The method according to any one of claims 28 to 35, characterized in that The first process does not include the process of the emergency service.

37. The method according to any one of claims 28 to 36, characterized in that The network equipment includes access network equipment and core network equipment.

38. A communication device, characterized in that: The method comprises a unit or module for executing the method according to any one of claims 1 to 10, or comprises a unit or module for executing the method according to any one of claims 11 to 17.

39. A communication device, characterized in that: The method comprises a unit or module for executing the method according to any one of claims 18 to 27, or comprises a unit or module for executing the method according to any one of claims 28 to 37.

40. A communication device, characterized in that: include: A processor and a memory, wherein the memory is used to store program instructions, and the processor is used to execute the program instructions in the memory to implement the method as claimed in any one of claims 1 to 17, or to implement the method as claimed in any one of claims 18 to 37.

41. A communication device, characterized in that: include: Processing circuit and interface circuit; wherein: The interface circuit is used to couple with a memory outside the communication device and provide a communication interface for the processing circuit to access the memory; the processing circuit is used to execute program instructions in the memory to implement the method as described in any one of claims 1 to 17, or to implement the method as described in any one of claims 18 to 37.

42. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or an instruction. When the computer program or the instruction is executed by the communication device, the method according to any one of claims 1 to 17 or the method according to any one of claims 18 to 37 is implemented.

Images