Communication method and communication device

Abstract

Provided are a communication method and a communication device, when a terminal device moves from a second cell to a first cell, the method comprising: the terminal device determining that the second cell is a cell supporting a tracking area identifier (TAI) network model, the first cell is a cell not supporting a tracking area identifier (TAI) network model, or the terminal device determines that the second cell is a cell supporting a TAI network model, and the first cell is a cell not supporting a TAI network model; the second cell is a cell which does not support the TAI network model, and the first cell is a cell which supports the TAI network model; and the terminal equipment sends registration request information to the network to which the first cell belongs. When the terminal device moves from the second cell to the first cell, and the network models supported by the first cell and the second cell are different, the terminal device is triggered to send the registration request information to the first cell, thereby ensuring the communication performance of the terminal device.

Description

Technical Field

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

[0002] Tracking area (TA) is a concept established by the long term evolution (LTE) / system architecture evolution (SAE) system for location management of user equipment. In a TA, terminal equipment may not update services. The function of TA is to manage the location of terminal equipment, which can be divided into paging management and location update management. The terminal equipment informs the evolved packet core (EPC) of its own tracking area TA through tracking area registration. Among them, TA is a cell-level configuration. Multiple cells can be configured with the same TA, and a cell can only belong to one TA.

[0003] Currently, when a terminal device successfully registers with the network to which the cell belongs, the location area of ​​the current terminal device is saved. In the scenario where the network changes due to the movement of the terminal device, the terminal device needs to initiate registration again. When the terminal device initiates registration again, it carries the registration location area that the terminal device last visited to the target network.

[0004] When a terminal device moves from a source cell to a target cell, it cannot be guaranteed that both the source cell and the target cell support tracking area identity (TAI). When the source cell and the target cell support different network models, how to ensure the communication performance of the terminal device has become a hot topic in current research. Summary of the invention

[0005] The embodiments of the present application provide a communication method and a communication device, which ensure the communication performance of a terminal device when the terminal device moves from a second cell to a first cell.

[0006] In a first aspect, a communication method is provided, which can be optionally executed by a terminal device, or by a component of the terminal device (such as a chip or circuit), or by a logic module or software that can implement all or part of the functions of the terminal device, without limitation. The terminal device includes a device in the terminal device or other equipment that needs to access the core network through an access network device.

[0007] In the case where the terminal device moves from the second cell to the first cell, the method includes:

[0008] Determine that the second cell is a cell that supports the tracking area identifier TAI network model, and the first cell is a cell that does not support the tracking area identifier TAI network model, or that the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model; send registration request information to the network to which the first cell belongs.

[0009] It should be understood that the terminal device sends the registration request information to the network to which the first cell belongs, which may be that the terminal device sends the registration request information to the network device (such as a base station) corresponding to the network to which the first cell belongs, that is, the network device corresponding to the network to which the first cell belongs receives the registration request information from the terminal device.

[0010] It should also be understood that the first cell is a cell that supports the TAI network model, or the first cell is a cell that does not support the TAI network model, which can be understood as the cell capability of the first cell, that is, whether the first cell can process the TAI related information included in the registration request information. Or it can also be understood that the first cell carries the TAI identifier, which means that the first cell is a cell that supports the TAI network model, or the first cell does not carry the TAI identifier, which means that the first cell is a cell that does not support the TAI network model.

[0011] It should also be understood that the second cell is a cell that supports the TAI network model, or the second cell is a cell that does not support the TAI network model, which can be understood as the cell capability of the second cell, that is, whether the second cell can process the TAI related information included in the registration request information. Or it can also be understood as whether the first cell carries the TAI identifier. If the first cell carries the TAI identifier, it means that the first cell is a cell that supports the TAI network model. If the first cell does not carry the TAI identifier, it means that the first cell is a cell that does not support the TAI network model.

[0012] It should also be understood that the network to which the first cell belongs is different from the network to which the second cell belongs. When the first cell is a cell that supports the TAI network model, the network to which the first cell belongs is a network that supports the TAI network model; when the first cell is a cell that does not support the TAI network model, the network to which the first cell belongs is a network that does not support the TAI network model. When the second cell is a cell that supports the TAI network model, the network to which the second cell belongs is a network that supports the TAI network model; when the second cell is a cell that does not support the TAI network model, the network to which the second cell belongs is a network that does not support the TAI network model.

[0013] According to the method provided in the present application, the terminal device moves from the second cell to the first cell, the second cell is the source service cell of the terminal device, and the first cell is the target service cell of the terminal device. The terminal device can move from the second cell to the first cell by reselection, selection, network search, redirection or switching. When the terminal device determines that the network models supported by the first cell and the second cell are different, that is, the first cell is a cell that supports the TAI network model, and the second cell is a cell that does not support the TAI network model; or the first cell is a cell that does not support the TAI network model, and the second cell is a cell that supports the TAI network model. The terminal device sends a registration request message to the network to which the first cell belongs, thereby ensuring the continuity of the services related to the terminal device and the communication performance of the terminal device.

[0014] In combination with the first aspect, in some possible implementations, the method further includes: the terminal device receives response information from the network to which the first cell belongs, the response information is determined based on the registration request information, and the response information is used to indicate whether the terminal device has successfully registered or failed to register.

[0015] It should be understood that the response information is determined based on the information other than TAI in the registration request information. When the registration request information includes TAI, the network to which the first cell belongs ignores the TAI in the registration request information, or does not read the TAI in the registration request information, and does not check the legitimacy of the TAI, and directly determines the response information based on the information other than TAI in the registration request information. When the registration request information does not include TAI, the network to which the first cell belongs can directly determine the response information based on the registration request information.

[0016] In combination with the first aspect, in some possible implementations, the second cell is a cell that supports the TAI network model, and the first cell is a cell that does not support the TAI network model. The registration request information includes a first TAI, and the first TAI is used to indicate the TAI of the network to which the terminal device has successfully registered. The method also includes: receiving response information from the network to which the first cell belongs, and the response information is determined based on the registration request information, wherein the first TAI in the registration request information is ignored.

[0017] Based on the above technical solution, when the terminal device moves from the second cell to the first cell, the second cell is a cell that supports the TAI network model, and the first cell is a cell that does not support the TAI network model. The registration request information sent by the terminal device to the network to which the first cell belongs includes the first TAI. When the first cell processes the registration request information, it ignores the first TAI in the registration request information and determines the response information based on other information in the registration request information except the first TAI. If the first cell is a network that does not support the TAI network model, the network to which the first cell belongs may not have the ability to process TAI-related information. By ignoring the first TAI carried in the registration request information, abnormal processing of the registration request information of the terminal device can be avoided, thereby ensuring the communication performance of the terminal device.

[0018] It should be understood that in the present application, the terminal device sends a registration request message to the network to which the first cell belongs, and the network to which the first cell belongs receives the registration request message from the terminal device. It can be that the access network corresponding to the first cell receives the registration request message from the terminal device, and sends the registration request message to the core network corresponding to the first cell, and the core network processes the registration request message. Similarly, the terminal device receives the response message from the network to which the first cell belongs. The response message is determined by the core network corresponding to the first cell after processing the registration request message, and is sent by the core network to the access network, and then the access network forwards the response message to the terminal device.

[0019] In combination with the first aspect, in some possible implementations, the second cell is a cell that supports the TAI network model, the first cell is a cell that does not support the TAI network model, the registration request information does not include the first TAI, and the first TAI is used to indicate the TAI of the terminal device that has successfully registered with the network to which the second cell belongs.

[0020] Based on the above technical solution, when the terminal device moves from the second cell to the first cell, the second cell is a cell that supports the TAI network model, and the first cell is a cell that does not support the TAI network model. When the terminal device perceives that the target cell is a cell that does not support the TAI network model, the registration request information sent by the terminal device to the network to which the first cell belongs does not include the first TAI. The network to which the first cell belongs receives the registration request information of the terminal device that does not include the first TAI, and can directly determine the response information based on the registration information, thereby avoiding the situation where the network to which the cell that does not support the TAI network model (the first cell) belongs handles the TAI-related information in the registration request information of the terminal device abnormally.

[0021] In combination with the first aspect, in some possible implementations, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model. The registration request information includes a second TAI, and the second TAI is used to indicate that the second cell is a cell that does not support the TAI network model, or the second TAI is used to indicate that the network to which the first cell belongs does not need to perform a legitimacy check on the TAI in the registration request information.

[0022] It should be understood that the second TAI is used to indicate that the network to which the first cell belongs does not need to perform a validity check on the TAI in the registration request information. That is, after the network to which the first cell belongs receives the registration request information from the terminal device, the network to which the first cell belongs reads the second TAI in the registration request information, and according to the indication in the second TAI, does not check the validity of the TAI included in the registration request information.

[0023] It should also be understood that the second TAI may be a TAI obtained through global mapping of the first cell that does not support the TAI network model, or the second TAI may be predefined by the protocol. When the terminal device moves from a cell that does not support the TAI network model (the second cell) to a cell that supports the TAI network model (the first cell), the registration request information sent by the terminal device to the network to which the first cell belongs includes the TAI predefined by the protocol (e.g., the second TAI).

[0024] Based on the above technical solution, when the terminal device moves from the second cell to the first cell, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model. The registration request information sent by the terminal device to the network to which the first cell belongs includes the second TAI. After the network to which the first cell belongs receives the registration request information, it determines that the second cell is a cell that does not support the TAI network model according to the second TAI in the registration request information. Then, the network to which the first cell belongs does not perform a validity check on the TAI in the registration request information, and directly determines the response information according to other information in the registration request information except TAI; or, after the network to which the first cell belongs receives the registration request information, the second TAI in the registration request information indicates that the network to which the first cell belongs does not need to perform a validity check on the TAI in the registration request information, and the network to which the first cell belongs directly determines the response information according to other information in the registration request information except TAI. This avoids the situation where the network to which the first cell belongs handles the TAI in the registration request information of the terminal device abnormally when the terminal device moves from a cell that does not support the TAI network model (the second cell) to a cell that supports the TAI network model (the first cell).

[0025] In combination with the first aspect, in some possible implementations, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model. When the terminal device successfully registers in the second cell, the registration request information does not include TAI.

[0026] It should be understood that when a terminal device moves from a cell that does not support the TAI network model (the second cell) to a cell that supports the TAI network model, since the second cell is a cell that does not support the TAI network model, when the terminal device successfully registers in the second cell, the terminal device does not have a TAI, that is, the registration request information does not include a TAI. After receiving the registration request information, the network to which the first cell belongs ignores the legitimacy check of the TAI in the registration request information, thereby avoiding the problem of abnormal registration request of the terminal device.

