Method and device used for wireless communication

Abstract

Disclosed are a method and device for wireless communication, comprising: sending a first registration request message, the first registration request message being an NAS message, the first registration request message comprising a first identifier, the first registration request message depending on communication with a network through a second identifier being abnormal; wherein the first identifier and the second identifier both identify the first node; the first identifier and the second identifier belong to globally unique identifiers; the first identifier and the second identifier are configured by fields with the same name in the NAS message. According to the invention, communication between the first identifier and the second identifier and the network can be better realized.

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, and to processing when a node configured with two identifiers by a field of the same name has an abnormality in communicating with a network through one of the identifiers. Background Art

[0002] In the future, the application scenarios of wireless communication systems will become more and more diversified, and different application scenarios will put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #72 plenary meeting decided to study the new radio (NR) (or Fifth Generation, 5G) technology, and the NR WI (Work Item) was passed at the 3GPP RAN #75 plenary meeting, and the standardization work on NR began.

[0003] In communication, both LTE (Long Term Evolution) and 5G NR involve accurate reception of reliable information, optimized energy efficiency, determination of information validity, flexible resource allocation, scalable system structure, efficient non-access layer information processing, low service interruption and drop rate, and support for low power consumption. This is of great significance to the normal communication between base stations and user equipment, the reasonable scheduling of resources, and the balancing of system loads. It can be said to be the cornerstone of high throughput, meeting the communication needs of various services, improving spectrum utilization, and improving service quality. It is indispensable for eMBB (ehanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication) and eMTC (enhanced Machine Type Communication). At the same time, in IIoT (Industrial Internet of Things, Industrial Internet of Things, V2X (Vehicular to X, vehicle-mounted communication), device-to-device communication, unlicensed spectrum communication, user communication quality monitoring, network planning optimization, NTN (Non Territerial Network, non-terrestrial network communication), TN (Territerial Network, terrestrial network communication), dual connectivity (Dual connectivity) system, wireless resource management and multi-antenna codebook selection, signaling design, neighbor management, business management, beamforming, there are extensive needs, information transmission methods are divided into broadcast and unicast, both transmission methods are essential for 5G systems, because they are very helpful to meet the above requirements. The UE can be connected to the network directly or through a relay.

[0004] As the scenarios and complexity of the system continue to increase, higher requirements are placed on reducing interruption rates, reducing latency, enhancing reliability, enhancing system stability, business flexibility, and power saving. At the same time, compatibility between different versions of different systems also needs to be considered during system design.

[0005] The meanings of the concepts, terms and abbreviations in this application may refer to the 3GPP standards, including but not limited to:

[0006] https: / / www.3gpp.org / ftp / Specs / archive / 21_series / 21.905 / 21905-h10.zip

[0007] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.300 / 38300-h10.zip

[0008] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.331 / 38331-h10.zip

[0009] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.305 / 38305-h10.zip

[0010] https: / / www.3gpp.org / ftp / Specs / archive / 23_series / 23.003 / 23003-h10.zip

[0011] https: / / www.3gpp.org / ftp / Specs / archive / 23_series / 23.501 / 23501-h10.zip

[0012] https: / / www.3gpp.org / ftp / Specs / archive / 24_series / 24.501 / 24501-h10.zip Summary of the invention

[0013] The researchers found that in the scenario where the first node has two identifiers configured by the same name field in the NAS message, how to let the network grasp the relevant information as soon as possible when an abnormality occurs in the communication with the network through the second identifier is a problem that needs to be solved. The researchers further found that when the first node has two identifiers configured by the same name field in the NAS message, namely the first identifier and the second identifier, the first node has the need to communicate through the first identifier and the need to communicate through the second identifier, and the communication through the first identifier and the communication through the second identifier are often carried out independently, which makes it impossible for the network to grasp this information in time when an abnormality occurs in the communication with the network through the second identifier, and thus it is impossible to take countermeasures in time. The researchers also found that when the first node has two SIM cards, the first identifier and the second identifier correspond to one SIM card respectively. In the prior art, the communication with the network through different SIM cards is often independent or even separated. The method proposed in this application is conducive to breaking the above limitations, and at the same time does not increase the complexity, but it can enable the network to grasp the information that the first node communicates with the network through the second identifier in a timely and effective manner, which is conducive to timely recovery and avoidance or reduction of resource waste. The researchers further discovered that when the first identifier and the second identifier of the first node are both of the same operator, for example, both are registered in the same core network, the complexity of implementing the method proposed in this application is very low, but the effect is very obvious.

[0014] In view of the above-mentioned problems, this application provides a solution.

[0015] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other. At the same time, the method proposed in the present application can also be used to solve other problems in communication, such as network optimization, artificial intelligence, and mobility management; the method proposed in the present application is also very suitable for solving problems in network convergence scenarios.

[0016] As an embodiment, the interpretation of the terminology in the present application refers to the definition of the 3GPP specification protocol TS38 series.

[0017] As an example, the interpretation of the terms in the present application refers to the definitions of the TS37 series of specification protocols of 3GPP.

[0018] The present application discloses a method in a first node used for wireless communication, comprising:

[0019] Sending a first registration request message, where the first registration request message is a NAS message, the first registration request message includes a first identifier, and an abnormality occurs when the first registration request message relies on communication with a network through a second identifier;

[0020] The first identifier and the second identifier both identify the first node; the first identifier and the second identifier are both globally unique identifiers; and the first identifier and the second identifier are configured by fields with the same name in a NAS message.

[0021] As an embodiment, the problems to be solved by the present application include: in a scenario where a first node has two identifiers configured with fields of the same name in a NAS message, when an abnormality occurs in communication with the network through the second identifier, how to let the network know that an abnormality occurs in communication between the first node and the network through the second identifier is a problem that needs to be solved.

[0022] As an embodiment, the benefits of the above method include: shortening the recovery time; avoiding or reducing the waste of resources; reducing the interruption time; ensuring the continuity of communication; better supporting network sharing; better supporting multi-SIM (Subscriber Identity Module) communication; better supporting multi-SIM communication under the same network / operator.

[0023] Specifically, according to one aspect of the present application, the first registration request message is sent in communication with the network through the first identifier.

[0024] Specifically, according to one aspect of the present application, a first registration approval message is received, where the first registration approval message is feedback of the first registration request message; the first registration approval message depends on an abnormality in the communication with the network through the second identifier.

[0025] Specifically, according to one aspect of the present application, the first identifier corresponds to a first NAS signaling connection; the second identifier corresponds to a second NAS signaling connection.

[0026] Specifically, according to one aspect of the present application, the first transmitter sends a second registration request message before the first registration request message is sent;

[0027] receiving a second registration approval message, where the second registration approval message is a feedback of the second registration request message; and configuring the first identifier with the second registration approval message;

[0028] Before the first registration request message is sent, sending a third registration request message;

[0029] receiving a third registration approval message, where the third registration approval message is a feedback of the third registration request message; and the third registration request message is configured with the second identifier;

[0030] The first identifier and the second identifier are both valid identifiers; the second registration request message, the second registration approval message, the third registration request message, and the third registration approval message are NAS messages respectively.

[0031] Specifically, according to one aspect of the present application, a first message is sent, wherein the first message indicates that the first identifier is associated with the second identifier.

[0032] Specifically, according to one aspect of the present application, the phrase "an abnormality occurs in communication with the network through the second identifier" includes: the RRC connection associated with the second identifier fails, deregistration of the second identifier is unsuccessful, communication with the network through the second identifier overheats, the hardware corresponding to the second identifier is removed or is no longer available, and at least one of the hardware corresponding to the second identifier fails.

[0033] Specifically, according to one aspect of the present application, after the first registration request message is received, the network registration state associated with the second identifier is set to an idle state or a deregistered state.

[0034] Specifically, according to one aspect of the present application, a second message is received through a first identifier, the second message is a NAS message, a container in the second message carries a third message for the second identifier, and the third message is a NAS message.

[0035] Specifically, according to one aspect of the present application, a fourth registration request message is sent, and the fourth registration request message is a NAS message; the fourth registration request message includes the first identifier; the fourth registration request message indicates that communication with the network through the second identifier is restored or is about to be restored.

[0036] Specifically, according to one aspect of the present application, the first node is an Internet of Things terminal.

[0037] Specifically, according to one aspect of the present application, the first node is a user equipment.

[0038] Specifically, according to one aspect of the present application, the first node is an access network device.

[0039] Specifically, according to one aspect of the present application, the first node is a vehicle-mounted terminal.

[0040] Specifically, according to one aspect of the present application, the first node is an aircraft.

[0041] Specifically, according to one aspect of the present application, the first node is a mobile phone.

[0042] The present application discloses a first node used for wireless communication, comprising:

[0043] A first transmitter sends a first registration request message, where the first registration request message is a NAS message, the first registration request message includes a first identifier, and an abnormality occurs in the communication between the first registration request message and the network through a second identifier;

[0044] The first identifier and the second identifier both identify the first node; the first identifier and the second identifier are both globally unique identifiers; and the first identifier and the second identifier are configured by fields with the same name in a NAS message.

[0045] As an embodiment, compared with the traditional solution, this application has the following advantages:

[0046] When an abnormality occurs in communication with the network through the second identifier, the network can promptly learn that the abnormality has occurred; vice versa, that is, when an abnormality occurs in communication with the network through the first identifier, it can also be promptly learned through the method proposed in this application.

[0047] When the first identifier and the second identifier are configured in the same core network, such as the network of the same operator, the complexity of implementation is particularly low, and coordination between different core networks can be avoided.

[0048] Give the network sufficient processing flexibility for different abnormal situations.

[0049] This is beneficial to ensuring the quality of communication. For example, when an abnormality occurs in the communication with the network through the second identifier, the network can take proactive measures; when recovering from the abnormality or about to recover from the abnormality, the network can also be prepared in advance. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0051] Figure 1 A flowchart of sending a first registration request message according to an embodiment of the present application is shown;

[0052] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present application is shown;

[0053] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0054] Figure 4 A schematic diagram showing a first communication device and a second communication device according to an embodiment of the present application is shown;

[0055] Figure 5 A flow chart showing wireless signal transmission according to an embodiment of the present application is shown;

[0056] Figure 6 A schematic diagram showing a communication scenario according to an embodiment of the present application is shown;

[0057] Figure 7 A schematic diagram showing an abnormality in which a first registration request message relies on communicating with a network through a second identifier according to an embodiment of the present application;

[0058] Figure 8 A schematic diagram showing an abnormality in which a first registration consent message relies on communicating with a network through a second identifier according to an embodiment of the present application;

[0059] Fig. 9 A schematic diagram showing that a fourth registration request message indicates that communication with a network through the second identifier is restored or is about to be restored according to an embodiment of the present application;

