# US 11,910,348 B2 · Register method in cell and terminal device > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,910,348 B2 - Document ID: US11910348B2 - Status: Granted - Kind: B2 - Application number: 17/423,306 - Filed: 2019-01-16 - Published: 2022-03-17 - Granted: 2024-02-20 - Earliest claimed: 2019-01-16 - Assignees: Huawei Technologies Co., Ltd. - Applicants: Huawei Technologies Co., Ltd. - Inventors: Ding Wang; Xiaoyan Duan; Liwei Cui - Web page: https://patentgrep.com/patent/US11910348B2 ## CPC - H04W 60/04: using triggered events - H04W 48/18: Selecting a network or a communication service - H04W 60/002: {Registration for requesting network slices} - H04W 60/06: De-registration or detaching - H04W 76/30: Connection release - H04W 84/042: {Public Land Mobile systems, e.g. cellular systems} - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A registration method applied in a terminal device includes sending a first request, where the first request is used to request to register in a first cell, receiving a first message, where the first message is used to indicate that the terminal device is successfully registered in the first cell, when the first message does not carry a first network slice identifier and the terminal device cannot establish a protocol data unit (PDU) session on a first network slice corresponding to the first network slice identifier, sending a second request, where the second request is used to request to register in a second cell, receiving a second message, where the second message carries a second network slice identifier, and establishing the PDU session on a second network slice corresponding to the second network slice identifier. ## Claims ### Claim 1 A registration method implemented by a terminal device, comprising: sending a first request requesting to register in a first cell; receiving, in response to the first request, a first message indicating that the terminal device is successfully registered in the first cell; sending, in response to the first message, a second request requesting to register in a second cell when the first message does not carry a first network slice identifier or when the first message carries the first network slice identifier and the terminal device cannot establish a protocol data unit (PDU) session on a first network slice corresponding to the first network slice identifier, wherein the second cell is different from the first cell; receiving, in response to the second request, a second message carrying a second network slice identifier; and establishing, in response to the second message, the PDU session on a second network slice corresponding to the second network slice identifier. ### Claim 2 (depends on 1) The registration method of claim 1, wherein before sending the second request, the registration method further comprises selecting the second cell from a first tracking area comprising the first cell. ### Claim 3 (depends on 2) The registration method of claim 2, further comprising marking the first cell as a barred cell. ### Claim 4 (depends on 1) The registration method of claim 1, wherein before sending the second request, the registration method further comprises selecting the second cell from a second tracking area, and wherein the second tracking area is different from a first tracking area comprising the first cell. ### Claim 5 (depends on 4) The registration method of claim 4, further comprising marking the first tracking area as a forbidden tracking area. ### Claim 6 (depends on 1) The registration method of claim 1, wherein before sending the second request, the registration method further comprises selecting the second cell from a second registration area, and wherein the second registration area is different from a first registration area comprising the first cell. ### Claim 7 (depends on 6) The registration method of claim 6, further comprising marking the first registration area as a forbidden registration area. ### Claim 8 (depends on 1) The registration method of claim 1, wherein before sending the second request, the registration method further comprises selecting the second cell from a second public land mobile network (PLMN), and wherein the second PLMN is different from a first PLMN comprising the first cell. ### Claim 9 (depends on 8) The registration method of claim 8, further comprising marking the first PLMN as a forbidden PLMN. ### Claim 10 (depends on 1) The registration method of claim 1, wherein before sending the second request, the registration method further comprises deregistering in the first cell. ### Claim 11 (depends on 1) The registration method of claim 1, wherein a registration type corresponding to the first message is non-emergency registration, and wherein either the first message does not carry allowed network slice selection assistance information (NSSAI) or the first message carries the allowed NSSAI and a length of the allowed NSSAI is zero. ### Claim 12 (depends on 1) The registration method of claim 1, wherein a registration type corresponding to the first message is non-emergency registration, wherein the first message does not carry configured network slice selection assistance information (NSSAI), wherein a service type of allowed NSSAI that is carried in the first message is different from a target service type, and wherein the first network slice identifier is comprised in the allowed NSSAI. ### Claim 13 (depends on 1) The registration method of claim 1, wherein a registration type corresponding to the first message is non-emergency registration, wherein a first service type of allowed network slice selection assistance information (NSSAI) and a second service type of configured NS SAI carried in the first message are different from a target service type, and wherein the first network slice identifier is comprised in the allowed NSSAI, in the configured NSSAI, or in the allowed NSSAI and the configured NSSAI. ### Claim 14 A terminal device, comprising a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to cause the terminal device to be configured to: receive a first message from a first cell, wherein the first message indicates that the terminal device is successfully registered in the first cell; and send, in response to the first message, a second request requesting to register in a second cell when the first message does not carry a first network slice identifier or when the first message carries the first network slice identifier and the terminal device cannot establish a protocol data unit (PDU) session on a first network slice corresponding to the first network slice identifier, wherein the second cell is different from the first cell. ### Claim 15 (depends on 14) The terminal device of claim 14, wherein the instructions further cause the terminal device to be configured to: receive a second message carrying a second network slice identifier; and establish, in response to the second message, the PDU session on a second network slice corresponding to the second network slice identifier. ### Claim 16 (depends on 14) The terminal device of claim 14, wherein before the terminal device sends the second request, the instructions further cause the terminal device to be configured to select the second cell from a first tracking area, and wherein the first tracking area comprises the first cell. ### Claim 17 (depends on 14) The terminal device of claim 14, wherein before the terminal device sends the second request, the instructions further cause the terminal device to be configured to select the second cell from a second tracking area, and wherein the second tracking area is different from a first tracking area comprising the first cell. ### Claim 18 (depends on 14) The terminal device of claim 14, wherein before the terminal device sends the second request, the instructions further cause the terminal device to be configured to select the second cell from a second registration area, and wherein the second registration area is different from a first registration area comprising the first cell. ### Claim 19 (depends on 14) The terminal device of claim 14, wherein before the terminal device sends the second request, the instructions further cause the terminal device to select the second cell from a second public land mobile network (PLMN) and wherein the second PLMN is different from a first PLMN comprising the first cell. ### Claim 20 A computer program product comprising computer-executable instructions stored on a non-transitory computer-readable medium that, when executed by a processor, cause an apparatus to: receive a first message from a first cell, wherein the first message indicates that a terminal device is successfully registered in the first cell; and send, in response to the first message, a second request requesting to register in a second cell when the first message does not carry a first network slice identifier or when the first message carries the first network slice identifier and the terminal device cannot establish a protocol data unit (PDU) session on a first network slice corresponding to the first network slice identifier, wherein the second cell is different from the first cell.