[0027] In combination with the first aspect, in some possible implementations, the registration request information also includes first information, and the first information is used to indicate that the second cell is a cell that does not support the TAI network model, or the first information is used to indicate that the second cell is a cell that supports the TAI network model.

[0028] In a possible implementation manner, the first information may also be used to indicate that the network to which the first cell belongs does not need to check the legitimacy of the TAI in the registration request information.

[0029] It should be understood that the registration request information includes the first information, and the first information is used to indicate the network model supported by the second cell. After the network to which the first cell belongs receives the registration request information, it determines the network model supported by the second cell according to the first information in the registration request information. Wherein, when the first cell is a cell that supports the TAI network model, the second cell is a cell that does not support the TAI network model, and the network to which the first cell belongs receives the registration request information, it determines that the second cell is a cell that does not support the TAI network model according to the first information in the registration request information, and the network to which the first cell belongs does not perform a validity check on the TAI in the registration request information. Wherein, when the first cell is a cell that does not support the TAI network model, the second cell is a cell that supports the TAI network model, and the network to which the first cell belongs receives the registration request information, it determines that the second cell is a cell that supports the TAI network model according to the first information in the registration request information, and the network to which the first cell belongs determines that it does not support the TAI network model, and does not perform a validity check on the TAI in the registration request information.

[0030] It should also be understood that the first information is used to indicate that the network to which the first cell belongs does not need to check the legitimacy of the TAI in the registration request information, that is, the network to which the first cell belongs can directly ignore the TAI in the registration request information and does not read the TAI in the registration request information.

[0031] In one possible implementation, when the first cell is a cell that supports the TAI network model, and the second cell is a cell that does not support the TAI network model, the registration request information may carry the second TAI and the first information. After the network to which the first cell belongs receives the registration request information, it determines that the second cell is a cell that does not support the TAI network model based on the first information in the registration request information, and the network to which the first cell belongs does not perform a legitimacy check on the second TAI in the registration request information.

[0032] In another possible implementation, when the first cell is a cell that does not support the TAI network model, the second cell is a cell that supports the TAI network model, and the registration request information may carry the first TAI and the first information. After the network to which the first cell belongs receives the registration request information, it determines that the second cell is a cell that supports the TAI network model based on the first information in the registration request information, and the network to which the first cell belongs determines that it does not support the TAI network model, and does not perform a legitimacy check on the first TAI in the registration request information.

[0033] In combination with the first aspect, in some possible implementations, the first information is an information element identifier IEI.

[0034] It should be understood that the first information may be carried in the registration request information and sent, or the first information may also be transmitted separately.

[0035] In a second aspect, a communication method is provided, which can be optionally executed by a network device, or can also be executed by a component of the network device (such as a chip or circuit), or can also be a logic module or software that can implement all or part of the network device functions, without limitation. This application takes the network device (or referred to as the network device) to which the first cell belongs as an example for detailed introduction.

[0036] The method includes:

[0037] Receive registration request information of a terminal device, or receive registration request information; send response information to the terminal device according to the registration request information, or send response information, the response information is used to indicate that the terminal device has successfully registered or failed to register, wherein the first cell is a cell that does not support the TAI network model, or the first cell is a cell that supports the TAI network model. Alternatively, in this application, receiving can be replaced by input, and sending can also be replaced by output or generation.

[0038] According to the method provided in the present application, the terminal device moves from the second cell to the first cell, wherein the second cell supports a different network model from the first cell. The first cell is a cell that supports the TAI network model, and the second cell is a cell that does not support the TAI network model; the first cell is a cell that does not support the TAI network model, and the second cell is a cell that supports the TAI network model. The terminal device sends a registration request message to the network device to which the first cell belongs, and the network device determines a response message based on the registration request message, wherein the response message is determined based on information other than TAI in the registration request message, that is, the response message has nothing to do with whether the registration request message includes TAI, or whether the included TAI is legal. When the terminal device moves between two cells that support different network models, abnormal processing of the registration request message by the network device is avoided, thereby ensuring the communication performance of the terminal device.

[0039] In combination with the second aspect, in some possible implementations, the first cell is a cell that does not support the TAI network model, the registration request information includes a first TAI, the first TAI is used to indicate the TAI that the terminal device has successfully registered with the network to which the second cell belongs, and the second cell is a cell that supports the TAI network model; based on the registration request information, a response message is sent to the terminal device, including: ignoring the first TAI in the registration request information.

[0040] Based on the above technical solution, when the terminal device moves from the second cell to the first cell, the second cell is a cell that supports the TAI network model, and the first cell is a cell that does not support the TAI network model. The registration request information sent by the terminal device to the network to which the first cell belongs includes the first TAI. When the core network associated with the first cell processes the registration request information, it will ignore the first TAI in the registration request information and determine the response information based on other information in the registration request information except the first TAI. If the first cell is a network that does not support the TAI network model, the network to which the first cell belongs may not have the ability to process TAI-related information. By ignoring the first TAI carried in the registration request information, abnormal processing of the registration request information of the terminal device can be avoided, thereby ensuring the communication performance of the terminal device.

[0041] In combination with the second aspect, in some possible implementations, the first cell is a cell that does not support the TAI network model, the registration request information does not include the first TAI, the first TAI is used to indicate the TAI that the terminal device has successfully registered with the network to which the second cell belongs, and the second cell is a cell that supports the TAI network model.

[0042] Based on the above technical solution, the second cell is a cell that supports the TAI network model, and the first cell is a cell that does not support the TAI network model. When the terminal device perceives that the target cell is a cell that does not support the TAI network model, the registration request information sent by the terminal device to the network to which the first cell belongs does not include the first TAI. The network to which the first cell belongs receives the registration request information of the terminal device that does not include the first TAI, and can directly determine the response information based on the registration information, thereby avoiding the situation where the network to which the cell that does not support the TAI network model (the first cell) belongs handles the TAI-related information in the registration request information of the terminal device abnormally.

[0043] In combination with the second aspect, in some possible implementations, the first cell is a cell that supports the TAI network model, and the registration request information includes a second TAI, and the second TAI is used to indicate that the second cell is a cell that does not support the TAI network model, or the second TAI is used to indicate that the network device does not need to perform a legitimacy check on the TAI in the registration request information, wherein the second cell is the cell accessed by the terminal device before accessing the first cell.

[0044] Based on the above technical solution, when the terminal device moves from the second cell to the first cell, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model. The registration request information sent by the terminal device to the network to which the first cell belongs includes the second TAI. After the network to which the first cell belongs receives the registration request information, it determines that the second cell is a cell that does not support the TAI network model according to the second TAI in the registration request information. Then, the network to which the first cell belongs does not perform a validity check on the TAI in the registration request information, and directly determines the response information according to other information in the registration request information except TAI; or, after the network to which the first cell belongs receives the registration request information, the second TAI in the registration request information indicates that the network to which the first cell belongs does not need to perform a validity check on the TAI in the registration request information, and the network to which the first cell belongs directly determines the response information according to other information in the registration request information except TAI. This avoids the situation where the network to which the first cell belongs handles the TAI related information in the registration request information of the terminal device abnormally when the terminal device moves from the cell that does not support the TAI network model (the second cell) to the cell that supports the TAI network model (the first cell).

[0045] In conjunction with the second aspect, in some possible implementations, the first cell is a cell that supports the TAI network model, and when the terminal device successfully registers in the second cell, the registration request information does not include the TAI, wherein the second cell is a cell that the terminal device accessed before accessing the first cell. Sending a response message to the terminal device according to the registration request information includes: not performing a legitimacy check on the TAI in the registration request information.

[0046] Based on the above technical solution, before the terminal device accesses the first cell, the service cell of the terminal device is the second cell. The second cell may be a cell that does not support the TAI network model. Then, when the service cell of the terminal device is the second cell, the terminal device registers without TAI, that is, the registration request information sent by the terminal device to the network to which the first cell belongs does not include TAI. The network to which the first cell belongs does not perform a validity check on the TAI in the registration request information, thereby avoiding the failure of terminal device registration due to abnormal processing of the TAI in the registration request information by the network to which the first cell belongs.

[0047] In combination with the second aspect, in some possible implementations, the registration request information also includes first information, and the first information is used to indicate that the second cell is a cell that does not support the TAI network model, or the first information is used to indicate that the second cell is a cell that supports the TAI network model, wherein the second cell is the cell accessed by the terminal device before accessing the first cell.

[0048] In a possible implementation manner, the first information may also be used to indicate that the network to which the first cell belongs does not need to perform a validity check on the TAI in the registration request information.

[0049] Based on the above technical solution, the registration request information includes the first information, which can indicate the network model supported by the second cell, or the first information can be directly used to indicate that the network to which the first cell belongs does not need to perform a legitimacy check on the TAI in the registration request information, thereby avoiding the network to which the first cell belongs from failing to register the terminal device due to the fact that the registration request information does not include TAI or the included TAI is inaccurate.

[0050] In combination with the second aspect, in some possible implementations, the first information is an information element identifier IEI.

[0051] In a third aspect, a communication method is provided, which can be optionally executed by a terminal device, or by a component of the terminal device (such as a chip or circuit), or by a logic module or software that can implement all or part of the functions of the terminal device, without limitation. The terminal device includes a device in the terminal device or other equipment that needs to access the core network through an access network device.

[0052] In the case where the terminal device moves from the second cell to the first cell, the method includes:

[0053] Determine the registration request information; send the registration request information to the network to which the first cell belongs. The network model supported by the first cell is a cell that supports the TAI network model, or a cell that does not support the TAI network model; the network model supported by the second cell is a cell that supports the TAI network model, or a cell that does not support the TAI network model.

[0054] It should be understood that the scenarios to which the present application is applicable include: the second cell is a cell that supports the TAI network model, and the first cell is a cell that does not support the TAI network model; the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model; the second cell is a cell that does not support the TAI network model, and the first cell is a cell that does not support the TAI network model.

[0055] According to the method provided by the present application, the terminal device moves from the second cell to the first cell, the first cell is the source service cell of the terminal device, and the second cell is the target service cell of the terminal device. The terminal device can move from the second cell to the first cell by reselection, selection, network search, redirection or switching. The terminal device determines the response information according to the network model supported by the target cell and / or the source cell and other information in the registration request information except TAI, so as to further avoid the situation where the network to which the first cell belongs processes the registration information abnormally.

[0056] In conjunction with the third aspect, in some possible implementations, the second cell is a cell that supports the TAI network model, the first cell is a cell that does not support the TAI network model, the registration request information includes a first TAI, and the first TAI is used to indicate a TAI to which the terminal device successfully registers with the network to which the second cell belongs. The method further includes:

[0057] Receive response information from the network to which the first cell belongs, where the response information is determined according to the registration request information, wherein the first TAI in the registration request information is ignored.

