WO2022067769A1

WO2022067769A1 - Communication method and related device

Info

Publication number: WO2022067769A1
Application number: PCT/CN2020/119672
Authority: WO
Inventors: 马川; 韩锋; 郑黎丽; 诸华林
Original assignee: 华为技术有限公司
Priority date: 2020-09-30
Filing date: 2020-09-30
Publication date: 2022-04-07

Abstract

Embodiments of the present application provide a communication method and a related device, applicable to a scenario where a terminal device requests emergency registration or an emergency service. The communication method of the embodiments of the present application comprises: a terminal device sends an emergency registration request or emergency service request to a core network device of a first network; the terminal device receives a reject message from the core network device, the reject message being used for instructing the core network device to reject the emergency registration request or emergency service request; the terminal device receives information which is from an access network device and is used for instructing the terminal device to be redirected to a second network for emergency registration or an emergency service. According to the technical solution of the embodiments of the present application, by instructing a terminal device to perform emergency registration or an emergency service, an emergency service is provided for the terminal device, and a communication service is ensured to work normally.

Description

Communication method and related equipment

technical field

The present application relates to the field of communication technologies, and in particular, to a communication method and related equipment.

Background technique

At present, the process in which a network provides an internet protocol multimedia subsystem (IMS) emergency service for a terminal device is as follows: the terminal device requests an emergency service from the network, and the core network of the network is directly connected to the IMS. Then, the network provides emergency services for terminal equipment through IMS.

It can be known from the above solution that the core network of the network is directly connected to the IMS, so that the network can provide emergency service services for the terminal equipment. However, when the core network of the network is not directly connected to the IMS, the network cannot provide emergency service services for terminal equipment. Therefore, how to provide emergency service services for terminal equipment and ensure normal communication services is an urgent problem to be solved.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a communication method and related equipment, so as to provide emergency services for terminal equipment and ensure normal communication services.

A first aspect of the embodiments of the present application provides a communication method, including:

The terminal device sends an emergency registration request or an emergency service request to a core network device (for example, an access and mobility management function, AMF) of the first network; then, the terminal device receives a rejection message from the core network device , the rejection message is used to instruct the core network device to reject the emergency registration request or emergency service request; the terminal device receives information from the access network device that instructs the terminal device to redirect to the second network for emergency registration or emergency service.

In this embodiment, during the emergency registration request process or the emergency service request process of the terminal device in the first network, the core network device rejects the emergency registration request or the emergency service request of the terminal device. The access network device sends information to the terminal device to instruct the terminal device to redirect to the second network for emergency registration or emergency service, so that the terminal device can perform emergency registration or emergency service through the second network, in order to provide the terminal device with emergency services , to ensure the normal service of communication. In addition, the terminal device is prevented from repeatedly requesting emergency registration or emergency service from the first network, the success rate of the terminal device requesting emergency registration or emergency service is improved, and user experience and communication system performance are improved.

In a possible implementation manner, the information for instructing the terminal device to redirect to the second network for emergency registration or emergency service includes indication information for instructing the terminal device to redirect to the second network for emergency service.

In this possible implementation manner, the access network device instructs the terminal device to redirect to the second network to perform the emergency service by means of indication information, which provides a specific indication manner.

In another possible implementation manner, the information used to instruct the terminal device to redirect to the second network to request emergency registration or emergency service includes the identifier of the second network.

In this possible implementation manner, the identifier of the second network may be used by the access network device to instruct the terminal device to redirect to the second network for emergency registration or emergency service, that is, another indication manner provided by this embodiment of the present application. Secondly, the identifier of the second network is the second network recommended by the access network device for the terminal device, so that the terminal device can perform emergency registration or emergency service through the second network, so as to improve the request efficiency and success rate of the terminal device requesting emergency services.

In another possible implementation manner, the terminal device receives information from the access network device for instructing the terminal device to redirect to the second network for emergency registration or emergency service, including:

The terminal device receives a radio resource control (radio resource control, RRC) release message from the access network device, where the RRC release message includes information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service.

In this possible implementation manner, the access network device uses the RRC release message in the emergency registration request process or the emergency service request process to carry the information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service, so as to avoid quoting A new message that provides specific implementations for embodiments of the scheme.

In another possible implementation manner, the method further includes:

The terminal device requests emergency registration or emergency service from the second network.

In this possible implementation manner, the terminal device receives the information sent by the access network device to instruct the terminal device to redirect to the second network for emergency registration or emergency service, and can request emergency registration or emergency service from the second network, In order to provide emergency services for the terminal equipment through the second network, the situation that the terminal equipment repeatedly requests emergency registration or emergency services from the first network is avoided, and the success rate and request efficiency of the terminal equipment requesting emergency services are improved.

In another possible implementation manner, the first network is a non-public network (non-public networks, NPN), and the second network is a public land mobile network (public land mobile networks, PLMN); or, the first network is a PLMN network , the second network is an NPN network; or, both the first network and the second network are NPN networks; or, both the first network and the second network are PLMN networks.

In this possible implementation, this embodiment is applicable to the scenario where terminal equipment in NPN network and PLMN network requests emergency registration or emergency service, and the solution of this embodiment is implemented to provide emergency service for terminal equipment through the second network.

A second aspect of the embodiments of the present application provides a communication method, including:

The core network device receives an emergency registration request or an emergency service request from the terminal device, and the core network device is a core network device of the first network. For example, the core network device is AMF. Then, the core network device sends a reject message to the terminal device, where the reject message is used to instruct the core network device to reject the emergency registration request or the emergency service request; the core network device sends a reject message to the access network device to instruct the access network device to release the terminal device The message for instructing the access network device to release the connection of the terminal device includes information for instructing the access network device to redirect the terminal device to the second network for emergency registration or emergency service.

In this embodiment, during the emergency registration request process or the emergency service request process of the terminal device in the first network, the core network device rejects the terminal device's emergency registration request or emergency service request, and the core network device sends a message to the access network device. Information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service, to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service, so as to Terminal equipment provides emergency services to ensure normal communication services. In addition, the terminal device is prevented from repeatedly requesting emergency registration or emergency service from the first network, the success rate of the terminal device requesting emergency registration or emergency service is improved, and user experience and communication system performance are improved.

In a possible implementation manner, the information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service includes information used to instruct the access network device to redirect the terminal device to the second network for emergency registration. Instructions for emergency registration or emergency services.

In this possible implementation manner, the core network device instructs the access network device to redirect the terminal device to the second network for emergency registration or emergency service by means of indication information, that is, a specific indication manner is provided.

In another possible implementation manner, the information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service includes the identifier of the second network.

In this possible implementation manner, the core network device uses the identifier of the second network to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service, that is, another specific instruction method is provided. In addition, the core network device recommends the second network to the access network device, so that the access network device can recommend the corresponding second network to the terminal device, which further helps the terminal device to perform emergency registration or emergency services through the second network, so as to ensure normal communication. service.

In another possible implementation manner, the first network is an NPN network, and the second network is a PLMN network; or, the first network is a PLMN network, and the second network is an NPN network; or, the first network and the second network are both NPN network; or, both the first network and the second network are PLMN networks.

In this possible implementation, this embodiment is applicable to a scenario where terminal equipment requests emergency registration or emergency services in an NPN network or PLMN network, and the solution of this embodiment is implemented to provide emergency services for terminal equipment through the second network.

In another possible implementation manner, the message used to instruct the access network device to release the connection of the terminal device is a UE context release command (user equipment context release command) message.

In this possible implementation manner, a specific message is provided in which the core network device sends a message to the access network device for instructing the access network device to release the connection of the terminal device on the NG interface.

A third aspect of the embodiments of the present application provides a communication method, including:

The access network device determines the information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service, and the access network device is the access network device in the first network; the access network device sends to the terminal device information for Information indicating that the terminal device is redirected to the second network for emergency registration or emergency service.

In this embodiment, the access network device sends information to the terminal device for instructing the terminal device to redirect to the second network to perform emergency registration or emergency service, so that the terminal device can perform emergency registration or emergency service through the second network, with a view to Terminal equipment provides emergency services to ensure normal communication services. In addition, the terminal device is prevented from repeatedly requesting emergency registration or emergency service from the first network, the success rate of the terminal device requesting emergency registration or emergency service is improved, and user experience and communication system performance are improved.

In a possible implementation manner, the method further includes: the access network device receives a message from a core network device (eg, AMF) of the first network for instructing the access network device to release the connection of the terminal device.

In this possible implementation manner, a trigger condition is provided that triggers the access network device to determine the information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service, and the core network device is used to instruct the access network device The message that the network device releases the connection of the terminal device on the NG interface determines that the core network device rejects the terminal device's emergency registration request or emergency service request.

In another possible implementation manner, the message used to instruct the access network device to release the connection of the terminal device includes information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service .

In this possible implementation manner, the core network device may send a message for instructing the access network device to release the connection of the terminal device to the access network device to instruct the access network device to redirect the terminal device to the second Information about emergency registration or emergency services performed by the network. In this way, the access network device may determine to instruct the terminal device to redirect the terminal device to the second network for emergency registration or emergency service according to the information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service, that is, Another trigger condition for the terminal device to determine information for instructing the terminal device to redirect to the second network for emergency registration or emergency service is provided.

In another possible implementation manner, the information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service includes information used to instruct the access network device to redirect the terminal device to the second network Instructions for emergency registration or emergency services.

In another possible implementation manner, the message used to instruct the access network device to release the connection of the terminal device on the NG interface is a UE context release command message.

In this possible implementation, a specific form of the message for instructing the access network device to release the connection of the terminal device on the NG interface is provided.

In this possible implementation manner, the core network device uses the identifier of the second network to indirectly instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service. In addition, the identifier of the second network is the second network recommended by the core network device to the access network device, so that the access network device can recommend the corresponding second network to the terminal device, and further help the terminal device to implement emergency registration through the second network. Or emergency services, ensure the normal service of communication, and improve the success rate and request efficiency of terminal equipment requesting emergency services.

In another possible implementation manner, the information for instructing the terminal device to redirect to the second network for emergency registration or emergency service includes indication information for instructing the terminal device to redirect to the second network for emergency registration or emergency service.

In this possible implementation manner, the access network device instructs the terminal device to redirect to the second network for emergency registration or emergency service by means of indication information, which provides a specific indication manner.

In another possible implementation manner, the information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service includes an identifier of the second network.

In this possible implementation manner, the access network device uses the identifier of the second network to indirectly instruct the terminal device to redirect to the second network for emergency registration or emergency service, which provides another specific instruction manner. In addition, the identifier of the second network is the second network recommended by the access network device to the terminal device, so as to further help the terminal device to implement emergency registration or emergency services through the second network, ensure normal communication services, and improve the terminal device's request for emergency services. success rate and request efficiency.

In another possible implementation manner, the access network device sends information to the terminal device for instructing the terminal device to redirect to the second network for emergency registration or emergency service, including:

The access network device sends an RRC release message to the terminal device, where the RRC release message includes information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service.

A fourth aspect of the embodiments of the present application provides a communication method, including:

The terminal device sends a registration request to the core network device (eg, AMF), and the registration request is used by the terminal device to request to register in the first network; then, the terminal device receives a registration acceptance from the core network device, and the registration acceptance includes instructions for the terminal device. information of emergency registration through a third network, where the third network is a network associated with the first network.

In this possible implementation manner, the terminal device determines that the third network supports emergency services, and requests the core network device of the first network for emergency registration through the third network during the registration process of the terminal device in the first network. Then, the terminal device receives the registration acceptance from the core network device, and determines the emergency registration through the third network according to the information included in the registration acceptance and used to instruct the terminal device to urgently register through the third network. In this way, the terminal device can perform emergency registration or emergency services through the third network, so that the first network can provide emergency services for the terminal device through the second network, so as to ensure normal communication services. When directly connected to the IMS, the first network cannot provide the terminal device with the IMS emergency service service. Compared with the existing way of directly connecting the IMS through the core network of the first network, so that the network can provide the terminal equipment with the IMS emergency service service, the technical solution of the present embodiment provides the terminal equipment of the first network with the emergency service. More diversification, expanding the ability of the first network to provide emergency services.

In a possible implementation manner, the information used to instruct the terminal device to register urgently through the third network includes a first registration type, and the first registration type includes urgent registration through the third network.

In this possible implementation, during the emergency registration process of the terminal device in the first network, the core network device indicates to the terminal device the emergency registration of the terminal device through the third network through the registration type field, so as to realize the core network device to the terminal device An emergency registration method for instructing the terminal device to register urgently through the third network.

In another possible implementation manner, the registration request includes information used to instruct the terminal device to request emergency registration through the third network.

In this possible implementation manner, the terminal device determines that the third network supports emergency services, and the terminal device may register the request to carry information indicating that the terminal device requests emergency registration through the third network, so as to request the core network device of the first network for the terminal device to register through the third network. The emergency registration method of the third network emergency registration.

In another possible implementation manner, the information used to instruct the terminal device to request emergency registration through the third network includes a first registration type, and the first registration type includes emergency registration through the third network.

In this possible implementation manner, the terminal device instructs the core network device through a registration type field in the registration request to indicate an emergency registration method in which the terminal device requests emergency registration through the third network.

In another possible implementation manner, the registration acceptance further includes an identifier of a third network, and the third network supports emergency services.

In this possible implementation manner, the core network device may also recommend a third network associated with the first network and supporting emergency services to the terminal device, so that the terminal device can register urgently through the third network, so that the first network can pass the third network through the third network. Three networks provide emergency services for terminal equipment.

In another possible implementation manner, the method further includes: the terminal device sends an RRC establishment request to the access network device, where the RRC establishment request includes information used to instruct the terminal device to request to provide emergency services for the terminal device through a third network; the terminal device Receive an RRC setup from an access network device.

In this possible implementation manner, the terminal device may initiate an RRC connection establishment request to the access network device, so as to realize the RRC connection between the terminal device and the access network device. The terminal equipment may carry information used to instruct the terminal equipment to request to provide emergency services for the terminal equipment through the third network in the RRC establishment request, so that the access network equipment can perform communication between the terminal equipment preconfigured for the terminal equipment and the third network. Emergency session resources for emergency registration or emergency services, so as to facilitate emergency registration or emergency services between the subsequent terminal device and the third network.

In another possible implementation manner, the information used to instruct the terminal device to request to provide emergency services to the terminal device through the second network includes a cause value, where the cause value includes: the terminal device requests to provide emergency services to the terminal device through the third network .

In this possible implementation manner, the terminal equipment may indicate to the access network equipment through the cause value field in the RRC establishment request that the terminal equipment requests to provide emergency services for the terminal equipment through the third network, that is, a specific indication method is provided.

In another possible implementation manner, before the terminal device sends the registration request to the core network device, the method further includes: the terminal device receives information from the access network device for indicating that the third network supports the emergency service.

In this possible implementation manner, a method for the terminal device to determine that the third network supports emergency services is provided, which provides conditions for the embodiments of the solution.

In another possible implementation manner, the information used to indicate that the third network supports the emergency service is system information used to indicate that the third network supports the emergency service.

In this possible implementation manner, based on the manner of sending information for indicating that the third network supports emergency services to the terminal equipment through the access network equipment, it is provided that the access network equipment indicates the third network through the system information of the access network equipment. The network supports emergency services.

In another possible implementation manner, the registration request includes information used to indicate that the terminal device requests emergency registration through the first network.

In this possible implementation manner, if the terminal device determines that at least one of the first network and the third network supports emergency services, the terminal device may register the request with information indicating that the terminal device requests emergency registration through the first network, so as to report to the third network. An emergency registration method in which the core network device of a network requests the terminal device to register urgently through the first network.

In another possible implementation manner, the information used to indicate emergency registration through the first network requested by the terminal device includes a second registration type, and the second registration type includes emergency registration through the first network.

In this possible implementation manner, the terminal device instructs the core network device through a registration type field in the registration request to indicate to the core network device an emergency registration method in which the terminal device requests emergency registration through the first network.

In another possible implementation manner, before the terminal device sends the registration request to the core network device, the method further includes: the terminal device receives an instruction from the access network device to indicate that at least one of the first network and the second network supports emergency services Information.

In this possible implementation manner, a method for the terminal device to determine that at least one network in the first network and the second network supports emergency services is provided, which provides conditions for the embodiments of the solution.

In another possible implementation manner, the information used to indicate that at least one network in the first network and the second network supports the emergency service is a system used to indicate that at least one network in the first network and the second network supports the emergency service information.

In this possible implementation manner, based on the method of sending information indicating that at least one network in the first network and the second network supports emergency services to the terminal device through the access network device, it is provided that the access network device can use the The system information of the network access device indicates that at least one of the first network and the second network supports emergency services.

In another possible implementation manner, the method further includes:

The terminal device receives the identification of the third network from the access network device, and the third network supports emergency services.

In this possible implementation manner, the access network device may recommend a third network associated with the first network and supporting emergency services to the terminal device, so that the terminal device can register urgently through the third network, so that the first network can pass the third network through the third network. Three networks provide emergency services for terminal equipment.

In another possible implementation manner, the first network is an NPN network, and the third network is a PLMN network; or, the first network is a PLMN network, and the third network is an NPN network; or, the first network and the third network are both NPN network; or, both the first network and the third network are PLMN networks.

In this possible implementation, this embodiment is applicable to the scenario where terminal equipment requests emergency registration or emergency services in NPN network or PLMN network, and the solution of this embodiment is implemented to provide emergency services for terminal equipment through a third network.

A fifth aspect of the embodiments of the present application provides a communication method, including:

The core network device receives a registration request sent from the terminal device, where the registration request is used by the terminal device to request to register in the first network; for example, the core network device is an AMF. Then, the core network device sends a registration acceptance to the terminal device, where the registration acceptance includes information for instructing the terminal device to urgently register through a third network, which is a network associated with the first network.

In this embodiment, the terminal device requests the core network device of the first network for emergency registration through the third network during the registration process of the terminal device in the first network. The core network device sends a registration acceptance to the terminal device, and determines the emergency registration through the third network according to the information included in the registration acceptance and used to instruct the terminal device to urgently register through the third network. In this way, the terminal device can perform emergency registration or emergency services through the third network, so that the first network can provide emergency services for the terminal device through the second network, so as to ensure normal communication services. When directly connected to the IMS, the first network cannot provide the terminal device with the IMS emergency service service. Compared with the existing way of directly connecting the IMS through the core network of the first network, so that the network can provide the terminal equipment with the IMS emergency service service, the technical solution of this embodiment provides the terminal equipment of the first network with the emergency service. More diversification, expanding the ability of the first network to provide emergency services.