[0060] Fig.10 The following is a schematic diagram illustrating a processing device used in a first node according to an embodiment of the present application.

[0061] Implementation

[0062] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, in the absence of conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily.

[0063] Example 1

[0064] Embodiment 1 illustrates a flowchart of sending a first registration request message according to an embodiment of the present application, as shown in the attached Figure 1 Attached Figure 1In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.

[0065] In Embodiment 1, the first node in the present application sends a first registration request message in step 101.

[0066] Among them, the first registration request message is a NAS message, the first registration request message includes a first identifier, the first registration request message relies on communication with the network through a second identifier and an exception occurs; the first identifier and the second identifier both identify the first node; the first identifier and the second identifier are both globally unique identifiers; the first identifier and the second identifier are configured by fields with the same name in the NAS message.

[0067] As an embodiment, the first node is a UE (User Equipment).

[0068] As an embodiment, the first node refers to a communication device composed of hardware such as a baseband, a radio frequency, and at least two SIM cards.

[0069] As an embodiment, when the first identifier and the second identifier are used for communication, at least part of the hardware resources are shared.

[0070] As an embodiment, when the first identifier and the second identifier are used for communication, at least part of the cache is shared.

[0071] As an embodiment, in a scenario where two identifiers are used, for example, two SIM numbers, communication with the network through each identifier is usually completely independent, especially at the NAS level, and at most only some simple mechanisms are supported to avoid possible conflicts between communication with the network through the two identifiers, so the effect achieved is very limited; there is currently no research on the scenario where an abnormality occurs when communicating with the network through one identifier, resulting in slow recovery and the network being unable to understand it in time, leading to a series of problems including waste of resources and decreased communication quality; the method proposed in the present application can solve the above problems at the NAS level in a timely manner through communication with the network through another identifier, so that the network can understand the abnormality as soon as possible, so that measures can be taken as soon as possible to restore the connection or release resources; this also has the advantage of simple implementation when the two identifiers, that is, the first identifier and the second identifier, belong to the same network and the same operator; at the same time, in the method proposed in the present application, relative independence is still maintained in communicating with the network through different identifiers, and the complexity of implementation is not increased, and the implementation is very flexible.

[0072] As an embodiment, the first node is in an RRC connected state.

[0073] As an embodiment, the first node is in an RRC connected state for the first identifier.

[0074] As an embodiment, the first node is in an RRC connected state for the second identifier.

[0075] As an embodiment, the first node establishes two RRC connections.

[0076] As an embodiment, the RRC connection established by the first node through the first identifier is a first RRC connection state.

[0077] As an embodiment, the RRC connection established by the first node through the second identifier is a second RRC connection state.

[0078] As an embodiment, the RRC connection established by the first node using the first identifier is a first RRC connection state.

[0079] As an embodiment, the RRC connection established by the first node using the second identifier is a second RRC connection state.

[0080] As an embodiment, the message requesting to establish the first RRC connection indicates the first identifier.

[0081] As an embodiment, the UE identifier included in the message requesting to establish the first RRC connection is or belongs to the first identifier.

[0082] As an embodiment, the message requesting to establish the first RRC connection includes partial bits of the first identifier.

[0083] As an embodiment, the message requesting to establish the first RRC connection includes a part of the TMSI included in the first identifier.

[0084] As an embodiment, the message requesting to establish the first RRC connection includes the first part of the TMSI included in the first identifier.

[0085] As an embodiment, the message requesting to establish the second RRC connection indicates the second identifier.

[0086] As an embodiment, the UE identifier included in the message requesting to establish the second RRC connection is or belongs to the second identifier.

[0087] As an embodiment, the message requesting to establish the second RRC connection includes partial bits of the second identifier.

[0088] As an embodiment, the message requesting to establish the second RRC connection includes a part of the TMSI (Temporary Mobile Subscriber Identity) included in the second identifier.

[0089] As an embodiment, the message requesting to establish the second RRC connection includes the first part of the TMSI included in the second identifier.

[0090] As an embodiment, after each successful completion of the RRC establishment process, an RRC connection is established.

[0091] As an embodiment, the TMSI includes 5G-S-TMSI.

[0092] As an embodiment, the TMSI includes NG-5G-S-TMSI.

[0093] As an embodiment, the TMSI includes 6G-S-TMSI.

[0094] As an embodiment, the TMSI includes NG-6G-S-TMSI.

[0095] As an embodiment, when the first RRC connection is established, a first SRB1 is established.

[0096] As an embodiment, when the second RRC connection is established, a second SRB1 is established.

[0097] As an embodiment, when the first RRC connection is established, a first SRB2 is established.

[0098] As an embodiment, when the second RRC connection is established, a second SRB2 is established.

[0099] As an embodiment, along with the establishment of the first RRC connection, a first SRB1 is established.

[0100] As an embodiment, along with the establishment of the first RRC connection, a first SRB2 is established.

[0101] As an embodiment, along with the establishment of the second RRC connection, a second SRB1 is established.

[0102] As an embodiment, along with the establishment of the second RRC connection, a second SRB2 is established.

[0103] As an embodiment, the first RRC connection is initiated and established by the NAS of the first node for the first identifier or the sub-identifier included in the first identifier; the second RRC connection is initiated and established by the NAS of the first node for the second identifier or the sub-identifier included in the second identifier.

[0104] As an embodiment, the first RRC connection is initiated by the NAS of the first node associated with the first identifier; the second RRC connection is initiated by the NAS of the first node associated with the second identifier.

[0105] As a sub-embodiment of this embodiment, the NAS associated with the first identifier and the NAS associated with the second identifier are different instances of the NAS protocol.

[0106] As an embodiment, the meaning of the first RRC connection includes: parameters configured during the process of establishing the first RRC connection.

[0107] As an embodiment, the meaning of passing through the first RRC connection includes: passing through the wireless bearer configured in the first RRC connection.

[0108] As an embodiment, the meaning of the first RRC connection includes: the first SRB1 configured through the first RRC connection.

[0109] As a sub-embodiment of this embodiment, the establishment of the first RRC connection is to configure the first SRB1.

[0110] As an embodiment, in the art, when a node enters the RRC connected state, it is necessary to establish SRB1.

[0111] As an embodiment, the meaning of the first RRC connection includes: the first SRB2 configured through the first RRC connection.

[0112] As an embodiment, the meaning of the second RRC connection includes: parameters configured during the process of establishing the second RRC connection.

[0113] As an embodiment, the meaning of passing through the second RRC connection includes: passing through the wireless bearer configured in the second RRC connection.

[0114] As an embodiment, the meaning of the second RRC connection includes: the second SRB1 configured through the second RRC connection.

[0115] As an embodiment, the meaning of the second RRC connection includes: the second SRB2 configured through the second RRC connection.

[0116] As an embodiment, the first SRB1 and the second SRB1 both belong to SRB1.

[0117] As an embodiment, the first SRB1 and the second SRB1 use different encryption keys.

[0118] As an embodiment, the first SRB1 and the second SRB1 correspond to different PDCP entities.

[0119] As an embodiment, the first SRB1 cannot be used by sending and receiving the second identifier.

[0120] As an embodiment, the second SRB1 cannot be used by sending and receiving the first identifier.

[0121] As an embodiment, the first SRB2 cannot be used by sending and receiving the second identifier.

[0122] As an embodiment, the second SRB2 cannot be used by sending and receiving the first identifier.

[0123] As an embodiment, the GUTI (Globally Unique Temporary UE Identity) configured in the first connection established between the first node and the core network is the first identifier.

[0124] As a sub-embodiment of this embodiment, the first identifier is configured by a registration approval message.

[0125] As a sub-embodiment of this embodiment, the second identifier is configured by a configuration update command.

[0126] As a sub-embodiment of this embodiment, the second identifier is configured by the 5G-GUTI field of the NAS message.

[0127] As a sub-embodiment of this embodiment, the second identifier is configured by the 6G-GUTI field of the NAS message.

[0128] As a sub-embodiment of this embodiment, the first node establishes the first connection by initiating a registration process.

[0129] As a sub-embodiment of this embodiment, only after the first connection is established can the first node use the service provided by the core network through the first identifier.

[0130] As an embodiment, the GUTI (Globally Unique Temporary UE Identity) configured in the second connection established between the first node and the core network is the second identifier.

[0131] As a sub-embodiment of this embodiment, the second identifier is configured by a registration approval message.

[0132] As a sub-embodiment of this embodiment, the second identifier is configured by a configuration update command.

[0133] As a sub-embodiment of this embodiment, the second identifier is configured by the 5G-GUTI field (field, field / domain) of the NAS message.

[0134] As a sub-embodiment of this embodiment, the second identifier is configured by the 6G-GUTI field of the NAS message.

[0135] As a sub-embodiment of this embodiment, the first node establishes the second connection by initiating a registration process.

[0136] As a sub-embodiment of this embodiment, only after the second connection is established can the first node use the service provided by the core network through the second identifier.

[0137] As an embodiment, the first node cannot communicate with the core network through the second connection using the first identifier.

[0138] As an embodiment, the first node cannot communicate with the core network through the first connection using the second identifier.

[0139] As an embodiment, the modulus value of the first identifier is used to determine the first paging occasion.

[0140] As an embodiment, the modulus value of the first identifier is used to determine the subframe of the first paging.

[0141] As an embodiment, the modulus value of the second identifier is used to determine the second paging occasion.

[0142] As an embodiment, the modulus value of the second identifier is used to determine the subframe of the second paging.

[0143] As an embodiment, the modulus value of the sub-identifier of the first identifier is used to determine the first paging occasion.

[0144] As an embodiment, the modulus value of the sub-identifier of the first identifier is used to determine the subframe of the first paging.

[0145] As an embodiment, the modulus value of the sub-identifier of the second identifier is used to determine the second paging occasion.

[0146] As an embodiment, the modulus value of the sub-identifier of the second identifier is used to determine the subframe of the second paging.

[0147] As an embodiment, the first node receives paging for the first identifier on the paging occasion and paging subframe determined by the first identifier.

[0148] As a sub-embodiment of this embodiment, the paging for the first identifier refers to that the paging message sent by the core network to the wireless access network indicates the first identifier.

[0149] As an embodiment, the first node receives paging for the second identifier on the paging occasion and paging subframe determined by the second identifier.

[0150] As a sub-embodiment of this embodiment, the paging for the second identifier refers to that the paging message sent by the core network to the wireless access network indicates the second identifier.

[0151] As an embodiment, the mobility flag carried by the first node in the registration request message for the first connection established in the core network is the first identifier.

[0152] As a sub-embodiment of this embodiment, the 5GS mobile identity field in the registration request message carries the first identifier.