[0058] In combination with the third aspect, in some possible implementations, the second cell is a cell that supports the TAI network model, the first cell is a cell that does not support the TAI network model, the registration request information does not include the first TAI, and the first TAI is used to indicate the TAI of the terminal device that has successfully registered with the network to which the second cell belongs.

[0059] In combination with the third aspect, in some possible implementations, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model, or the second cell is a cell that does not support the TAI network model, and the first cell is a cell that does not support the TAI network model,

[0060] The registration request information includes a second TAI, where the second TAI is used to indicate that the second cell is a cell that does not support the TAI network model, or the second TAI is used to indicate that the network to which the first cell belongs does not need to perform a validity check on the TAI in the registration request information.

[0061] In combination with the third aspect, in some possible implementations, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model, or the second cell is a cell that does not support the TAI network model, and the first cell is a cell that does not support the TAI network model. When the terminal device successfully registers in the second cell, the registration request information does not include TAI.

[0062] In combination with the third aspect, in some possible implementations, the registration request information also includes first information, and the first information is used to indicate that the second cell is a cell that does not support the TAI network model, or the first information is used to indicate that the second cell is a cell that supports the TAI network model.

[0063] In a possible implementation manner, the first information may also be used to indicate that the network to which the first cell belongs does not need to check the legitimacy of the TAI in the registration request information.

[0064] In combination with the third aspect, in some possible implementations, the first information is an information element identifier IEI.

[0065] In a fourth aspect, a communication method is provided, which may be optionally executed by a network device, or may be executed by a component of the network device (such as a chip or circuit), or may be a logic module or software that can implement all or part of the network device functions, without limitation. This application takes the network device to which the first cell belongs as an example for exemplary description.

[0066] The method includes: receiving registration request information of a terminal device, or receiving registration request information; sending response information to the terminal device according to the registration request information, or sending response information, wherein the response information is used to indicate that the terminal device has successfully registered or failed to register, wherein the first cell is a cell that does not support a tracking area identifier TAI network model, or the first cell is a cell that supports a tracking area identifier TAI network model.

[0067] In conjunction with the fourth aspect, in some possible implementations, the first cell is a cell that does not support the TAI network model, the registration request information includes a first TAI, the first TAI is used to indicate the TAI of a network to which the terminal device successfully registers, and the second cell is a cell that supports the TAI network model.

[0068] According to the registration request information, a response message is sent to the terminal device, including:

[0069] The first TAI in the Registration Request message is ignored.

[0070] In combination with the fourth aspect, in some possible implementations, the first cell is a cell that does not support the TAI network model, the registration request information does not include the first TAI, the first TAI is used to indicate the TAI that the terminal device has successfully registered with the network to which the second cell belongs, and the second cell is a cell that supports the TAI network model.

[0071] In combination with the fourth aspect, in some possible implementations, the first cell is a cell that supports the TAI network model, or the first cell is a cell that does not support the TAI network model, and the registration request information includes a second TAI, and the second TAI is used to indicate that the second cell is a cell that does not support the TAI network model, or the second TAI is used to indicate that the network device does not need to perform a legitimacy check on the TAI in the registration request information, wherein the second cell is the cell accessed by the terminal device before accessing the first cell.

[0072] In conjunction with the fourth aspect, in some possible implementations, the first cell is a cell that supports the TAI network model, or the first cell is a cell that does not support the TAI network model, and when the terminal device successfully registers in the second cell, the registration request information does not include the TAI, wherein the second cell is the cell that the terminal device accessed before accessing the first cell. Sending a response message to the terminal device according to the registration request information includes: not performing a legitimacy check on the TAI in the registration request information.

[0073] In combination with the fourth aspect, in some possible implementations, the registration request information also includes first information, and the first information is used to indicate that the second cell is a cell that does not support the TAI network model, or the first information is used to indicate that the second cell is a cell that supports the TAI network model, wherein the second cell is the cell accessed by the terminal device before accessing the first cell.

[0074] In conjunction with the fourth aspect, in some possible implementations, the first information is an information element identifier IEI.

[0075] In a fifth aspect, a communication device is provided, which includes: a processing unit, used to determine that the second cell is a cell that supports a tracking area identifier TAI network model, and the first cell is a cell that does not support a tracking area identifier TAI network model, or that the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model; a transceiver unit, used to send registration request information to the network to which the first cell belongs.

[0076] The transceiver unit can perform the reception and transmission processing in the aforementioned first aspect; the processing unit can perform other processing except reception and transmission in the aforementioned first aspect.

[0077] In a sixth aspect, a communication device is provided, which includes: a transceiver unit for receiving registration request information of a terminal device; the transceiver unit is also used to send response information to the terminal device according to the registration request information, and the response information is used to indicate that the terminal device has successfully registered or failed to register, wherein the first cell is a cell that does not support a tracking area identifier TAI network model, or the first cell is a cell that supports a tracking area identifier TAI network model.

[0078] The transceiver unit can perform the reception and transmission processing in the aforementioned second aspect.

[0079] In a possible implementation, the communication device may further include a processing unit, which may perform other processing in addition to receiving and sending in the aforementioned second aspect.

[0080] In a seventh aspect, a communication device is provided, the device comprising: a processing unit, configured to determine registration request information; and a transceiver unit, configured to send registration request information to a network to which a first cell belongs. The network model supported by the first cell is a cell that supports a TAI network model, or a cell that does not support a TAI network model; and the network model supported by the second cell is a cell that supports a TAI network model, or a cell that does not support a TAI network model.

[0081] The transceiver unit can perform the reception and transmission processing in the aforementioned third aspect; the processing unit can perform other processing except reception and transmission in the aforementioned third aspect.

[0082] In an eighth aspect, a communication device is provided, which includes: a transceiver unit for receiving registration request information of a terminal device; the transceiver unit is also used to send response information to the terminal device according to the registration request information, and the response information is used to indicate that the terminal device has successfully registered or failed to register, wherein the first cell is a cell that does not support a tracking area identifier TAI network model, or the first cell is a cell that supports a tracking area identifier TAI network model.

[0083] The transceiver unit can perform the reception and transmission processing in the aforementioned fourth aspect.

[0084] In one possible implementation, the communication device may further include a processing unit, which may perform other processing in addition to receiving and sending in the aforementioned fourth aspect.

[0085] In a ninth aspect, a communication device is provided, which includes: a transceiver unit and a processing unit, the transceiver unit is used to execute the steps of sending and receiving information in the methods provided by the above aspects, and the processing unit is used to execute the steps of processing in the methods provided by the above aspects.

[0086] In a tenth aspect, a communication device is provided, the device comprising: a processor, configured to execute a program, and when the program is executed, the processor is configured to execute the methods provided in the above aspects.

[0087] In a possible implementation, the communication device further includes a memory, and the memory is used to store programs.

[0088] In the eleventh aspect, the present application provides a processor for executing the methods provided in the above aspects. In the process of executing these methods, the process of sending the above information and obtaining / receiving the above information in the above methods can be understood as the process of the processor outputting the above information and the process of the processor receiving the input above information. When outputting the above information, the processor outputs the above information to the transceiver so that it can be transmitted by the transceiver. After being output by the processor, the above information may also need to be processed otherwise before reaching the transceiver. Similarly, when the processor receives the input information, the transceiver obtains / receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to be processed otherwise before being input into the processor.

[0089] Based on the above principles, for example, the receiving request message mentioned in the above method can be understood as the information that the processor receives input. For the operations such as transmission, sending and obtaining / receiving involved in the processor, if there is no special explanation, or if it does not conflict with its actual role or internal logic in the relevant description, it can be more generally understood as the processor output and receiving, input and other operations, rather than the transmission, sending and receiving operations directly performed by the radio frequency circuit and antenna. In the implementation process, the above processor can be a processor specifically used to execute these methods, or it can be a processor that executes computer instructions in the memory to execute these methods, such as a general-purpose processor. The above memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip, or it can be set on different chips respectively. The embodiment of the present application does not limit the type of memory and the setting method of the memory and the processor.

[0090] In a twelfth aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a program for executing the methods provided in the above aspects.

[0091] In a thirteenth aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer is used to execute the methods provided in the above aspects.

[0092] In a fourteenth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface to execute the methods provided in the above aspects.

[0093] Optionally, as an implementation manner, the chip may further include a memory, in which instructions are stored, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the methods provided by the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0094] Figure 1 It is a schematic block diagram of a registration area provided in this application.

[0095] Figure 2 It is a schematic block diagram of another registration area provided in this application.

[0096] Figure 3 It is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0097] Figure 4 It is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0098] Figure 5 It is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0099] Figure 6 It is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0100] Figure 7 It is a schematic block diagram of a communication device 10 provided in an embodiment of the present application.

[0101] Figure 8 It is a schematic block diagram of a communication device 20 provided in an embodiment of the present application.

[0102] Fig. 9 It is a structural diagram of a network device 30 provided in this application.

[0103] Fig.10 It is a structural diagram of a terminal device 40 provided in this application. DETAILED DESCRIPTION

[0104] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0105] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, fifth generation (5G) system or new radio (NR), and future communication systems.

[0106] The terminal device in the embodiments of the present application may refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a future Public Land Mobile Network (PLMN), etc., and the embodiments of the present application are not limited to this.

[0107] The network device in the embodiment of the present application can be a device for communicating with a terminal device. The network device can be a base station (base transceiver station, BTS) in a global system of mobile communication (GSM) system or code division multiple access (CDMA), or a base station (NodeB, NB) in a wideband code division multiple access (WCDMA) system, or an evolutionary base station (eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN) scenario, or the network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a 5G network, or a network device in a future evolved PLMN network, etc., and the embodiments of the present application are not limited.

[0108] In order to facilitate the understanding of the technical solution provided by this application, the professional terms involved in this application are introduced below:

[0109] Tracking area (TA)

[0110] TA is a new concept for UE location management in the LTE system. It is defined as a free movement area where the terminal device does not need to update the location service. The TA function is to achieve the management of the terminal location, which can be divided into paging management and location update relationship. TA is a cell-level configuration. Multiple cells can be configured with the same TA, and a cell belongs to only one TA.

[0111] The TA identifier is called the tracking area identity (TAI), which is composed of the PLMN and the tracking area code (TAC). The PLMN is composed of the mobile country code (MCC) and the mobile network code (MNC). Figure 1 shown.

[0112] It should be understood that for a network that supports the TAI network model, the registration area corresponding to the network is composed of one or more TAIs, and the structure of each TAI is as follows: Figure 1 shown.