In another possible implementation manner, the registration acceptance further includes the identifier of the second network, and the second network supports emergency services.

In another possible implementation manner, the method further includes: the core network device sends information to the access network device for instructing the access network device terminal device to register urgently through the third network.

In this possible implementation manner, the core network device may notify the access network device to perform emergency registration through the third network, so that the access network device can determine the emergency registration method of the terminal device.

In another possible implementation manner, the information used to instruct the access network equipment terminal equipment to urgently register through the third network includes indication information of information used to instruct the access network equipment terminal equipment to urgently register through the third network.

In this possible implementation manner, the core network equipment instructs the access network equipment terminal equipment to register urgently through the third network by means of indication information, that is, a specific indication form is provided.

In another possible implementation manner, the method further includes:

The core network device sends the identification of the third network to the access network device, and the third network supports emergency services. For example, the core network device is AMF.

In this possible implementation manner, the core network device can recommend the third network to the access network device, so that the access network device can recommend the third network supporting emergency services to the terminal device, so that the first network can be configured as the first network through the second network. Terminal equipment provides emergency services.

In an implementation manner, this embodiment is applicable to a scenario where a terminal device in an NPN network or a PLMN network requests an emergency registration or emergency service, and the solution of this embodiment is implemented to provide an emergency service for the terminal device through a third network.

A sixth aspect of the embodiments of the present application provides a communication method, including:

The access network device sends information for indicating that the third network supports emergency services to the terminal device, where the access network device is an access network device of the first network, and the third network is a network associated with the first network.

In this embodiment, the access network device indicates to the terminal device that the third network supports emergency services, so that the terminal device can request emergency registration or emergency services through the third network, so that the first network can provide emergency services for the terminal device through the second network , to ensure the normal service of communication.

In a possible implementation manner, the information used to indicate that the third network supports the emergency service includes indication information used to indicate that the third network supports the emergency service.

In this possible implementation manner, the access network device instructs the third network to support the emergency service by means of indication information, that is, a specific indication manner is provided.

In this possible implementation manner, the access network device may broadcast information for indicating that the third network supports the emergency service through system information of the access network device.

In another possible implementation manner, after the access network device sends the information for indicating that the third network supports the emergency service to the terminal device, the method further includes: the access network device receives an RRC establishment request from the terminal device, and the RRC establishment includes: Information used to instruct the terminal equipment to request to provide emergency services for the terminal equipment through the third network; the access network equipment sends RRC establishment to the terminal equipment.

In this possible implementation manner, the terminal device may initiate an RRC connection establishment request to the access network device, so as to realize the RRC connection between the terminal device and the access network device. The terminal equipment may carry information used to instruct the terminal equipment to request to provide emergency services for the terminal equipment through the third network in the RRC establishment request, so that the access network equipment can perform communication between the terminal equipment preconfigured for the terminal equipment and the third network. Emergency session resources for emergency registration or emergency services, so as to facilitate subsequent emergency registration or emergency services between the terminal device and the third network.

A seventh aspect of an embodiment of the present application provides a communication method, including:

The access network device sends information to the terminal device indicating that at least one network in the first network and the third network supports emergency services, the access network device is the access network device of the first network, and the third network is the same as the first network. Network associated network.

In this embodiment, the access network device indicates to the terminal device that there is at least one network emergency service in the first network and the third network, so that the terminal device can request emergency registration or emergency service through the first network, and then the core network device determines the terminal Emergency registration method for the device.

In a possible implementation manner, the information used to indicate that at least one network in the first network and the third network supports the emergency service includes indication information used to indicate that at least one network in the first network and the third network supports the emergency service .

In this possible implementation manner, the access network device uses indication information to indicate that at least one of the first network and the third network supports emergency services, that is, a specific indication manner is provided.

In another possible implementation manner, the information for indicating that at least one network in the first network and the third network supports emergency services includes a system for indicating that at least one network in the first network and the third network supports emergency services information.

In this possible implementation manner, the access network device may broadcast information used to indicate that at least one of the first network and the third network supports emergency services through system information of the access network device.

In another possible implementation manner, the method further includes: the access network device receives information from the core network device for instructing the access network device terminal device to register urgently through the third network;

The access network device sends the identification of the third network to the terminal device, and the third network supports emergency services.

In this possible implementation manner, the access network device may recommend a third network that supports emergency services to the terminal device, so that the terminal device can register urgently through the third network, so that the first network can provide emergency services for the terminal device through the third network. business.

In another possible implementation manner, the method further includes:

The access network device receives the identification of the third network from the core network device.

In this possible implementation manner, this embodiment is applicable to a scenario in which a terminal device in an NPN network or a PLMN network requests emergency registration or emergency services.

An eighth aspect of an embodiment of the present application provides a communication method, including:

The terminal device sends a registration request to the core network device of the first network, where the registration request is used for the terminal device to request to register in the first network; the terminal device receives a registration acceptance from the core network device, and the registration acceptance includes at least one of the following: the first network Yes/No to support emergency services, yes/no to the third network to support emergency services; the third network is a network associated with the first network.

In this embodiment, the terminal device can determine whether or not the first network and the third network respectively support emergency services according to the registration acceptance, so that the terminal device can select the corresponding network to perform emergency registration or emergency services, ensure normal communication services, and improve the The success rate of the device successfully requesting emergency services from the network and the request efficiency of requesting emergency services.

In a possible implementation manner, the registration acceptance further includes an identifier of a third network, and the third network supports emergency services.

In this possible implementation manner, the core network device may recommend a third network that supports emergency services to the terminal device, so that the first network provides emergency services for the terminal device through the third network.

A ninth aspect of an embodiment of the present application provides a communication method, including:

The core network device receives a registration request from the terminal device, where the registration request is used by the terminal device to request to register in the first network; for example, the core network device is an AMF. The core network device sends a registration acceptance to the terminal device, and the registration acceptance includes at least one of the following: whether the first network supports emergency services, whether the third network supports emergency services; the third network is a network associated with the first network.

In this embodiment, the core network device sends a registration acceptance to the terminal device, and the registration acceptance includes at least one of the following: whether the first network supports emergency services, and whether the third network supports emergency services, so that the terminal device can accept the registration according to the Determine whether or not the first network and the third network support emergency services respectively, so that the terminal device can select the corresponding network for emergency registration or emergency services, ensure normal communication services, and improve the success rate of the terminal device successfully requesting emergency services from the network. Request efficiency for requesting urgent services.

In this possible implementation, this embodiment is applicable to a scenario in which a terminal device in an NPN network or a PLMN network requests emergency registration or emergency services.

A tenth aspect of the embodiments of the present application provides a communication method, including:

The access network device sends information for indicating whether or not the third network supports emergency services to the terminal device, where the third network is a network associated with the first network, and the access network device is an access network device of the first network.

In this embodiment, the access network device indicates to the terminal device whether or not the third network supports emergency services, so that the terminal device determines whether or not to select the first network for emergency registration, so as to avoid when the first network and the third network cannot When the emergency service is provided, the terminal device repeatedly initiates an emergency registration request or an emergency service request to the first network or the third network, so as to improve the success rate and request efficiency of the terminal device successfully requesting the emergency service from the network.

In a possible implementation manner, the information used to indicate whether or not the third network supports emergency services includes indication information used to indicate whether the third network supports emergency services.

In this possible implementation manner, the access network device indicates to the terminal device whether or not the third network supports emergency services by means of indication information, that is, a specific indication manner is provided.

In another possible implementation manner, the information used to indicate whether or not the third network supports the emergency service is system information of the access network device.

In this possible implementation manner, the access network device indicates to the terminal device whether or not the third network supports emergency services through the system information of the access network device, that is, a specific information form is provided, which improves the realization of the solution. sex.

In another possible implementation manner, the method further includes:

The access network device sends information for indicating whether the first network supports the emergency service to the terminal device.

In this possible implementation manner, the access network device indicates to the terminal device whether or not the first network supports emergency services, so that the terminal device determines whether or not to select the first network for emergency registration, thereby avoiding when the first network and the third network When the network cannot provide the emergency service, the terminal device repeatedly initiates the emergency registration request or the emergency service request to the first network, so as to improve the success rate and request efficiency of the terminal device successfully requesting the emergency service from the network.

In another possible implementation manner, the information used to indicate whether or not the first network supports emergency services includes indication information used to indicate whether the first network supports emergency services.

In this possible implementation manner, the access network device indicates to the terminal device whether or not the first network supports emergency services by means of indication information, that is, a specific indication manner is provided.

In another possible implementation manner, the information used to indicate whether or not the first network supports the emergency service is system information of the access network device.

In this possible implementation manner, the access network device indicates to the terminal device whether or not the first network supports emergency services through the system information of the access network device, that is, a specific information form is provided, which improves the realization of the solution sex.

An eleventh aspect of the embodiments of the present application provides a communication method, including:

The terminal device receives information from the access network device of the first network used to indicate whether or not the third network supports emergency services, and the third network is a network associated with the first network; The information of whether the network supports emergency services determines whether or not to select the first network.

In this embodiment, the terminal device receives information from the access network device of the first network indicating whether or not the third network supports emergency services, so that the terminal device determines whether or not to select the first network for emergency registration, avoiding the need for emergency registration. When neither the first network nor the third network can provide emergency services, the terminal device repeatedly initiates an emergency registration request or emergency service request to the first network or the third network, so as to improve the success rate of the terminal device successfully requesting emergency services from the network. Request efficiency to ensure normal communication services.

In another possible implementation manner, the method further includes:

The terminal device receives information from the access network device for indicating whether or not the first network supports emergency services;

The terminal device determines whether or not to select the first network according to the information used to indicate whether or not the third network supports emergency services, including:

The terminal device determines whether or not to select the first network according to the information used to indicate whether the first network supports the emergency service and the information used to indicate whether the third network supports the emergency service.

In this possible implementation manner, the access network device may send the information used to indicate whether the first network supports the emergency service or not to the terminal device, so that the terminal device can, according to the information used to indicate whether or not the first network supports the emergency service, information and the information used to indicate whether the third network supports emergency services to determine whether to select the first network, to avoid the terminal equipment repeating to the first network or the third network when neither the first network nor the third network can provide emergency services. The third network initiates the emergency registration request or the emergency service request, so as to improve the success rate and request efficiency of the terminal device successfully requesting the emergency service from the network, and ensure the normal service of the communication.

In another possible implementation manner, the terminal device determines whether or not to select the first network according to the information used to indicate whether the first network supports the emergency service or the information used to indicate whether the third network supports the emergency service. include:

When the terminal device determines that the first network supports emergency services and the second network does not support emergency services, the terminal device determines to select the first network; or,

When the terminal device determines that the first network supports the emergency service and the third network supports the emergency service, the terminal device determines to select the first network; or,

When the terminal device determines that the first network does not support emergency services and the third network supports emergency services, the terminal device determines to select the first network; or,

When the terminal device determines that the first network does not support the emergency service and the third network does not support the emergency service, the terminal device determines not to select the first network.

In a possible implementation, it is provided that the terminal device determines whether or not to select the first network according to the information used to indicate whether the first network supports the emergency service or the information used to indicate whether the third network supports the emergency service. Specific process.

In an implementation manner, this embodiment is applicable to a scenario in which a terminal device in an NPN network or a PLMN network requests emergency registration or emergency services.

A twelfth aspect of an embodiment of the present application provides a communication method, including:

The access network device sends information to the terminal device for indicating whether or not at least one of the first network and the third network supports emergency services, the access network device is the access network device of the first network, and the third network is A network associated with the first network.

In this embodiment, the access network device indicates to the terminal device whether or not at least one of the first network and the third network supports emergency services, so that the terminal device can Whether there is information about whether at least one network supports emergency services to determine whether or not to select the first network for emergency registration, so as to avoid the terminal equipment repeating to the first network or the third network when neither the first network nor the third network can provide emergency services. The problem of initiating an emergency registration request or an emergency service request is to improve the success rate and request efficiency of the terminal device successfully requesting the emergency service from the network, and ensure the normal service of communication.

In a possible implementation manner, the information used to indicate whether at least one of the first network and the third network supports the emergency service includes the information used to indicate whether there is at least one of the first network and the third network. Indicates that the network supports emergency services.

In this possible implementation manner, the access network device uses indication information to indicate to the terminal device whether or not at least one of the first network and the third network supports emergency services, that is, a specific indication manner is provided.

In another possible implementation manner, the information used to indicate whether or not the first network and the third network support the emergency service is system information of the access network device.

In this possible implementation manner, the access network device indicates to the terminal device whether or not the first network and the third network support emergency services through the system information of the access network device, that is, a specific information form is provided, which improves the feasibility of the program.

A thirteenth aspect of an embodiment of the present application provides a communication method, including:

The terminal device receives information from the access network device of the first network for indicating whether/whether at least one of the first network and the third network supports emergency services, and the third network is a network associated with the first network; then , the terminal device determines whether or not to select the first network according to the information used to indicate whether or not at least one of the first network and the third network supports emergency services.

In this embodiment, the access network device indicates to the terminal device whether or not at least one of the first network and the third network supports emergency services, so that the terminal device can indicate whether or not one of the first network and the third network supports emergency services according to the There is information that at least one network supports emergency services to determine whether or not to select the first network for emergency registration, so as to avoid the terminal device repeatedly sending the first network or the third network when neither the first network nor the third network can provide emergency services. The problem of emergency registration request or emergency service request is to improve the success rate and request efficiency of terminal equipment successfully requesting emergency service from the network, and ensure the normal service of communication.

In a possible implementation manner, the information used to indicate whether or not at least one network in the first network and the third network supports emergency services includes information used to indicate whether there is at least one network in the first network and the third network. Instructions to support emergency services.

In this possible implementation manner, the access network device uses indication information to indicate whether or not at least one of the first network and the third network supports the emergency service.

In another possible implementation manner, the information used to indicate whether or not at least one of the first network and the third network supports the emergency service is system information of the access network device.

In another possible implementation manner, the terminal device determines whether or not to select the first network according to information used to indicate whether or not at least one of the first network and the third network supports emergency services, including: when the terminal device determines When at least one network in the first network and the third network supports the emergency service, the terminal device determines to select the first network; or, when the terminal device determines that neither the first network nor the third network supports the network of the emergency service, the terminal device determines Do not select the first network.

In this possible implementation, a specific process is provided for the terminal device to determine whether or not to select the first network according to the information used to indicate whether or not at least one of the first network and the third network supports emergency services.

A fourteenth aspect of an embodiment of the present application provides a communication device, including:

a sending unit, configured to send an emergency registration request or an emergency service request to the core network device of the network of the first network;

The receiving unit is configured to receive a rejection message from the core network device, where the rejection message is used to instruct the core network device to reject the emergency registration request or the emergency service request; receiving a rejection message from the access network device is used to instruct the terminal device to redirect to the second network for processing. Emergency registration or emergency business information.

In another possible implementation manner, the information used to instruct the terminal device to redirect to the second network to request emergency registration or emergency service includes an identifier of the second network.

In another possible implementation manner, the receiving unit is specifically used for:

Receive a radio resource control (radio resource control, RRC) release message from the access network device, where the RRC release message includes information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service.

In another possible implementation manner, the communication device further includes a processing unit, and the processing unit is further configured to:

Request emergency registration or emergency service from the second network.

A fifteenth aspect of an embodiment of the present application provides a communication device, including:

a receiving unit, configured to receive an emergency registration request or an emergency service request from a terminal device, where the core network device is a core network device of the first network;

The sending unit is configured to send a reject message to the terminal device, where the reject message is used to instruct the core network device to reject the emergency registration request or the emergency service request; send a message to the access network device to instruct the access network device to release the connection of the terminal device message, the message used to instruct the access network device to release the connection of the terminal device includes information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service.

In another possible implementation manner, the message used to instruct the access network device to release the connection of the terminal device is a UE context release command message.

A sixteenth aspect of an embodiment of the present application provides a communication device, including:

a processing unit, configured to determine information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service, where the access network device is an access network device in the first network;

A sending unit, configured to send information to the terminal device for instructing the terminal device to redirect to the second network for emergency registration or emergency service.

In a possible implementation manner, the communication device further includes a receiving unit, and the receiving unit is further configured to:

A message for instructing the access network device to release the connection of the terminal device from the core network device of the first network is received.

In another possible implementation manner, the information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service includes the identifier of the second network.

In another possible implementation manner, the sending unit is specifically used for:

An RRC release message is sent to the terminal device, where the RRC release message includes information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service.

A seventeenth aspect of an embodiment of the present application provides a communication device, including:

a sending unit, configured to send a registration request to the core network device, where the registration request is used by the terminal device to request to register in the first network;

The receiving unit is configured to receive a registration acceptance from the core network device, where the registration acceptance includes information used to instruct the terminal device to urgently register through a third network, where the third network is a network associated with the first network.

In another possible implementation manner, the sending unit is also used for:

Send an RRC setup request to the access network device, where the RRC setup request includes information used to instruct the terminal device to request an emergency service for the terminal device through a third network; and receive the RRC setup from the access network device.

In another possible implementation manner, the receiving unit is also used for:

Information from the access network device for indicating that the third network supports emergency services is received.

In another possible implementation manner, the receiving unit is also used for:

Information is received from the access network device for indicating that at least one of the first network and the second network supports emergency services.

In another possible implementation manner, the receiving unit is also used for:

The identification of the third network from the access network device is received, and the third network supports emergency services.

An eighteenth aspect of an embodiment of the present application provides a communication device, including:

a receiving unit, configured to receive a registration request sent from the terminal device, where the registration request is used by the terminal device to request to register in the first network;

The sending unit is configured to send a registration acceptance to the terminal device, where the registration acceptance includes information used to instruct the terminal device to urgently register through a third network, where the third network is a network associated with the first network.

In another possible implementation manner, the information used to instruct the terminal device to request emergency registration through the first network includes a second registration type, and the second registration type includes emergency registration through the first network.

In another possible implementation manner, the sending unit is also used for:

The information used to instruct the access network device terminal device to register urgently through the third network is sent to the access network device.

In another possible implementation manner, the sending unit is also used for:

The identifier of the third network is sent to the access network device, and the third network supports emergency services.

A nineteenth aspect of an embodiment of the present application provides a communication device, including:

The sending unit is configured to send information for indicating that the third network supports emergency services to the terminal device, where the access network device is an access network device of the first network, and the third network is a network associated with the first network.

In another possible implementation manner, the communication device further includes a receiving unit, and the receiving unit is further configured to:

receiving an RRC establishment request from a terminal device, where the RRC establishment includes information used to instruct the terminal device to request to provide emergency services for the terminal device through a third network;