[0153] As a sub-embodiment of this embodiment, the name in the registration request message includes a mobileidentity field carrying the first identifier.

[0154] As a sub-embodiment of this embodiment, the 6GS mobile identity field in the registration request message carries the first identifier.

[0155] As an embodiment, the mobility flag carried by the first node in the registration request message for the second connection established in the core network is the second identifier.

[0156] As a sub-embodiment of this embodiment, the 5GS mobile identity field in the registration request message carries the second identifier.

[0157] As a sub-embodiment of this embodiment, the name in the registration request message includes a mobileidentity field carrying the second identifier.

[0158] As a sub-embodiment of this embodiment, the 6GS mobile identity field in the registration request message carries the second identity.

[0159] As an embodiment, the core network of the 5G network includes or is referred to as 5GS.

[0160] As an embodiment, the core network of the 6G network includes or is called 6GS.

[0161] As an embodiment, the first identifier and the second identifier are configured by a protocol entity with the same name.

[0162] As an embodiment, the first identifier and the second identifier are identifiers of the same protocol layer.

[0163] As an embodiment, the first identifier and the second identifier include the same number of bits.

[0164] As an embodiment, the first identifier is a SUCI (Subscription Concealed Identifier); the second identifier is another SUCI.

[0165] As an embodiment, the first identifier corresponds to a SUCI (Subscription Concealed Identifier); the second identifier corresponds to another SUCI.

[0166] As an embodiment, the first identifier is a 5G-GUTI; the second identifier is another 5G-GUTI.

[0167] As an embodiment, the first identifier is a 6G-GUTI; the second identifier is another 6G-GUTI.

[0168] As an embodiment, the first identifier is a GUTI; the second identifier is another GUTI.

[0169] As an embodiment, the first identifier is an IMEI (International Mobile station Equipment Identity); the second identifier is another IMEI.

[0170] As an embodiment, the first identifier is an IMEISV (International Mobile station Equipment Identity and Software Version number); the second identifier is another IMEISV.

[0171] As an embodiment, the first identifier is a 5G-S-TMSI (5G-S-Temporary MobileSubscriber Identity); the second identifier is another 5G-S-TMSI.

[0172] As an embodiment, the first identifier is a 6G-S-TMSI; the second identifier is another 6G-S-TMSI.

[0173] As an embodiment, the first identifier is an EUI-64 (Extended Unique Identifier 64); the second identifier is another EUI-64.

[0174] As an embodiment, the first identifier and the second identifier each include at least 16 bits.

[0175] As an embodiment, the first identifier and the second identifier each include at most 36 bits.

[0176] As an embodiment, the first identifier and the second identifier each include at most 72 bits.

[0177] As an embodiment, the first identifier and the second identifier each include at most 96 bits.

[0178] As an embodiment, the first identifier and the second identifier each include at most 256 bits.

[0179] As an embodiment, any parameter in the present application may be either configured by the network or generated by the first node according to an internal algorithm, such as randomly.

[0180] As an example, the value of any parameter in the present application, including but not limited to the value of a timer and the value of a counter, is limited unless otherwise stated.

[0181] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 1024 times of 65536.

[0182] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 65536 or 65535.

[0183] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 1024.

[0184] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 640 or 320.

[0185] As an embodiment, the present application is directed to NR.

[0186] As an embodiment, the present application is directed to wireless communication networks after NR.

[0187] As an embodiment, the serving cell refers to the cell where the UE resides. Performing a cell search includes the UE searching for a suitable cell of the selected PLMN (Public Land Mobile Network) or SNPN (Stand-alone Non-Public Network), selecting the suitable cell to provide available services, and monitoring the control channel of the suitable cell. This process is defined as residing on the cell; that is, a residing cell is the serving cell of the UE relative to the UE. Residing on a cell in the RRC idle state or the RRC inactive state has the following benefits: it enables the UE to receive system messages from the PLMN or SNPN; after registration, if the UE wishes to establish an RRC connection or continue a suspended RRC connection, the UE can do so by performing initial access on the control channel of the residing cell; the network can page the UE; and the UE can receive ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert System) notifications.

[0188] As an embodiment, for a UE in an RRC connected state that is not configured with CA / DC (carrier aggregation / dual connectivity), there is only one service cell including a primary cell. For a UE in an RRC connected state that is configured with CA / DC (carrier aggregation / dual connectivity), the service cell is used to indicate a set of cells including a special cell (SpCell) and all cells from the small cell. The primary cell (Primary Cell) is an MCG (Master Cell Group) cell that operates on the main frequency. The UE performs an initial connection establishment process or initiates connection reconstruction on the primary cell. For dual connection operations, the special cell refers to the PCell (Primary Cell) of the MCG or the PSCell (Primary SCGCell) of the SCG (Secondary Cell Group); if it is not a dual connection operation, the special cell refers to the PCell.

[0189] As an embodiment, the operating frequency of the SCell (Secondary Cell) is a secondary frequency.

[0190] As an example, individual contents of an information element are referred to as fields.

[0191] As an embodiment, MR-DC (Multi-Radio Dual Connectivity) refers to dual connectivity between E-UTRA and NR nodes, or dual connectivity between two NR nodes.

[0192] As an embodiment, in MR-DC, the wireless access node that provides the control plane connection to the core network is the master node, which may be a master eNB, a master ng-eNB, or a master gNB.

[0193] As an embodiment, MCG refers to a group of service cells associated with a master node in MR-DC, including SpCells, and may also, optionally, include one or more SCells.

[0194] As an embodiment, PCell is the SpCell of MCG.

[0195] As an embodiment, the PSCell is the SpCell of the SCG.

[0196] As an embodiment, in MR-DC, the control plane connection to the core network is not provided, and the radio access node that provides additional resources to the UE is a slave node. The slave node can be an en-gNB, a slave ng-eNB or a slave gNB.

[0197] As an embodiment, in MR-DC, a group of service cells associated with a slave node is a SCG (secondary cell group), including a SpCell and, optionally, one or more SCells.

[0198] As an embodiment, the SpCell is a PCell or the SpCell is a PSCell.

[0199] As an embodiment, the RRC information block refers to an information block (information element) in an RRC message.

[0200] As an embodiment, SSB may be referred to as SS\PBCH, or SS block.

[0201] As an embodiment, L1 is Layer-1 or physical layer.

[0202] As an embodiment, the first node is not configured with DC.

[0203] As an embodiment, the first node is not configured with CA.

[0204] As an embodiment, the first node is configured with DC and / or CA.

[0205] As an embodiment, the first node supports multi-SIM communication.

[0206] As an embodiment, the SIM includes a USIM (Universal Subscriber Identity Module).

[0207] As an embodiment, the first node supports MUSIM (Multi-Universal Subscriber Identity Module) communication.

[0208] As an embodiment, the first node uses MUSIM feature.

[0209] As an embodiment, one RRC information block may include one or more RRC information blocks.

[0210] As an embodiment, an RRC information block may not include any RRC information block, but only include at least one parameter.

[0211] As an embodiment, the radio bearer includes at least a signaling radio bearer and a data radio bearer.

[0212] As an embodiment, the radio bearer is a service or an interface of a service provided by the PDCP layer to a higher layer.

[0213] As a sub-embodiment of this embodiment, the higher layer includes one of the RRC layer, NAS, and SDAP layer.

[0214] As an embodiment, the signaling radio bearer is a service or an interface of services provided by PDCP to a higher layer.

[0215] As a sub-embodiment of this embodiment, the higher layer includes the RRC layer, at least the former in the NAS.

[0216] As an embodiment, the data radio bearer is a service or an interface of services provided by PDCP to a higher layer.

[0217] As a sub-embodiment of this embodiment, the higher layer includes the SDAP layer, at least the former in NAS.

[0218] As an embodiment, the first node sends the first registration request message through the first identifier.

[0219] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: sending the first registration request message through the first RRC connection.

[0220] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: sending the first registration request message through the first connection.

[0221] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: sending the first registration request message through the first SRB1.

[0222] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: sending the first registration request message through the first SRB2.

[0223] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: the first registration request message is sent for the first identifier.

[0224] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: the first registration request message is sent through the connection identified by the first identifier.

[0225] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: sending the first registration request message through a SIM card corresponding to the first identifier.

[0226] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: not sending the first registration request message through the second RRC connection.

[0227] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: not sending the first registration request message through the second connection.

[0228] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: not sending the first registration request message through the second SRB1.

[0229] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: not sending the first registration request message through the second SRB2.

[0230] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: the first registration request message is a registration request of the first identifier.

[0231] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: the first registration request message includes the first identifier.

[0232] As an embodiment, the meaning of sending the first registration request message through the first identifier includes: the 5GS mobile identity of the first registration request message includes the first identifier.

[0233] As an embodiment, the 5GS mobile identity of the first registration request message includes the first identifier.

[0234] As an embodiment, the 6GS mobile identity of the first registration request message includes the first identifier.

[0235] As an embodiment, the name of the first registration request message includes a mobile identity field including the first identifier.

[0236] As an embodiment, the first identifier is different from the second identifier.

[0237] As an embodiment, the sentence “the first identifier and the second identifier are different” means that the first identifier and the second identifier have the same number of bits but different bits.

[0238] As an embodiment, the meaning of the sentence that the first identifier and the second identifier are different is: the first identifier and the second identifier both include n bits, n is a positive integer, the i-th bit of the first identifier is different from the i-th bit of the second identifier; i is a positive integer not greater than n.

[0239] As an embodiment, the first identifier and the second identifier are respectively stored in variables with the same name as the first node.

[0240] As an embodiment, the first identifier and the second identifier are configured by fields with the same name in a NAS message.

[0241] As a sub-embodiment of this embodiment, the first identifier and the second identifier are configured by two NAS messages respectively.

[0242] As a sub-embodiment of this embodiment, the fields with the same name are fields with the same name and at the same level in a NAS message with the same name.

[0243] As a sub-embodiment of this embodiment, the same level means that they are all sub-items of this message, or they are all grandchildren of this message, and so on.

[0244] As a sub-embodiment of this embodiment, the NAS messages for configuring the first identifier and the second identifier are both registration approval messages.

[0245] As an embodiment, the first node maintains a registration status with the core network through the first identifier and the second identifier respectively.

[0246] As an embodiment, the first node and the core network perform separate registration processes, the first identifier of the first node is configured in one registration process of the separate registration processes, and the second identifier of the first node is configured in another registration process of the separate registration processes.

[0247] As an embodiment, a registration process includes sending a registration request message and receiving a registration approval message.

[0248] As an embodiment, the first identifier and the second identifier are both valid identifiers.

[0249] As an embodiment, configuring the second identifier is not for the purpose of updating or replacing the first identifier.