[0113] It should also be understood that the registration area corresponding to the network that does not support the TAI network model is different from the above Figure 1 The TAI shown is different. Figure 2 The following is a schematic diagram of the registration area corresponding to a network that does not support the TAI network model. Figure 2 As shown, the registration area can be composed of MCC, MNC and radius. The radius is the radius distance issued with the location of the network device as the center. The registration area corresponding to the network that does not support the TAI network model can also only include the radius. The MCC and MNC corresponding to the network that does not support the TAI network model can be directly obtained by the terminal device from the PLMN broadcast by the current cell.

[0114] It should also be understood that the relevant information of the cell (for example, the system information block 1 (SIB1) in the system message) of the network that does not support the TAI network model does not include TAI related information. Alternatively, it can also be understood that the cell under the coverage of the network that does not support the TAI network model does not include TAI information.

[0115] It should also be understood that the resources of MCC are uniformly allocated and managed by the ITU, and are mainly used to uniquely identify the country where the mobile user is located. MCC consists of 3 decimal digits. For example, China's MCC is 460. MNC is used to identify the mobile network to which the mobile customer belongs, and it is a total of 2 to 3 digits. In the same country, if there are multiple PLMNs, they are distinguished by MNC. For example, the MNC used by China Mobile's system is 00, 02, 04, and 07. TAC is allocated by the operator itself and is used to locate the unique identifier for mobile users.

[0116] For example, the registration area corresponding to the network supporting the TAI network model is shown in Table 1:

[0117] Table 1

[0118]

[0119] Table 1 above is the content of the registration area corresponding to the network supporting the TAI network model. The 5GS tracking area identifier is a 7-byte type 3 information element. Among them, the MCC is located in bits 1 to bit 4 in octets 2 and 3 of the registration area; the MNC is bits 5 to bit 8 in octet 3 of the registration area, and octet 4; the TAC is located in octets 5, octet 6 and octet 7 of the registration area, that is, TAC consists of 3 octets.

[0120] For example, the registration area corresponding to the network that does not support the TAI network model is shown in Table 2:

[0121] Table 2

[0122]

[0123] Table 2 above is the specific content of the registration area corresponding to the network that does not support the TAI network model, where MCC is located in bits 1 to bit 4 in octet 2 and octet 3 of the registration area; MNC is bits 5 to bit 8 in octet 3 of the registration area, and octet 4; the radius is located in octet 7 of the registration area, that is, the radius consists of 1 octet. As shown in Table 2, octet 5 and octet 6 of the registration area corresponding to the network that does not support the TAI network model are 0.

[0124] It should be understood that the registration area corresponding to the network that does not support the TAI network model may also only include the tracking area radius or the registration area radius. The tracking area radius and the registration area radius are used to represent the paging area that does not support the TAI network model.

[0125] It should also be understood that in the embodiments of the present application, the network that supports the TAI network model may be a terrestrial network, and the network that does not support the TAI network model may be a satellite network.

[0126] At present, due to factors such as the movement of the terminal device's position, the change in the terminal device's communication quality, or the heavy load of the service cell corresponding to the terminal device, the terminal device moves from the source cell (e.g., the second cell) to the target cell (e.g., the first cell). The first cell and the second cell support different network models, or the first cell and the second cell are cells that do not support the TAI network model. The registration request information sent by the terminal device to the target cell may carry the last visited registered TAI or may not carry the last visited registered TAI. Due to the particularity of the network model supported by the target cell and the network model supported by the source cell, the target cell may handle the exception according to the content / format of the registration area included in the registration information of the terminal device, resulting in the terminal device being unable to register normally in the target network and the communication performance being reduced.

[0127] Based on the technical problems existing in the above analysis, an embodiment of the present application provides a communication method, which can ensure the communication performance of the terminal device when the terminal device moves from the second cell to the first cell.

[0128] Figure 3 It is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0129] The second cell is the source service cell of the terminal device, and the first cell is the target service cell of the terminal device. The network device to which the second cell belongs is network device #2, and the network device to which the first cell belongs is network device #1.

[0130] 301. The terminal device determines that the network models supported by the first cell and the second cell are different.

[0131] Specifically, when the terminal device moves from the second cell to the first cell, the second cell is a cell that supports the TAI network model, and the first cell is a cell that does not support the TAI network model; or, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model. That is, the terminal device determines that the network models supported by the first cell and the second cell are different.

[0132] It should be understood that the terminal device determines that the first cell and the second cell support different network models, triggering the terminal device to send a registration request message to the first cell. The registration request message is used to request access to the network to which the first cell belongs.

[0133] It should also be understood that when the second cell is a cell that does not support the network model, and the first cell is also a cell that does not support the network model, Figure 3 The step 301 shown in is an optional step, that is, the terminal device does not need to perform step 301. When the terminal device moves from the second cell to the first cell, the terminal device can directly send a registration request message to the network device #1.

[0134] 302. The terminal device sends a registration request message to the network device #1.

[0135] Correspondingly, network device #1 receives the registration request information sent from the terminal device.

[0136] It should be understood that the network model supported by the first cell is: supporting the TAI network model, or not supporting the TAI network model; the network model supported by the second cell is: supporting the TAI network model, or not supporting the TAI network model.

[0137] It should also be understood that the terminal device moving from the second cell to the first cell includes: the terminal device reselecting from the second cell to the first cell, or the terminal device switching from the second cell to the first cell, or the terminal device updating the service cell from the second cell to the first cell.

[0138] In a possible implementation manner, before the terminal device moves from the second cell to the first cell, the terminal device completes registration in the second cell.

[0139] The terminal device sends a registration request message to the network device #1, and the registration request message may include the TAI or may not include the TAI.

[0140] In one possible implementation, the second cell is a cell that supports the TAI network model, the first cell is a cell that does not support the TAI network model, and the registration request information includes the first TAI, or the registration request information does not include the first TAI. The first TAI is used to indicate the TAI to which the terminal device successfully registers in the network to which the second cell belongs.

[0141] It should be understood that the first TAI may be a TAI that broadcasts the selected PLMN in the cell (eg, the second cell) where the terminal device resides.

[0142] In another possible implementation, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model; or the second cell is a cell that does not support the TAI network model, and the first cell is a cell that does not support the TAI network model, and the registration request information includes a second TAI. The second TAI is used to indicate that the second cell is a cell that does not support the TAI network model, or the second TAI is used to indicate that network device #1 does not need to check the legitimacy of the TAI in the registration request information.

[0143] In another possible implementation, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model; or the second cell is a cell that does not support the TAI network model, and the first cell is a cell that does not support the TAI network model, and the registration request information does not include TAI. Since the second cell is a cell that does not support the TAI network model, that is, when the second cell provides services for the terminal device, the terminal device fails to obtain TAI, and when the terminal device moves from the second cell to the first cell, the registration information does not include TAI.

[0144] In another possible implementation, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model; or, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that does not support the TAI network model; or, the second cell is a cell that supports the TAI network model, and the first cell is a cell that does not support the TAI network model, and the registration request information includes the first information. The first information can be used to indicate that the second cell is a cell that does not support the TAI network model, or, the first information is used to indicate that the second cell is a cell that supports the TAI network model, or, the first information can be used to indicate that network device #1 does not need to perform a legitimacy check on the TAI in the registration request information.

[0145] Exemplarily, the first information is IEI.

[0146] For example, the IEI is in TLV (type-length-value) format, as shown in Table 3:

[0147] Table 3

[0148]

[0149] Based on the above Table 3, the specific value of Indication can be used to indicate that the cell (e.g., the second cell) where the terminal device last registered is a cell that supports the TAI network model, or a cell that does not support the TAI network model. When the value of indication is 0, the IEI is used to indicate that the second cell is a cell that supports the TAI network model; when the value of indication is 1, the IEI is used to indicate that the second cell is a cell that does not support the TAI network model; or, when the value of indication is 1, the IEI is used to indicate that the second cell is a cell that supports the TAI network model; when the value of indication is 0, the IEI is used to indicate that the second cell is a cell that does not support the TAI network model.

[0150] Among them, the specific value of Indication in Table 3 can also be used to indicate that network device #1 does not need to perform a validity check on the TAI in the registration request information. For example, when the value of indication is 0, the IEI is used to indicate that network device #1 does not need to perform a validity check on the TAI in the registration request information; or, when the value of indication is 1, the IEI is used to indicate that network device #1 does not need to perform a validity check on the TAI in the registration request information.

[0151] For example, the IEI is in TV format, as shown in Table 4:

[0152] Table 4

[0153]

[0154] Based on the above Table 4, the specific value of Indication can be used to indicate that the cell (for example, the second cell) where the terminal device last registered is a cell that supports the TAI network model, or a cell that does not support the TAI network model. When the value of indication is 0, the IEI is used to indicate that the second cell is a cell that supports the TAI network model; when the value of indication is 1, the IEI is used to indicate that the second cell is a cell that does not support the TAI network model; or, when the value of indication is 1, the IEI is used to indicate that the second cell is a cell that supports the TAI network model; when the value of indication is 0, the IEI is used to indicate that the second cell is a cell that does not support the TAI network model.

[0155] Among them, the specific value of Indication in Table 4 can also be used to indicate that network device #1 does not need to perform a validity check on the TAI in the registration request information. For example, when the value of indication is 0, the IEI is used to indicate that network device #1 does not need to perform a validity check on the TAI in the registration request information; or, when the value of indication is 1, the IEI is used to indicate that network device #1 does not need to perform a validity check on the TAI in the registration request information.

[0156] 303. The terminal device receives the response information sent by the network device #1.

[0157] Accordingly, network device #1 sends a response message to the terminal device.

[0158] Specifically, the network device #1 receives a registration request message sent from the terminal device, where the registration request message is used to request access to the first cell. The network device #1 determines response information according to the registration request message, and sends the response information to the terminal device.

[0159] The response information may be used to indicate whether the terminal device has been successfully registered or has failed to be registered.

[0160] In a possible implementation, when the second cell is a cell that supports the TAI network model and the first cell is a cell that does not support the TAI network model, assuming that the registration request information includes the first TAI, after network device #1 receives the registration request information, it ignores the first TAI and determines the response information based on other information in the registration request information except the first TAI. Wherein, network device #1 does not perform any operation (such as a read operation) on the first TAI in the registration request information. Assuming that the registration request information does not include the first TAI, network device #1 can directly determine the response information based on the registration information.

[0161] In another possible implementation, when the second cell is a cell that does not support the TAI network model and the first cell is a cell that supports the TAI network model, or when the second cell is a cell that does not support the TAI network model and the first cell is a cell that does not support the TAI network model, assuming that the registration request information includes the second TAI, network device #1 receives the registration request information, determines that the second cell is a cell that does not support the TAI network model based on the second TAI, network device #1 does not perform a legitimacy check on the TAI in the registration request information, and determines the response information based on other information in the registration request information except the second TAI.