The sending unit is also used to:

Send RRC setup to the terminal device.

A twentieth aspect of an embodiment of the present application provides a communication device, including:

The sending unit is configured to send information to the terminal device indicating that at least one network in the first network and the third network supports emergency services, the access network device is the access network device of the first network, and the third network is the same as the third network. A network associated network.

receiving information from the core network equipment of the first network for instructing the access network equipment terminal equipment to register urgently through the third network;

The sending unit is also used to:

The identifier of the third network is sent to the terminal device, and the third network supports emergency services.

In another possible implementation manner, the receiving unit is also used for:

An identification of a third network is received from a core network device of the first network.

A twenty-first aspect of an embodiment of the present application provides a communication device, including:

a sending unit, configured to send a registration request to the core network device of the first network, where the registration request is used by the terminal device to request to register in the first network;

a receiving unit, configured to receive a registration acceptance from a core network device; the registration acceptance includes at least one of the following: whether the first network supports emergency services, whether the third network supports emergency services; the third network is associated with the first network network of.

A twenty-second aspect of an embodiment of the present application provides a communication device, including:

a receiving unit, configured to receive a registration request from the terminal device, where the registration request is used by the terminal device to request to register in the first network;

A sending unit, configured to send a registration acceptance to the terminal device, where the registration acceptance includes at least one of the following: whether the first network supports emergency services, whether the third network supports emergency services; the third network is a network associated with the first network .

A twenty-third aspect of an embodiment of the present application provides a communication device, including:

The sending unit is configured to send information for indicating whether or not the third network supports emergency services to the terminal device, where the third network is a network associated with the first network, and the access network device is an access network device of the first network.

In another possible implementation manner, the sending unit is also used for:

The information for indicating whether or not the first network supports emergency services is sent to the terminal device.

A twenty-fourth aspect of an embodiment of the present application provides a communication device, including:

a receiving unit, configured to receive information from an access network device of the first network for indicating whether or not a third network supports emergency services, where the third network is a network associated with the first network;

The processing unit is configured to determine whether or not to select the first network according to the information used to indicate whether or not the third network supports emergency services.

In another possible implementation manner, the receiving unit is also used for:

receiving information from an access network device indicating whether or not the first network supports emergency services;

The processing unit is specifically used for:

Whether or not to select the first network is determined according to the information indicating whether the first network supports the emergency service and the information indicating whether the third network supports the emergency service.

In another possible implementation manner, the processing unit is specifically used for:

When the terminal device determines that the first network supports emergency services and the second network does not support emergency services, it determines to select the first network; or,

When the terminal device determines that the first network supports the emergency service and the third network supports the emergency service, it determines to select the first network; or,

When the terminal device determines that the first network does not support emergency services and the third network supports emergency services, it determines to select the first network; or,

When the terminal device determines that the first network does not support the emergency service and the third network does not support the emergency service, it determines not to select the first network.

A twenty-fifth aspect of an embodiment of the present application provides a communication device, including:

A sending unit, configured to send information to the terminal device for indicating whether or not at least one of the first network and the third network supports emergency services, the access network device is the access network device of the first network, and the third network is the network associated with the first network.

A twenty-sixth aspect of an embodiment of the present application provides a communication device, including:

A receiving unit, configured to receive information from an access network device of the first network for indicating whether or not at least one of the first network and the third network supports emergency services, and the third network is associated with the first network The internet;

The processing unit is configured to determine whether or not to select the first network according to the information indicating whether or not at least one of the first network and the third network supports emergency services.

When the terminal device determines that at least one of the first network and the third network supports emergency services, it determines to select the first network; or,

When the terminal device determines that neither the first network nor the third network supports the network of the emergency service, it determines not to select the first network.

A twenty-seventh aspect of an embodiment of the present application provides a communication device, where the communication device includes: a processor, a memory, and a transceiver connected to the processor. A computer program or computer instruction is stored in the memory, and the processor is further configured to invoke and execute the computer program or computer instruction stored in the memory, so that the processor implements any one of the first to thirteenth aspects an implementation.

Optionally, the terminal device further includes a transceiver, and the processor is configured to control the transceiver to perform any one of the implementation manners in the first aspect.

A twenty-eighth aspect of an embodiment of the present application provides a computer program product including computer instructions, characterized in that, when it runs on a computer, the computer is made to perform the implementation of any one of the first to thirteenth aspects Way.

A twenty-ninth aspect of an embodiment of the present application provides a computer-readable storage medium, including computer instructions, and when the instructions are executed on a computer, the computer executes any one of the first to thirteenth aspects Method to realize.

A thirtieth aspect of an embodiment of the present application provides a communication device, where the communication device includes entities such as network equipment, terminal equipment, or chips, and the communication device includes a processor for invoking a computer program or computer instruction in a memory, so that the processor executes Any one of the above-mentioned first to thirteenth aspects is implemented.

Optionally, the processor is coupled to the memory through an interface.

A thirty-first aspect of an embodiment of the present application provides a communication system, where the communication system includes the communication device of the fifteenth aspect and the communication device of the sixteenth aspect; or, the communication device of the eighteenth aspect and the communication device of the twentieth aspect communication device.

Through the above technical solution, in the emergency registration request process or emergency service request process of the terminal device in the first network, the core network device of the first network rejects the emergency registration request or emergency service request of the terminal device. The access network device sends information to the terminal device for instructing the terminal device to redirect to the second network for emergency registration or emergency service, so as to provide the terminal device with emergency services and ensure normal communication services.

Description of drawings

FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the application;

2 is a schematic diagram of another network architecture according to an embodiment of the present application;

FIG. 3A is a schematic diagram of an embodiment of a communication method according to an embodiment of the present application;

FIG. 3B is a schematic diagram of another embodiment of the communication method of this embodiment;

FIG. 4 is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

FIG. 5 is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

FIG. 6 is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

FIG. 7 is a schematic diagram of another embodiment of a communication method according to an embodiment of the present application;

FIG. 8 is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

FIG. 9 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 10 is another schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 11 is another schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 12 is another schematic structural diagram of a communication device according to an embodiment of the present application;

13 is another schematic structural diagram of a terminal device according to an embodiment of the present application;

FIG. 14 is another schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 15 is a schematic diagram of a communication system according to an embodiment of the present application.

Detailed ways

Embodiments of the present application provide a communication method and related equipment, so as to provide emergency services for terminal equipment and ensure normal communication services.

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the protection scope of this application.

The term "and/or" that appears in this application can be an association relationship to describe associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in this application generally indicates that the related objects are an "or" relationship.

In this embodiment of the present application, the terminal equipment (terminal equipment) may also be referred to as user equipment (user equipment).

equipment, UE), mobile station (mobile station, MS), mobile terminal (mobile terminal), client (station, STA), etc. The terminal equipment can communicate with one or more core network, for example, the terminal device may be a mobile phone (or "cellular" phone), a computer with a mobile terminal, etc., for example, may be a portable, pocket-sized, hand-held, computer-built-in or vehicle-mounted mobile device , and 5G through the terminal equipment in the network or the terminal equipment in the future evolution network, etc.

In this embodiment of the present application, an access network device is a device that provides a wireless communication function for a terminal device, and may also be referred to as an access device, a (R)AN device, or a network device. For example, access devices include but are not limited to: next generation node base station (gNB) in 5G communication system, evolved node B (eNB) in LTE system, radio network controller (radio network controller) , RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved nodeB, or home node B, HNB), Base band unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), small base station equipment (pico), mobile switching center, or network equipment in future networks, etc. . This application does not limit the specific types of wireless access network equipment. In systems using different radio access technologies, the names of devices with radio access network device functions may be different.

In the embodiment of the present application, the core network device is a control plane network function provided by the network, and is responsible for access control, registration management, service management, and mobility management of terminal devices accessing the network. In the embodiment of the present application, the core network device may be an access and mobility management function (AMF) in a 5G communication system, or a core network device in a future network, or the like. This application does not limit the specific types of core network equipment. In different communication systems, the names of core network devices may be different.

IMS is a general multimedia service platform. The core network of the IMS access network can provide voice services, video services, or short message services for terminal equipment. The basic function of IMS is to support emergency (calling) services.

The NPN network is a network under discussion in the 3rd generation partnership project (3GPP) fifth generation wireless communication (5th generation, 5G) standard, which is different from the traditional cellular network (cellular network), NPN network Only certain users with specific permissions are allowed to access. The NPN network is divided into two networking modes: independent networking (standalone) and non-standalone networking (non-standalone). The embodiments of this application are applicable to an NPN network in any networking manner, which is not specifically limited in this application. The above network architectures shown in FIG. 1 and FIG. 2 take the NPN network in the independent networking mode as an example for introduction. In practical applications, the networking mode of the NPN network is not limited.

The PLMN network is a network established and operated by the government or its approved operators for the purpose of providing land mobile communication services to the public, mainly mobile network operators (mobile network operators, MNOs) to provide users with mobile broadband access services. public network. The PLMN described in this application may specifically be a network that meets the requirements of the 3rd generation partnership project (3GPP) standard, which is referred to as a 3GPP network for short. 3GPP networks usually include but are not limited to fifth-generation (5th-generation, 5G) networks (referred to as 5G networks), fourth-generation (4th-generation, 4G) networks (referred to as 4G networks), or future sixth-generation networks. Mobile communication network (referred to as 6G network), etc.

In this embodiment of the present application, the first network refers to a network corresponding to a cell where the terminal device is currently located. The first network may be an NPN network or a PLMN network.

In this embodiment of the present application, the third network is a network associated with the first network. The association between the first network and the third network includes: a non-3rd generation partnership project (3GPP) inter-network interworking function (non-3GPP) is used between the core network of the first network and the core network of the third network. interworking function, N3IWF) or other interface connections. For example, as shown in FIG. 2, the user plane function (UPF) 207 of the network A is connected to the N3IWF 208, the UPF 211 of the network B is connected to the N3IWF 208, and the UPF 211 is connected to the IMS 212, that is, the network B supports emergency services. In this way, network A can provide emergency services for terminal equipment of network A through network B. The third network is an NPN network or a PLMN network.

In this embodiment of the present application, the second network refers to other networks except the first network, or other networks except the first network and the third network. If the first network adopts the method of directly connecting the IMS through the core network of the first network to provide emergency services for the terminal equipment of the first network, then when the core network of the first network is not directly connected to the IMS, the first network cannot provide emergency services for the terminal equipment of the first network. The terminal equipment of the network provides emergency services, and the second network is a network other than the first network. If the first network directly connects to the IMS through the core network of the first network to provide emergency services for the terminal devices of the first network, and the first network can also connect to the core network of a third network supporting IMS through the core network of the first network To realize that the first network provides emergency services for terminal devices of the first network through a third network supporting IMS, and the core network of the first network is not directly connected to the IMS and the third network associated with the first network does not support emergency services, the third network The second network is a network other than the first network and the third network. Wherein, the second network is an NPN network or a PLMN network.

Regarding the problem of how to provide emergency services for terminal devices in the first network, the embodiment of the present application provides two possible network architectures, which are described below with reference to FIG. 1 and FIG. 2 respectively.

Please refer to FIG. 1 , which is a schematic diagram of a network architecture of a communication method according to an embodiment of the present application. In FIG. 1 , network A includes terminal equipment 101 , an access network of network A, and a core network of network A. The access network of the network A includes an access network device 102 (only one access network device is shown in FIG. 1 , in practical applications, the access network of the network A may include multiple access network devices). The core network of network A includes access and mobility management AMF103, unified data management UDM104, policy control management PCF105, session management function SMF106 and user plane function UPF107.

When the terminal device 101 accesses the network A, it first passes through the access network device 102 , and then connects with the network A and the core network through the access network device 102 .

The access and mobility management AMF103 is used for the control plane network function provided by the network A, and is responsible for the access control, registration management, service management, mobility management, etc. of the terminal equipment accessing the network. For example, including mobility status management, assigning user temporary identity, authentication, registration and other functions

Unified data management (UDM) 104 is a control plane function provided by the operator, responsible for storing subscriber permanent identifier (SUPI), security context (security context), subscription data of subscribers in network A and other information. The above-mentioned subscribers of network A may specifically be users using services provided by network A, for example, users using China Telecom's terminal equipment core cards, or users using China Mobile's terminal equipment core cards. Exemplarily, the SUPI of the subscriber may be the number of the core card of the terminal device, or the like. The above-mentioned security context may be data (cookie) or token (token) stored on a local terminal device (eg, mobile phone). The subscription data of the above-mentioned subscribers may be the supporting services of the terminal device chip card, such as the data package of the mobile phone chip card, and the like.

The policy control function (PCF) 105 is used to be a control plane function provided by the operator, and is used to provide the session management function SMF 106 with the policy of the protocol data unit (protocol data unit, PDU) session. The policies may include charging-related policies, QoS-related policies, authorization-related policies, and the like.

The session management function (session management function, SMF) 106 is used for the control plane network function provided by the network A, and is responsible for managing the protocol data unit (protocol data unit, PDU) session of the terminal device 101. A PDU session is a channel for transmitting PDUs, and terminal devices need to transmit PDUs to and from the data network through the PDU session. PDU sessions may be established, maintained, deleted, etc. by the SMF 106. SMF 106 is also used for session management (eg session establishment, modification and release, etc.), service and session continuity (service and session continuity, SSC) mode selection, and session-related functions such as roaming.

The user plane function UPF107 is a gateway provided by the operator, and is a gateway for the network A to communicate with the data network. UPF 107 includes user plane-related functions such as packet routing and transmission, packet detection, service usage reporting, quality of service (QoS) processing, legal interception, upstream packet detection, and downstream packet storage.

IMS108 is a general multimedia service platform. The core network of the IMS access network can provide voice services, video services, or short message services for terminal equipment. The basic function of IMS is to support emergency (calling) services. The UPF 107 is connected to the IMS 108 through the N6 interface, so that the network A provides the terminal device 101 with emergency services.

For the related introduction of the terminal device 101, please refer to the related introduction above, and details are not repeated here. For the related introduction of the access network device 102, please refer to the above-mentioned related, which will not be repeated here.

In Figure 1, N2, N3, N6, N7, N8, N10 and N11 are interface serial numbers. Exemplarily, for the meaning of the above-mentioned interface serial number, reference may be made to the meaning defined in the 3GPP standard protocol, and this application does not limit the meaning of the above-mentioned interface serial number. The interface names between various network functions in FIG. 1 are just an example. In specific implementation, the interface names of the system architecture may also be other names, which are not limited in this application.

In the above FIG. 1 , the network A is an NPN network or a PLMN network.

Please refer to FIG. 2 , which is a schematic diagram of another network architecture of the communication method according to an embodiment of the present application. In FIG. 2, the network A includes the access network of the network A and the core network of the network A. The access network of network A includes access network equipment 202 . The core network of network A includes AMF203, UDM204, PCF205, SMF206 and UPF207. The core network of network B includes AMF209, SMF208 and UPF211.

N3IWF208 is used to provide services for the establishment of IP connections between terminal equipment and the network.

For example, if the UPF 207 of the network A is connected to the N3IWF 208, the UPF 211 of the network B is connected to the N3IWF 208, and the UPF 211 of the network B is connected to the IMS 212, then the network B supports emergency services.

That is, after the terminal device 201 is connected to the network A, the UPF 207 of the network A is connected to the N3IWF208, and the terminal device 201 can be connected to the network B through the NI3WF208.

Specifically, after the terminal device 201 accesses the network A, the network A may send the IP address of the N3IWF208 to the terminal device 201, or preconfigure the IP address of the NI3WF208 in the terminal device. The terminal device 201 may initiate an IP connection establishment request to the N3IWF 208 through the UPF 207 of the network A through the IP address of the N3IWF 208 . The N3IWF 208 establishes an IP connection between the terminal device 201 and the network B, so that the terminal device 201 can perform registration and service access on the network B through the IP connection established between the terminal device 201 and the network B.

As can be seen from Figure 2, the core network (core net, CN) of network A and the core network supporting network B are connected through NI3WF208, so that network A and network B can communicate with user plane and control plane through N3IWF208. On the other hand, the UPF 211 of the network B is directly connected to the IMS 212, that is, the network B supports the emergency service, so that the network B provides the terminal equipment of the network A with the emergency service.

It should be noted that the network A can send the IP addresses of multiple N3IWFs to the terminal device 201 (if there are multiple networks associated with the network A, that is, the network A is connected to different networks through different N3IWFs), or preconfigured multiple IP addresses. Then, the terminal device 201 selects the corresponding N3IWF, and initiates an IP connection establishment request through the selected IP address of the N3IWF, so as to request the N3IWF selected by the terminal device 201 to be the N3IWF corresponding to the terminal device and the N3IWF selected by the terminal device 201. And the network associated with the first network establishes an IP connection. The above-mentioned FIG. 2 takes the network A sending or configuring the IP address of the N3IWF 208 to the terminal device 201 as an example for introduction.

The data network DN213 may also be called a packet data network (PDN), which is usually a network located outside the PLMN, such as a third-party network. Exemplarily, the network A can access multiple data networks 213, and multiple services can be deployed on the data network DN 213, so as to provide the terminal device 201 with services such as data and/or voice.

For example, the data network DN213 may be a private network of a smart factory, the sensor installed in the workshop of the smart factory may be the terminal device 201, and the control server of the sensor is deployed in the data network DN213, and the control server can provide services for the sensor. The sensor can communicate with the control server, obtain the instruction of the control server, and transmit the collected sensor data to the control server according to the instruction. For another example, the data network DN 213 can be an internal office network of a company, and the mobile phones or computers of employees of the company can be terminal devices 201, and the mobile phones or computers of employees can access information, data resources, etc. on the internal office network of the company. The terminal device 201 can establish a connection with the network A through an interface provided by the network A (eg, the N1 interface in FIG. 2 , etc.), and use the data and/or voice services provided by the network A. The terminal device 201 can also access the data network DN 213 through the network A, and use the operator services deployed on the data network DN 213 and/or the services provided by a third party. The above-mentioned third party may be a service party other than the network A and the terminal device 201 , and may provide other data and/or voice services for the terminal device 201 . Wherein, the specific expression form of the above third party can be specifically determined according to the actual application scenario, and is not limited here.

The terminal device 201 is similar to the terminal device 101 shown in FIG. 1 , the access network device 202 is similar to the access network device 102 shown in FIG. 2 , the AMF 203 and AMF 209 are similar to the AMF 103 shown in the foregoing FIG. 1 , and the UDM 204 is similar to the foregoing UDM104 shown in Figure 1 is similar, PCF205 is similar to PCF105 shown in Figure 1, SMF206, SMF208 are similar to SMF106 shown in Figure 1, UPF207 and UPF211 are similar to UPF107 shown in Figure 1, IMS212 is similar to Figure 1 The IMS 108 in the IMS 108 is similar. For details, please refer to the related introduction in FIG. 1 , which will not be repeated here.