[0250] As an embodiment, configuring the first identifier is not for the purpose of updating or replacing the second identifier.

[0251] As an embodiment, the first identifier is a globally unique identifier of the first node; the second identifier is another globally unique identifier of the first node.

[0252] As a sub-embodiment of this embodiment, the globally unique identifier includes a permanent equipment identifier (permanent equipment identifier).

[0253] As a sub-embodiment of this embodiment, the global unique identifier is at the subscription user level.

[0254] As a sub-embodiment of this embodiment, the globally unique identifier is at the core network level.

[0255] As a sub-embodiment of this embodiment, the globally unique identifier is allocated by the core network.

[0256] As a sub-embodiment of this embodiment, the globally unique identifier is or is included in a SIM card fixed in the first node.

[0257] As a sub-embodiment of this embodiment, the globally unique identifier is or includes a fixed identifier.

[0258] As a sub-embodiment of this embodiment, the globally unique identifier is or includes one determined by the first node itself.

[0259] As a sub-embodiment of this embodiment, the globally unique identifier is or includes the identifier carried in the registration request information sent by the first node.

[0260] As an embodiment, the NAS message is a message in the NAS protocol.

[0261] As an embodiment, the NAS message is a message generated by the NAS and sent to the NAS of the other end.

[0262] As an embodiment, the NAS message is a message between the UE and the core network.

[0263] As an embodiment, the first registration request is or includes REGISTRATION REQUEST.

[0264] As an embodiment, the first registration request includes a registration type.

[0265] As a sub-embodiment of this embodiment, the registration type included in the first registration request depends on an abnormality in the communication with the network through the second identifier.

[0266] As a sub-embodiment of this embodiment, the registration type included in the first registration request indicates that an abnormality occurs in the communication with the network through the second identifier.

[0267] As a sub-embodiment of this embodiment, the registration type included in the first registration request is mobility registration update.

[0268] As a sub-embodiment of this embodiment, the registration type included in the first registration request is initial registration.

[0269] As an embodiment, the first registration request includes the first identifier.

[0270] As an embodiment, the first registration request includes a tracking area identifier.

[0271] As an embodiment, the first registration request includes a tracking area identifier for the second identifier.

[0272] As an embodiment, the first registration request includes network slice information.

[0273] As an embodiment, the first registration request includes an update type.

[0274] As an embodiment, the first registration request includes DRX information.

[0275] As an embodiment, the first registration request includes a PLMN identifier.

[0276] As an embodiment, the first registration request includes a PLMN identifier for the second identifier.

[0277] As an embodiment, the first registration request message is sent as a response to an abnormality in communication with the network through the second identifier.

[0278] As an embodiment, the first registration request message indicates that an abnormality occurs in the communication with the network through the second identifier.

[0279] As an embodiment, the sentence that the first registration request message depends on an abnormality in communication with the network through the second identifier includes: sending the first registration request message as a response to an abnormality in communication with the network through the second identifier.

[0280] As an embodiment, the sentence that the first registration request message relies on an abnormality in communication with the network through the second identifier includes: the first registration request message indicates that an abnormality occurs in communication with the network through the second identifier.

[0281] As an embodiment, the first registration request message is triggered by an abnormality in the communication between the second identifier and the network.

[0282] As an embodiment, the first identifier and the second identifier are different.

[0283] As an embodiment, the first identifier and the second identifier include an equal number of bits.

[0284] As an embodiment, the first identifier and the second identifier are equal in size.

[0285] As an embodiment, the first identifier is a GUTI; the second identifier is another GUTI.

[0286] As an embodiment, the first identifier is a 5G-GUTI.

[0287] As a sub-embodiment of this embodiment, the second identifier is another 5G-GUTI.

[0288] As an embodiment, the first identifier corresponds to a first NAS signaling connection; the second identifier corresponds to a second NAS signaling connection.

[0289] As an embodiment, the first NAS signaling connection is or belongs to the first connection.

[0290] As an embodiment, the second NAS signaling connection is or belongs to the second connection.

[0291] As an embodiment, the NAS signaling connection is a signaling connection between the UE and the core network.

[0292] As an embodiment, the NAS signaling connection is a signaling connection between the UE and the AMF of the core network.

[0293] As an embodiment, the phrase "an abnormality occurs in communication with the network through the second identifier" includes: an RRC connection associated with the second identifier fails.

[0294] As a sub-embodiment of this embodiment, the second RRC connection is released.

[0295] As a sub-embodiment of this embodiment, the RRC idle state is entered for the second identifier.

[0296] As an embodiment, the phrase "communication with the network through the second identifier is abnormal" means that the second connection fails.

[0297] As an embodiment, the phrase "abnormality occurs in communication with the network through the second identifier" includes: deregistration of the second identifier is unsuccessful.

[0298] As a sub-embodiment of this embodiment, a DEREGISTRATION REQUEST cannot be successfully sent in the communication with the network through the second identifier.

[0299] As a sub-embodiment of this embodiment, no DEREGISTRATION ACCEPT is received in the communication with the network through the second identifier.

[0300] As an embodiment, the phrase "communication with the network through the second identifier is abnormal" includes: communication with the network through the second identifier is overheated.

[0301] As an embodiment, the phrase "communication with the network through the second identifier is abnormal" means that the hardware corresponding to the second identifier is removed or is no longer available.

[0302] As a sub-embodiment of this embodiment, the hardware corresponding to the second identifier is removed, including: the SIM card corresponding to the second identifier is removed.

[0303] As a sub-embodiment of this embodiment, the hardware corresponding to the second identifier being removed includes: a SIM card corresponding to the second identifier is abnormal.

[0304] As an embodiment, the phrase "communication with the network through the second identifier is abnormal" means that at least one of the hardware corresponding to the second identifier fails.

[0305] As a sub-embodiment of this embodiment, the SIM card corresponding to the second identifier cannot be identified.

[0306] As an embodiment, the abnormality in the communication with the network through the second identifier refers to: being unable to communicate with the network through the second identifier.

[0307] As an embodiment, the abnormality in the communication with the network through the second identifier is or includes: the inability of the first node to communicate with the network through the second identifier indicates that the abnormality in the communication with the network through the second identifier occurs.

[0308] As an embodiment, the abnormality occurring in the communication with the network through the second identifier is or includes: an unrecoverable abnormality associated with the second identifier of the first node.

[0309] As an embodiment, the abnormality in the communication with the network through the second identifier is or includes: an abnormality associated with the second identifier of the first node that cannot be recovered within a given time.

[0310] As an embodiment, after the first registration request message is received, the network registration state associated with the second identifier is set to an idle state.

[0311] As a sub-embodiment of this embodiment, in the core network, the network registration state associated with the second identifier is set to an idle state.

[0312] As a sub-embodiment of this embodiment, when the first registration request message is received, the deregistration timer associated with the second identifier has not expired.

[0313] As an embodiment, after the first registration request message is received, the network registration state associated with the second identifier is set to a deregistration state.

[0314] As a sub-embodiment of this embodiment, in the core network, the network registration state associated with the second identifier is set to a deregistration state.

[0315] As a sub-embodiment of this embodiment, when the first registration request message is received, the deregistration timer associated with the second identifier has not expired.

[0316] As an embodiment, after the first registration request message is received, the second identifier becomes invalid.

[0317] As an embodiment, after the first registration request message is received, the second identifier is set to a de-registered state.

[0318] As an embodiment, after the first registration request message is received, the context associated with the second identifier is released by AMF.

[0319] As an embodiment, after the first registration request message is received, the resources for the second identifier are released by the AMF.

[0320] As an embodiment, after the first registration request message is received, the core network terminates the charging for the second identification communication.

[0321] As an embodiment, after the first registration request message is received, the core network notifies the counterpart node that communicates with the second identifier.

[0322] As an embodiment, after the first registration request message is received, the core network deletes the cached data for the second identifier.

[0323] As a sub-embodiment of this embodiment, the data in the cache includes application layer data.

[0324] As a sub-embodiment of this embodiment, the AMF notifies the gateway to delete the data in the cache.

[0325] As an embodiment, the core network includes AMF.

[0326] As an embodiment, the core network includes SMF (session management function).

[0327] As an embodiment, communicating with the network through the first identifier refers to communication between the first node and the core network through the first identifier.

[0328] As an embodiment, communicating with the network through the first identifier refers to communication between the first node and the core network through the second identifier.

[0329] Example 2

[0330] Embodiment 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in the attached Figure 2 shown.

[0331] Attached Figure 2A diagram of a network architecture 200 for 5G NR, LTE (Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced) systems is illustrated. The 5G NR or LTE network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 may include one or more UEs (User Equipment) 201, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet-switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol terminations toward UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). gNB 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (transmitting receiving node), or some other suitable term. gNB 203 provides an access point to 5GC / EPC 210 for UE 201. Examples of UE 201 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, cars, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term.gNB203 is connected to 5GC / EPC210 via the S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF213. MME / AMF / SMF211 is the control node that handles signaling between UE201 and 5GC / EPC210. ​​In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF212, which itself is connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and packet-switched streaming services.

[0332] As an embodiment, the first node in the present application is UE201.

[0333] As an embodiment, the base station of the second node in the present application is gNB203.

[0334] As an embodiment, the wireless link from the UE201 to the NR Node B is an uplink.

[0335] As an embodiment, the wireless link from the NR Node B to UE201 is a downlink.

[0336] As an embodiment, the UE 201 supports relay transmission.

[0337] As an embodiment, the UE 201 includes a mobile phone.

[0338] As an embodiment, the UE 201 is a vehicle including a car.

[0339] As an embodiment, the gNB203 is a macrocellular base station.

[0340] As an embodiment, the gNB203 is a micro cell base station.

[0341] As an embodiment, the gNB203 is a pico cell base station.

[0342] As an embodiment, the gNB203 is a flying platform device.

[0343] As an embodiment, the gNB203 is a satellite device.

[0344] Example 3