[0162] In another possible implementation, when the second cell is a cell that does not support the TAI network model and the first cell is a cell that supports the TAI network model, or when the second cell is a cell that does not support the TAI network model and the first cell is a cell that does not support the TAI network model, assuming that the registration request information does not include TAI, network device #1 receives the registration request information and directly determines the response information based on the registration request information.

[0163] In another possible implementation, when the second cell is a cell that does not support the TAI network model and the first cell is a cell that supports the TAI network model, or when the second cell is a cell that does not support the TAI network model and the first cell is a cell that does not support the TAI network model, or when the second cell is a cell that supports the TAI network model and the first cell is a cell that supports the TAI network model, assuming that the registration request information includes the first information, the network device #1 determines the network model supported by the second cell (a cell that supports the TAI network model and a cell that does not support the TAI network model) according to the first information, and further determines the response information according to the information other than TAI received in the registration request information. Alternatively, the first information is used to indicate that the network device #1 does not need to perform a validity check on the TAI in the registration request information, and the network device #1 determines the response information directly according to the other information other than TAI in the registration request information according to the first information.

[0164] It should be understood that when network device #1 determines the response information based on the registration request information, the response information is determined based on other information in the registration request information except TAI, thereby ensuring that in the scenario where the terminal device moves from the second cell to the first cell, the response information received by the terminal device will not be affected by whether the second cell supports the TAI network model, thereby ensuring communication performance.

[0165] It should also be understood that step 303 is an optional step. That is, after network device #1 receives the registration information from the terminal device, it may not send a response message to the terminal device. For example, according to the protocol between network device #1 and the terminal device, the network device determines that the terminal device is successfully registered based on the registration request information, and network device #1 does not need to send a response message to the terminal device. Accordingly, within the first time period after the terminal device sends the registration request information to network device #1, if no response information from network device #1 is received, the terminal device defaults to successfully accessing the network to which the first cell belongs.

[0166] According to the above Figure 3According to the method shown, when the terminal device moves from the second cell to the first cell, and the network models supported by the first cell and the second cell are different, the terminal device can be triggered to send a registration request message to the network to which the first cell belongs, thereby ensuring the communication performance of the terminal device. At the same time, when the first cell and the second cell are respectively a cell that supports the TAI network model and a cell that does not support the TAI network model, or a cell that does not support the TAI network model and a cell that supports the TAI network model, or a cell that does not support the TAI network model and a cell that does not support the TAI network model, the network device #1 determines the response information based on other information except TAI in the registration request information of the terminal device. Whether the TAI is carried in the registration request information has nothing to do with whether the terminal device can successfully register and access the network to which the first cell belongs, thereby avoiding the situation where the network device #1 handles the registration request information of the terminal device abnormally.

[0167] It should be understood that, in combination with the above Figure 3 The method shown will be described in detail below with reference to specific scenarios.

[0168] The embodiments of the present application can be applied to the following three scenarios:

[0169] Scenario 1: The second cell is a cell that supports the TAI network model; the first cell is a cell that does not support the TAI network model. That is, the terminal device moves from a cell that supports the TAI network model to a cell that does not support the TAI network model.

[0170] Scenario 2: The second cell is a cell that does not support the TAI network model; the first cell is a cell that supports the TAI network model. That is, the terminal device moves from a cell that does not support the TAI network model to a cell that supports the TAI network model.

[0171] Scenario 3: The second cell is a cell that does not support the TAI network model; the first cell is a cell that does not support the TAI network model. That is, the terminal device moves from a cell that does not support the TAI network model to a cell that does not support the TAI network model.

[0172] In combination with the above three different scenarios, detailed description will be given below in combination with specific embodiments.

[0173] For scenario 1, the second cell is a cell that supports the TAI network model, and the first cell is a cell that does not support the TAI network model. That is, the terminal device moves from a cell that supports the TAI network model to a cell that does not support the TAI network model.

[0174] Figure 4 It is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0175] In a possible implementation, the registration request information includes a first TAI, where the first TAI is used to indicate a TAI obtained after the terminal device completes registration in the second cell. Figure 4 The following steps may be included:

[0176] 401. The terminal device sends a registration request message to the network device #1.

[0177] Correspondingly, network device #1 receives the registration request information sent from the terminal device.

[0178] The registration request information includes a first TAI, and the first TAI is used to indicate the TAI with which the terminal device is successfully registered when the service cell of the terminal device is the second cell (a cell that supports the TAI network model).

[0179] 402. The terminal device receives the response information sent by the network device #1.

[0180] Accordingly, network device #1 sends a response message to the terminal device.

[0181] In one possible implementation, network device #1 receives a registration request message sent from a terminal device, and determines that the second cell is a cell that supports the TAI network model based on the first TAI in the registration request message. Network device #1 ignores the first TAI in the registration request message, that is, network device #1 does not read the first TAI in the registration request message, and does not perform any operation (e.g., legitimacy check) on the first TAI in the registration request message. Network device #1 directly determines the response information based on other information in the registration request message except the first TAI, and sends the response information to the terminal device.

[0182] It should be understood that the response information received by the terminal device from network device #1 is not affected by the first TAI in the registration request information, that is, the success or failure of the registration of the terminal device has nothing to do with whether the source service cell of the terminal device supports the TAI network model.

[0183] In another possible implementation, the registration request information does not include the first TAI, and the first TAI is used to indicate the TAI of the terminal device that is successfully registered when the serving cell of the terminal device is the second cell. Figure 4 The following steps may be included:

[0184] 401', the terminal device sends a registration request message to the network device #1.

[0185] Correspondingly, network device #1 receives the registration request information sent from the terminal device.

[0186] The registration request information does not include the first TAI, which is used to indicate the TAI with which the terminal device is successfully registered when the service cell of the terminal device is the second cell (a cell that supports the TAI network model).

[0187] In one possible implementation, the service cell of the terminal device moves from the second cell to the first cell. When the terminal device determines or perceives that the second cell is a cell that supports the TAI network model and the first cell is a network that does not support the TAI network model, the terminal device determines not to carry the first TAI in the registration request information sent to network device #1 based on the network models supported by the second cell and the first cell.

[0188] 402', the terminal device receives the response information sent by the network device #1.

[0189] Accordingly, network device #1 sends a response message to the terminal device.

[0190] In one possible implementation, after network device #1 receives the registration request information from the terminal device, it can directly determine the corresponding response information based on the registration request information, thereby avoiding the situation where the first cell processes the first TAI included in the registration request information abnormally, thereby improving the communication performance of the terminal device.

[0191] In another possible implementation, after network device #1 receives the registration request information from the terminal device, it determines that the registration request information does not carry TAI-related information, and network device #1 ignores the check on the legitimacy of the TAI in the registration request information, thereby avoiding the situation where the registration request information of the terminal device is abnormally processed due to TAI-related information due to the different network models supported by the second cell and the first cell, thereby improving the communication performance of the terminal device.

[0192] In another possible implementation, the registration request information includes first information, where the first information is used to indicate a network model supported by the second cell. Figure 4 The following steps may be included:

[0193] 401", the terminal device sends a registration request message to network device #1.

[0194] Correspondingly, network device #1 receives the registration request information sent from the terminal device.

[0195] The registration request information includes first information, and the first information is used to indicate a network model supported by the second cell, that is, the first information is used to indicate that the second cell is a cell that supports the TAI network model, or the first information is used to indicate that the second cell is a cell that does not support the TAI network model. The first information can also be used to indicate that network device #1 does not need to perform a legitimacy check on the TAI in the registration request information.

[0196] 402", the terminal device receives the response information sent by network device #1.

[0197] Accordingly, network device #1 sends a response message to the terminal device.

[0198] It should be understood that the second cell is a cell that supports the TAI network model, and the first cell is a network that does not support the TAI network model. The first information is used to indicate that the second cell is a cell that supports the TAI network model. After network device #1 receives the registration request information and determines that the second cell is a cell that supports the TAI network model based on the first information in the registration request information, it can directly ignore the TAI in the registration request information and determine the response information based on the information other than TAI in the registration request information.

[0199] In one possible implementation, network device #1 receives a registration request message sent from a terminal device, and determines that the second cell is a cell that supports the TAI network model based on the first information in the registration request message. When the registration request message includes the first TAI, network device #1 ignores the legitimacy check of the TAI-related information in the registration request message, and does not perform a legitimacy check on the TAI-related information included in the registration request message. Network device #1 directly determines the response information based on other information in the registration request message except the TAI, and sends the response information to the terminal device.

[0200] In another possible implementation, network device #1 receives the registration request information sent from the terminal device, and determines that the second cell is a network supporting the TAI network model according to the first information in the registration request information. When the registration request information does not include the first TAI, network device #1 directly determines the response information according to the registration request information of the current terminal device, and sends the response information to the terminal device.

[0201] According to the above Figure 4The method shown in mainly introduces a scenario in which a terminal device moves from a cell that supports the TAI network model to a cell that does not support the TAI network model. When the registration request information of the terminal device includes the first TAI, the network device #1 can directly ignore the first TAI and determine the response information based on other information in the registration request information except the first TAI; or, when the terminal device perceives that the first cell is a network that does not support the TAI network model, the registration request information of the terminal device does not include the first TAI, thereby avoiding the situation in which the network device #1 processes the first TAI abnormally; or, the first information in the registration request information of the terminal device is used to indicate the network model supported by the second cell, and the network device #1 can determine based on the first information not to perform a legitimacy check on the TAI-related information in the registration request information, or directly ignore the TAI-related information in the registration request information and determine the response information.

[0202] For scenario 2, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model. That is, the terminal device moves from a cell that does not support the TAI network model to a cell that supports the TAI network model.

[0203] Figure 5 It is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0204] In a possible implementation manner, the registration request information includes a second TAI, and the second TAI is used to indicate that the network device #1 does not need to perform a validity check on the TAI in the registration request information.

[0205] like Figure 5 The following steps may be included:

[0206] 501. The terminal device sends a registration request message to the network device #1.

[0207] Correspondingly, network device #1 receives the registration request information sent from the terminal device.

[0208] The registration request information includes the second TAI.

[0209] It should be understood that the second TAI can be a second TAI determined by the second cell according to a fixed mapping or according to the protocol when the service cell of the terminal device is the second cell. The cell device that supports the TAI network model can identify the second TAI and determine that the source service cell is a cell that does not support the TAI network model; the cell device that does not support the TAI network model can also identify the second TAI and determine that the source service cell is a cell that does not support the TAI network model.

[0210] 502. The terminal device receives the response information sent by the network device #1.

[0211] Accordingly, network device #1 sends a response message to the terminal device.