As can be seen from the network architecture shown in FIG. 2 above, the core network of network A does not need to be directly connected to the IMS, which expands the ability of network A to provide emergency services, and makes network A more diverse in providing emergency services for terminal equipment. For example, network A can provide emergency services for terminal devices by directly connecting to the IMS through the core network of network A. Alternatively, network A can connect to network B supporting emergency services through N3IWF, and then establish terminal devices for terminal devices of network A through N3IWF. IP connection with network B, and then network B provides emergency services for terminal equipment.

In the network architecture shown in FIG. 2 above, the network A is an NPN network or a PLMN network, and the network B is an NPN network or a PLMN network. For the related introduction of the NPN network and the PLMN network, please refer to the related introduction above, and will not be repeated here.

It should be noted that the above-mentioned FIG. 1 and FIG. 2 are only two possible network architectures for the network A to provide emergency services for the terminal equipment of the network A. For network A, the core network of network A can be directly connected to the IMS, and at the same time, the core network of network A is also connected to the core network of network B supporting IMS through N3IWF or other interfaces. In this way, network A can provide emergency services to terminal devices of network A through the IMS directly connected to network A, and can also provide emergency services to terminal devices of network A through network B associated with network A.

In this embodiment of the present application, for a situation where the first network does not support emergency services, or for a situation where the first network does not support emergency services and a third network associated with the first network does not support emergency services, the embodiment of the present application provides FIG. 3A The technical solution of the illustrated embodiment is to facilitate the terminal device to perform emergency registration or emergency service through the second network, avoid the terminal device repeatedly requesting emergency registration or emergency service from the first network, and improve the success of the terminal device requesting emergency registration or emergency service. rate, improving user experience and communication system performance.

The situation that the first network does not support the emergency service includes: the core network of the first network is not directly connected to the IMS.

The situation where the first network does not support emergency services and the third network associated with the first network also does not support emergency services includes: the core network of the first network is not directly connected to the IMS, and cannot provide emergency services for terminal devices of the first network; and, The third network associated with the first network does not support emergency services, and the first network cannot provide emergency registration or emergency services for terminal devices of the first network through the third network.

Please refer to FIG. 3A , which is a schematic diagram of a communication method according to an embodiment of the present application. In Figure 3A, the communication method includes:

301. The terminal device sends an emergency registration request or an emergency service request to a core network device (eg, AMF) of the first network. Correspondingly, the core network device of the first network receives the emergency registration request or the emergency service request from the terminal device.

The emergency registration request is used for the terminal device to request emergency registration from the core network device of the first network.

The emergency service request is used by the terminal device to request the emergency service from the core network device of the first network.

Specifically, the terminal device sends an emergency registration request or an emergency service request to an access network device of the first network, and then the access network device sends an emergency registration request or an emergency service request to the core network device.

Optionally, the emergency registration request is an emergency registration message, or an emergency registration request included in other messages sent by the terminal device to the core network device. The emergency service request is an emergency service request message, or an emergency service request included in other messages sent by the terminal device to the core network device.

For example, the terminal device sends an emergency registration request message or an emergency service request message to the access network device through an uplink information transfer message, where the emergency registration request message is a NAS message, and the emergency service request message is a NAS message. Then, the access network device sends an emergency registration request message or an emergency service request message to the core network device through an uplink non-access stratum transport (uplink non-access stratum transport) message.

The technical solution in this embodiment can be applied to the network architecture of FIG. 1 and the network architecture of FIG. 2, but does not belong to a limitation on the network architecture applicable to this embodiment, and the technical solution of this embodiment is also applicable to other The method of instructing terminal equipment to perform emergency registration or emergency service under the network architecture.

For example, in the network architecture shown in FIG. 1, if the UPF 107 of the network A is not directly connected to the IMS 108, the network A does not support emergency services and cannot provide emergency services for the terminal equipment 102 of the network A, then after step 301, execute the steps 302 to step 304.

For example, in the network architecture shown in Figure 2, the UPF 207 of the network A is not directly connected to the IMS, so the network A does not support emergency services and cannot provide the terminal equipment 201 of the network A with emergency services. Moreover, if the UPF 211 of the network B associated with the network A is not directly connected to the IMS 212, that is, the network B does not support emergency services, then the network A cannot provide the terminal equipment 201 of the network A with emergency services through the network B, then after step 301, execute step 301 302 to step 304.

302. The core network device sends a rejection message to the terminal device. Correspondingly, the terminal device receives the rejection message from the core network device.

The rejection message is used to instruct the core network device to reject the emergency registration request or the emergency service request.

For example, the core network device verifies the emergency registration request or emergency service request of the terminal device (including determining whether the first network supports emergency services or whether the first network can provide emergency services); if the verification fails, the core network The device sends a rejection message to the terminal device through the access network device of the first network, so as to reject the provision of emergency services for the terminal device. Reasons for failing the verification include that the first network does not support the emergency service or the first network cannot provide the emergency service, for example, the emergency service cannot be provided due to a fault or a heavy current load.

For example, the core network device verifies the emergency registration request or emergency service request of the terminal device (including determining whether/whether the first network and the third network support emergency services, or whether the first network and the third network can provide emergency services or not service); if the verification fails, the core network device sends a rejection message to the terminal device through the access network device of the first network to refuse to provide the terminal device with an emergency service. The reasons for failing the verification include that neither the first network nor the third network supports emergency services, or that neither the first network nor the third network can provide emergency services. For example, emergency services cannot be provided due to failure or heavy current load.

For an emergency registration request of a terminal device, the rejection message is a registration reject message. For the urgent service request of the terminal device, the rejection message is a service reject message.

Specifically, the rejection message may be sent by the core network device to the access network device of the first network, and then the access network device may send the rejection message to the terminal device. For example, the core network device sends a reject message to the access network device of the first network through a downlink non-access stratum transport message, where the reject message is a NAS message. Then, the access network device sends a rejection message to the terminal device through a downlink information transfer message.

303. The access network device determines information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service.

The second network is a network other than the first network, or, the second network is a network other than the first network and the third network.

For example, if the core network of the first network is not directly connected to the IMS, that is, the first network does not support emergency services, the second network is a network other than the first network.

For example, the core network of the first network is not directly connected to the IMS, and cannot provide emergency services for the terminal equipment of the first network. The third network does not support emergency services, that is, the third network is not directly connected to the IMS, and the first network cannot provide emergency registration or emergency services for the terminal equipment of the first network through the third network. Three networks other than the network.

The redirection refers to replacing the terminal device with a network serving the terminal device, so that the terminal device can initiate a request of the terminal device through the network. The request of the terminal device includes an emergency registration request, an emergency service request, and the like.

There are various indication manners for the information used to instruct the terminal device to perform emergency registration or emergency service with the second network, and two possible implementation manners are shown below.

Indication mode 1: the information used to instruct the terminal device to perform emergency registration or emergency service with the second network includes instruction information used to instruct the terminal device to perform emergency registration or emergency service with the second network.

In the instruction mode 1, the access network device instructs the terminal device to perform emergency registration or emergency service with the second network by means of instruction information.

In order to facilitate emergency registration of the terminal device through the second network, the access network device may recommend one or more candidate second networks for the terminal device. Optionally, the information used to instruct the terminal device to perform emergency registration or emergency service with the second network further includes an identifier of the second network.

The identifiers of the second networks include identifiers of one or more second networks sent by the core network device to the access network device, or include identifiers of one or more second networks determined by the access network device.

Two selection manners for the access network device to select one or more second networks are shown below. The following selection manner is only an example, and does not limit the technical manner of the embodiments of the present application.

Selection mode 1: The access network device selects one or more second networks from preconfigured networks that support or may support emergency services.

Selection mode 2: The access network device selects one or more second networks from the identifiers of the second networks sent by the core network device. The core network device may send the identifier of the second network to the access network device in step 303a or step 303b in FIG. 3B, or send the identifier of the second network to the access network device through other messages.

Indication mode 2: the information used to instruct the terminal device to perform emergency registration or emergency service with the second network includes the identifier of the second network.

In the instruction mode 2, the access network device indirectly instructs the terminal device to perform emergency registration or emergency service with the second network through the identifier of the second network. For the identification of the second network and the manner in which the access network device determines the identification of the second network, please refer to the relevant introduction in the foregoing indication mode 1, and details are not repeated here.

It can be seen from the instruction mode 1 and the instruction mode 2 that the access network device instructs the terminal device to request emergency registration or emergency service from the second network through the information element in the information for instructing the terminal device to perform emergency registration or emergency service with the second network.

The following shows several possible ways for the access network device to determine the information for instructing the terminal device to redirect to the second network for emergency registration or emergency service with reference to FIG. 3B . It should be noted that the following examples do not limit the way of determining the access network device. In this embodiment of the present application, the access network device determines the method used to instruct the terminal device to redirect to the second network for emergency registration or emergency service. The manner in which the information is determined is not limited.

Determination method 1: The access network device receives a message from the core network device for instructing the access device to release the connection of the terminal device, then the access network device determines the message used to instruct the terminal device to redirect to the second network for emergency registration or emergency business information.

In the determination method 1, optionally, as shown in FIG. 3B , this embodiment further includes step 303 a , and step 303 a is performed before step 303 .

Step 303a: The core network device sends a message for instructing the access network device to release the connection of the terminal device to the access network device. Correspondingly, the access network device receives a message from the core network device for instructing the access device to release the connection of the terminal device.

Specifically, the message used to instruct the access network device to release the connection of the terminal device is a message used to instruct the access network device to release the connection of the terminal device on the NG interface.

Optionally, the message used to indicate the connection of the terminal device released by the access network device is a UE context release command (UE context release command) message.

It should be noted that the core network device may send the rejection message in step 302 in FIG. 3A and the rejection message in step 302a in determination method 1 in FIG. 3B to the access network device through the same message or different messages to indicate the access network device A message to release the connection of the terminal device.

For example, the core network device sends the rejection message of step 302 in FIG. 3A to the access network device through downlink transmission of the non-access stratum message, and sends the above-mentioned determination method 1 in FIG. 3B to the access network device through the UE context release command message to the access network device. The message in step 302a is used to instruct the access network device to release the connection of the terminal device.

Then, after the access network device receives the message for instructing the access device to release the connection of the terminal device, the access network device may determine that the core network device rejects the emergency registration request or emergency service request of the terminal device. Therefore, the access network device may perform step 303 in the determination method 1 in FIG. 3B .

Determination mode 2: The access network device receives information from the core network device for instructing the access network device to redirect the terminal device to the second network to request emergency registration or emergency service. Then, the access network device determines, according to the information for instructing the access network device to redirect the terminal device to the second network to request emergency registration or emergency service, information for instructing the terminal device to redirect to the second network to perform emergency registration or emergency service .

Optionally, as shown in FIG. 3B , this embodiment further includes step 303 b , and step 303 b is performed before step 303 .

Step 303b: The core network device sends information to the access network device for instructing the access network device to redirect the terminal device to the second network to request emergency registration or emergency service. Correspondingly, the access network device receives information from the core network device for instructing the access network device to redirect the terminal device to the second network to request emergency registration or emergency service.

There are various indication manners for the information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service, and two possible indication manners are shown below.

Indication mode 1: The information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service includes the information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service. business instructions.

In the indication mode 1, the core network device instructs the access network device to redirect the terminal device to the second network for emergency registration or emergency service by means of indication information.

Optionally, the core network device may recommend one or more second networks for the access network device, so that the access network device selects candidate second networks from the one or more second networks, and sends the candidate second network to the terminal device. The identifier of the second network is convenient for the terminal device to register or perform emergency services through the second network. Optionally, the information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service further includes an identifier of the second network.

The identifier of the second network is the identifier of the NPN network or the identifier of the PLMN network. For example, SNPN ID or PLMN ID. The identification of the second network includes the identification of one or more second networks.

In an implementation manner, the access network device instructs the terminal device to redirect to the second network for emergency registration or emergency service through the indication information, and feeds back one or more identifiers of the second network to the access network device, so as to facilitate the access network The device selects the identifier of the candidate second network for the terminal device, and sends the identifier of the candidate second network to the terminal device.

Indication mode 2: the information used to instruct the access network device to redirect the terminal device to the second network for emergency registration or emergency service includes the identifier of the second network.

For the identifier of the second network, please refer to the foregoing related introduction, which will not be repeated here.

In the instruction mode 2, the core network device indirectly instructs the access network device to redirect the terminal device to the second network for emergency registration or emergency service through the identifier of the second network. Further, the access network device selects the identifiers of the candidate second networks from the identifiers of one or more second networks sent by the core network device, and sends the identifiers of the candidate second networks to the terminal device.

It can be seen from the instruction mode 1 and the instruction mode 2 that the core network device can instruct the access network device to use the information element in the information for instructing the access network device to redirect the terminal device to the second network for emergency registration or emergency service. The device is redirected to the second network for emergency registration or emergency service.

The above step 303 specifically includes:

The access network device determines information for instructing the terminal device to redirect to the second network for emergency registration or emergency service according to the information for instructing the access network device to redirect the terminal device to the second network to request emergency registration or emergency service.

Optionally, this embodiment further includes step 303 a , and step 303 a is performed before step 303 .

Step 303a: The core network device sends a message for instructing the access network device to release the connection of the terminal device to the access network device. Correspondingly, the access network device receives a message from the core network device for instructing the access network device to release the connection of the terminal device.

After the access network device receives the message for instructing the access device to release the connection of the terminal device, the access network device may determine that the core network device rejects the emergency registration request or emergency service request of the terminal device. The access network device may determine the information used in step 303b for instructing the access network device to redirect the terminal device to the second network to request emergency registration or emergency service to instruct the terminal device to redirect to the second network for emergency registration or emergency service. business information.

For the related introduction of the message used to instruct the access network device to release the connection of the terminal device, please refer to the related introduction in the foregoing determination method 1, and details are not repeated here.

It should be noted that, in the determination method 2, there is no fixed execution order between step 303a and step 303b, and step 303a can be executed first, and then step 303b; or, step 303b is executed first, and then step 303a is executed; or, according to In this case, step 303a and step 303b are performed at the same time, which is not specifically limited in this application.

In addition, the core network device may send the rejection message in step 302 in FIG. 3A and the rejection message in step 303a in determination method 2 of FIG. 3B to the access network device through the same message or different messages to instruct the access network device to release the terminal The device connection message and the information in step 303b in the determination method 2 of FIG. 3B used to instruct the access network device to redirect the terminal device to the second network to request emergency registration or emergency service.

For example, the core network device sends a reject message to the access network device through downlink transmission of the non-access stratum message, and sends the access network device through the UE context release command message to the access network device in step 303a in the determination method 2 of FIG. The message of the network access device releasing the connection of the terminal device and the information in step 303b in the determination method 2 of FIG. 3B used to instruct the access network device to redirect the terminal device to the second network to request emergency registration or emergency service.

304. The access network device sends, to the terminal device, information for instructing the terminal device to redirect to the second network for emergency registration or emergency service. Correspondingly, the terminal device receives information from the access network device for instructing the terminal device to redirect to the second network for emergency registration or emergency service.

For a related introduction of the information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service, please refer to the related introduction of step 303 in FIG. 3A , which is not repeated here.

Optionally, the access network device sends an RRC release message to the terminal device, where the RRC release message includes information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service.

In this embodiment, the access network device sends the rejection message in step 302 in FIG. 3A and the rejection message in step 304 in FIG. 3A to the terminal device through the same message or different messages, which are used to instruct the terminal device to send an emergency to the second network. Information for registration or emergency business.

For example, the access network device sends a reject message to the terminal device through a downlink information transmission message, and sends information for instructing the terminal device to perform emergency registration or emergency service with the second network to the terminal device through an RRC release message.

In this embodiment of the present application, the terminal device sends an emergency registration request or an emergency service request to the core network device of the first network. Then, the core network device verifies the emergency registration request or the emergency service request, and if the verification fails, the core network device sends a rejection message to the terminal device. Then, the access network device determines information for instructing the terminal device to redirect to the second network for emergency registration or emergency service, and sends to the terminal device information for instructing the terminal device to redirect to the second network for emergency registration or emergency service information, so that the terminal device can perform emergency registration or emergency services through the second network, and ensure normal communication services.

In this embodiment of the present application, after the terminal device receives the information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service in step 304 of the above-mentioned embodiment shown in FIG. The network requests urgent registration or urgent business. Optionally, the embodiment shown in FIG. 3A further includes step 305 , and step 305 is executed after step 304 .

305. The terminal device requests an emergency registration or emergency service from the second network.

The terminal device determines according to the information used to instruct the terminal device to request emergency registration or emergency services from the second network: the first network does not support emergency services or cannot provide emergency services, or, neither the first network nor the third network supports emergency services or Emergency services cannot be provided. Then, the terminal device selects the second network and requests the core network device of the second network for emergency registration or emergency service.

Two possible determination manners for the terminal device to select the second network are shown below, and the following determination manner is only an example, and does not limit the technical manner of the embodiments of the present application.

Option 1: The information used to instruct the terminal device to request emergency registration or emergency service from the second network includes the identifier of the second network. The terminal device determines the second network from the identification of the second network.

Option 2: The terminal device determines the second network from preconfigured networks that support or may support emergency services.

It should be noted that, for the situation that the first network supports emergency services and the third network supports emergency services, or, for the situation that the first network does not support emergency services and the third network supports emergency services, the terminal equipment, access network equipment and For the execution flow between core network devices, reference may be made to the related introduction of the embodiment shown in FIG. 5 , which is not repeated here.

The embodiment of the present application also provides another embodiment. The technical solution of the embodiment is similar to the technical solution of the embodiment shown in FIG. 3A , and the differences are:

Step 303 is not executed, and step 304 is replaced with: the core network device sends information to the terminal device for instructing the terminal device to redirect to the second network for emergency registration or emergency service. Correspondingly, the terminal device receives information from the core network device for instructing the terminal device to redirect to the second network for emergency registration or emergency service.

Wherein, the indication mode of the information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service is the same as that generated by the access network device in step 303 in FIG. 3A and used to instruct the terminal device to redirect to the second network. The manner of indicating the information for emergency registration or emergency service is similar. For details, please refer to the related introduction in step 303 in FIG. 3A , which will not be repeated here.