[0345] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture of the control plane 300 for a first node (UE, gNB) and a second node (gNB, UE), or between two UEs is shown in three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to as PHY301 herein. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first node and the second node and the two UEs through PHY301. The L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides support for inter-zone mobility of the first node between the second node. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between the first nodes. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layer using RRC signaling between the second node and the first node. The PC5-S (PC5 Signaling Protocol) sublayer 307 is responsible for processing the signaling protocol of the PC5 interface. The radio protocol architecture of the user plane 350 includes Layer 1 (L1 layer) and Layer 2 (L2 layer). The radio protocol architecture for the first node and the second node in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS flows and data radio bearers (DRBs) to support the diversity of services. SRB can be regarded as a service or interface provided by the PDCP layer to a higher layer, such as the RRC layer. In the NR system, SRBs include SRB1, SRB2, and SRB3, which are used to transmit different types of control signaling. SRB is a bearer between the UE and the access network, and is used to transmit control signaling including RRC signaling between the UE and the access network. SRB1 has a special meaning for the UE. After each UE establishes an RRC connection, there will be SRB1 for transmitting RRC signaling. Most of the signaling is transmitted through SRB1. If SRB1 is interrupted or cannot be used, the UE must perform RRC reconstruction; each RRC connection establishes an SRB1. SRB2 is generally only used to transmit NAS signaling or signaling related to security; each RRC connection establishes an SRB2. The UE may not configure SRB3. Except for emergency services, the UE must establish an RRC connection with the network for subsequent communication. Although not shown, the first node may have several upper layers above the L2 layer 355. In addition, it also includes a network layer (e.g., IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., remote UE, server, etc.).

[0346] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0347] As an example, Figure 3 The wireless protocol architecture in is applicable to the second node in this application.

[0348] As an embodiment, the first registration request message in the present application is generated by NAS.

[0349] As an embodiment, the first registration approval message in the present application is generated by NAS.

[0350] As an embodiment, the second registration request message in the present application is generated by NAS.

[0351] As an embodiment, the second registration approval message in the present application is generated by NAS.

[0352] As an embodiment, the third registration request message in the present application is generated by NAS.

[0353] As an embodiment, the third registration approval message in the present application is generated by NAS.

[0354] As an embodiment, the fourth registration request message in the present application is generated by NAS.

[0355] As an embodiment, the first message in the present application is generated in NAS.

[0356] As an embodiment, the second message in the present application is generated by NAS.

[0357] As an embodiment, the third message in the present application is generated by NAS.

[0358] Example 4

[0359] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application, as shown in the attached figure. Figure 4 shown. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

[0360] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, and may optionally also include a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and an antenna 452.

[0361] The second communication device 410 includes a controller / processor 475 , a memory 476 , a receiving processor 470 , a transmitting processor 416 , and may optionally also include a multi-antenna receiving processor 472 , a multi-antenna transmitting processor 471 , a transmitter / receiver 418 and an antenna 420 .

[0362] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, the upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the functionality of the L2 (Layer-2) layer. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for the retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0363] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program codes and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

[0364] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission function at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.

[0365] In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the reception function at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 storing program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0366] As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 apparatus at least: sends a first registration request message, the first registration request message is a NAS message, the first registration request message includes a first identifier, the first registration request message relies on communication with the network through a second identifier and an abnormality occurs; wherein the first identifier and the second identifier both identify the first node; the first identifier and the second identifier are both globally unique identifiers; the first identifier and the second identifier are configured by fields with the same name in the NAS message.

[0367] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates an action when executed by at least one processor, the action including: sending a first registration request message, the first registration request message is a NAS message, the first registration request message includes a first identifier, the first registration request message relies on communication with the network through a second identifier and an exception occurs; wherein the first identifier and the second identifier both identify the first node; the first identifier and the second identifier are both globally unique identifiers; the first identifier and the second identifier are configured by fields with the same name in the NAS message.

[0368] As an embodiment, the first communication device 450 corresponds to the first node in this application.

[0369] As an embodiment, the second communication device 410 corresponds to the second node in this application.

[0370] As an embodiment, the first communication device 450 is a UE.

[0371] As an embodiment, the first communication device 450 is a vehicle-mounted terminal.

[0372] As an embodiment, the first communication device 450 is a mobile phone.

[0373] As an embodiment, the second communication device 450 is a relay.

[0374] As an embodiment, the second communication device 410 is a satellite.

[0375] As an embodiment, the second communication device 410 is an aircraft.

[0376] As an embodiment, the second communication device 410 is a base station.

[0377] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the first registration approval message in the present application.

[0378] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the second registration approval message in the present application.

[0379] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the second registration approval message in the present application.

[0380] As an embodiment, the transmitter 454 (including the antenna 452), the transmission processor 468 and the controller / processor 459 are used to send the first registration request message in the present application.

[0381] As an embodiment, the transmitter 454 (including the antenna 452), the transmission processor 468 and the controller / processor 459 are used to send the first registration request message in the present application.

[0382] As an embodiment, the transmitter 454 (including the antenna 452), the transmission processor 468 and the controller / processor 459 are used to send the second registration request message in the present application.

[0383] As an embodiment, the transmitter 454 (including the antenna 452), the transmission processor 468 and the controller / processor 459 are used to send the third registration request message in the present application.

[0384] As an embodiment, the transmitter 454 (including the antenna 452), the transmit processor 468 and the controller / processor 459 are used to send the first message in the present application.

[0385] As an embodiment, the transmitter 454 (including the antenna 452), the transmit processor 468 and the controller / processor 459 are used to send the second message in the present application.

[0386] As an embodiment, the transmitter 454 (including the antenna 452), the transmission processor 468 and the controller / processor 459 are used to send the fourth registration request message in the present application.

[0387] Example 5

[0388] Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 Attached Figure 5 In the example, U01 corresponds to the first node of the present application. It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in the present application, wherein the steps in F51 and F52 are optional.

[0389] for First node U01 , sending a second registration request message in step S5101; receiving a second registration approval message in step S5102; sending a third registration request message in step S5103; receiving a third registration approval message in step S5104; sending a first registration request message in step S5105; receiving a first registration approval message in step S5106; sending a first message in step S5107; and sending a second message in step S5108.

[0390] for Second node U02 , receiving the second request message in step S5201; sending the second registration approval message in step S5202; receiving the third registration request message in step S5203; sending the third registration approval message in step S5204; receiving the first registration request message in step S5205; sending the first registration approval message in step S5206; receiving the first message in step S5207; receiving the second message in step S5208.

[0391] In Example 5, the first registration request message is a NAS message, the first registration request message includes a first identifier, and an exception occurs in the communication between the first registration request message and the network through the second identifier; wherein the first identifier and the second identifier both identify the first node; the first identifier and the second identifier are both globally unique identifiers; the first identifier and the second identifier are configured by fields with the same name in the NAS message.

[0392] As an embodiment, the second node U02 is a core network node.

[0393] As an embodiment, the second node U02 is the AMF of the core network.

[0394] As an embodiment, the second node U02 is responsible for access and / or mobility association of the core network.

[0395] As an embodiment, the second node U02 is a functional entity of the core network responsible for access and / or mobility association.

[0396] As an embodiment, the first node U01 communicates with the second node U02 via the NAS protocol.

[0397] As an embodiment, when the first node U01 has two identifiers, namely the first identifier and the second identifier, for example, they are the numbers configured when two SIM cards communicate with the network, then the communications through different SIM cards are usually independent. The problem caused by this is that, although the two identifiers, or the two SIM cards belong to the same node, when an abnormality occurs in the communication with the network through the second identifier, the network cannot be notified in a timely and effective manner, resulting in a long interruption of transmission and waste of resources. In the present application, the above-mentioned abnormality is indicated to the network through the first registration request message for the first identifier, which can effectively solve these problems and improve the communication quality of nodes with two identifiers or two SIM cards.

[0398] As an embodiment, the second registration approval message is a response to the second registration request message.

[0399] As an embodiment, the third registration approval message is a response to the third registration request message.

[0400] As an embodiment, the first registration approval message is a response to the first registration request message.

[0401] As an embodiment, step S5102 is after step S5101.

[0402] As an embodiment, step S5104 is after step S5103.

[0403] As an embodiment, step S5101 and step S5103 are not required to have a clear sequence.

[0404] As an embodiment, step S5102 and step S5104 are not required to have a clear sequence.

[0405] As an embodiment, step S5102 and step S5103 are not required to have a clear sequence.

[0406] As an embodiment, step S5101 and step S5104 are not required to have a clear sequence.

[0407] As an embodiment, step S5101 precedes step S5105.

[0408] As an embodiment, step S5102 precedes step S5105.

[0409] As an embodiment, step S5103 precedes step S5105.

[0410] As an embodiment, step S5104 precedes step S5105.

[0411] As an embodiment, step S5106 is after step S5105.

[0412] As an embodiment, step S5108 is after step S5105.

[0413] As an embodiment, step S5108 is after step S5106.

[0414] As an embodiment, step S5107 precedes step S5105.

[0415] As an embodiment, step S5107 is after step S5104.

[0416] As an embodiment, step S5107 is after step S5102.

[0417] As an embodiment, the registration request may be sent multiple times or periodically.

[0418] As an embodiment, there is no dependency between step S5101 and step S5103.

[0419] As an embodiment, the second registration approval message is a feedback of the second registration request message; the second registration approval message configures the first identifier.

[0420] As an embodiment, the third registration approval message is a feedback of the third registration request message; and the third registration request message configures the second identifier.

[0421] As an embodiment, the first identifier and the second identifier are both valid identifiers.

[0422] As an embodiment, the third registration request message is not a sequel to the second registration request message.

[0423] As a sub-embodiment of this embodiment, the third registration request message and the second registration request message do not belong to the same periodic registration process.

[0424] As a sub-embodiment of this embodiment, the third registration request message and the second registration request message are for different NAS signaling connections.

[0425] As a sub-embodiment of this embodiment, the third registration request message and the second registration request message are for the second identifier and the first identifier respectively.

[0426] As a sub-embodiment of this embodiment, the third registration request message is not intended to update the second registration request message.

[0427] As an embodiment, the second registration request message is not a sequel to the third registration request message.

[0428] As a sub-embodiment of this embodiment, the second registration request message and the third registration request message do not belong to the same periodic registration process.

[0429] As a sub-embodiment of this embodiment, the second registration request message and the third registration request message are for different NAS signaling connections.

[0430] As a sub-embodiment of this embodiment, the second registration request message and the third registration request message are for the second identifier and the first identifier respectively.

[0431] As a sub-embodiment of this embodiment, the second registration request message is not intended to update the third registration request message.

[0432] As an embodiment, the second registration request message, the second registration approval message, the third registration request message, and the third registration approval message are NAS messages respectively.

[0433] As an embodiment, the first registration request message is a REGISTRATION REQUEST message.

[0434] As an embodiment, the second registration request message is a REGISTRATION REQUEST message.

[0435] As an embodiment, the third registration request message is a REGISTRATION REQUEST message.

[0436] As an embodiment, the first registration approval message is a REGISTRATIONACCEPT message.

[0437] As an embodiment, the second registration approval message is a REGISTRATIONACCEPT message.

[0438] As an embodiment, the third registration approval message is a REGISTRATIONACCEPT message.

[0439] As an embodiment, the sentence "the first identifier and the second identifier are configured by fields of the same name in a NAS message" means: the first identifier is configured by the second registration approval message.