[0212] In one possible implementation, network device #1 receives a registration request message sent from a terminal device, and determines that the second cell is a cell that does not support the TAI network model based on the second TAI in the registration request message. Network device #1 does not perform a validity check on the TAI in the registration request message. Network device #1 directly determines the response message based on other information in the registration request message except the TAI, and sends the response message to the terminal device.

[0213] It should be understood that the response information received by the terminal device from network device #1 is not affected by whether the registration request information includes TAI, and whether the included TAI is legal, that is, the success or failure of the terminal device's registration has nothing to do with the source cell of the terminal device not supporting the TAI network model.

[0214] In another possible implementation, the registration request message does not include the TAI. Figure 5 The following steps may be included:

[0215] 501', the terminal device sends a registration request message to the network device #1.

[0216] Correspondingly, network device #1 receives the registration request information sent from the terminal device.

[0217] The registration request information does not include TAI.

[0218] It should be understood that the second cell is a cell that does not support the TAI network model, that is, the terminal device does not have a registered TAI within the coverage of the second cell. When the terminal device moves from the second cell to the first cell, the registration request information sent by the terminal device to the network device #1 does not include TAI.

[0219] 502', the terminal device receives the response information sent by the network device #1.

[0220] Accordingly, network device #1 sends a response message to the terminal device.

[0221] In one possible implementation, after network device #1 receives registration request information from a terminal device, network device #1 determines that the registration request information does not include TAI. The network device #1 directly determines the corresponding response information based on the registration request information, thereby avoiding abnormal processing of the registration request information by the first cell and improving the communication performance of the terminal device.

[0222] In another possible implementation, the registration request information includes first information, where the first information is used to indicate a network model supported by the second cell. Figure 5 The following steps may be included:

[0223] 501", the terminal device sends a registration request message to network device #1.

[0224] Correspondingly, network device #1 receives the registration request information sent from the terminal device.

[0225] The registration request information includes first information, and the first information can be used to indicate that the second cell is a cell that does not support the TAI network model.

[0226] In one possible implementation, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model. The first information is used to indicate the source service cell of the network device #1 terminal device, that is, the second cell is a cell that does not support the TAI network model.

[0227] 502", the terminal device receives the response information sent by network device #1.

[0228] Accordingly, network device #1 sends a response message to the terminal device.

[0229] In one possible implementation, network device #1 receives a registration request message sent from a terminal device, and determines that the second cell is a cell that does not support the TAI network model based on the first information in the registration request message. When the registration request message includes the second TAI, network device #1 does not perform a validity check on the TAI in the registration request message. Network device #1 directly determines the response information based on other information in the registration request message except the TAI, and sends the response information to the terminal device.

[0230] In another possible implementation, network device #1 receives a registration request message sent from a terminal device, and determines, based on the first information in the registration request message, that the second cell is a cell that does not support the TAI network model, and the registration request message of the terminal device does not include TAI. Network device #1 directly determines the response information based on the registration request information of the current terminal device, and sends the response information to the terminal device.

[0231] According to the above Figure 5The method shown in mainly introduces a scenario in which a terminal device moves from a cell that does not support the TAI network model to a cell that supports the TAI network model. When the registration request information of the terminal device includes a second TAI, network device #1 determines that the second cell is a cell that does not support the TAI network model. Network device #1 can directly ignore the TAI included in the registration request information and determine the response information based on other information in the registration request information except TAI; or, the registration request information of the terminal device does not include TAI, and network device #1 directly determines the response information based on the registration request information, thereby avoiding abnormal processing of TAI by network device #1; or, the first information in the registration request information of the terminal device is used to indicate that the first network is a network that does not support TAI. Network device #1 can determine not to check the TAI in the registration request information based on the first information, or directly ignore the TAI in the registration request information and determine the response information.

[0232] It should be understood that according to the detailed description of the above scenario one and scenario two, it can be seen that the network models supported by the first cell and the second cell in scenario one and scenario two are completely different, that is, when the first cell is a network that supports the TAI network model, the second cell is a network that does not support the TAI network model; or, when the first cell is a network that does not support the TAI network model, the second cell is a network that supports the TAI network model. Based on the above scenario one and scenario two shown in Figure 4 and Figure 5 In one possible implementation of the method shown, before the terminal device sends a registration request message to the network device #1, Figure 4 and Figure 5 The method shown may also include:

[0233] The terminal device determines that the network model supported by the source service cell is different from the network model supported by the target service cell.

[0234] Specifically, the terminal device moves from the second cell to the first cell, and the terminal device perceives that the network model supported by the second cell is different from the network model supported by the first cell. The registration request information determined by the terminal device can be as described above. Figure 4 and Figure 5 The contents included in the registration request information described in detail in the text are sent to network device #1, which is used by network device #1 to determine the network model supported by the second cell and further determine whether to check the legitimacy of the TAI in the registration request information, thereby avoiding abnormal registration of the terminal device due to the different network models supported by the source cell and the target cell, and improving communication performance.

[0235] For scenario three, the first network is a network that does not support the TAI network model; the second network is a network that does not support the TAI network model. That is, the service network of the terminal device moves from a network that does not support the TAI network model to a network that does not support the TAI network model.

[0236] Figure 6 It is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0237] In a possible implementation, the registration request information includes a second TAI, and the second TAI is used by the first cell to determine that the second cell is a cell that does not support the TAI network model. Figure 6 The following steps may be included:

[0238] 601. The terminal device sends a registration request message to the network device #1.

[0239] Correspondingly, network device #1 receives the registration request information sent from the terminal device.

[0240] The registration request information includes the second TAI.

[0241] 602. The terminal device receives the response information sent by the network device #1.

[0242] Accordingly, network device #1 sends a response message to the terminal device.

[0243] In one possible implementation, network device #1 receives a registration request message sent from a terminal device, and determines that the second cell is a cell that does not support the TAI network model based on the second TAI in the registration request message. Network device #1 does not perform a validity check on the TAI in the registration request message. Network device #1 directly determines the response message based on other information in the registration request message except the TAI, and sends the response message to the terminal device.

[0244] It should be understood that the response information received by the terminal device from network device #1 is not affected by whether the registration request information includes TAI, or whether the included TAI is legal, that is, the success or failure of the terminal device's registration has nothing to do with the source cell of the terminal device not supporting the TAI network model.

[0245] In another possible implementation, the registration request message does not include the TAI. Figure 6 The following steps may be included:

[0246] 601', the terminal device sends a registration request message to the network device #1.

[0247] Correspondingly, network device #1 receives the registration request information sent from the terminal device.

[0248] It should be understood that the second cell is a cell that does not support the TAI network model, that is, the terminal device does not have a registered TAI within the coverage of the second cell. When the terminal device moves from the second cell to the first cell, the registration request information sent by the terminal device to the network device #1 does not include TAI.

[0249] 602', the terminal device receives the response information sent by the network device #1.

[0250] Accordingly, network device #1 sends a response message to the terminal device.

[0251] In one possible implementation, after network device #1 receives registration request information from a terminal device, network device #1 determines that the registration request information does not include TAI. The network device #1 directly determines the corresponding response information based on the registration request information, thereby avoiding abnormal processing of the registration request information by the first cell and improving the communication performance of the terminal device.

[0252] In another possible implementation, the registration request information includes first information, where the first information is used to indicate a network model supported by the second cell. Figure 6 The following steps may be included:

[0253] 601", the terminal device sends a registration request message to network device #1.

[0254] Correspondingly, network device #1 receives the registration request information sent from the terminal device.

[0255] The registration request information includes first information, and the first information can be used to indicate that the second cell is a cell that does not support the TAI network model.

[0256] In one possible implementation, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that does not support the TAI network model. The first information is used to indicate the source service cell of the terminal device, that is, the second cell is a cell that does not support the TAI network model.

[0257] 602", the terminal device receives the response information sent by network device #1.

[0258] Accordingly, network device #1 sends a response message to the terminal device.

[0259] In a possible implementation, network device #1 receives a registration request message sent from a terminal device, and determines that the second cell is a cell that does not support the TAI network model based on the first information in the registration request message. When the registration request message includes the second TAI, network device #1 does not perform a validity check operation on the TAI in the registration request message. Network device #1 directly determines the response information based on other information in the registration request message except the TAI, and sends the response information to the terminal device.

[0260] In another possible implementation, network device #1 receives the registration request information sent from the terminal device, and determines that the second cell is a cell that does not support the TAI network model according to the first information in the registration request information. When the registration request information does not include TAI, network device #1 directly determines the response information according to the registration request information of the current terminal device, and sends the response information to the terminal device.

[0261] It should be understood that the method applicable to the above scenario three is similar to the method shown in the above scenario two. To avoid redundancy, please refer to the method in the above scenario two. Figure 5 The detailed description will not be repeated here.

[0262] According to the above Figure 6 The method shown in mainly introduces a scenario in which the service network of a terminal device moves from a cell that does not support the TAI network model to a cell that does not support the TAI network model. When the registration request information of the terminal device includes a second TAI, network device #1 determines that the second cell is a cell that does not support the TAI network model. Network device #1 may not perform a legitimacy check on the TAI included in the registration request information, and determine the response information based on other information in the registration request information except TAI; or, the registration request information of the terminal device does not include TAI, and network device #1 directly determines the response information based on the registration request information, thereby avoiding abnormal processing of TAI by network device #1; or, the first information in the registration request information of the terminal device indicates that the second cell is a cell that does not support TAI, and network device #1 may determine based on the first information not to check the TAI in the registration request information, or directly ignore the TAI in the registration request information.

[0263] Combined with the above Figures 4 to 6 The communication method provided by the embodiment of the present application is described in detail. Figure 7-10 The communication device provided in the embodiment of the present application is described in detail. It is understood that the description of the device embodiment corresponds to the description of the method embodiment, so the contents not described in detail can be referred to the above method embodiment, and for the sake of brevity, they will not be repeated here.

[0264] Figure 71 is a schematic block diagram of a communication device 10 provided in an embodiment of the present application. The device 10 includes a transceiver unit 11 and a processing unit 12. The transceiver unit 11 can implement corresponding communication functions, and the processing unit 12 is used to perform data processing, or in other words, the transceiver unit 11 is used to perform operations related to receiving and sending, and the processing unit 12 is used to perform other operations besides receiving and sending. The transceiver unit 11 can also be called a communication interface or a communication unit.

[0265] It should be understood that the transceiver unit in the present application may be referred to as a transceiver module, and the processing unit may be referred to as a processing module.