For the situation that the first network supports emergency services and the third network also supports emergency services, or, for the situation that the first network does not support emergency services and the third network supports emergency services, in this embodiment of the present application, the terminal device sends the first network The core network device sends a registration request, and the registration request is used for the terminal device to request to register in the first network; then, the core network device sends a registration acceptance to the terminal device, and the registration acceptance includes information used to instruct the terminal device to urgently register through the third network, The third network is a network associated with the first network. In this way, the terminal device can register urgently through the third network, so that the first network can provide emergency services for the terminal device of the first network through the third network.

It can be known from the above solution that the terminal device can obtain the core network device of the first network during the registration process of the terminal device (for example, the emergency registration process of the terminal device in the first network) as an emergency registration method for determining the emergency service for the terminal device. In practical applications, the terminal device in this embodiment of the present application may also acquire an emergency registration method for the emergency service of the terminal device in other processes, which is not specifically limited in this application. For example, the terminal device may acquire the emergency registration method for the emergency service of the terminal device during the service request process of the terminal device in the first network (eg, the emergency service request process of the terminal device in the first network). The following description is given by taking an example of an emergency registration manner in which the terminal device acquires the core network device of the first network during the emergency registration process of the terminal device in the first network to determine the emergency service for the terminal device.

The following describes the technical solutions of the embodiments of the present application with reference to FIG. 4 and FIG. 5 respectively.

In the embodiment shown in FIG. 4 , the terminal device determines that the third network supports emergency services, and requests the core network device of the first network for emergency registration through the third network during the emergency registration process of the terminal device in the first network. Then, the terminal device receives the registration acceptance from the core network device, and determines the emergency registration through the third network according to the information included in the registration acceptance and used to instruct the terminal device to urgently register through the third network. For details, please refer to the related introduction in the embodiment shown in FIG. 4 later.

In the embodiment shown in FIG. 5 , the terminal device determines that at least one network in the first network and the third network supports emergency services, and requests the core network device of the first network to pass the emergency service during the emergency registration process of the first network. After a network emergency registration, the terminal device receives the registration acceptance from the core network device, and determines the emergency registration through the third network by the information included in the registration acceptance for instructing the terminal device to urgently register through the third network. For details, please refer to the related introduction in the embodiment shown in FIG. 5 later.

The embodiments shown in FIG. 4 and FIG. 5 are applicable to the network architecture shown in the aforementioned FIG. 2 , but are not a limitation of the network architecture to which this embodiment applies. The technical solutions of this embodiment are also applicable to the network architecture of other networks. The method instructing the terminal device to perform emergency registration or emergency service under the framework.

Please refer to FIG. 4 , which is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application. In Figure 4, the communication method includes:

401. The terminal device sends a registration request to a core network device (for example, AMF) of the first network. Correspondingly, the core network device of the first network receives the registration request from the terminal device.

The registration request is used for the terminal device to request emergency registration in the first network.

In this embodiment, the registration request includes information used to instruct the terminal device to request emergency registration through the third network.

Optionally, the information used to instruct the terminal device to request emergency registration through the third network includes the first registration type. The first registration type includes emergency registration through a third network.

The first registration type is used to indicate that the terminal device requests emergency registration through the third network.

In this embodiment, for the emergency service of the terminal device, the registration type of the terminal device includes two registration types, namely, emergency registration through the first network and emergency registration through the third network. In step 401, the terminal device requests the core network device of the first network to perform emergency registration through the third network through a registration request.

For example, the third network is a PLMN network, and the information used to instruct the terminal device to request emergency registration through the third network includes a first registration type: PLMN emergency registration (emergency registration via PLMN).

Specifically, the first registration type is an information element in the information used to instruct the terminal device to request emergency registration through the third network. That is, the terminal device instructs the terminal device to request emergency registration through the third network through an information element in the information for instructing the terminal device to request emergency registration through the third network.

In this embodiment, optionally, the information used to instruct the terminal device to request emergency registration through the third network includes instruction information used to instruct the terminal device to request emergency registration through the third network. That is, the terminal device instructs the terminal device to request emergency registration through the third network by means of indication information.

Then, the indication information used to instruct the terminal device to request emergency registration through the third network includes the first registration type; or, the indication information used to instruct the terminal device to request emergency registration through the third network is the first registration type, that is, the first registration type The type is a specific form of indication information used to instruct the terminal device to request emergency registration through the third network, that is, a registration type field. In practical applications, the indication information used to instruct the terminal device to request emergency registration through the third network may also be other types of fields, so as to instruct the terminal device to request emergency registration through the third network.

Specifically, in the above-mentioned network architecture shown in FIG. 2 , the access network device sends the information used to indicate whether or not the third network supports emergency services to the terminal device through any one of broadcast, unicast and multicast. , or, preconfigure the information that the third network supports emergency services on the terminal device. The terminal device determines that the third network supports emergency services. Therefore, the terminal device sends a registration request to the access network device of the first network, and then the access network device sends a registration request to the core network device of the first network to request the core network device for emergency registration of the terminal device through the third network. Emergency registration method.

In this embodiment, the registration request is a registration request (registration request) message of the terminal device; or, it is a registration request carried by the terminal device in other messages sent to the core network device.

For example, the terminal device sends a registration request message to the access network device of the first network through an RRC setup complete (RRC setup complete) message, where the registration request message is a NAS message. Then, the access network device sends a registration request message to the core network device of the first network through the initial UE message, that is, the initial UE message includes the registration request message.

402. The core network device sends a registration accept (registration accept) to the terminal device. Correspondingly, the terminal device receives the registration acceptance from the core network device.

Wherein, the registration acceptance includes information used to instruct the terminal device to register urgently through the third network.

Specifically, after the core network device receives the registration request sent by the terminal device in the above step 401, the core network device performs access control on the terminal device. If the terminal device is allowed to access the first network, the core network device sends a registration acceptance to the terminal device. . And, the registration acceptance includes information for instructing the terminal device to urgently register through the third network, so as to instruct the terminal device to urgently register through the third network. Then, the terminal device receives the registration acceptance of the core network device, and the terminal device performs RRC reconfiguration to complete the emergency registration of the terminal device in the first network.

Optionally, the indication manner of the information for instructing the terminal device to urgently register through the third network includes the first registration type. For the relevant introduction of the first registration type, please refer to the relevant introduction in the foregoing step 401, which will not be repeated here.

In this embodiment, optionally, the information used to instruct the terminal device to urgently register through the third network includes instruction information used to instruct the terminal device to urgently register through the third network. That is, the terminal device instructs the terminal device to register urgently through the third network by means of indication information.

Then, the indication information used to instruct the terminal device to urgently register through the third network includes the first registration type; or, the indication information used to instruct the terminal device to urgently register through the third network is the first registration type, that is, the first registration type can be It is understood as a specific form of the indication information used to instruct the terminal device to register urgently through the third network, that is, the registration type field. In practical applications, the indication information used to instruct the terminal device to urgently register through the third network may also use other types of fields to instruct the terminal device to urgently register through the third network.

In this embodiment, the core network device may also select a candidate third network for the terminal device, so that the terminal device can register urgently through the third network. Optionally, the information used to instruct the terminal device to urgently register through the third network further includes an identifier of the third network.

The third network is a third network selected by the core network device from the networks associated with the first network, and the third network supports emergency services.

The identification of the third network includes the identification of one or more third networks. For example, the identification of the third network is an NPN ID, or a PLMN ID.

Specifically, the core network device may select one or more third networks from the networks associated with the first network, and carry it in the information for instructing the terminal device to urgently register through the third network.

In this embodiment, the core network device first sends a registration acceptance to the access network device of the first network, and then the access network device forwards the registration acceptance to the core network device.

Optionally, the registration acceptance is a registration acceptance (registration accept) message of the terminal device, or is a registration acceptance carried by the terminal device in other messages sent to the core network device.

For example, the core network device sends a registration accept message to the access network device of the first network through an initial context setup request (initial context setup request) message, that is, the initial context setup request message includes the registration accept message. In an implementation, the registration accept message is a NAS message. Then, the access network device sends a registration acceptance message to the terminal device through an RRC reconfiguration (RRC reconfiguration) message. The access network device sends an RRC reconfiguration complete (RRC reconfiguration complete) message to the terminal device, and then the access network device sends an initial context setup response (initial context setupresponse) message to the core network device, thereby completing the terminal device in the first network. Emergency registration.

In the embodiment of the present application, the terminal device sends a registration request to the core network device of the first network, and the registration request includes information used to instruct the terminal device to request emergency registration through the third network; then, the core network device sends a registration acceptance to the terminal device, The registration acceptance includes information for instructing the terminal device to urgently register through the third network. In this way, the terminal device can perform emergency registration or emergency services through the third network, so that the first network can provide emergency services for the terminal device through the second network. Compared with the existing way of directly connecting the IMS through the core network of the first network, so that the network can provide the terminal equipment with the IMS emergency service service, the technical solutions of the embodiments of the present application provide the terminal equipment of the first network with the emergency service. methods are more diverse. Moreover, when the core network device of the first network is not directly connected to the IMS, the problem that the first network cannot provide the terminal device with the IMS emergency service service is solved. That is, the first network can provide the terminal device with the emergency service through the third network that supports the emergency service.

In this embodiment of the present application, in step 402 of the above-mentioned embodiment shown in FIG. 4 , after the terminal device receives the information for instructing the terminal device to register urgently through the third network, the terminal device may request the third network for emergency registration or urgent business. Optionally, the above embodiment shown in FIG. 4 further includes step 403 , and step 403 is executed after step 402 .

403. The terminal device requests an emergency registration or emergency service from a third network.

Specifically, the terminal device determines to register urgently through the third network according to the information used to instruct the terminal device to register urgently through the third network; then, the terminal device selects the third network, and requests the third network for urgent registration or emergency service through the N3IWF. For specific IP connection establishment included in the process of requesting emergency registration or emergency service by the terminal device from the core network device of the third network through the N3IWF, please refer to the related introduction in FIG.

The terminal device may select the third network through the identifier of the third network included in the information for instructing the terminal device to urgently register with the third network; or, the terminal device may select the third network through a preconfigured network that supports or may support emergency services.

In this embodiment of the present application, in order to enable the access network device of the first network to preconfigure the terminal device with emergency session resources for the terminal device to perform emergency services or emergency registration through the third network, the above-mentioned embodiment shown in FIG. 4 further includes step 404 and step 405, and steps 404 and 405 are performed after step 403.

404. The terminal device sends an RRC setup request (RRC setup request) to the access network device of the first network. Correspondingly, the access network device of the first network receives the RRC establishment request from the terminal device.

Wherein, the RRC establishment request includes information used to instruct the terminal device to request to provide emergency services for the terminal device through the third network.

Specifically, the terminal device indicates to the access network device through the RRC establishment request that the terminal device requests to provide emergency services for the terminal device through the third network. Then, the access network device determines according to the RRC establishment request that the terminal device requests emergency registration through the third network or requests to provide emergency services through the third network. The access network device configures the terminal device with emergency session resources for emergency registration or emergency service between the terminal device and the third network. Secondly, the RRC establishment request is used by the terminal equipment to request to establish an RRC connection with the access network equipment.

In this embodiment, the information element in the information for instructing the terminal device to request to provide the terminal device with an emergency service through the third network instructs the terminal device to request to provide the terminal device with an emergency service through the third network.

Optionally, the information used to instruct the terminal device to request to provide emergency services for the terminal device through the third network includes a cause value, where the cause value includes: the terminal device requests to provide emergency services to the terminal device through the third network.

Specifically, the reason value may be an RRC establishment reason, and the terminal device instructs the terminal device to request an emergency service for the terminal device through the third network through the RRC establishment reason. For example, the third network is a PLMN network, and the reason value is that the terminal equipment requests to perform emergency services through the PLMN network.

Optionally, the information used to instruct the terminal device to request to provide the terminal device with an emergency service through the third network includes indication information used to instruct the terminal device to request to provide the terminal device with an emergency service through the third network. That is, the terminal device instructs the terminal device to request to provide emergency services for the terminal device through the third network by means of indication information.

Then, the indication information for instructing the terminal equipment to request to provide emergency services for the terminal equipment through the third network includes a cause value, or the indication information for instructing the terminal equipment to request to provide emergency services for the terminal equipment through the third network is the reason value. That is, the cause value can be understood as a specific form of indication information used to instruct the terminal device to request to provide emergency services for the terminal device through the third network, that is, the cause value field. In practical applications, the indication information used to instruct the terminal device to request to provide emergency services to the terminal device through the third network may also use other types of fields to indicate that the terminal device requests to provide emergency services to the terminal device through the third network.

In this embodiment, the RRC establishment request is an RRC establishment request message of the terminal device; or, it is an RRC establishment request carried in other messages sent by the terminal device to the access network device, which is not specifically limited in this application. For example, the terminal device sends an RRC establishment request message to the access network device, where the RRC establishment request message includes information used to instruct the terminal device to request to provide emergency services for the terminal device through the third network.

405. The access network device sends an RRC setup (RRC setup) to the terminal device. Correspondingly, the terminal device receives the RRC establishment from the access network device.

The RRC establishment is used to instruct the terminal device to establish an RRC connection with the access network device.

In this embodiment, the RRC establishment is an RRC establishment message, or is an RRC establishment carried in other messages sent by the access network device to the terminal device, which is not specifically limited in this application.

It should be noted that, in this embodiment, there is no obvious execution sequence between steps 404 to 405 and steps 401 to 402 . Steps 404 to 405 may be performed first, or steps 401 to 402 may be performed first, or steps 404 to 405 and steps 401 to 402 may be performed simultaneously depending on the situation, which is not specifically limited in this application.

If steps 404 to 405 are executed before steps 401 to 402, steps 404 to 405 can be understood as an RRC establishment request executed by the terminal device before the registration process of steps 401 to 402.

In this embodiment of the present application, the access network device of the first network may send information for indicating that the third network supports the emergency service to the terminal device, so as to notify the terminal device that the third network supports the emergency service. Optionally, the above-mentioned embodiment shown in FIG. 4 further includes step 406 , and step 406 is performed before steps 401 to 403 .

406. The access network device sends information for indicating that the third network supports the emergency service to the terminal device. Correspondingly, the terminal device receives information from the terminal device indicating that the third network supports the emergency service.

For example, as shown in FIG. 2 , the third network is network B, and the core network of network B and the core network of network A are connected through the N3IWF. The UPF 211 of the network B is directly connected to the IMS 212, so the network B supports emergency services. Then, the access network device 202 in the network A can send the information for indicating that the network B supports the emergency service to the terminal device 201 in the network A.

In this embodiment, optionally, the information used to instruct the third network to support the emergency service includes indication information used to instruct the third network to support the emergency service.

For example, when the indication information for indicating that the third network supports the emergency service is expressed as any of the following: "Yes", "true", or "1", it indicates that the third network supports the emergency service. Then, the terminal device may determine that the third network supports the emergency service by using the indication information for indicating that the third network supports the emergency service.

It should be noted that there is no fixed execution order between step 406 and step 404 to step 405. Step 406 may be executed first, or step 404 to step 406 may be executed first, or, according to the situation, step 404 to step 405 and step 405 may be executed at the same time. 406.

In this embodiment, the access network device sends the information for indicating that the third network supports the emergency service in any form of broadcast, unicast and multicast.

In a possible implementation manner, the information used to indicate that the third network supports the emergency service is system information of the access network device used to indicate that the third network supports the emergency service.

Specifically, the access network device may send the information for indicating that the third network supports the emergency service through the system information of the access network device in the cell corresponding to the first network.

In this embodiment of the present application, the access network device may notify the terminal device whether or not the first network supports emergency services. Optionally, the embodiment shown in FIG. 4 further includes step 407 .

407. The access network device sends the information used to indicate whether the first network supports the emergency service to the terminal device. Correspondingly, the terminal device receives information from the access network device indicating whether or not the first network supports the emergency service.

For example, as shown in FIG. 2 , the first network is network A, and the core network of network A is not directly connected to the IMS, so network A does not support emergency services. Then, the access network device can send the information for indicating that the network A does not support the emergency service to the terminal device.

In this embodiment, optionally, the information used to indicate whether or not the first network supports the emergency service includes indication information used to indicate whether the first network supports the emergency service.

The following describes the indication information used to indicate whether or not the first network supports emergency services with reference to specific examples.

For example, when the indication information used to indicate whether or not the first network supports emergency services is "yes" or "true", it means that the first network supports emergency services; it is used to indicate whether or not the first network supports emergency services When the indication information is "null", it means that the first network does not support emergency services.

For example, when the indication information used to indicate whether or not the first network supports emergency services is "yes" or "true", it means that the first network supports emergency services; it is used to indicate whether or not the first network supports emergency services When the indication information is "no (false)", it means that the first network does not support emergency services.

For example, when the indication information for indicating whether or not the first network supports emergency services is "1", it means that the first network supports emergency services; the indication information for indicating whether or not the first network supports emergency services is "0" , it indicates that the first network does not support emergency services.

The above shows possible forms and corresponding meanings of the indication information for indicating whether or not the first network supports emergency services. In practical applications, the indication information used to indicate whether or not the first network supports emergency services may also have other representations, which are not specifically limited in this application.

In this embodiment, the access network device sends the information for indicating that the first network supports the emergency service to the terminal device through any one of broadcast, unicast and multicast. In a possible implementation manner, the information used to indicate that the first network supports the emergency service is system information sent by the access network device and used to indicate whether or not the first network supports the emergency service.

Specifically, the access network device may send information for indicating whether or not the first network supports the emergency service through the system information of the access network device in the cell corresponding to the first network.

The access network device may send the information in the above step 406 for indicating that the third network supports the emergency service and the information in the above step 407 for indicating whether/whether the first network supports the emergency service to the terminal device through the same system information or different system information. information.

In this embodiment, steps 406 and 407 are processes in which the access network device indicates to the terminal device whether or not the first network and the third network support emergency services, and the access network device indicates to the terminal device whether the first network and the third network support emergency services. For more details on whether the network supports emergency services, please refer to the embodiment shown in FIG. 7 later.

It should be noted that there is no obvious execution order for step 407 and steps 401 to 406. Step 407 may be executed first, or steps 401 to 406 may be executed first, or steps 401 to 406 and 407 may be executed simultaneously according to the situation. This application is not limited.

Steps 401 and 402 in the above-mentioned embodiment shown in FIG. 4 are described by taking as an example that the core network device determines that the terminal device urgently registers through the third network. If the first network also supports emergency services, that is, the core network of the first network is directly connected to the IMS. Then, in a possible implementation manner, the registration request sent by the terminal device in step 401 may also include information used to instruct the terminal device to request emergency registration through the first network. Then, in step 402, the core network device may instruct the terminal device to urgently register through the first network through the registration acceptance, or the core network device may instruct the terminal device to urgently register through the third network through the registration acceptance.