[0440] As an embodiment, the sentence "the first identifier and the second identifier are configured by fields of the same name in a NAS message" means that the second identifier is configured by the third registration approval message.

[0441] As an embodiment, the sentence "the first identifier and the second identifier are configured by fields with the same name in the NAS message" means: the first identifier is configured by a field named "5GSmobility identity" in the second registration approval message.

[0442] As a sub-embodiment of this embodiment, the second identity is configured by a field named "5GS mobility identity" in the third registration approval message.

[0443] As an embodiment, the sentence "the first identifier and the second identifier are configured by fields with the same name in the NAS message" means: the first identifier is configured by a field named "6GSmobility identity" in the second registration approval message.

[0444] As a sub-embodiment of this embodiment, the second identity is configured by a field named "6GS mobility identity" in the third registration approval message.

[0445] As an embodiment, the sentence "the second registration approval message is configured with the first identifier" means that the second registration approval message is for the first identifier.

[0446] As an embodiment, the sentence "the second registration approval message is configured with the first identifier" means that the second registration approval message is not for the second identifier.

[0447] As an embodiment, the sentence "the second registration approval message configures the first identifier" means that the NAS signaling connection corresponding to or established by the second registration approval message is for the first identifier.

[0448] As an embodiment, the sentence "the second registration approval message is configured with the first identifier" means that the second connection corresponding to or established by the second registration approval message is for the first identifier.

[0449] As an embodiment, the sentence "the third registration approval message is configured with the second identifier" means that the third registration approval message is for the second identifier.

[0450] As an embodiment, the sentence that the third registration approval message is configured with the second identifier means that the third registration approval message is not for the first identifier.

[0451] As an embodiment, the sentence that the third registration approval message configures the second identifier means that the second connection corresponding to or established by the third registration approval message is for the second identifier.

[0452] As an embodiment, the sentence that the third registration approval message configures the second identifier means that the NAS signaling connection corresponding to or established by the third registration approval message is for the second identifier.

[0453] As an embodiment, the sentence “the first registration request message includes a first identifier” means that the first registration request message is for the first identifier.

[0454] As an embodiment, the sentence that the first registration request message includes a first identifier includes: the first registration request message is for or through a NAS signaling connection associated with the first identifier.

[0455] As an embodiment, the sentence “the first registration request message includes the first identifier” means that the first registration request message is for or is associated with a SIM card through the first identifier.

[0456] As an embodiment, after sending a registration request message, receiving a corresponding registration approval message is the prior art in the art.

[0457] As a sub-embodiment of this embodiment, the first registration consent message relies on the abnormality in the communication with the network through the second identifier, which is not a prior art. This method is conducive to the network to promptly handle the abnormality in the communication with the second identifier through communication with the first identifier.

[0458] As an embodiment, the first message indicates that the first identifier and the second identifier are associated.

[0459] As an embodiment, the first node U01 sends the first message by communicating with the network through the first identifier.

[0460] As a sub-embodiment of this embodiment, the first node U01 communicates with the network through the second identifier to send a message indicating that the first identifier is associated with the second identifier.

[0461] As a sub-embodiment of this embodiment, the above method is conducive to the network's verification of the association relationship between the first identifier and the second identifier.

[0462] As an embodiment, the first node U01 sends the first message by communicating with the network through the second identifier.

[0463] As a sub-embodiment of this embodiment, the first node U01 sends a message indicating that the first identifier is associated with the second identifier through communication with the network via the first identifier.

[0464] As a sub-embodiment of this embodiment, the above method is conducive to the network's verification of the association relationship between the first identifier and the second identifier.

[0465] As an embodiment, the phrase "the first identifier and the second identifier are associated" means that the first identifier and the second identifier both identify the first node.

[0466] As an embodiment, the phrase "the first identifier and the second identifier are associated" means that the first identifier and the second identifier are physically co-located.

[0467] As an embodiment, the phrase "the first identifier and the second identifier are associated" means that the first identifier is a primary identifier and the second identifier is a secondary identifier.

[0468] As an embodiment, the phrase "the first identifier and the second identifier are associated" means that the first NAS signaling connection and the second NAS signaling connection are controlled by the same node.

[0469] As an embodiment, the phrase "the first identifier and the second identifier are associated" means that the first node supports coordination with the network communication through the first identifier and the second identifier.

[0470] As an embodiment, the first message is a NAS message.

[0471] As an embodiment, the first message is a REGISTRATION REQUEST message.

[0472] As an embodiment, the first message is a ULNAS transport message.

[0473] As an embodiment, the first registration request message is used to indicate that an abnormality has occurred in the communication with the network through the second identifier instead of other NAS messages. The benefits include: it is conducive to indicating richer registration-related information; the registration request can be configured to be sent periodically, and carrying information indicating that an abnormality has occurred in the communication with the network through the second identifier does not occupy additional signaling resources.

[0474] As an embodiment, after the second node U02 receives the first registration request message, and the first registration request message indicates that an abnormality occurs in the communication with the network through the second identifier, and the first registration request message indicates that the RRC connection associated with the second identifier fails, then the second node U02 suspends sending information through the second identifier to communicate with the network.

[0475] As a sub-embodiment of this embodiment, a container of the first registration approval message includes a NAS message for communicating with the network through the second identifier.

[0476] As a sub-embodiment of this embodiment, the NAS message in the one container of the first registration approval message configures at least one timer in the communication with the network through the second identifier, and expiration of the at least one timer triggers deregistration.

[0477] As an embodiment, after the second node U02 receives the first registration request message, and the first registration request message indicates that an abnormality occurs in the communication with the network through the second identifier and the deregistration of the second identifier is unsuccessful, the second node U02 deletes the second identifier and / or sets the status associated with the second identifier to a deregistration status.

[0478] As an embodiment, after the second node U02 receives the first registration request message, and the first registration request message indicates that an abnormality occurs in the communication with the network through the second identifier, and the communication with the network through the second identifier is overheated, the second node U02 suspends sending information through the second identifier to communicate with the network.

[0479] As an embodiment, after the second node U02 receives the first registration request message, and the first registration request message indicates that an abnormality occurs in the communication with the network through the second identifier because the hardware corresponding to the second identifier is removed or is no longer available, the second node U02 stops sending information through the second identifier to communicate with the network, deletes the second identifier, deletes the context associated with the second identifier, and releases the second connection.

[0480] As an embodiment, after the second node U02 receives the first registration request message, and the first registration request message indicates that the abnormality in the communication with the network through the second identifier is due to a failure of the hardware corresponding to the second identifier, the second node U02 suspends sending information through the second identifier to communicate with the network.

[0481] As an embodiment, the second message is a NAS message, a container in the second message carries a third message for the second identifier, and the third message is a NAS message.

[0482] As an embodiment, the second message is the first registration approval message.

[0483] As an embodiment, the second message is a message other than the first registration approval message.

[0484] As a sub-embodiment of this embodiment, the second message is later than the first registration approval message.

[0485] As an embodiment, the second message is a registration approval message.

[0486] As an embodiment, the second message is a DLNAS transport message.

[0487] As an embodiment, the third message is for the second connection.

[0488] As an embodiment, the third message is for the SIM card corresponding to the second identification pair.

[0489] As an embodiment, the third message is for communication between the SIM card corresponding to the second identification pair and the network.

[0490] As an embodiment, the third message indicates a configuration update.

[0491] As an embodiment, the third message indicates paging.

[0492] As an embodiment, the third message indicates deregistration.

[0493] As an embodiment, the first node U01 sends a fourth registration request message, and the fourth registration request message is a NAS message.

[0494] As a sub-embodiment of this embodiment, the fourth registration request message is a REGISTRATION REQUEST message.

[0495] As a sub-embodiment of this embodiment, the fourth registration request message is sent after the first registration request message.

[0496] As a sub-embodiment of this embodiment, the fourth registration request message is sent after the first registration approval message.

[0497] As a sub-embodiment of this embodiment, the fourth registration request message is sent after the second message.

[0498] As a sub-embodiment of this embodiment, the fourth registration request message includes the first identifier.

[0499] As a sub-embodiment of this embodiment, the meaning of the sentence that the fourth registration request message includes the first identifier includes: the fourth registration request message is for the first identifier.

[0500] As a sub-embodiment of this embodiment, the sentence that the fourth registration request message includes the first identifier means that the fourth registration request message is for the SIM card associated with the first identifier.

[0501] As a sub-embodiment of this embodiment, the sentence "the fourth registration request message includes the first identifier" means that the fourth registration request message is for a connection associated with the first identifier.

[0502] As a sub-embodiment of this embodiment, the sentence that the fourth registration request message includes the first identifier means that the fourth registration request message is for the first connection.

[0503] As a sub-embodiment of this embodiment, the meaning of the sentence that the fourth registration request message includes the first identifier includes: the fourth registration request message is for the first NAS signaling connection.

[0504] As a sub-embodiment of this embodiment, the fourth registration request message indicates that communication with the network through the second identifier is resumed.

[0505] As a sub-embodiment of this embodiment, the fourth registration request message indicates that communication with the network through the second identifier is about to be restored.

[0506] As a sub-embodiment of this embodiment, the advantage of the above method is that it can enable the network to prepare for abnormal recovery in advance, which is conducive to reducing the interruption time of communicating with the network through the second identifier and ensuring the quality of communicating with the network through the second identifier.

[0507] Example 6

[0508] Embodiment 6 illustrates a schematic diagram of a communication scenario according to an embodiment of the present application, as shown in the attached Figure 6 shown.

[0509] As an embodiment, the communication between the first node and the network through the first identifier refers to communication with the core network; the communication between the first node and the network through the second identifier also refers to communication with the core network.

[0510] As a sub-embodiment of this embodiment, the first registration request is a NAS message.

[0511] As an embodiment, the NAS is terminated between the first node and the core network.

[0512] As an embodiment, the NAS message is a message belonging to the NAS layer protocol.

[0513] As an embodiment, the first node communicates with the core network through the first identifier and the second identifier at the same time. During the communication process, an abnormality occurs in the communication with the network through the second identifier.

[0514] As an embodiment, the first node communicates with the network through the first cell via the first identifier; the first node communicates with the network through the first cell via the second identifier.

[0515] As an embodiment, the first node communicates with the network via the first identifier and communicates with the network via the second identifier through the same access network.

[0516] As an embodiment, the first node communicates with the network through the first identifier and communicates with the network through the second identifier both with the same core network.

[0517] As an embodiment, the first node communicates with the network through the first identifier and communicates with the network through the second identifier, both of which are communications with the same AMF.

[0518] As an embodiment, the first node communicates with the network through the first identifier and communicates with the network through the second identifier both with the same unit that manages access and / or mobility.