[0266] In one possible design, the apparatus 10 may correspond to the terminal device in the above method embodiment, or a network device (eg, network device #1).

[0267] The device 10 may include a device for executing Figures 3 to 6 Furthermore, each unit in the device 10 and the above-mentioned other operations and / or functions are respectively for implementing Figures 3 to 6 The corresponding process of the method shown.

[0268] Exemplarily, the transceiver unit 11 in the apparatus 10 performs the receiving and sending operations performed by the terminal device in the above-mentioned method embodiments, and the processing unit 12 performs operations other than the receiving and sending operations.

[0269] In one possible implementation, the processing unit 12 is used to determine that the second cell is a cell that supports the tracking area identifier TAI network model, and the first cell is a cell that does not support the tracking area identifier TAI network model, or the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model; the transceiver unit 11 is used to send registration request information to the network to which the first cell belongs.

[0270] Optionally, the transceiver unit 11 is further used to receive response information from the network to which the first cell belongs, where the response information is determined based on the registration request information, and is used to indicate whether the terminal device has been successfully registered or failed to be registered.

[0271] In another possible implementation, the processing unit 12 is used to determine the registration request information; the transceiver unit 11 is used to send the registration request information to the network to which the first cell belongs. The network model supported by the first cell is a cell that supports the TAI network model, or a cell that does not support the TAI network model; the network model supported by the second cell is a cell that supports the TAI network model, or a cell that does not support the TAI network model.

[0272] In combination with the above two possible implementation methods, optionally, the second cell is a cell that supports the TAI network model, and the first cell is a cell that does not support the TAI network model. The registration request information includes a first TAI, and the first TAI is used to indicate the TAI of the network to which the terminal device has successfully registered in the second cell. The transceiver unit 11 is also used to receive response information from the network to which the first cell belongs, and the response information is determined based on the registration request information, wherein the first TAI in the registration request information is ignored.

[0273] Optionally, the second cell is a cell that supports the TAI network model, the first cell is a cell that does not support the TAI network model, the registration request information does not include the first TAI, and the first TAI is used to indicate the TAI with which the terminal device has successfully registered in the network to which the second cell belongs.

[0274] Optionally, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model. The registration request information includes a second TAI, and the second TAI is used to indicate that the second cell is a cell that does not support the TAI network model, or the second TAI is used to indicate that the network to which the first cell belongs does not need to perform a legitimacy check on the TAI in the registration request information.

[0275] Optionally, the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model. When the terminal device successfully registers in the second cell, the registration request information does not include TAI.

[0276] Optionally, the registration request information also includes first information, and the first information is used to indicate that the second cell is a cell that does not support the TAI network model, or the first information is used to indicate that the second cell is a cell that supports the TAI network model, or the first information can also be used to indicate that the network to which the first cell belongs does not need to check the legitimacy of the TAI in the registration request information.

[0277] Optionally, the first information is an information element identifier IEI.

[0278] The device 10 may include a device for executing Figures 3 to 6 The units of the method performed by the network device #1 in the apparatus 10 are respectively for implementing Figures 3 to 6 The corresponding process of the method shown.

[0279] Exemplarily, the transceiver unit 11 in the apparatus 10 performs the receiving and sending operations performed by the network device #1 in the above-mentioned method embodiments, and the processing unit 12 performs operations other than the receiving and sending operations.

[0280] In one possible implementation, the transceiver unit 11 is used to receive registration request information of a terminal device; the transceiver unit 11 is also used to send response information to the terminal device based on the registration request information, and the response information is used to indicate that the terminal device has successfully registered or failed to register, wherein the first cell is a cell that does not support the TAI network model, or the first cell is a cell that supports the TAI network model.

[0281] Optionally, the first cell is a cell that does not support the TAI network model, and the registration request information includes a first TAI, and the first TAI is used to indicate the TAI that the terminal device has successfully registered with the network to which the second cell belongs, and the second cell is a cell that supports the TAI network model; the transceiver unit 11 is also used to send a response message to the terminal device based on the registration request information, including: a processing unit 12, which is used to ignore the first TAI in the registration request information.

[0282] Optionally, the first cell is a cell that does not support the TAI network model, the registration request information does not include the first TAI, the first TAI is used to indicate the TAI that the terminal device has successfully registered with the network to which the second cell belongs, and the second cell is a cell that supports the TAI network model.

[0283] Optionally, the first cell is a cell that supports the TAI network model, and the registration request information includes a second TAI, and the second TAI is used to indicate that the second cell is a cell that does not support the TAI network model, or, the second TAI is used to indicate that the network device does not need to perform a legitimacy check on the TAI in the registration request information, wherein the second cell is the cell accessed by the terminal device before accessing the first cell.

[0284] Optionally, the first cell is a cell that supports the TAI network model. When the terminal device successfully registers in the second cell, the registration request information does not include TAI, wherein the second cell is the cell accessed by the terminal device before accessing the first cell, and the processing unit 12 is used for not performing a legitimacy check on the TAI in the registration request information.

[0285] Optionally, the registration request information also includes first information, and the first information is used to indicate that the second cell is a cell that does not support the TAI network model, or the first information is used to indicate that the second cell is a cell that supports the TAI network model, wherein the second cell is the cell accessed by the terminal device before accessing the first cell, or the first information can also be used to indicate that the network to which the first cell belongs does not need to perform a legitimacy check on the TAI in the registration request information.

[0286] Optionally, the first information is an information element identifier IEI.

[0287] Figure 8A schematic diagram of a communication device 20 provided in an embodiment of the present application. In a possible design, the device 20 may correspond to the terminal device or network device #1 in the above method embodiment.

[0288] The device 20 may include a processor 21 (ie, an example of a processing unit) and a memory 22. The memory 22 is used to store instructions, and the processor 21 is used to execute the instructions stored in the memory 22, so that the device 20 can implement the following Figures 4 to 6 The steps performed by the terminal device or network device in the corresponding method.

[0289] Furthermore, the device 20 may also include an input port 23 (i.e., an example of a transceiver unit) and an output port 24 (i.e., another example of a transceiver unit). Furthermore, the processor 21, the memory 22, the input port 23, and the output port 24 may communicate with each other through an internal connection path to transmit control and / or data signals. The memory 22 is used to store a computer program, and the processor 21 may be used to call and run the computer program from the memory 22 to control the input port 23 to receive a signal, and control the output port 24 to send a signal, thereby completing the steps of the terminal device or network device in the above method. The memory 22 may be integrated in the processor 21, or may be provided separately from the processor 21.

[0290] Optionally, if the communication device 20 is a communication equipment, the input port 23 is a receiver, and the output port 24 is a transmitter. The receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they may be collectively referred to as a transceiver.

[0291] Optionally, if the communication device 20 is a chip or a circuit, the input port 23 is an input interface, and the output port 24 is an output interface.

[0292] As an implementation method, the functions of the input port 23 and the output port 24 may be implemented by a transceiver circuit or a dedicated transceiver chip. The processor 21 may be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.

[0293] As another implementation method, it is possible to use a general-purpose computer to implement the communication device provided in the embodiment of the present application. That is, the program code that implements the functions of the processor 21, the input port 23, and the output port 24 is stored in the memory 22, and the general-purpose processor implements the functions of the processor 21, the input port 23, and the output port 24 by executing the code in the memory 22.

[0294] For the concepts, explanations, detailed descriptions and other steps involved in the device 20 and related to the technical solution provided in the embodiment of the present application, please refer to the description of these contents in the aforementioned method or other embodiments, which will not be repeated here.

[0295] Fig. 9 A simplified schematic diagram of the structure of a network device 30 is shown. The network device includes a part 31 and a part 32. Part 31 is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals; part 32 is mainly used for baseband processing, controlling the network device, etc. Part 31 can generally be referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc. Part 32 is generally the control center of the network device, and can generally be referred to as a processing unit, which is used to control the network device to perform the processing operations on the network device side in the above method embodiment.

[0296] The transceiver unit of part 31 may also be referred to as a transceiver or a transceiver, etc., which includes an antenna and a radio frequency circuit, wherein the radio frequency circuit is mainly used for radio frequency processing. For example, the device used to implement the receiving function in part 31 may be regarded as a receiving unit, and the device used to implement the transmitting function may be regarded as a transmitting unit, that is, part 31 includes a receiving unit and a transmitting unit. The receiving unit may also be referred to as a receiver, a receiver, or a receiving circuit, etc., and the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0297] Part 32 may include one or more single boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute the program in the memory to realize the baseband processing function and the control of the network device. If there are multiple single boards, each single board can be interconnected to enhance the processing capability. As an optional implementation, multiple single boards may share one or more processors, or multiple single boards may share one or more memories, or multiple single boards may share one or more processors at the same time.

[0298] For example, in one implementation, Fig. 9 The network devices shown can be Figures 4 to 6 Any network device shown in the method shown, such as the first network device, the second network device, etc.

[0299] The transceiver unit in part 31 is used to perform Figures 4 to 6 The steps related to the transmission and reception of any network device in the method shown; part 32 is used to perform Figures 3 to 6 The method shown may be performed by any network device.

[0300] It should be understood that Fig. 9 This is only an example and not a limitation. The network device including the transceiver unit and the processing unit may not rely on Fig. 9 The structure shown.

[0301] When the device 40 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; and the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip.

[0302] Fig.10 This is a schematic diagram of the structure of a terminal device 40 provided in this application. For ease of explanation, Fig.10 Only the main components of the communication device are shown. Fig.10 As shown, the terminal device 40 includes a processor, a memory, a control circuit, an antenna, and an input and output device.

[0303] The processor is mainly used to process the communication protocol and communication data, as well as to control the entire terminal device, execute the software program, and process the data of the software program, for example, to support the terminal device to perform the actions described in the above-mentioned transmission precoding matrix indication method embodiment. The memory is mainly used to store software programs and data, for example, to store the codebook described in the above-mentioned embodiment. The control circuit is mainly used for conversion between baseband signals and radio frequency signals and processing of radio frequency signals. The control circuit and the antenna can also be called a transceiver, which is 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, keyboards, etc. are mainly used to receive data input by users and output data to users.

[0304] When the communication device is turned on, the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data.

[0305] Those skilled in the art will appreciate that for ease of description, Fig.10 Only one memory and processor are shown. In an actual terminal device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., which is not limited in the embodiments of the present application.

[0306] As an optional implementation, the processor may include a baseband processor and a central processing unit. The baseband processor is mainly used to process the communication protocol and communication data, and the central processing unit is mainly used to control the entire terminal device, execute software programs, and process software program data. Fig.10The processor in integrates the functions of the baseband processor and the central processing unit. Those skilled in the art will understand that the baseband processor and the central processing unit may also be independent processors, which are interconnected through technologies such as buses. Those skilled in the art will understand that the terminal device may include multiple baseband processors to adapt to different network standards, and the terminal device may include multiple central processing units to enhance its processing capabilities. The various components of the terminal device may be connected through various buses. The baseband processor may also be described as a baseband processing circuit or a baseband processing chip. The central processing unit may also be described as a central processing circuit or a central processing chip. The function of processing the communication protocol and communication data may be built into the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing function.