Secondly, if the first network supports emergency services and the second network does not support emergency services, in the above step 401, the terminal device may request for emergency registration through the first network. In step 402, the core network device may send information to the terminal device for instructing the terminal device to register urgently through the first network, so that the terminal device requests emergency registration or emergency service through the first network.

Please refer to FIG. 5 , which is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application. In Figure 5, the communication method includes:

501. The terminal device sends a registration request to a core network device (for example, AMF) of the first network. Correspondingly, the core network device of the first network receives the registration request from the terminal device.

In this embodiment, the registration request includes information used to instruct the terminal device to request emergency registration through the first network.

Optionally, the information used to instruct the terminal device to request emergency registration through the first network includes a second registration type, and the second registration type includes emergency registration through the first network.

In this embodiment, for the emergency service of the terminal device, the registration type of the terminal device includes two registration types, namely, emergency registration through the first network and emergency registration through the third network. The third network is a network associated with the first network. In step 501, the terminal device requests the core network device of the first network to perform emergency registration through the first network.

For example, the first network is an NPN network, and the information used to instruct the terminal device to request emergency registration through the first network includes a second registration type: emergency registration (emergency registration).

Specifically, the above-mentioned second registration type is an information element in the information used to instruct the terminal device to request emergency registration with the first network. That is, the terminal device instructs the terminal device to request emergency registration through the first network through the information element used to instruct the terminal device to request emergency registration with the first network.

In this embodiment, optionally, the information used to instruct the terminal device to request emergency registration with the first network includes instruction information used to instruct the terminal device to request emergency registration through the first network. That is, the terminal device instructs the terminal device to request emergency registration through the first network by means of indication information.

Then, the indication information used to instruct the terminal device to request emergency registration through the first network includes the second registration type; or, the indication information used to instruct the terminal device to request emergency registration through the first network is the second registration type, that is, the second registration type The type is a specific form of indication information used to instruct the terminal device to request emergency registration through the first network, that is, a registration type field. In practical applications, the indication information used to instruct the terminal device to request emergency registration through the first network may also be other types of fields, so as to instruct the terminal device to request emergency registration through the first network.

Specifically, in the above-mentioned network architecture shown in FIG. 2 , the access network device sends information to the terminal device through any one of broadcast, unicast and multicast to indicate that there is at least one of the first network and the third network. The network supports urgent business information. Then, the terminal device can determine that at least one of the first network and the third network supports emergency services. Therefore, the terminal device sends a registration request to the core network device of the first network through the access network device of the first network, so as to request the core network device of the first network for an emergency registration method of emergency registration of the terminal device through the first network.

In this embodiment, the specific form of the registration request is similar to the specific form of the registration request in step 401 in the embodiment shown in FIG. 4 . For details, please refer to the relevant introduction of step 401 in the embodiment shown in FIG. 4 . Repeat. The process of sending the registration request by the terminal device to the core network device through the access network device is similar to the process of sending the registration request by the terminal device to the core network device through the access network device in step 401 in the aforementioned embodiment shown in FIG. 4 . For details, please refer to The related introduction of step 401 in the embodiment shown in the foregoing FIG. 4 will not be repeated here.

502. The core network device sends a registration accept (registration accept) to the terminal device. Correspondingly, the terminal device receives the registration acceptance from the core network device.

Specifically, after the core network device receives the registration request sent by the terminal device in step 501, the core network device performs access control on the terminal device. If the terminal device is allowed to access the first network, the core network device sends a registration request to the terminal device. accept. And, if the core network device determines that the third network supports the emergency service, the registration acceptance includes information for instructing the terminal device to register urgently through the third network. Then, the terminal device receives the registration acceptance of the core network device, and the terminal device performs RRC reconfiguration to complete the emergency registration of the terminal device in the first network.

Optionally, the information used to instruct the terminal device to register urgently through the third network includes a first registration type, and the first registration type is used to instruct the terminal device to request urgent registration through the third network.

Specifically, the first registration type is an information element in the information for the terminal device to urgently register through the third network, that is, the terminal device instructs the terminal device to request through the information element in the information for instructing the terminal device to urgently register through the third network Emergency registration through the third network.

Then, the indication information used to instruct the terminal device to urgently register through the third network includes the first registration type; or, the indication information used to instruct the terminal device to urgently register through the third network is the first registration type, that is, the first registration type is A specific form of the indication information used to instruct the terminal device to request emergency registration through the third network, that is, the registration type field. In practical applications, the indication information used to instruct the terminal device to urgently register through the third network may also be other types of fields, so as to instruct the terminal device to urgently register through the third network.

In this embodiment, the core network device may also select a candidate third network for the terminal device, so that the terminal device can register urgently through the third network. Optionally, the information used to instruct the terminal device to pass through the third network urgently further includes the identifier of the third network.

For the specific introduction of the identifier of the third network, please refer to the related introduction of step 402 in the embodiment shown in FIG. 4 , which will not be repeated here.

In this embodiment, the specific form of registration acceptance is similar to the specific form of registration acceptance in step 402 in the foregoing embodiment shown in FIG. 4 . For details, please refer to the relevant introduction of step 402 in the foregoing embodiment shown in FIG. 4 . I won't go into details here. The process for the core network device to send the registration acceptance to the terminal device is similar to the process for the core network device to send the registration acceptance to the terminal device in step 402 in the embodiment shown in FIG. 4. For details, please refer to the embodiment shown in FIG. 4. The related introduction of step 402 will not be repeated here. The process of the terminal equipment RRC reconfiguration to complete the registration in the first network is similar to the process of the terminal equipment RRC reconfiguration to complete the registration in the first network in step 402 in the aforementioned embodiment shown in FIG. 4 , please refer to FIG. The related introduction of step 402 in the embodiment shown in 4 will not be repeated here.

In this embodiment, the core network device may notify the access network device that the terminal device determined by the core network device is an emergency registration method of emergency registration through the third network. Optionally, the embodiment shown in FIG. 5 further includes step 503 , and step 503 is performed after step 501 .

503. The core network device sends information to the access network device for instructing the access network device terminal device to register urgently through the third network. Correspondingly, the access network device receives information from the core network device for instructing the access network device terminal device to register urgently through the third network.

There are various indication manners for instructing the access network equipment terminal equipment to register the information urgently through the third network, and two possible indication manners are shown below.

Indication mode 1: the information used to instruct the access network equipment terminal equipment to urgently register through the third network includes indication information used to instruct the access network equipment terminal equipment to urgently register through the third network.

In step 503, the core network device instructs the access network device terminal device to urgently register through the third network, that is, the core network device instructs the access network device to urgently register through the third network by means of instruction information.

It should be noted that, when the core network device determines that the terminal device does not urgently register through the third network, the core network device may send information for indicating that the terminal device does not urgently register through the third network to the terminal device.

For example, when the indication information sent by the core network device to the access network device and used to indicate whether or not the terminal device is to register urgently through the third network is "yes" or "true", it means that the terminal device urgently registers through the third network Registration, or, means that the terminal device performs emergency services through the third network. When the indication information sent by the core network device to the access network device indicating whether or not the terminal device urgently registers through the third network is "null", it means that the terminal device does not urgently register through the third network, or, it means that the terminal device does not register through the third network urgently. network for emergency business.

For example, when the indication information sent by the core network device to the access network device to indicate whether or not the terminal device is to register urgently through the third network is "1", it means that the terminal device urgently registers through the third network, or, it means that the terminal device is urgently registered through the third network. Emergency services are carried out through the third network. When the indication information sent by the core network device to the access network device indicating whether or not the terminal device is urgently registered through the third network is "0", it means that the terminal device does not urgently register through the third network, or it indicates that the terminal device does not register through the third network. network for emergency business.

The above shows possible forms and corresponding meanings of the indication information used to indicate whether or not the terminal equipment is urgently registered through the third network. In practical applications, the indication information may also have other representation forms, which are not specifically limited in this application.

Indication mode 2: the information used to instruct the access network equipment terminal equipment to urgently register through the third network includes the identifier of the third network, and the third network supports emergency services.

Specifically, the core network device selects one or more third networks from the networks associated with the first network, and sends the identifiers of the one or more third networks to the access network device, that is, the core network device The identifier indirectly instructs the access network device terminal device to register urgently through the third network.

Based on the indication method 1, the core network device also sends the identification of the third network to the access network device, so that the access network device can recommend the third network for the terminal device for the terminal device to perform emergency registration or emergency services through the third network. For the relevant introduction about the identifier of the third network, please refer to the relevant introduction in the foregoing indication mode 2, and details are not repeated here.

It should be noted that, in this embodiment, the core network device may send the identification of the third network and the information used to instruct the terminal device of the access network to urgently register through the third network to the access network device through the same message or different messages. For example, the core network device sends the identification of the third network and the information used to instruct the access network device terminal device to register urgently through the third network to the access network device through an initial context request setup (initial context setup request) message.

In this embodiment, the core network device may send the registration acceptance in the above step 502 and the registration acceptance in the above step 503 to the access network device through the same message or a different message. information, and then the access network device forwards the registration acceptance to the terminal device. For example, the core network device sends a registration acceptance and information for instructing the access network device terminal device to urgently register through the third network to the access network device through an initial context establishment request message. Then, the access network device forwards the registration acceptance to the terminal device through an RRC reconfiguration (RRC reconfiguration) message.

It should be noted that there is no fixed execution order between the above step 503 and the above step 502, and the step 502 may be executed first, or the step 503 may be executed first, or the step 502 and the step 503 may be executed simultaneously according to the situation.

In the embodiment of the present application, the terminal device sends a registration request to the core network device of the first network, where the registration request includes information used to instruct the terminal device to request emergency registration through the first network; then, the core network device sends a registration acceptance to the terminal device, The registration acceptance includes information for instructing the terminal device to urgently register through the third network. In this way, the terminal device can perform emergency registration or emergency services through the third network, so that the first network can provide the terminal device with emergency services through the second network. Compared with the existing way of directly connecting the IMS through the core network of the first network, so that the network can provide the terminal equipment with the IMS emergency service service, the technical solutions of the embodiments of the present application provide the terminal equipment of the first network with the emergency service. methods are more diverse. Moreover, when the core network device of the first network is not directly connected to the IMS, the problem that the first network cannot provide the terminal device with the IMS emergency service service is solved. That is, the first network can provide the terminal device with the emergency service through the third network that supports the emergency service.

In this embodiment of the present application, the access network device may also recommend a third network associated with the first network for the terminal device, so that the terminal device can register urgently through the third network. Optionally, the embodiment shown in FIG. 5 further includes step 504 , and step 504 is executed after step 503 .

504. The access network device sends the identifier of the third network to the terminal device. Correspondingly, the terminal device receives the identifier of the third network from the access network device.

The identifiers of the third networks include identifiers of one or more third networks, and the third networks support emergency services.

Specifically, the access network device may select one or more identifiers of the third network from the identifiers of the third networks sent by the core network device received in step 502, and send one or more identifiers of the third network to the terminal device 's identification. Alternatively, the access network device selects one or more third networks from preconfigured supported or possibly supported third networks, and sends the identifiers of the one or more third networks to the terminal device.

In this embodiment, the access network device may send the registration acceptance of the core network device and the identifier of the third network in the foregoing step 502 to the terminal device through the same message or different messages.

For example, the access network device sends the registration acceptance and the identity of the third network to the terminal device through the RRC reconfiguration message. That is, the RRC reconfiguration message includes the registration acceptance and the identity of the third network.

In this embodiment of the present application, after the terminal device receives the information for instructing the terminal device to register urgently through the third network in step 502 of the above-mentioned embodiment shown in FIG. 5 , the terminal device may request the third network for emergency registration or emergency registration. business. Optionally, the above-mentioned embodiment shown in FIG. 5 further includes step 505 , and step 505 is executed after step 502 . If the access network device executes the above step 504 , the step 505 can be executed after the step 504 .

505. The access network device requests the third network for emergency registration or emergency service.

Step 505 is similar to step 403 in the foregoing embodiment shown in FIG. 4 . For details, please refer to the relevant introduction of step 403 in the foregoing embodiment shown in FIG. 4 , which will not be repeated here.

In this embodiment of the present application, the access network device of the first network may send information to the terminal device indicating that at least one network in the first network and the third network supports emergency services, so as to notify the terminal device of the first network and the third network. At least one network in the network supports emergency services. Optionally, the above-mentioned embodiment shown in FIG. 5 further includes step 506 , and step 506 is performed before steps 501 to 505 .

506. The access network device sends, to the terminal device, information indicating that at least one of the first network and the third network supports the emergency service. Correspondingly, the terminal device receives information from the access network device indicating that at least one of the first network and the third network supports the emergency service.

For example, as shown in FIG. 2 , the first network is network A, and the third network is network B. The core network of network B and the core network of network A are connected through N3IWF208. The UPF 211 of the network B is directly connected to the IMS 212, so the network B supports emergency services. Then, the access network device 202 in the network A may send the information for indicating that at least one of the network A and the network B supports the emergency service to the terminal device 201 in the network A.

Optionally, the information used to indicate that at least one network in the first network and the third network supports the emergency service includes indication information used to indicate that at least one network in the first network and the third network supports the emergency service.

For example, the indication information used to indicate that at least one of the first network and the third network supports emergency services is represented as any one of the following: "Yes" or "true", or "1", or "0" , it means that at least one of the first network and the third network supports emergency services. Then, the terminal device may determine that at least one network in the first network and the third network supports the emergency service by using the indication information for indicating that at least one network in the first network and the third network supports the emergency service.

In this embodiment, the access network device sends the information for indicating that at least one network in the first network and the third network supports the emergency service in any form of broadcast, unicast and multicast. In a possible implementation manner, the information used to indicate that at least one network in the first network and the third network supports the emergency service is the information of the access network device used to indicate that at least one network in the first network and the third network supports the emergency service. System information for emergency services.

Specifically, the access network device may send information indicating that at least one network in the first network and the third network supports the emergency service through the system information of the access network device in the cell corresponding to the first network.

In this embodiment, step 506 is a process in which the access network device indicates to the terminal device whether or not at least one network in the first network and the third network supports emergency services. Under the technical solution of this embodiment, the access network device For more details on indicating to the terminal device whether or not at least one of the first network and the third network supports emergency services, please refer to the embodiment shown in FIG. 8 later.

The above-mentioned embodiment shown in FIG. 5 shows a technical solution in which the core network device instructs the terminal device to urgently register through the third network. In the above-mentioned embodiment shown in FIG. 5 , the first network also supports emergency services, that is, the core network of the first network is directly connected to the IMS. Then, in a possible implementation manner, in step 502, the core network device may instruct the terminal device to register urgently through the first network to the terminal device through registration acceptance.

Secondly, if the first network supports emergency services and the second network does not support emergency services, in step 502, the core network device may instruct the terminal device to register the terminal device urgently through the first network through the registration acceptance, so that the terminal device can pass the first network. Request urgent registration or urgent business.

In the embodiment of the present application, during the common registration process (including initial registration, mobile registration update, periodic registration update, etc.) of the terminal device in the first network, the terminal device can obtain whether or not the first network and the third network support emergency Service information, so that the terminal device can select the corresponding network for emergency registration or emergency service, avoid the terminal device repeatedly requesting emergency registration or emergency service from the first network, improve the success rate of the terminal device requesting emergency registration or emergency service, and improve user experience and communication system performance. The following will be introduced in conjunction with the embodiment shown in FIG. 6 , and the embodiment of the embodiment shown in FIG. 6 is applicable to the aforementioned network architecture shown in FIG. 2 , but does not belong to a limitation on the network architecture to which this embodiment is applicable , the technical solution of this embodiment is also applicable to the scenario of indicating to the terminal device whether the network supports emergency services under the architecture of other networks.

Please refer to FIG. 6 , which is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application. In Figure 6, the communication method includes:

601. The terminal device sends a registration request (registration accept) to a core network device (for example, AMF) of the first network. Correspondingly, the core network device of the first network receives the registration request from the terminal device.

The registration request is used for the terminal device to request to register in the first network.

Specifically, the registration of the terminal device in the first network may include initial registration, mobile registration update, periodic registration update, and the like.

602. The core network device sends a registration accept (registration accept) to the terminal device. Correspondingly, the terminal device receives the registration acceptance from the core network device.

Wherein, the registration acceptance includes at least one of the following information:

Whether the first network supports emergency services, whether the third network supports emergency services.

For example, if the first network is an NPN network and the third network is a PLMN network, the registration acceptance includes whether the NPN network supports emergency services, and/or whether the PLMN network supports emergency services.

In this embodiment, if there is a third network that supports emergency services in the third network associated with the first network, the core network device may select one or more third networks from the third network associated with the first network for the terminal device. identification, so that the terminal device can select a third network that supports emergency services from the identifications of one or more third networks, and perform emergency registration or emergency services through the third network.

Then, optionally, the registration acceptance further includes the identifier of the third network, and the third network supports emergency services.

The identifiers of the third networks include identifiers of one or more third networks. For example, NPN ID or PLMN ID.

Specifically, the core network device first sends the registration acceptance to the access network device of the first network, and then the access network device forwards it to the terminal device.

In this embodiment, the specific form of registration acceptance is similar to the specific form of registration acceptance in step 402 in the foregoing embodiment shown in FIG. 4 . For details, please refer to the relevant introduction of step 402 in the foregoing embodiment shown in FIG. 4 . I won't go into details here. The process for the core network device to send the registration acceptance to the terminal device through the access network device is similar to the process for the core network device to send the registration acceptance to the terminal device in step 402 in the embodiment shown in FIG. The related introduction of step 402 in the illustrated embodiment will not be repeated here. The process of the terminal equipment RRC reconfiguration to complete the registration in the first network is similar to the process of the terminal equipment RRC reconfiguration to complete the registration in the first network in step 402 in the aforementioned embodiment shown in FIG. 4 , please refer to FIG. The related introduction of step 402 in the embodiment shown in 4 will not be repeated here.

In the embodiment of the present application, the terminal device sends a registration request to the core network device of the first network; then, the core network device sends a registration acceptance to the terminal device, and the registration acceptance includes at least one of the following: whether or not the first network supports emergency services, The third network is/is not supporting emergency services. In this way, the terminal device can determine whether or not the first network and the third network respectively support emergency services according to the registration acceptance, so that the terminal device can select the corresponding network for emergency registration or emergency services, and improve the success of the terminal device requesting the network for emergency services. rate and efficiency of requests for urgent business.