[0519] As an embodiment, the communicating with the network includes transmitting a NAS message.

[0520] As an embodiment, the communication with the network particularly refers to transmitting NAS messages.

[0521] As an embodiment, the communication with the network means transmitting NAS messages.

[0522] As an embodiment, whether the communication with the network is abnormal is determined by whether the signaling connection is abnormal.

[0523] As an embodiment, whether the communication with the network is abnormal is determined by whether the signaling connection is interrupted.

[0524] As an embodiment, the meaning of abnormality in communicating with the network through the second identifier includes: being unable to receive a NAS message from the core network.

[0525] As an embodiment, the meaning of an abnormality in communicating with the network through the second identifier includes: a NAS message from the core network cannot be successfully sent.

[0526] As an embodiment, the meaning of abnormality in communicating with the network through the second identifier includes: it is impossible to successfully send a NAS message from the core network.

[0527] As an embodiment, the meaning of abnormality in communication with the network through the second identifier includes: communication with the network through the second identifier cannot be restored within a certain time; the certain time is configured by the network or determined by the first node based on implementation.

[0528] As a sub-embodiment of this embodiment, the certain time is equal to the length of several DRX cycles.

[0529] As a sub-embodiment of this embodiment, the certain period of time may be infinite, that is, it can never be restored.

[0530] As a sub-embodiment of this embodiment, the certain time is not shorter than 1 millisecond.

[0531] As a sub-embodiment of this embodiment, the certain time is not shorter than 10 milliseconds.

[0532] As a sub-embodiment of this embodiment, the certain time is not shorter than 1024 milliseconds.

[0533] As a sub-embodiment of this embodiment, the certain time is not shorter than 1024 frames.

[0534] As a sub-embodiment of this embodiment, the certain time is not shorter than a DRX cycle.

[0535] As an embodiment, the meaning of abnormality in communication with the network through the second identifier includes: abnormality in communication with the core network.

[0536] As an embodiment, the meaning of an abnormality in communication with the network through the second identifier includes: an abnormality in AMF communication with the core network.

[0537] As an embodiment, the meaning of abnormality in communication with the network through the second identifier includes: abnormality in communication with a unit that manages access and / or mobility of the core network.

[0538] As an embodiment, it is obvious that when an abnormality occurs in the communication with the network through the second identifier, the first node cannot inform the network of the abnormality through the communication with the network through the second identifier, which will cause a long interruption, affect business transmission, and waste network resources.

[0539] As an embodiment, the service cell of the first node is the first cell; the communication between the first node and the network through the first identifier passes through the first cell; and the communication between the first node and the network through the second identifier passes through the first cell.

[0540] As a sub-embodiment of this embodiment, the first cell is a PCell of the first node.

[0541] As a sub-embodiment of this embodiment, the first node is not configured with a DC.

[0542] As a sub-embodiment of this embodiment, the first node is not configured with CA.

[0543] As a sub-embodiment of this embodiment, the first node has only one service cell, namely the first cell.

[0544] As a sub-embodiment of this embodiment, the wireless link between the first node and the first cell is normal.

[0545] As a sub-embodiment of this embodiment, no radio link failure occurs between the first node and the first cell.

[0546] As a sub-embodiment of this embodiment, no radio link failure occurs to the first node.

[0547] As a sub-embodiment of this embodiment, no switching failure occurs in the first node.

[0548] As a sub-embodiment of this embodiment, the communication between the first node and the first cell is normal.

[0549] As a sub-embodiment of this embodiment, no abnormality occurs in the communication between the first node and the first cell.

[0550] As an embodiment, an abnormality occurs in the communication with the network through the second identifier, in particular, an abnormality occurs in the NAS layer, or an abnormality occurs in the SIM card associated with the second identifier.

[0551] As an embodiment, the abnormality in communicating with the network through the second identifier includes failure in deregistration of the second identifier.

[0552] As a sub-embodiment of this embodiment, deregistration for the second identifier includes sending a deregistration request message carrying the second identifier.

[0553] As a sub-embodiment of this embodiment, deregistration for the second identity includes sending a deregistration request message with a field or domain whose name includes "mobility identity" carrying the second identity.

[0554] As a sub-embodiment of this embodiment, deregistration for the second identity includes sending a deregistration request message carrying the second identity in a field or domain named "5GS mobility identity".

[0555] As a sub-embodiment of this embodiment, deregistration of the second identity includes sending a deregistration request message that carries the second identity in a field or domain named "6GS mobility identity".

[0556] As an embodiment, the abnormality in communicating with the network through the second identifier includes that a registration request for the second identifier is unsuccessful.

[0557] As a sub-embodiment of this embodiment, the registration request for the second identifier includes sending a registration request message carrying the second identifier.

[0558] As a sub-embodiment of this embodiment, the registration request for the second identity includes sending a registration request message that carries the second identity in a field or domain whose name includes "mobility identity".

[0559] As a sub-embodiment of this embodiment, the registration request for the second identity includes sending a registration request message carrying the second identity in a field or domain named "5GS mobility identity".

[0560] As a sub-embodiment of this embodiment, the registration request for the second identity includes sending a registration request message that carries the second identity in a field or domain named "6GS mobility identity".

[0561] Example 7

[0562] Embodiment 7 illustrates a schematic diagram of a first registration request message according to an embodiment of the present application that relies on communication with the network through the second identifier and an abnormality occurs, as shown in the attached Figure 7 shown.

[0563] As an embodiment, the meaning that the first registration request message relies on the communication with the network through the second identifier being abnormal includes: the first registration request message indicates that the communication with the network through the second identifier is abnormal.

[0564] As a sub-embodiment of this embodiment, the benefits of the above method include: the core network can be notified as soon as possible that an abnormality has occurred in the communication with the network through the second identifier; it is beneficial to save signaling overhead, for example, the first registration request message belongs to a periodic registration process.

[0565] As an embodiment, the meaning of the abnormality in the communication between the first registration request message and the network through the second identifier includes: the abnormality in the communication between the first registration request message and the network through the second identifier triggers the first registration request message.

[0566] As a sub-embodiment of this embodiment, the benefits of the above method include: the core network can be notified as soon as possible that an abnormality has occurred in the communication with the network through the second identifier.

[0567] As an embodiment, the meaning of the first registration request message relying on an abnormality in communication with the network through the second identifier includes: the first registration request message is a message in a periodic registration request for the first identifier; when an abnormality occurs in communication with the network through the second identifier, the period of the periodic registration request is set to the smaller of the period of the periodic registration request for the first identifier and the period of the periodic registration request for the second identifier.

[0568] As a sub-embodiment of this embodiment, the benefits of the above method include: it can better take into account the registration requirements in the communication with the network through the first identifier and the communication with the network through the second identifier.

[0569] As a sub-embodiment of this embodiment, the periodic registration request for the first identifier means that the registration request message in the periodic registration includes the first identifier.

[0570] As a sub-embodiment of this embodiment, the meaning of the periodic registration request for the first identifier is that the "5GS mobility identity" field of the registration request message in the periodic registration includes the first identifier.

[0571] As a sub-embodiment of this embodiment, the meaning of the periodic registration request for the first identity is that the "6GS mobility identity" field of the registration request message in the periodic registration includes the first identity.

[0572] As a sub-embodiment of this embodiment, the periodic registration request for the second identifier means that the registration request message in the periodic registration includes the second identifier.

[0573] As a sub-embodiment of this embodiment, the meaning of the periodic registration request for the second identifier is that the "5GS mobility identity" field of the registration request message in the periodic registration includes the second identifier.

[0574] As a sub-embodiment of this embodiment, the meaning of the periodic registration request for the second identity is that the "6GS mobility identity" field of the registration request message in the periodic registration includes the second identity.

[0575] As an embodiment, the first registration request message indicates the reason why an abnormality occurs in communication with the network through the second identifier.

[0576] As an embodiment, the first registration request message indicates the type of abnormality that occurs in the communication with the network through the second identifier.

[0577] As an embodiment, the first registration request message indicates the time when an abnormality occurs in communication with the network through the second identifier.

[0578] As an embodiment, the first registration request message is sent through communication between the first identifier and the network.

[0579] As an embodiment, the sentence that the first registration request message indicates that an abnormality occurs in communication with the network through the second identifier means: the first registration request message indicates that an abnormality occurs in communication with the core network through the second identifier.

[0580] As an embodiment, the sentence "The first registration request message indicates that an abnormality occurs in communication with the network through the second identifier" means: the first registration request message indicates that an abnormality occurs in communication with the AMF through the second identifier.

[0581] As an embodiment, the sentence "the first registration request message indicates that an abnormality occurs in the communication with the network through the second identifier" means that: the first registration request message indicates that an abnormality occurs in the NAS signaling connection associated with the second identifier.

[0582] As an embodiment, the sentence “the first registration request message indicates that an abnormality occurs in communication with the network through the second identifier” means: the first registration request message indicates that an abnormality occurs in NAS layer communication through the second identifier.

[0583] As an embodiment, the abnormality occurring in the communication with the network through the second identifier means or includes: the communication with the network through the second identifier cannot be restored by itself.

[0584] As an embodiment, the abnormality occurring in the communication with the network through the second identifier means or includes: the communication with the network through the second identifier is interrupted.

[0585] As an embodiment, the abnormality occurring in the communication with the network through the second identifier means or includes: a serious failure occurring in the communication with the network through the second identifier.

[0586] As an embodiment, the abnormality occurring in the communication with the network through the second identifier means or includes: the signaling connection with the network through the second identifier is interrupted or fails.

[0587] As an embodiment, the meaning of the abnormality occurring in the communication with the network through the second identifier is or includes: a NAS layer failure occurs in the communication with the network through the second identifier.

[0588] As an embodiment, when the NAS layer of the first node receives an indication from a lower layer indicating that the lower layer has failed, it is determined that an abnormality has occurred in the communication with the network through the second identifier.

[0589] As a sub-embodiment of this embodiment, the lower layer includes an RRC layer.

[0590] As a sub-embodiment of this embodiment, the failure occurring in the lower layer includes RRC connection failure.

[0591] As a sub-embodiment of this embodiment, the failure occurring in the lower layer includes RRC connection failure and inability to recover.

[0592] As an embodiment, when the RRC layer of the first node fails, the RRC layer of the first node indicates to a higher layer that an RRC connection failure has occurred.

[0593] As a sub-embodiment of this embodiment, the higher layer of the first node determines that an abnormality occurs in communication with the network through the second identifier.

[0594] Example 8

[0595] Embodiment 8 illustrates a schematic diagram of a first registration approval message according to an embodiment of the present application that an abnormality occurs in communication with the network through the second identifier, as shown in the attached figure. Figure 8 shown.