[0307] like Fig.10 As shown, the terminal device 40 includes a transceiver unit 41 and a processing unit 42. The transceiver unit may also be referred to as a transceiver, a transceiver, a transceiver device, etc. Optionally, the device used to implement the receiving function in the transceiver unit 41 may be regarded as a receiving unit, and the device used to implement the sending function in the transceiver unit 41 may be regarded as a sending unit, that is, the transceiver unit 41 includes a receiving unit and a sending unit. Exemplarily, the receiving unit may also be referred to as a receiver, a receiver, a receiving circuit, etc., and the sending unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0308] Fig.10 The terminal device shown can perform Figures 4 to 6 The detailed description of the actions performed by the terminal device in the method shown is omitted here to avoid redundancy.

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

[0310] For example, when the computer program is executed by a computer, the computer can implement the method performed by network device #1 in the above method embodiment.

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

[0312] An embodiment of the present application also provides a communication system, which includes the network device in the above embodiment.

[0313] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

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

[0315] The embodiments of the present application do not specifically limit the specific structure of the execution subject of the method provided in the embodiments of the present application, as long as it is possible to communicate according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application. For example, the execution subject of the method provided in the embodiments of the present application may be a network device, or a functional unit in the network device that can call and execute a program.

[0316] Various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein may encompass a computer program accessible from any computer-readable device, carrier, or medium. For example, a computer-readable medium may include, but is not limited to, a magnetic storage device (e.g., a hard disk, a floppy disk, or a magnetic tape, etc.), an optical disk (e.g., a compact disc (CD), a digital versatile disc (DVD), etc.), a smart card, and a flash memory device (e.g., an erasable programmable read-only memory (EPROM), a card, a stick, or a key drive, etc.).

[0317] The various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.

[0318] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0319] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM may include the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0320] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage unit / module) can be integrated into the processor.

[0321] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0322] Those of ordinary skill in the art will appreciate that the units and steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of protection of this application.

[0323] Those skilled in the art can clearly understand that, for the sake of convenience and brevity of description, the specific working processes of the above-described devices and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0324] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0325] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to implement the solution provided by the present application.

[0326] In addition, each functional unit in each embodiment of the present application may be integrated into one unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0327] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrations. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium may include, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0328] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims and the specification.

Claims

1. A communication method, characterized in that: The method is applied to a terminal device, or to a device in the terminal device, and when the terminal device moves from a second cell to a first cell, the method includes: Determining that the second cell is a cell that supports a tracking area identifier TAI network model, and the first cell is a cell that does not support a tracking area identifier TAI network model, or that the second cell is a cell that does not support the TAI network model, and the first cell is a cell that supports the TAI network model; Send registration request information to the network to which the first cell belongs.

2. The method according to claim 1, characterized in that The second cell is a cell supporting the TAI network model, the first cell is a cell not supporting the TAI network model, the registration request information includes a first TAI, and the first TAI is used to indicate a TAI with which the terminal device has successfully registered in the network to which the second cell belongs. The method further comprises: Receive response information from a network to which the first cell belongs, where the response information is determined according to the registration request information, wherein the first TAI in the registration request information is ignored.

3. The method according to claim 1, characterized in that The second cell is a cell that supports the TAI network model, the first cell is a cell that does not support the TAI network model, the registration request information does not include the first TAI, and the first TAI is used to indicate the TAI with which the terminal device has successfully registered in the network to which the second cell belongs.

4. The method according to claim 1, characterized in that: The second cell is the cell that does not support the TAI network model, and the first cell is the cell that supports the TAI network model. The registration request information includes a second TAI, where the second TAI is used to indicate that the second cell is the cell that does not support the TAI network model, or the second TAI is used to indicate that the network to which the first cell belongs does not need to perform a legitimacy check on the TAI in the registration request information.

5. The method according to any one of claims 1 to 4, characterized in that The registration request information also includes first information, where the first information is used to indicate that the second cell is the cell that does not support the TAI network model, or the first information is used to indicate that the second cell is the cell that supports the TAI network model.

6. A communication method, characterized in that: The method is applied to a network device, or to a device in the network device, the network device is a network device to which a first cell belongs, and the method includes: Receiving registration request information from a terminal device; Sending response information to the terminal device according to the registration request information, wherein the response information is used to indicate whether the terminal device has been successfully registered or failed to be registered, The first cell is a cell that does not support the tracking area identifier TAI network model, or the first cell is a cell that supports the tracking area identifier TAI network model.

7. The method according to claim 6, characterized in that The first cell is a cell that does not support the TAI network model, the registration request information includes a first TAI, the first TAI is used to indicate the TAI of the network to which the terminal device successfully registers, and the second cell is a cell that supports the TAI network model, The sending response information to the terminal device according to the registration request information includes: The first TAI in the registration request information is ignored.

8. The method according to claim 6, characterized in that The first cell is a cell that does not support the TAI network model, the registration request information does not include the first TAI, the first TAI is used to indicate the TAI that the terminal device has successfully registered with the network to which the second cell belongs, and the second cell is a cell that supports the TAI network model.

9. The method according to claim 6, characterized in that The first cell is the cell supporting the TAI network model, the registration request information includes a second TAI, the second TAI is used to indicate that the second cell is the cell not supporting the TAI network model, or the second TAI is used to indicate that the network device does not need to perform a validity check on the TAI in the registration request information, The second cell is a cell accessed by the terminal device before accessing the first cell.

10. The method according to claim 6, characterized in that The first cell is the cell supporting the TAI network model, When the terminal device successfully registers in the second cell, the registration request information does not include TAI, wherein the second cell is a cell accessed by the terminal device before accessing the first cell, The sending response information to the terminal device according to the registration request information includes: No validity check is performed on the TAI of the registration request information.

11. The method according to any one of claims 6 to 10, characterized in that The registration request information further includes first information, where the first information is used to indicate that the second cell is the cell that does not support the TAI network model, or the first information is used to indicate that the second cell is the cell that supports the TAI network model. The second cell is a cell accessed by the terminal device before accessing the first cell.

12. A communication device, characterized in that: The communication device is applied to a terminal device, the terminal device moves from a second cell to a first cell, and the communication device includes: a processing unit, configured to determine that the second cell is a cell supporting a tracking area identifier TAI network model, and the first cell is a cell not supporting a tracking area identifier TAI network model, or that the second cell is a cell not supporting the TAI network model, and the first cell is a cell supporting the TAI network model; The transceiver unit is used to send registration request information to the network to which the first cell belongs.

13. The device according to claim 12, characterized in that The second cell is a cell supporting the TAI network model, the first cell is a cell not supporting the TAI network model, the registration request information includes a first TAI, and the first TAI is used to indicate a TAI with which the terminal device has successfully registered in the network to which the second cell belongs. The transceiver unit is further used to receive response information from a network to which the first cell belongs, wherein the response information is determined according to the registration request information, wherein the first TAI in the registration request information is ignored.

14. The device according to claim 12, characterized in that The second cell is a cell that supports the TAI network model, the first cell is a cell that does not support the TAI network model, the registration request information does not include the first TAI, and the first TAI is used to indicate the TAI with which the terminal device has successfully registered in the network to which the second cell belongs.

15. The device according to claim 12, characterized in that The second cell is the cell that does not support the TAI network model, and the first cell is the cell that supports the TAI network model. The registration request information includes a second TAI, where the second TAI is used to indicate that the second cell is the cell that does not support the TAI network model, or the second TAI is used to indicate that the network to which the first cell belongs does not need to perform a legitimacy check on the TAI in the registration request information.

16. The device according to any one of claims 12 to 15, characterized in that The registration request information also includes first information, where the first information is used to indicate that the second cell is the cell that does not support the TAI network model, or the first information is used to indicate that the second cell is the cell that supports the TAI network model.

17. A communication device, characterized in that: The communication device is a network device to which the first cell belongs, and the communication device includes: A transceiver unit, used to receive registration request information from a terminal device; The transceiver unit is further configured to send a response message to the terminal device according to the registration request message, wherein the response message is used to indicate whether the terminal device has successfully registered or failed to register. The first cell is a cell that does not support the tracking area identifier TAI network model, or the first cell is a cell that supports the tracking area identifier TAI network model.

18. The device according to claim 17, characterized in that The first cell is a cell that does not support the TAI network model, the registration request information includes a first TAI, the first TAI is used to indicate the TAI of the terminal device that has successfully registered with the network to which the second cell belongs, and the second cell is a cell that supports the TAI network model, The communication device further includes: A processing unit is used to ignore the first TAI in the registration request information.

19. The device according to claim 17, characterized in that The first cell is a cell that does not support the TAI network model, the registration request information does not include the first TAI, the first TAI is used to indicate the TAI that the terminal device has successfully registered with the network to which the second cell belongs, and the second cell is a cell that supports the TAI network model.

20. The device according to claim 17, characterized in that The first cell is the cell supporting the TAI network model, the registration request information includes a second TAI, the second TAI is used to indicate that the second cell is the cell not supporting the TAI network model, or the second TAI is used to indicate that the network device does not need to perform a validity check on the TAI in the registration request information, The second cell is a cell accessed by the terminal device before accessing the first cell.

21. The device according to claim 17, characterized in that The first cell is the cell supporting the TAI network model, and when the terminal device successfully registers in the second cell, the registration request information does not include TAI, wherein the second cell is the cell accessed by the terminal device before accessing the first cell, The communication device further includes: The processing unit is configured to not perform a validity check on the TAI in the registration request information.

22. The device according to any one of claims 17 to 21, characterized in that The registration request information further includes first information, where the first information is used to indicate that the second cell is the cell that does not support the TAI network model, or the first information is used to indicate that the second cell is the cell that supports the TAI network model. The second cell is a cell accessed by the terminal device before accessing the first cell.

23. A communication device, characterized in that: include: A processor, configured to execute a computer program so that the communication device executes the method according to any one of claims 1 to 5; or so that the communication device executes the method according to any one of claims 6 to 11.

24. The device according to claim 23, characterized in that The communication device further comprises a memory, the memory being coupled to the processor, the memory storing the computer program.

25. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the computer is enabled to execute the method according to any one of claims 1 to 5, or to execute the method according to any one of claims 6 to 11.

26. A computer program product, characterized in that The computer program product comprises a computer program or instructions for executing the method according to any one of claims 1 to 5; or, the computer program product comprises a computer program or instructions for executing the method according to any one of claims 6 to 11.

Images