In this embodiment of the present application, after the terminal device receives step 602, the terminal device may determine whether or not the first network and the third network support emergency services according to the registration acceptance.

Case 1: The first network supports emergency services and the third network does not support emergency services. For case 1, after step 601, the terminal device executes the following step 603a.

Case 2: The first network does not support emergency services and the third network supports emergency services. For case 2, then, after step 601, the terminal device executes the following step 603b.

603a. The terminal device requests an emergency registration or emergency service from the first network.

603b. The terminal device requests an emergency registration or emergency service from the third network.

Specifically, the terminal device selects the third network, and requests emergency registration or emergency service from the core network device of the third network through the N3IWF. For specific IP connection establishment included in the process of requesting emergency registration or emergency service by the terminal device from the core network device of the third network through the N3IWF, please refer to the related introduction in FIG.

The manner in which the terminal device selects the third network includes that the terminal device selects the third network from the identifier of the second network sent by the core network device; or, the terminal device selects the third network from a preconfigured third network that supports or may support emergency services Select the third network.

It should be noted that when the terminal device determines that both the first network and the third network support emergency services, the terminal device may select the first network or the third network to perform emergency registration or emergency services. In practical applications, the terminal device can also select a corresponding network to perform emergency registration or emergency service according to the priority of the network. For example, if the priority of the first network is higher than that of the third network, the terminal device selects the first network for emergency registration or emergency service.

When the terminal device determines that neither the first network nor the third network supports the emergency service, the terminal device does not select the first network and the third network to avoid the terminal device from initiating an emergency registration request or emergency service to the first network or the third network request, but the first network or the third network cannot provide the emergency service, so as to improve the success rate and request efficiency of the terminal device successfully requesting the emergency service from the network.

Please refer to FIG. 7 , which is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application. In Figure 7, the communication method includes:

701. The access network device of the first network sends the information used to indicate whether or not the third network supports the emergency service to the terminal device. Correspondingly, the terminal device receives information from the access network device of the first network for indicating whether or not the third network supports the emergency service.

For example, as shown in FIG. 2 , the first network is network A, and the third network is network B. The core network of network B and the core network of network A are connected through N3IWF208. The UPF 211 of the network B is directly connected to the IMS 212, so the network B supports emergency services. Then, the access network device 202 in the network A can send the information for indicating that the network B supports the emergency service to the terminal device 201 in the network A.

In this embodiment, optionally, the information used to indicate whether or not the first network supports the emergency service includes indication information used to indicate that the third network supports the emergency service.

The following describes the indication information used to instruct the third network to support the emergency service with reference to an example.

For example, when the indication information used to indicate that the third network supports the emergency service is "true", it means that the third network supports the emergency service; when the indication information used to indicate that the third network supports the emergency service is "null", it means that the third network supports the emergency service Emergency business is not supported.

Specifically, if at least one third network supports emergency services in the networks associated with the first network, the indication information for indicating that the third network supports emergency services is "yes" or "true". If none of the networks associated with the first network support the emergency service, the indication information used to indicate that the third network supports the emergency service is "null".

For example, when the indication information used to indicate that the third network supports emergency services is "Yes" or "true", it means that the third network supports emergency services; the indication information used to indicate that the third network supports emergency services is "No" (false)", it means that the third network does not support emergency services.

Specifically, if at least one third network supports emergency services in the networks associated with the first network, the indication information for indicating that the third network supports emergency services is "yes" or "true". If none of the networks associated with the first network support the emergency service, the indication information used to indicate that the third network supports the emergency service is "no (false)".

For example, when the indication information used to indicate that the third network supports the emergency service is "1", it means that the third network supports the emergency service; when the indication information used to indicate that the third network supports the emergency service is "0", it means that the third network supports the emergency service Emergency business is not supported.

Specifically, if at least one third network supports the emergency service in the network associated with the first network, the indication information used to indicate that the third network supports the emergency service is "1". If none of the networks associated with the first network support the emergency service, the indication information used to indicate that the third network supports the emergency service is "0".

Possible forms and corresponding meanings of the above-mentioned indication information used to indicate that the third network supports emergency services. In practical applications, the indication information used to indicate that the third network supports emergency services may also have other representation forms. The application is not limited.

In this embodiment, the access network device sends information for indicating whether or not the third network supports the emergency service to the terminal device through any one of broadcast, unicast and multicast. In a possible implementation manner, the information used to indicate whether or not the third network supports the emergency service is system information sent by the access network device and used to indicate whether or not the third network supports the emergency service.

Specifically, the access network device may send the information for indicating whether or not the third network supports the emergency service through the system information of the access network device in the cell corresponding to the first network.

702. The terminal device determines whether or not to select the first network according to the information used to indicate whether or not the third network supports the emergency service.

Specifically, when the terminal device determines that the third network supports emergency services, the terminal device determines to select the first network, so that the first network can provide emergency services for the terminal device through the third network. When the terminal device determines that the third network does not support emergency services, the terminal device may determine not to select the first network, so as to avoid the situation that the terminal device requests emergency services from the third network, but the third network cannot provide emergency services. The success rate of requesting urgent business.

In this embodiment, the access network device may also notify the terminal device whether or not the first network supports emergency services, so that the terminal device can further determine whether or not to select the first network in combination with the information on whether or not the first network supports emergency services . Optionally, the embodiment shown in FIG. 7 further includes step 703 , and step 703 is performed before step 702 .

703. The access network device sends the information used to indicate whether or not the first network supports the emergency service to the terminal device. Correspondingly, the terminal device receives information from the access network device indicating whether or not the first network supports the emergency service.

Step 703 is similar to step 407 in the foregoing embodiment shown in FIG. 4 . For details, please refer to the relevant introduction of step 407 in the foregoing embodiment shown in FIG. 4 , which will not be repeated here.

In this embodiment, the access network device may send the information in step 701 for indicating whether the third network supports emergency services and the information in step 703 for indicating whether the first network supports emergency services through the same system information Alternatively, the access network device may also send the information in step 701 for indicating whether/whether the third network supports emergency services and the information in step 703 for indicating whether the first network supports emergency services through different system information. , which is not specifically limited in this application.

It should be noted that there is no fixed execution order between step 702 and step 701, and step 701 may be executed first, or step 702 may be executed first, or concurrently according to the situation, which is not limited in this application.

Based on step 703, the above step 702 specifically includes:

The terminal device determines whether or not to select the first network according to the information indicating whether the third network supports the emergency service and the information indicating whether the first network supports the emergency service.

The following describes the determination process of the terminal device with reference to whether the first network and the third network support/whether emergency services are supported.

When the terminal device determines that the first network supports the emergency service and the third network does not support the emergency service, the terminal device may determine to select the first network. Then, the terminal device can request emergency registration or emergency service from the first network.

When the terminal device determines that the first network supports the emergency service and the third network supports the emergency service, the terminal device determines to select the first network. Since both the first network and the second network support emergency services, the terminal device can request emergency registration or emergency services from the first network; alternatively, the terminal device can also perform a process similar to that shown in FIG. The device (eg, AMF) requests emergency registration through the third network.

When the terminal device determines that the first network does not support the emergency service and the third network supports the emergency service, the terminal device determines to select the first network. Then, the terminal device may perform a process similar to that shown in FIG. 4 above to request the core network device of the first network for emergency registration through the third network.

It should be noted that, when the terminal device selects the corresponding network for emergency registration or emergency service, if the access network devices of multiple networks broadcast multiple networks and the networks associated with the multiple networks support the emergency service, the terminal The device can determine multiple candidate networks that support emergency services through the received broadcast message, and then select a corresponding network from the multiple candidate networks to perform emergency registration or emergency services. That is to say, the terminal device determines that the first network can be selected, but since the terminal device determines that other multiple networks also support emergency services, the terminal device can select one network from multiple candidate networks and perform emergency registration or emergency services through the network. For example, the terminal device may select a network with a higher priority to perform emergency registration or emergency service according to the priorities of multiple candidate networks, and if the priority of the first network is higher, the terminal device may select the first network.

In this embodiment of the present application, the terminal device receives information from the access network device of the first network for indicating whether/whether the third network supports emergency services and information for indicating whether or not the first network supports emergency services; then , the terminal device determines whether or not to select the first network according to the information used to indicate whether the third network supports the emergency service and the information used to indicate whether the first network supports the emergency service, thereby avoiding the first network and the third network When the network cannot provide emergency services, the terminal device repeatedly initiates emergency registration requests or emergency service requests to the first network or the third network, so as to improve the success rate and request efficiency of the terminal device successfully requesting emergency services from the network.

Please refer to FIG. 8 , which is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application. In Figure 8, the communication method includes:

801. The access network device of the first network sends, to the terminal device, information used to indicate whether or not at least one of the first network and the third network supports the emergency service. Correspondingly, the terminal device receives information from the access network device of the first network indicating whether or not at least one of the first network and the third network supports the emergency service.

Among them, the information used to indicate whether or not at least one of the first network and the third network supports emergency services.

For example, as shown in FIG. 2 , the first network is network A, and the third network is network B. The core network of network B and the core network of network A are connected through N3IWF208. The UPF 211 of the network B is directly connected to the IMS, so the network B supports emergency services. Then, the access network device 202 in the network A may send information to the terminal device 201 in the network A for indicating that at least one network in the network A and the network B supports the emergency service. That is to say, when at least one of the network A and the network B supports the emergency service, the access network device sends information to the terminal device indicating that at least one of the network A and the network B supports the emergency service. When neither network A nor network B supports emergency services (that is, neither the core network of network A nor the core network of network B is directly connected to the IMS), the access network device sends a message to the terminal device indicating that both network A and network B are Information that does not support urgent business.

In this embodiment, optionally, the information used to indicate whether or not the first network and the third network support emergency services include indication information used to indicate whether or not the first network and the third network support emergency services.

The following describes the indication information used to indicate whether the first network and the third network support emergency services with reference to an example.

For example, when the indication information used to indicate whether or not the first network and the third network support emergency services is "yes" or "true", it means that the third network supports emergency services; it is used to indicate that the first network and the third network support emergency services. When the indication information of whether or not the third network supports the emergency service is "null", it means that the third network does not support the emergency service.

Specifically, if at least one of the first network and the third network supports emergency services, the indication information used to indicate whether or not the first network and the third network support emergency services is "yes" or "true" )”. If neither the first network nor the third network supports the emergency service, the indication information for indicating whether or not the first network and the third network support the emergency service is "null".

For example, when the indication information used to indicate whether or not the first network and the third network support emergency services is "yes" or "true", it means that the third network supports emergency services; it is used to indicate that the first network and the third network support emergency services. When the indication information of whether the third network supports the emergency service is "no (false)", it means that the third network does not support the emergency service.

Specifically, if at least one of the first network and the third network supports emergency services, the indication information used to indicate whether or not the first network and the third network support emergency services is "yes" or "true (true)" ". If neither the first network nor the third network supports the emergency service, the indication information for indicating whether or not the first network and the third network support the emergency service is "false".

For example, when the indication information used to indicate whether or not the first network and the third network support emergency services is "1", it means that the third network supports emergency services; it is used to indicate whether the first network and the third network support emergency services. When the service indication information is "0", it means that the third network does not support emergency services.

Specifically, if at least one of the first network and the third network supports emergency services, the indication information for indicating whether the first network and the third network support emergency services is "1". If neither the first network nor the third network supports the emergency service, the indication information for indicating whether or not the first network and the third network support the emergency service is "0".

The possible forms and corresponding meanings of the above-mentioned indication information used to indicate whether the first network and the third network support emergency services are used to indicate whether or not the first network and the third network support emergency services. The indication information of the emergency service may also have other representation forms, which are not specifically limited in this application.

In this embodiment, the access network device sends, to the terminal device, information used to indicate whether or not the first network and the third network support emergency services through any one of broadcast, unicast, and multicast. In a possible implementation manner, the information used to indicate whether or not the first network and the third network support the emergency service is the information sent by the access network device to indicate whether or not the first network and the third network support the emergency service. system message.

Specifically, the access network device may send information for indicating whether or not the first network and the third network support emergency services through the system information of the access network device in the cell corresponding to the first network.

802. The terminal device determines whether or not to select the first network according to the information used to indicate whether or not at least one of the first network and the third network supports the emergency service.

Specifically, when the terminal device determines that at least one of the first network and the third network supports emergency services, the terminal device determines to select the first network, so that the first network can provide emergency services for the terminal device through the third network. When the terminal device determines that neither the first network nor the third network supports emergency services, the terminal device may determine not to select the first network, so as to avoid that the terminal device requests emergency services from the first network or the third network, and the first network or The third network cannot provide the emergency service, thereby improving the success rate of the terminal device requesting the emergency service.

It should be noted that, when a terminal device selects a network for emergency registration or emergency services, if the access network devices of multiple networks broadcast multiple networks and the networks associated with the multiple networks support emergency services, the terminal device can pass The received broadcast message determines multiple candidate networks that support emergency services, and then selects a corresponding network from the multiple candidate networks to perform emergency registration or emergency services. That is to say, the terminal device determines that the first network can be selected, but since the terminal device determines that other multiple networks also support emergency services, the terminal device can select one network from multiple candidate networks and perform emergency registration or emergency services through the network. For example, the terminal device may select a network with a higher priority to perform emergency registration or emergency service according to the priorities of multiple candidate networks. If the priority of the first network is higher, the terminal device may select the first network.

In this embodiment of the present application, the terminal device receives information from the access network device of the first network that indicates whether or not at least one of the first network and the third network supports emergency services; The information indicating whether or not at least one network in the first network and the third network supports emergency services determines whether or not to select the first network, so as to avoid the terminal equipment repeating to the emergency service when neither the first network nor the third network can provide emergency services The first network or the third network initiates the emergency registration request or the emergency service request, so as to improve the success rate and request efficiency of the terminal device successfully requesting the emergency service from the network.

A communication device provided by an embodiment of the present application is described below. Please refer to FIG. 9 , which is a schematic structural diagram of a communication apparatus 900 according to an embodiment of the present application. The communication device 900 includes a transmitting unit 901 and a receiving unit 902 . Optionally, the communication apparatus 900 further includes a processing unit 903 .

When the communication apparatus 900 is a terminal device or a chip in the terminal device, the communication apparatus 900 can be used to execute all or part of the steps performed by the terminal device in the embodiment shown in FIG.

For example, the sending unit 901 is configured to execute step 301 in the embodiment shown in FIG. 3A. The receiving unit 902 is configured to execute steps 302 and 304 of the embodiment shown in FIG. 3A above; the processing unit 903 is configured to execute step 305 of the embodiment shown in FIG. 3A above.

Another communication apparatus provided in the embodiment of the present application is described below. Please refer to FIG. 10 , which is a schematic structural diagram of a communication apparatus 1000 in an embodiment of the present application. The communication apparatus 1000 includes a sending unit 1001 and a receiving unit 1002 .

When the communication device 1000 is a core network device or a chip in the core network device, the communication device 1000 can be used to perform all or part of the steps performed by the core network device in the embodiments shown in FIG. 3A and FIG. 3B , and the above method embodiments may be referred to. related descriptions in .

For example, the sending unit 1001 is configured to perform step 301 in the embodiment shown in FIG. 3A , step 303 a in determination mode 1 in the embodiment shown in FIG. 3B , or determination mode 2 in the embodiment shown in FIG. 3B . step 303a and step 303b. The receiving unit 1002 is configured to perform step 302 in the above-mentioned embodiment shown in FIG. 3A .

In this embodiment of the present application, when the communication apparatus 900 shown in FIG. 9 is an access network device, or a chip in the access network device, the communication apparatus 900 can be used to execute the access network device of the embodiment shown in FIG. 3A . For some or all of the steps to be performed, reference may be made to the relevant descriptions in the foregoing method embodiments. The communication device 900 includes a sending unit 901 , a receiving unit 902 , and a processing unit 903 .

For example, the receiving unit 902 is configured to perform step 303a of determination mode 1 in the embodiment shown in FIG. 3B ; or steps 303a and 303b of determination mode 2 in the embodiment shown in FIG. 3B . The sending unit 901 is configured to execute step 304 in the above-mentioned embodiment shown in FIG. 3A . The processing unit 903 is configured to execute step 303 in the above-mentioned embodiment shown in FIG. 3A .

In this embodiment of the present application, when the communication device 900 shown in FIG. 9 is a terminal device, when the communication device 900 is a terminal device or a chip in the terminal device, the communication device 900 can be used to execute the functions shown in FIG. 4 or FIG. 5 . For all or part of the steps performed by the terminal device in the embodiments, reference may be made to the relevant descriptions in the foregoing method embodiments.

The communication device 900 includes a transmitting unit 901 and a receiving unit 902 . Optionally, the communication apparatus 900 further includes a processing unit 903 .

In a possible implementation manner, the sending unit 901 is configured to perform step 401 , step 404 and step 407 in the above-mentioned embodiment shown in FIG. 4 . The receiving unit 901 is configured to execute step 402, step 405 and step 406 in the above-mentioned embodiment shown in FIG. 4 . The processing unit 903 is configured to execute step 403 in the above-mentioned embodiment shown in FIG. 4 .

In another possible implementation manner, the sending unit 901 is configured to perform step 501 in the above-mentioned embodiment shown in FIG. 5 . The receiving unit 901 is configured to execute step 502, step 504 and step 506 in the above-mentioned embodiment shown in FIG. 5 . Optionally, the processing unit 903 is configured to perform step 505 in the above embodiment shown in FIG. 5 .

In this embodiment of the present application, when the communication apparatus 1000 shown in FIG. 10 is a core network device or a chip in the core network device, the communication apparatus 1000 can be used to execute the core network device in the embodiment shown in FIG. 4 or FIG. 5 . For all or part of the steps, reference may be made to the relevant descriptions in the foregoing method embodiments.

In a possible implementation manner, the receiving unit 1002 of the communication device 1000 is configured to perform step 401 in the above embodiment shown in FIG. 4 , and the sending unit 1001 of the communication device 1000 is configured to perform the above embodiment shown in FIG. step 402.

In another possible implementation manner, the receiving unit 1002 of the communication apparatus 1000 is configured to perform step 501 in the above-mentioned embodiment shown in FIG. 5 . The sending unit 1001 of the communication device 1000 is configured to execute step 502 and step 503 in the above-mentioned embodiment shown in FIG. 5 .

In this embodiment of the present application, when the communication apparatus 1000 shown in FIG. 10 is an access network device, or a chip in the access network device, the communication apparatus 1000 may be used to perform the access in the embodiment shown in FIG. 4 or FIG. 5 . For all or part of the steps performed by the network device, reference may be made to the relevant descriptions in the foregoing method embodiments.