[0596] As an embodiment, the meaning that the first registration approval message depends on the abnormality in the communication with the network through the second identifier includes: the first registration approval message carries a response to the abnormality in the communication with the network through the second identifier.

[0597] As an embodiment, the meaning that the first registration approval message relies on an abnormality in communication with the network through the second identifier includes: the first registration approval message carries processing signaling for an abnormality in communication with the network through the second identifier.

[0598] As an embodiment, the meaning that the first registration approval message relies on the abnormality in the communication with the network through the second identifier includes: the first registration approval message confirms that the abnormality in the communication with the network through the second identifier occurs.

[0599] As an embodiment, the meaning that the first registration approval message depends on the abnormality of the communication with the network through the second identifier includes: the first registration approval message carries a message for the communication with the network through the second identifier.

[0600] As a sub-embodiment of this embodiment, a container in the first registration approval message carries the message for communicating with the network through the second identifier.

[0601] As a sub-embodiment of this embodiment, the message for communicating with the network through the second identifier is a NAS message.

[0602] As a sub-embodiment of this embodiment, the message for communicating with the network through the second identifier is a deregistration message.

[0603] As a sub-embodiment of this embodiment, a paging message is configured for the message communicated with the network through the second identifier.

[0604] As a sub-embodiment of this embodiment, a message for configuring NAS parameters for the message communicated with the network through the second identifier.

[0605] As a sub-embodiment of this embodiment, a message of at least one timer in the communication with the network through the second identifier is configured for the message of the communication with the network through the second identifier.

[0606] As a sub-embodiment of this embodiment, the message configuration update signaling is performed for the communication with the network through the second identifier.

[0607] As a sub-embodiment of this embodiment, a tracking area is configured for the message communicated with the network through the second identifier.

[0608] As a sub-embodiment of this embodiment, DRX is configured for the message communicated with the network through the second identifier.

[0609] As an embodiment, the above method is helpful to alleviate the impact caused by abnormal communication with the network through the second identifier.

[0610] Example 9

[0611] Embodiment 9 illustrates a schematic diagram of a fourth registration request message indicating that communication with the network through the second identifier is restored or about to be restored according to an embodiment of the present application, as shown in the attached Fig. 9 shown.

[0612] As an embodiment, the fourth registration request message indicates that communication with the network through the second identifier is resumed.

[0613] As an embodiment, the fourth registration request message indicates that communication with the network through the second identifier is about to be restored.

[0614] As an embodiment, the fourth registration request message explicitly indicates that the communication with the network through the second identifier is restored or is about to be restored.

[0615] As an embodiment, the restoration of communication with the network through the second identifier corresponds to an abnormality in communication with the network through the second identifier.

[0616] As an embodiment, the communication with the network through the second identifier is about to be restored corresponding to the abnormality in the communication with the network through the second identifier.

[0617] As an embodiment, the fourth registration request message implicitly indicates that the communication with the network through the second identifier is restored or is about to be restored.

[0618] As an embodiment, the fourth registration request message is REGISTRATION REQUEST.

[0619] As an embodiment, the fourth registration request message indicates that an abnormality has occurred in the communication with the network through the second identifier, which means that the communication with the network through the second identifier has been restored or is about to be restored.

[0620] As an embodiment, the fourth registration request message uses 1 bit to indicate that the communication with the network through the second identifier is restored or is about to be restored.

[0621] As an embodiment, the advantage of the fourth registration request message indicating that the communication with the network through the second identifier is about to be restored is that the network can be prepared as early as possible to reduce the impact of abnormal communication with the network through the second identifier.

[0622] Example 10

[0623] Embodiment 10 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig.10 As shown in the attached Fig.10In the embodiment, the processing device 1000 in the first node includes a first receiver 1001 and a first transmitter 1002.

[0624] In embodiment 10, the first transmitter 1002 sends a first registration request message, the first registration request message is a NAS message, the first registration request message includes a first identifier, and the first registration request message relies on communication with a network through a second identifier and an abnormality occurs;

[0625] The first identifier and the second identifier both identify the first node; the first identifier and the second identifier are both globally unique identifiers; and the first identifier and the second identifier are configured by fields with the same name in a NAS message.

[0626] As an embodiment, the first receiver 1001 receives a first registration approval message, where the first registration approval message is a feedback of the first registration request message; the first registration approval message depends on an abnormality in the communication with the network through the second identifier.

[0627] As an embodiment, the first identifier corresponds to a first NAS signaling connection; the second identifier corresponds to a second NAS signaling connection.

[0628] As an embodiment, the first transmitter 1002 sends a second registration request message before the first registration request message is sent;

[0629] The first receiver 1001 receives a second registration approval message, where the second registration approval message is a feedback of the second registration request message; the second registration approval message configures the first identifier;

[0630] The first transmitter 1002 sends a third registration request message before the first registration request message is sent;

[0631] The first receiver 1001 receives a third registration approval message, where the third registration approval message is a feedback of the third registration request message; the third registration request message configures the second identifier;

[0632] The first identifier and the second identifier are both valid identifiers; the second registration request message, the second registration approval message, the third registration request message, and the third registration approval message are NAS messages respectively.

[0633] As an embodiment, the first transmitter 1002 sends a first message, where the first message indicates that the first identifier is associated with the second identifier.

[0634] As an embodiment, the phrase "an abnormality occurs in communication with the network through the second identifier" includes: failure of the RRC connection associated with the second identifier, unsuccessful deregistration of the second identifier, overheating of communication with the network through the second identifier, the hardware corresponding to the second identifier is removed or is no longer available, and at least one of the hardware corresponding to the second identifier fails.

[0635] As an embodiment, after the first registration request message is received, the network registration state associated with the second identifier is set to an idle state or a deregistered state.

[0636] As an embodiment, the first receiver 1001 receives a second message through a first identifier, where the second message is a NAS message, and a container in the second message carries a third message for the second identifier, where the third message is a NAS message.

[0637] As an embodiment, the first transmitter 1002 sends a fourth registration request message, which is a NAS message; the fourth registration request message includes the first identifier; and the fourth registration request message indicates that communication with the network through the second identifier is restored or is about to be restored.

[0638] As an embodiment, the first node is a user equipment (UE).

[0639] As an embodiment, the first node is a terminal supporting a large delay difference.

[0640] As an embodiment, the first node is a terminal supporting NTN.

[0641] As an embodiment, the first node is an aircraft or a ship.

[0642] As an embodiment, the first node is a mobile phone or a vehicle-mounted terminal.

[0643] As an embodiment, the first node is a terminal supporting MUSIM.

[0644] As an embodiment, the first node is an Internet of Things terminal or an industrial Internet of Things terminal.

[0645] As an embodiment, the first node is a device supporting low-latency and high-reliability transmission.

[0646] As an embodiment, the first receiver 1001 includes at least one of the antenna 452, receiver 454, receiving processor 456, multi-antenna receiving processor 458, controller / processor 459, memory 460, or data source 467 in Example 4.

[0647] As an embodiment, the first transmitter 1002 includes at least one of the antenna 452, transmitter 454, transmit processor 468, multi-antenna transmit processor 457, controller / processor 459, memory 460, or data source 467 in Embodiment 4.

[0648] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication, machine type communication) terminals, eMTC (enhancedMTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers, satellite communication equipment, ship communication equipment, NTN user equipment and other wireless communication equipment. The base stations or system equipment in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point, sending and receiving node), NTN base stations, satellite equipment, flight platform equipment and other wireless communication equipment.

[0649] The present invention may be implemented in other specified forms without departing from its core or essential features. Therefore, the embodiments disclosed herein should be considered as illustrative rather than restrictive in any way. The scope of the invention is determined by the appended claims rather than the preceding description, and all modifications within their equivalent meanings and regions are considered to be included therein.

Claims

1. A first node for wireless communication, wherein: include: The first transmitter sends a first registration request message, where the first registration request message is a NAS (Non-AccessStratum) message, the first registration request message includes a first identifier, and the first registration request message relies on communication with a network through a second identifier and an abnormality occurs; The first identifier and the second identifier both identify the first node; the first identifier and the second identifier are both globally unique identifiers; and the first identifier and the second identifier are configured by fields with the same name in a NAS message.

2. The first node according to claim 1, characterized in that: include: A first receiver receives a first registration approval message, where the first registration approval message is a feedback of the first registration request message; The first registration approval message depends on the communication with the network through the second identifier and an abnormality occurs.

3. The first node according to claim 1 or 2, characterized in that: The first identifier corresponds to a first NAS signaling connection; the second identifier corresponds to a second NAS signaling connection.

4. The first node according to any one of claims 1 to 3, characterized in that: include: The first transmitter sends a second registration request message before the first registration request message is sent; A first receiver receives a second registration approval message, where the second registration approval message is a feedback of the second registration request message; The second registration approval message configures the first identifier; The first transmitter sends a third registration request message before the first registration request message is sent; The first receiver receives a third registration approval message, where the third registration approval message is a feedback of the third registration request message; The third registration request message configures the second identifier; The first identifier and the second identifier are both valid identifiers; the second registration request message, the second registration approval message, the third registration request message, and the third registration approval message are NAS messages respectively.

5. The first node according to any one of claims 1 to 4, characterized in that: include: The first transmitter sends a first message, where the first message indicates that the first identifier is associated with the second identifier.

6. The first node according to any one of claims 1 to 5, characterized in that: include: The phrase "an abnormality occurs in communication with the network through the second identifier" includes: the RRC connection associated with the second identifier fails, deregistration of the second identifier is unsuccessful, communication with the network through the second identifier overheats, the hardware corresponding to the second identifier is removed or is no longer available, and the hardware corresponding to the second identifier fails.

7. The first node according to any one of claims 1 to 6, characterized in that: After the first registration request message is received, the network registration state associated with the second identifier is set to an idle state or a deregistered state.

8. The first node according to any one of claims 1 to 7, characterized in that: include: A first receiver receives a second message through a first identifier, where the second message is a NAS message, and a container in the second message carries a third message for the second identifier, where the third message is a NAS message.

9. The first node according to any one of claims 1 to 8, characterized in that: include: The first transmitter sends a fourth registration request message, where the fourth registration request message is a NAS message; The fourth registration request message includes the first identifier; and the fourth registration request message indicates that communication with the network through the second identifier is restored or is about to be restored.

10. A method in a first node for wireless communication, wherein: include: Sending a first registration request message, where the first registration request message is a NAS message, the first registration request message includes a first identifier, and an abnormality occurs when the first registration request message relies on communication with a network through a second identifier; The first identifier and the second identifier both identify the first node; the first identifier and the second identifier are both globally unique identifiers; and the first identifier and the second identifier are configured by fields with the same name in a NAS message.

Images