In a possible implementation manner, the sending unit 1001 of the communication apparatus 1000 is configured to perform step 404 in the above-mentioned embodiment shown in FIG. 4 . The receiving unit 1002 of the communication device 1000 is configured to execute step 402, step 405, step 406 and step 407 in the above-mentioned embodiment shown in FIG. 4 .

In another possible implementation manner, the sending unit 1001 of the communication apparatus 1000 is configured to perform step 504 and step 506 in the above-mentioned embodiment shown in FIG. 5 . The receiving unit 1002 of the communication device 1000 is configured to perform step 503 in the above-mentioned embodiment shown in FIG. 5 .

In the embodiment of the present application, when the communication device 900 shown in FIG. 9 is a terminal device, when the communication device 900 is a terminal device or a chip in the terminal device, the communication device 900 can be used to execute the process in the embodiment shown in FIG. 6 . For all or part of the steps performed by the terminal device, reference may be made to the relevant descriptions in the foregoing method embodiments.

Specifically, the sending unit 901 is configured to perform step 601 in the embodiment shown in FIG. 6 above. The receiving unit 901 is configured to perform step 602 in the above-mentioned embodiment shown in FIG. 6 . The processing unit 903 is configured to execute step 603a or step 603b in the above-mentioned embodiment shown in FIG. 6 .

In this embodiment of the present application, when the communication apparatus 1000 shown in FIG. 10 is a core network device, or a chip or an on-chip chip in the core network device, the communication apparatus 1000 can be used to execute the execution of the core network device in the embodiment shown in FIG. 6 . For all or part of the steps, reference may be made to the relevant descriptions in the foregoing method embodiments.

For example, the receiving unit 1002 of the communication device 1000 is configured to perform steps 601 and 603a in the embodiment shown in FIG. 6, and the sending unit 1001 of the communication device 1000 is configured to perform step 602 in the embodiment shown in FIG. 6. .

Another communication apparatus provided in the embodiment of the present application is described below. Please refer to FIG. 11 , which is a schematic structural diagram of a communication apparatus 1100 in an embodiment of the present application. The communication apparatus 1100 includes a sending unit 1101 . Optionally, the communication apparatus 1100 further includes a processing unit 1102 .

When the communication apparatus 1100 shown in FIG. 11 is an access network device, or a chip or an on-chip chip in the access network device, the communication apparatus 1100 can be used to execute the execution of the access network device in the embodiment shown in FIG. 7 or 8 . For all or part of the steps, reference may be made to the relevant descriptions in the foregoing method embodiments.

In a possible implementation manner, the sending unit 1101 of the communication apparatus 1100 is configured to perform step 701 and step 703 in the above-mentioned embodiment shown in FIG. 7 . The processing unit 1102 is configured to determine the information used to indicate whether the third network supports emergency services in step 701 in the embodiment shown in FIG. 7 and the information used in step 703 in the embodiment shown in FIG. 7 to determine whether the third network supports emergency services. Information indicating whether or not the first network supports emergency services.

In another possible implementation manner, the sending unit 1101 of the communication apparatus 1100 is configured to perform step 802 in the above embodiment shown in FIG. 8 . The processing unit 1102 is used for the information used in step 801 in the above-mentioned embodiment shown in FIG. 8 to indicate whether at least one of the first network and the third network supports emergency services.

Another communication apparatus provided in the embodiment of the present application is described below. Please refer to FIG. 12 , which is a schematic structural diagram of a communication apparatus 1200 according to an embodiment of the present application. The communication apparatus 1200 includes a receiving unit 1201 and a processing unit 1202 .

When the communication apparatus 1200 shown in FIG. 12 is a terminal device, or a chip in the terminal device, or a chip on a chip, the communication apparatus 1200 can be used to execute all or all of the execution of the terminal device in the embodiment shown in FIG. 7 or FIG. 8 . For some steps, reference may be made to the relevant descriptions in the foregoing method embodiments.

In a possible implementation manner, the receiving unit 1201 is configured to perform step 701 and step 703 in the above-mentioned embodiment shown in FIG. 7 . The processing unit 1202 is configured to execute step 702 in the above-mentioned embodiment shown in FIG. 7 .

In another possible implementation manner, the receiving unit 1201 is configured to perform step 801 in the above-mentioned embodiment shown in FIG. 8 . The processing unit 1202 is configured to execute step 802 in the above-mentioned embodiment shown in FIG. 8 .

A possible schematic structural diagram of the terminal device is shown below through FIG. 13 .

FIG. 13 shows a schematic structural diagram of a simplified terminal device. For ease of understanding and illustration, in FIG. 13 , the terminal device takes a mobile phone as an example. As shown in FIG. 13 , the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input and output device. The processor is mainly used to process communication protocols and communication data, control terminal equipment, execute software programs, and process data of software programs. The memory is mainly used to store software programs and data. The radio frequency circuit is mainly used for the conversion of the baseband signal and the radio frequency signal and the processing of the radio frequency signal. Antennas are mainly used to send and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, and keyboards, are mainly used to receive data input by users and output data to users. It should be noted that some types of terminal equipment may not have input and output devices.

When data needs to be sent, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal through the antenna in the form of electromagnetic waves. When data is sent to the terminal device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, which converts the baseband signal into data and processes the data. For ease of illustration, only one memory and processor are shown in FIG. 13 . In an actual end device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device or the like. The memory may be set independently of the processor, or may be integrated with the processor, which is not limited in this embodiment of the present application.

In the embodiments of the present application, the antenna and the radio frequency circuit with a transceiver function may be regarded as a transceiver unit of the terminal device, and the processor with a processing function may be regarded as a processing unit of the terminal device. As shown in FIG. 13 , the terminal device includes a transceiver unit 1310 and a processing unit 1320 . The transceiving unit may also be referred to as a transceiver, a transceiver, a transceiving device, or the like. The processing unit may also be referred to as a processor, a processing single board, a processing module, a processing device, and the like. Optionally, the device for implementing the receiving function in the transceiver unit 1310 may be regarded as a receiving unit, and the device for implementing the transmitting function in the transceiver unit 1310 may be regarded as a transmitting unit, that is, the transceiver unit 1310 includes a receiving unit and a transmitting unit. The transceiver unit may also sometimes be referred to as a transceiver, a transceiver, or a transceiver circuit. The receiving unit may also sometimes be referred to as a receiver, receiver, or receiving circuit, or the like. The transmitting unit may also sometimes be referred to as a transmitter, a transmitter, or a transmitting circuit, or the like.

It should be understood that the transceiving unit 1310 is configured to perform the sending and receiving operations of the terminal device in the above method embodiments, and the processing unit 1320 is configured to perform other operations on the terminal device in the above method embodiments except the transceiving operations.

In a possible implementation manner, the transceiver unit 1310 is configured to perform step 301, step 302 and step 304 in the above-mentioned embodiment shown in FIG. other sending and receiving steps. The processing unit 1320 is configured to execute step 305 in the embodiment shown in FIG. 3A, and/or the processing unit 1320 is further configured to execute other processing steps of the terminal device in the embodiment of the present application.

In another possible implementation manner, the transceiver unit 1310 is configured to perform steps 401, 402, 404, 405, 406 and 407 in the above-mentioned embodiment shown in FIG. 4, and/or the transceiver unit 1310 also uses to perform other transceiving steps of the terminal device in the embodiment of the present application. The processing unit 1320 is configured to execute step 403 in the above-mentioned embodiment shown in FIG. 4 , and/or the processing unit 1320 is further configured to execute other processing steps of the terminal device in the embodiment of the present application.

In another possible implementation manner, the transceiver unit 1310 is configured to execute steps 501, 502, 504 and 506 in the above-mentioned embodiment shown in FIG. 5, and/or the transceiver unit 1310 is also configured to execute the embodiments of the present application Other sending and receiving steps of the terminal equipment. The processing unit 1320 is configured to execute step 505 in the above-mentioned embodiment shown in FIG. 5 , and/or the processing unit 1320 is further configured to execute other processing steps of the terminal device in the embodiment of the present application.

In another possible implementation manner, the transceiver unit 1310 is configured to perform steps 601 and 602 in the above-mentioned embodiment shown in FIG. 6 , and/or the transceiver unit 1310 is further configured to perform other transceivers of the terminal device in this embodiment of the present application step. The processing unit 1320 is configured to execute step 603a and step 603b in the above-mentioned embodiment shown in FIG. 6 , and/or the processing unit 1320 is further configured to execute other processing steps of the terminal device in the embodiment of the present application.

In another possible implementation manner, the transceiver unit 1310 is configured to perform steps 701 and 703 in the above-mentioned embodiment shown in FIG. 7 , and/or the transceiver unit 1310 is further configured to perform other transceivers of the terminal device in this embodiment of the present application step. The processing unit 1320 is configured to execute step 702 in the embodiment shown in FIG. 7, and/or the processing unit 1320 is further configured to execute other processing steps of the terminal device in the embodiment of the present application.

In another possible implementation manner, the transceiving unit 1310 is configured to perform step 801 in the above-mentioned embodiment shown in FIG. 8 , and/or the transceiving unit 1310 is further configured to perform other transceiving steps of the terminal device in this embodiment of the present application. The processing unit 1320 is configured to execute step 802 in the above-mentioned embodiment shown in FIG. 8 , and/or the processing unit 1320 is further configured to execute other processing steps of the terminal device in the embodiment of the present application.

When the terminal device is a chip, the chip includes a transceiver unit and a processing unit. Wherein, the transceiver unit may be an input/output circuit or a communication interface; the processing unit may be a processor or a microprocessor or an integrated circuit or a logic circuit integrated on a chip. In the above method embodiments, the sending operation corresponds to the output of the input-output circuit, and the receiving operation corresponds to the input of the input-output circuit.

The present application also provides a communication device, please refer to FIG. 14 , another schematic structural diagram of the communication device 1400 in the embodiment of the present application

The communication device 1400 includes: a processor 1401 , a memory 1402 and a transceiver 1403 .

The processor 1401, the memory 1402 and the transceiver 1403 are respectively connected through a bus, and computer instructions are stored in the memory.

When the communication apparatus 1400 is a core network device, or a chip in the core network device, the communication apparatus 1400 can be used to execute the core network device in the embodiment shown in FIG. 3A , FIG. 3B , FIG. 4 , FIG. 5 or FIG. 6 . For the steps, reference may be made to the relevant descriptions in the foregoing method embodiments.

The sending unit 1001 and the receiving unit 1002 in the foregoing FIG. 10 may specifically be the transceiver 1403 in this embodiment, and thus the specific implementation of the transceiver 1403 will not be described again.

In this embodiment of the present application, when the communication apparatus 1400 shown in FIG. 14 is an access network device, or a chip in the access network device, the communication apparatus 1400 may be used to perform the connection in the embodiments shown in FIG. 3A and FIG. 3B . For the steps performed by the network access device, reference may be made to the relevant descriptions in the foregoing method embodiments.

Then, the sending unit 901 and the receiving unit 902 in the foregoing FIG. 9 may specifically be the transceiver 1403 in this embodiment, and thus the specific implementation of the transceiver 1403 will not be repeated. The aforementioned processing unit 903 in FIG. 9 may specifically be the processor 1401 in this embodiment, and thus the specific implementation of the processor 1401 will not be described again.

In this embodiment of the present application, when the communication apparatus 1400 shown in FIG. 14 is an access network device or a chip in the access network device, the communication apparatus 1400 may be used to perform the connection in the embodiment shown in FIG. 4 or FIG. 5 . For the steps performed by the network access device, reference may be made to the relevant descriptions in the foregoing method embodiments.

Then, the transmitting unit 1001 and the receiving unit 1002 in the foregoing FIG. 10 may specifically be the transceiver 1403 in this embodiment, and thus the specific implementation of the transceiver 1403 will not be repeated.

In this embodiment of the present application, when the communication apparatus 1400 shown in FIG. 14 is an access network device, or a chip in the access network device, the communication apparatus 1400 may be used to perform the connection in the embodiment shown in FIG. 7 or FIG. 8 . For the steps performed by the network access device, reference may be made to the relevant descriptions in the foregoing method embodiments.

Then, the sending unit 1101 in the aforementioned FIG. 11 may specifically be the transceiver 1403 in this embodiment, and thus the specific implementation of the transceiver 1403 will not be described again.

Referring to FIG. 15 , an embodiment of the present application further provides a communication system, where the communication system includes an access network device and a core network device.

In a possible implementation manner, the access network device is configured to perform all or part of the steps performed by the access network device in the embodiments shown in FIG. 3A and FIG. 3B . The core network device is configured to perform all or part of the steps performed by the core network device in the embodiment shown in FIG. 3A and FIG. 3B .

In another possible implementation manner, the access network device is configured to perform all or part of the steps performed by the access network device in the embodiment shown in FIG. 5 . The core network device is configured to perform all or part of the steps performed by the core network device in the embodiment shown in FIG. 5 .

Embodiments of the present application further provide a computer program product including computer instructions, which, when run on a computer, enables the computer to execute the operations shown in FIGS. 3A, 3B, 4, 5, 6, 7, and 8 above. The communication method of the illustrated embodiment.

Embodiments of the present application further provide a computer-readable storage medium, including computer instructions, when the computer instructions are run on the computer, the computer can execute the above-mentioned FIG. 3A , FIG. 3B , FIG. 4 , FIG. 5 , FIG. 6 , and FIG. 7 . and the communication method of the embodiment shown in FIG. 8 .

An embodiment of the present application further provides a chip device, including a processor for invoking a computer program or computer instruction stored in a memory, so that the processor executes the above-mentioned FIG. 3A , FIG. 3B , FIG. 4 , FIG. 5 , FIG. 6 , and FIG. 7 and the communication method of the embodiment shown in FIG. 8 .

Optionally, the processor is coupled to the memory through an interface.

Optionally, the chip device further includes a memory, where computer programs or computer instructions are stored in the memory.

Wherein, the processor mentioned in any of the above can be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more of the above-mentioned Fig. 3A, 3B, 4, 5, 6, 7 and 8 of the integrated circuit for program execution of the communication method of the embodiment. The memory mentioned in any one of the above can be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM), and the like.

In addition, it should be noted that the device embodiments described above are only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units , that is, it can be located in one place, or it can be distributed to multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment. In addition, in the drawings of the device embodiments provided in the present application, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.

From the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general-purpose hardware. Special components, etc. to achieve. Under normal circumstances, all functions completed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structures used to implement the same function can also be various, such as analog circuits, digital circuits or special circuit, etc. However, a software program implementation is a better implementation in many cases for this application. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence or the parts that make contributions to the prior art, and the computer software products are stored in readable storage media, such as computer floppy disks, U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., including several instructions to make a computer device execute the methods of various embodiments of the present application.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product.

A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transferred from a website site, computer, network device, or local computing device, A computing device or data center transmits data to another website site, computer, network device, or local computing device, by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wirelessly (eg, infrared, wireless, microwave, etc.) computing device or data center for transmission. A computer-readable storage medium can be any available medium that a computer can store, or a network device that includes one or more available media integrated, or a data storage device such as a local computing device, a data center, or the like. Useful media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), and the like.

It is to be understood that reference throughout the specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic associated with the embodiment is included in at least one embodiment of the present application. Thus, appearances of "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. Interchangeability, the above description has generally described the components and steps of each example in terms of function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions. The computer software products are stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present application.

In a word, the above descriptions are only preferred embodiments of the technical solutions of the present application, and are not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included within the protection scope of this application.

Claims

A communication method, characterized in that the method comprises:

The terminal device sends an emergency registration request or an emergency service request to the core network device of the first network;

receiving, by the terminal device, a rejection message from the core network device, where the rejection message is used to instruct the core network device to reject the emergency registration request or the emergency service request;

The terminal device receives information from the access network device for instructing the terminal device to redirect to the second network for emergency registration or emergency service.
The method according to claim 1, wherein the information for instructing the terminal device to redirect to the second network for emergency registration or emergency service comprises instructing the terminal device to redirect to the second network for emergency registration or emergency service. 2. Indication information for the network to perform emergency services.
The method according to claim 1 or 2, wherein the information for instructing the terminal device to redirect to a second network for emergency registration or emergency service includes an identifier of the second network.
A communication method, characterized in that the method comprises:

The access network device determines information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service, where the access network device is an access network device of the first network;

The access network device sends the information for instructing the terminal device to redirect to the second network for emergency registration or emergency service to the terminal device.
The method according to claim 4, wherein the information for instructing the terminal device to redirect to the second network for emergency registration or emergency service comprises: instructing the terminal device to redirect to the second network for emergency registration or emergency service. The indication information that the second network performs emergency registration or emergency service, and/or the identifier of the second network.
A communication device, characterized in that the communication device comprises:

a sending unit, configured to send an emergency registration request or an emergency service request to the core network device of the first network;

a receiving unit, configured to receive a rejection message from the core network device, where the rejection message is used to instruct the core network device to reject the emergency registration request or the emergency service request;

The terminal device receives information from the access network device for instructing the terminal device to redirect to the second network for emergency registration or emergency service.
The communication apparatus according to claim 6, wherein the information for instructing the terminal device to redirect to the second network for emergency registration or emergency service comprises instructing the terminal device to redirect to the second network for emergency registration or emergency service. Indication information for the second network to perform emergency services.
The communication apparatus according to claim 6 or 7, wherein the information for instructing the terminal device to redirect to a second network for emergency registration or emergency service includes an identifier of the second network.
A communication device, characterized in that the communication device comprises:

a processing unit, configured to determine information used to instruct the terminal device to redirect to the second network for emergency registration or emergency service, where the access network device is an access network device of the first network;

A sending unit, configured to send the information for instructing the terminal device to redirect to the second network for emergency registration or emergency service to the terminal device.
The communication apparatus according to claim 9, wherein the information for instructing the terminal device to redirect to the second network for emergency registration or emergency service comprises: instructing the terminal device to redirect to the second network for emergency registration or emergency service. information indicating that the second network performs emergency registration or emergency service, and/or the identifier of the second network.
A communication device, characterized in that the communication device includes a processor, and the processor is configured to invoke a computer program or computer instructions in the memory, so that the communication device executes any one of claims 1 to 3 or, causing the communication device to perform the method according to any one of claims 4 to 5.
A computer-readable storage medium, characterized by comprising computer instructions, which, when the computer instructions are executed on a computer, cause the computer to execute the method according to any one of claims 1 to 3; or, cause the computer to execute A method as claimed in any one of claims 4 to 5.