Communication method, communication device, communication system, storage medium, and program product

Abstract

The present invention relates to a communication method, a communication device, a communication system, a storage medium, and a program product. The method is executed by a first node and comprises: receiving first information; and sending second information on the basis of the first information, wherein the second information comprises a first terminal access stratum context, and the first terminal access stratum context is a terminal access stratum context of a first terminal. By means of the solution of the present invention, functional fragmentation and complexity caused by different connection states can be reduced, and implementation at a first terminal is facilitated, thereby achieving rapid service establishment.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of wireless communication, and more particularly to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] With the increasing intelligence of people's lives and work, Machine Type Communication (MTC) technology is being widely used. With the continuous advancement of MTC technology and the emergence of Internet of Things (IoT) devices, MTC services, as a crucial support, enable efficient connectivity and data management for a large number of IoT devices through specialized network architectures and functional entities. Summary of the Invention

[0003] The technical problem that needs to be solved is how to simplify IoT implementation and reduce the functional differentiation and complexity caused by different connection states in order to quickly establish business.

[0004] According to a first aspect of the present disclosure, a communication method is provided. The method is performed by a first node. The method includes: receiving first information; and sending second information based on the first information, the second information including a first terminal access layer context, wherein the first terminal access layer context is the terminal access layer context of the first terminal.

[0005] According to a second aspect of the present disclosure, a communication method is provided. The method is performed by a first access network node. The method includes: sending first information to the first node, the first information instructing the first node to send second information, the second information including a first terminal access layer context, the first terminal access layer context being the terminal access layer context of the first terminal, and the first access network node being a serving node of the first terminal.

[0006] According to a third aspect of the present disclosure, a communication method is provided. The method is performed by a first terminal. The method includes: sending first information to a first node, the first information instructing the first node to send second information, the second information including a first terminal access layer context, the first terminal access layer context being a terminal access layer context associated with the first information among a plurality of terminal access layer contexts.

[0007] According to a fourth aspect of the present disclosure, a communication device is provided. This communication device is used to perform the communication method as described in the first, second, or third aspect.

[0008] According to a fifth aspect of the present disclosure, a communication system is provided. The communication system includes a first node, a first access network node, and a first terminal. The first node is configured to perform the communication method as described in the first aspect. The first access network node is configured to perform the communication method as described in the second aspect. The first terminal is configured to perform the communication method as described in the third aspect.

[0009] According to a sixth aspect of the present disclosure, a storage medium is provided. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in the first, second, or third aspect.

[0010] According to a seventh aspect of the present disclosure, a program product is provided. The program product includes at least one of a program and instructions. When the program or instructions are executed by a communication device, they implement the steps of the communication method as described in the first, second, or third aspect.

[0011] According to an eighth aspect of the present disclosure, a computer program is provided. When the computer program is run on a computer, it causes the computer to perform the communication method as described in the first, second, or third aspect.

[0012] According to a ninth aspect of the present disclosure, a chip or chip system is provided. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication methods described in the first, second, or third aspects.

[0013] According to the embodiments of this disclosure, the functional differentiation and complexity caused by different connection states can be reduced, making it easier for the first terminal to implement and enabling rapid establishment of services.

[0014] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not constitute a limitation on the embodiments of this disclosure. Attached Figure Description

[0015] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.

[0016] Figure 1A is a schematic diagram of an architecture of a communication system provided according to an embodiment of the present disclosure.

[0017] Figure 1B is an interactive schematic diagram of an exemplary communication method provided according to an embodiment of the present disclosure.

[0018] Figure 1C is another interactive schematic diagram of an exemplary communication method provided according to an embodiment of the present disclosure.

[0019] Figure 1D is another interactive schematic diagram of an exemplary communication method provided according to an embodiment of the present disclosure.

[0020] Figure 1E is another interactive schematic diagram of an exemplary communication method provided according to an embodiment of the present disclosure.

[0021] Figure 1F is an interactive schematic diagram of an exemplary communication method provided according to an embodiment of the present disclosure.

[0022] Figure 2A is a schematic diagram of another architecture of a communication system provided according to an embodiment of the present disclosure.

[0023] Figure 2B is a schematic diagram of another architecture of a communication system provided according to an embodiment of the present disclosure.

[0024] Figure 2C is a schematic diagram of another architecture of a communication system provided according to an embodiment of the present disclosure.

[0025] Figure 3A is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure.

[0026] Figure 3B is another interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0027] Figure 3C is another interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0028] Figure 3D is another interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0029] Figure 4 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0030] Figure 5A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0031] Figure 5B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. Detailed Implementation

[0032] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0033] In a first aspect, embodiments of this disclosure provide a communication method. The method is executed by a first node. The method includes: receiving first information; and sending second information based on the first information, the second information including a first terminal access layer context, the first terminal access layer context being the terminal access layer context of the first terminal.

[0034] In the above embodiments, the first node can provide the terminal access layer context of the first terminal as a node for managing the terminal context to support communication service requirements. This eliminates the need to distinguish the context management process under different connection states, thereby reducing the functional differentiation and complexity caused by different connection states.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is sent by the first terminal, and the first information indicates at least one of the following: the context index of the first terminal; the device type of the first terminal; the service type of the first terminal; the network slice associated with the first terminal; and the terminal identifier of the first terminal.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the first terminal access layer context is a terminal access layer context associated with the first information among a plurality of terminal access layer contexts.

[0037] In the above embodiments, the first terminal access layer context can be selected from multiple terminal access layer contexts that are associated with the first information. Since the multiple terminal access layer contexts are already stored, during the communication process, the first terminal access layer context can be quickly determined from multiple terminal access layer contexts based on the first information provided by the first terminal, without the need for other process interactions, thereby improving service transmission and realizing rapid service establishment.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is received by the first node during the initial access process of the first terminal.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0040] The first terminal access layer context is updated based on the third information, which is sent by the first terminal and / or determined by the first node based on the Quality of Service (QoS).

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, one or more access network nodes are registered on the first node, and the terminal access layer context of the one or more access network nodes is stored in the first node; the first information is sent by the first access network node among the one or more access network nodes, the first access network node is the service node of the first terminal, the first information includes the first identifier of the first terminal, and the first terminal access layer context is associated with the first identifier.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the first node is deployed in one of the following: a core network, an access network, or a cloud.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the first node communicates with one or more access network nodes via application layer protocol signaling; or, the first node communicates with one or more access network nodes via Internet Protocol.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes one of the following:

[0045] Send a paging message within the registration area of ​​the first node, the registration area including the radio notification area of ​​one or more access network nodes;

[0046] Send the fourth message to the first core network device. The fourth message is used to trigger the first core network device to send a paging message.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0048] The system receives the fifth information sent by the first access network node. The fifth information includes the first identifier, the second terminal access layer context, and the first terminal security context of the first terminal. The system associates and stores the first identifier, the second terminal access layer context, and the first terminal security context of the first terminal.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: sending sixth information to a first access network node, the fifth information including a second identifier of the first terminal, the second identifier being an identifier assigned by the first node for the first terminal for the next use.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the second information further includes a second identifier of the first terminal, the second identifier being an identifier assigned by the first node for the first terminal for the next use.

[0051] In conjunction with some embodiments of the first aspect, in some embodiments, the second information also includes the second terminal security context of the first terminal.

[0052] In the above embodiments, the first node can provide the terminal access layer context of the first terminal and serve as a node for managing the terminal context. The first node can also be deployed on different network nodes to support communication service requirements. This eliminates the need to distinguish the context management process under different connection states, thereby reducing the functional differentiation and complexity caused by different connection states.

[0053] In a second aspect, embodiments of this disclosure provide a communication method. The method is performed by a first access network node. The method includes: sending first information to the first node, the first information instructing the first node to send second information, the second information including a first terminal access layer context, the first terminal access layer context being the terminal access layer context of the first terminal, and the first access network node being a serving node of the first terminal.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, one or more access network nodes are registered on the first node, the terminal access layer context of one or more access network nodes is stored in the first node, the first information includes the first identifier of the first terminal, and the first terminal access layer context is associated with the first identifier.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the first node is deployed in one of the following: a core network, an access network, or a cloud.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, the first node communicates with one or more access network nodes via application layer protocol signaling; or, the first node communicates with one or more access network nodes via Internet Protocol.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes:

[0058] Send a fifth message to the first node. The fifth message includes a first identifier, a second terminal access layer context, and a first terminal security context of the first terminal. The fifth message is used to trigger the first node to associate and store the first identifier, the second terminal access layer context, and the first terminal security context of the first terminal.

[0059] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes:

[0060] The system receives the sixth information sent by the first node. The sixth information includes the second identifier of the first terminal, which is the identifier assigned by the first node to the first terminal for the next use.

[0061] In conjunction with some embodiments of the second aspect, in some embodiments, the second information further includes a second identifier of the first terminal, which is an identifier assigned by the first node for the first terminal for the next use.

[0062] In conjunction with some embodiments of the second aspect, in some embodiments, the second information also includes the second terminal security context of the first terminal.

[0063] In a third aspect, embodiments of this disclosure provide a communication method. The method is executed by a first terminal. The method includes: sending first information to a first node, the first information instructing the first node to send second information, the second information including a first terminal access layer context, the first terminal access layer context being a terminal access layer context associated with the first information among a plurality of terminal access layer contexts.

[0064] In conjunction with some embodiments of the third aspect, in some embodiments, the first information indicates at least one of the following: the context index of the first terminal; the device type of the first terminal; the service type of the first terminal; and the network slice associated with the first terminal.

[0065] In conjunction with some embodiments of the third aspect, in some embodiments, the first information is received by the first node during the initial access process of the first terminal.

[0066] In some embodiments of the third aspect, the above method further includes: sending third information to the first node, the third information being used to trigger the first node to update the first terminal access layer context.

[0067] In a fourth aspect, embodiments of this disclosure provide a communication device, such as a first node. The communication device includes a transceiver module configured to receive first information and, based on the first information, send second information, the second information including a first terminal access layer context, the first terminal access layer context being the terminal access layer context of a first terminal.

[0068] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information is sent by the first terminal, and the first information indicates at least one of the following: the context index of the first terminal; the device type of the first terminal; the service type of the first terminal; the network slice associated with the first terminal; and the terminal identifier of the first terminal.

[0069] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first terminal access layer context is the terminal access layer context associated with the first information among a plurality of terminal access layer contexts.

[0070] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information is received by the first node during the initial access process of the first terminal.

[0071] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described communication device further includes: a processing module configured to update the first terminal access layer context based on third information, the third information being sent by the first terminal and / or determined by the first node based on Quality of Service (QoS).

[0072] In conjunction with some embodiments of the fourth aspect, in some embodiments, one or more access network nodes are registered on the first node, and the terminal access layer context of the one or more access network nodes is stored in the first node; the first information is sent by the first access network node among the one or more access network nodes, the first access network node is the service node of the first terminal, the first information includes the first identifier of the first terminal, and the first terminal access layer context is associated with the first identifier.

[0073] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first node is deployed in one of the following: a core network, an access network, or a cloud.

[0074] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first node communicates with one or more access network nodes via application layer protocol signaling; or, the first node communicates with one or more access network nodes via Internet Protocol.

[0075] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured as one of the following:

[0076] Send a paging message within the registration area of ​​the first node, the registration area including the radio notification area of ​​one or more access network nodes;

[0077] Send the fourth message to the first core network device. The fourth message is used to trigger the first core network device to send a paging message.

[0078] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described communication device further includes: a storage module;

[0079] The transceiver module is also configured to receive fifth information sent by the first access network node. The fifth information includes a first identifier, a second terminal access layer context, and a first terminal security context of the first terminal.

[0080] The storage module is configured to associate and store the first identifier, the second terminal access layer context, and the first terminal security context of the first terminal.

[0081] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to send sixth information to the first access network node, the sixth information including a second identifier of the first terminal, the second identifier being an identifier assigned by the first node for the first terminal for next use.

[0082] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second information further includes a second identifier of the first terminal, the second identifier being an identifier assigned by the first node for the first terminal for the next use.

[0083] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second information also includes the second terminal security context of the first terminal.

[0084] In a fifth aspect, embodiments of this disclosure provide a communication device, such as a first access network node. The communication device includes a transceiver module configured to send first information to the first node, the first information instructing the first node to send second information, the second information including a first terminal access layer context, the first terminal access layer context being the terminal access layer context of the first terminal, and the first access network node being a serving node of the first terminal.

[0085] In conjunction with some embodiments of the fifth aspect, in some embodiments, one or more access network nodes are registered on the first node, and the terminal access layer context of the one or more access network nodes is stored in the first node. The first information includes a first identifier of the first terminal, and the first terminal access layer context is associated with the first identifier.

[0086] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first node is deployed in one of the following: a core network, an access network, or a cloud.

[0087] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first node communicates with one or more access network nodes via application layer protocol signaling; or, the first node communicates with one or more access network nodes via Internet Protocol.

[0088] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module is further configured to send fifth information to the first node. The fifth information includes a first identifier, a second terminal access layer context, and a first terminal security context of the first terminal. The fifth information is used to trigger the first node to associate and store the first identifier, the second terminal access layer context, and the first terminal security context of the first terminal.

[0089] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module is further configured to receive sixth information sent by the first node, the sixth information including a second identifier of the first terminal, the second identifier being an identifier assigned by the first node for the first terminal for next use.

[0090] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second information further includes a second identifier of the first terminal, the second identifier being an identifier assigned by the first node for the first terminal for the next use.

[0091] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second information also includes the second terminal security context of the first terminal.

[0092] In a sixth aspect, embodiments of this disclosure provide a communication device, such as a first terminal. The communication device includes: a transceiver module configured to send first information to a first node, the first information instructing the first node to send second information, the second information including a first terminal access layer context, the first terminal access layer context being a terminal access layer context associated with the first information among a plurality of terminal access layer contexts.

[0093] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first information indicates at least one of the following: the context index of the first terminal; the device type of the first terminal; the service type of the first terminal; and the network slice associated with the first terminal.

[0094] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first information is received by the first node during the initial access process of the first terminal.

[0095] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transceiver module is further configured to send third information to the first node, the third information being used to trigger the first node to update the first terminal access layer context.

[0096] In a seventh aspect, embodiments of this disclosure provide a communication device. This communication device is used to perform the communication methods described in any of the first, second, third, and possible embodiments thereof.

[0097] In an eighth aspect, embodiments of this disclosure provide a communication system. The communication system includes a first node, a first access network node, and a first terminal. The first node is configured to perform the communication method as described in any of the first aspect and its possible embodiments. The first access network node is configured to perform the communication method as described in any of the second aspect and its possible embodiments. The first terminal is configured to perform the communication method as described in any of the third aspect and its possible embodiments.

[0098] In a ninth aspect, embodiments of this disclosure provide a storage medium. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any of the first, second, third, and possible embodiments thereof.

[0099] In a tenth aspect, embodiments of this disclosure provide a program product. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the steps of the communication method as described in any of the first, second, third, and possible embodiments thereof.

[0100] In an eleventh aspect, embodiments of this disclosure provide a computer program. When this computer program is run on a computer, it causes the computer to perform the communication methods described in any of the first, second, third, and possible embodiments thereof.

[0101] In a twelfth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication methods described in any of the first, second, third, and possible embodiments thereof.

[0102] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0103] This disclosure provides a communication method, a communication device, a communication system, a storage medium, and a program product. In some embodiments, terms such as communication method, information processing method, and information transmission method can be used interchangeably; terms such as communication device, communication equipment, network equipment, network function, and network entity can be used interchangeably; and terms such as communication system and information processing system can be used interchangeably.

[0104] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0105] In the embodiments disclosed herein, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the various embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0106] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0107] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0108] In the embodiments of this disclosure, "a plurality of" means two or more.

[0109] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0110] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0111] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0112] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0113] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0114] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0115] In some embodiments, terms such as “greater than,” “more than,” “higher than,” and “exceeding” can be used interchangeably; terms such as “greater than or equal to,” “not less than,” “more than or equal to,” “not less than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably; terms such as “less than,” “less than,” and “lower than” can be used interchangeably; and terms such as “less than or equal to,” “not greater than,” “less than or equal to,” “not more than,” “lower than or equal to,” “not higher than,” and “below” can be used interchangeably.

[0116] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0117] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0118] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0119] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0120] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0121] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0122] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0123] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0124] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0125] Figure 1A is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure. As shown in Figure 1A, the communication system 100 includes a first node 101, a first access network node 102, and a first terminal 103.

[0126] In some embodiments, the first access network node 102 is deployed in the access network.

[0127] In some embodiments, the first node 101 may be deployed in an access network, a core network, or the cloud. In one embodiment, the first node 101 may be at least one of a cloud server, an access network device, and a core network device in a cloud computing architecture.

[0128] In some embodiments, the terminal includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0129] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0130] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0131] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0132] In some embodiments, the communication system 100 may include a 5G communication system (5GS) or a 6G communication system (6GS). It should be noted that the communication system 100 may also be other communication systems, such as a 4G communication system (LTE), and this disclosure does not specifically limit it.

[0133] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions provided in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this disclosure are also applicable to similar technical problems.

[0134] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0135] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or some of the main components in the communication system 100, but are not limited thereto. The main components shown in FIG1A are illustrative. The communication system 100 may include all or some of the main components in 1A, or may include other main components outside of 1A. The number and form of each main component are arbitrary. Each main component may be physical or virtual. The connection relationship between the main components is illustrative. The main components may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0136] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0137] In recent years, the introduction of MTC (Medium-Terminal) devices has brought about signaling congestion and load issues. These issues mainly arise in two scenarios: when MTC applications require MTC devices to perform the same task simultaneously; and when a large number of MTC users are roaming users, their serving network is unavailable, and they reside on the local network, leading to a significant signaling load. As the demand for MTC services increases and its application scenarios become more widespread, potential RAN-side enhancement technologies have been proposed to meet the needs of MTC services and improve RAN support for MTC. These include resource allocation for a large number of MTC UEs, low mobility considerations, power-saving mechanisms, ultra-low service cycles, and how a large number of MTC UEs impacts RAN-side performance.

[0138] To address the above issues, RAN-side enhancements primarily focus on improving signaling effectiveness and reducing UE power consumption. For example, two projects were proposed: Small Data and Device Triggering Enhancements (SDDTE) and UE Power Consumption Optimizations (UEPCOP).

[0139] It should be noted that machine-type communication (primarily meter reading services, considering meters are generally located in poor coverage areas such as basements) typically involves periodically reporting data packets of relatively fixed size, and most MTC UEs are in a relatively static state. Therefore, considering these characteristics, the SI led by RAN1 aimed to reduce the processing complexity of MTC UEs. Simultaneously, considering that some MTC UEs may be in poor coverage environments, coverage enhancement is needed for these MTC UEs.

[0140] In some embodiments, the MTC service is a 6G MTC service. In one embodiment, the MTC service may include a 6G IoT service. In some embodiments, the 6G IoT service may include services related to IoT devices based on ambient energy, meter reading services, services related to industrial wireless sensors, video surveillance and other related services, services related to wearable devices, 6G AIoT services, and IoT services supported by 6G UEs. In some embodiments, the MTC service may include a 5G IoT service, and this disclosure does not impose any limitations.

[0141] In some embodiments, MTC service requirements involve 6G IoT, targeting environmental energy-based IoT devices, characterized by low cost, low power consumption, battery-free operation, small size, and massive connectivity. For meter reading services, it features strong coverage, low complexity, energy efficiency, small packet data transmission, infrequent service activity, low latency sensitivity, and massive connectivity. For industrial wireless sensors, it offers low complexity, high reliability, small packet size, latency sensitivity, and massive connectivity. For wearable devices, it provides low data rate, energy efficiency, and massive connectivity. For video surveillance, it is primarily uplink-based with high bandwidth.

[0142] In some embodiments of NR, a new Radio Resource Control (RRC) connection state is introduced to reduce control plane (CP) connection establishment latency. This disclosure can enhance the RRC disconnected state. The RRC connection state is described below.

[0143] It should be noted that the RRC connection state can include: RRC_INACTIVE, RRC_IDLE, and RRC_CONNECTED.

[0144] In some embodiments, RRC_INACTIVE is an inactive state, meaning the UE is connected to the network but is inactive. When the UE is inactive for a certain period of time, the connection will change from the RRC_CONNECTED state to the RRC_INACTIVE state to save terminal power and reduce signaling load.

[0145] In some embodiments, RRC_IDLE is an idle state, which is the access layer state in which a UE is camped on a cell but has not established any RRC connection. The UE will enter the RRC_IDLE state when it is disconnected from the network or is in an unregistered state.

[0146] In some embodiments, RRC_CONNECTED is a connected state, indicating that an RRC connection has been established between the UE and the network. The UE enters the RRC_CONNECTED state when it needs to transmit data or is in an active state.

[0147] In some embodiments, the characteristics of the RRC_INACTIVE state include: (1) the connection between the RAN and CN is maintained; (2) the UE (e.g., a terminal or IoT device) and at least one gNB retain the access layer context; (3) the UE is reachable from the RAN side, and the relevant parameters are configured by the RAN; (4) when the UE moves within the RNA notification area configured by the RAN, it does not need to notify the network side, but when it moves out of the RNA notification area, it needs to notify the network side; (5) the UE moves within the RNA notification area according to the cell selection reselection method.

[0148] It should be noted that the RAN configuration parameters for RRC states can include configuration parameters regarding RRC state transitions. For example, these may include the configuration information required to transition the UE from the RRC_CONNECTED state to the RRC_INACTIVE state. These configuration parameters allow the UE to enter the low-power RRC_INACTIVE state when data transmission is not required, while maintaining connectivity with the core network, so that the RRC connection can be quickly restored when needed.

[0149] The configuration parameters of RRC_INACTIVE can be configured through the RRC_Release message and may include one or more of the following: SuspendConfig, Terminal Identifier (such as I-RNTI), RNA (RAN Notification Area), RAN DRX Period (Radio Access Network Discontinuous Reception Period), RAN Notification Area Update (RNAU) Periodic Configuration, and Next-Hop Chaining Counter (NCC).

[0150] In some embodiments, SuspendConfig represents the configuration information for the RRC_INACTIVE state, including context information that the UE needs to retain in the RRC_INACTIVE state, timer settings, etc.

[0151] In some embodiments, the I-RNTI is a unique UE identifier for the anchor base station. It may include: I-RNTI (40 bits) and short I-RNTI (24 bits).

[0152] In some embodiments, the RAN notification area may include: a list of cells, a list of RAN Area IDs, and a list of TAIs.

[0153] It should be noted that the RAN area code is broadcast in the cell's system broadcast. The RAN area is larger than the cell, but smaller than the Tracking Area (TA). For example, the RAN area code is 8 bits, indicating that there are a maximum of 255 RAN areas within a TA.

[0154] It's important to note that the TAI list contains information on all TAIs within the network, which is crucial for location and mobility management. When a UE moves between different TAIs, a Tracking Area Update (TAU) procedure needs to be performed to notify the network of its current location. Maintaining the TAI list helps ensure that the network can accurately track the UE's location and provide necessary services.

[0155] In some embodiments, the RAN DRX period is used to calculate the paging frame (PF) or paging opportunity (PO) of the initial paging message in the RAN. The DRX period is selected for PF or PO calculation based on the minimum value among the cell default DRX period, UE specific DRX period, and RAN DRX period.

[0156] In some embodiments, the periodic configuration of RNAU can be used to control periodic RNAU.

[0157] In some embodiments, NCC is used as the key for MSG4 during the RRC resume process. During the RRC resume process, the key for MSG4 can be encrypted or verified using the NCC algorithm. By calculating the normalized cross-correlation coefficient of the two sequences, NCC can assess their similarity, thereby ensuring the integrity and security of MSG4.

[0158] It should be noted that the states RRC_INACTIVE, RRC_IDLE, and RRC_CONNECTED can be transitioned between each other, and may include at least one of the following:

[0159] 1. The RRC setup process (3 steps: SRB0-SRB1-SRB1) allows the UE to switch from RRC_IDLE to RRC_CONNECTED. Here, SRB stands for Signaling Radio Bearer.

[0160] 2. The RRC release process (1 step: SRB1) can be used to switch from RRC_CONNECTED to RRC_IDLE or RRC_INACTIVE.

[0161] 3. The RRC Resume process (3 steps: SRB0-SRB1-SRB1) allows the UE to switch from RRC_INACTIVE to RRC_CONNECTED.

[0162] 4. The RRC Resume process (2 steps: SRB0-SRB1) allows the UE to switch from RRC_INACTIVE to RRC_INACTIVE or RRC_IDLE.

[0163] 5. The RRC Resume procedure (2-step: SRB0-SRB0) allows the UE to transition from RRC_INACTIVE to RRC_INACTIVE. For example, it can be released to the RRC_IDLE state through the RRC release procedure, or kept in the RRC_INACTIVE state through the RRCReject / RRC release message.

[0164] It should be noted that the RRC Resume process may fail to transition the UE to the RRC_CONNECTED state for some reason (such as network policy, resource limitations, etc.), and instead keep it in the RRC_INACTIVE state or release it to the RRC_IDLE state.

[0165] In some embodiments, the initial RRC state transition of RRC_INACTIVE uses the RRC connection recovery process in NR, as follows:

[0166] (1) Triggering reason

[0167] In some embodiments, for a UE in the RRC_INACTIVE state, this process is triggered when uplink data arrives, the periodic RNAU timer times out, or an initial RAN paging is received.

[0168] (2) RRC connection restored to RRC_CONNECTED

[0169] As shown in Figure 1B, the RRC connection recovery process includes:

[0170] Step S101: The UE sends an RRC Connection Resume Request to the network: The UE sends this request on SRB0 via the uplink common control channel (UL_CCCH), carrying the UE's AS layer initial identification information, ShortMAC-I, and the reason for the request. This message corresponds to Msg3 in the random access procedure. After sending this message, the UE activates security, generates a key, and resumes SRB1 to wait for MSG4.

[0171] Step S102: The network sends an RRC Resume message to the UE: The gNB sends this message on SRB1 via the downlink dedicated control channel (DL_DCCH). This message corresponds to Msg4 in the random access procedure. MSG4 is encrypted and protected for integrity.

[0172] Step S103: The UE sends an RRC Resume Complete message to the network: The UE sends this message on SRB1 via the uplink dedicated control channel (UL-DCCH), without carrying any actual information, and serves as an RRC layer confirmation.

[0173] (3) The RRC connection is restored to RRC_INACTIVE;

[0174] In some embodiments, if the base station (network) decides to release the UE to the RRC_INACTIVE state (e.g., periodic RNAU) after receiving the RRC connection restoration request message, the base station carries an RRCRelease message in the MSG4 message, which updates the INACTIVE configuration parameters.

[0175] In one example, as shown in Figure 1C, the RRC connection recovery process includes:

[0176] Step S111: The UE sends an RRC Resume Request to the network;

[0177] Step S112: The network sends an RRC release message (RRCRelease) to the UE. The RRCelease message carries the suspend configuration (RRCRelease with suspend configuration).

[0178] (4) The RRC connection is restored to RRC_IDLE;

[0179] In some embodiments, if the base station (network) decides to release the UE to the RRC_IDLE state after receiving the RRC connection restoration request message, the base station carries the RRCRelease message in the MSG4 message.

[0180] In one example, as shown in Figure 1D, the RRC connection recovery process includes:

[0181] Step S121: The UE sends an RRC Resume Request to the network;

[0182] Step S122: The network sends an RRC release message (RRCRelease) to the UE.

[0183] (5) RRC connection recovery failed

[0184] In some embodiments, if at least one of the following occurs: the RRC connection recovery request timer T319 times out, the integrity protection verification of the RRC connection recovery message (MSG4) fails, or cell reselection occurs during the T310 operation, then the RRC connection reconstruction fails for the above reasons, and the UE returns to the RRC_IDLE state.

[0185] In some embodiments, if the gNB does not have the UE's context information, an RRC connection re-establishment message is sent on SRB0 via the downlink common control channel (DL_CCCH). Upon receiving this message, the UE deletes the previous context and performs the RRC connection establishment procedure.

[0186] In one example, as shown in Figure 1E, the RRC connection recovery process includes:

[0187] Step S131: The UE sends an RRC Resume Request to the network;

[0188] Step S132: If there is no UE context information in the network, an RRC connection re-establishment message (RRC Setup) is sent on SRB0 via DL_CCCH;

[0189] Step S133: The UE establishes an RRC connection and sends an RRC connection establishment complete message to the network.

[0190] In some embodiments, the UE receives an RRCReject message, for example, due to network load control reasons. At this time, the UE returns to the initial RRC_INACTIVE state.

[0191] In one example, as shown in Figure 1F, the RRC connection recovery process includes:

[0192] Step S141: The UE sends an RRC Resume Request to the network;

[0193] Step S142: The network sends an RRC connection rejection message (RRCReject) to the UE for reasons such as load control. Therefore, the UE returns to the initial RRC_INACTIVE state.

[0194] It should be noted that both the RRC connection reconstruction and recovery processes require restoring the RRC connection and services based on the existing network context. The RRC connection reconstruction process focuses on restoring the RRC connection and requires an RRC connection reconfiguration message to configure the bearer. The RRC connection recovery process focuses on restoring both the RRC connection and the service bearer; therefore, the RRC connection recovery process has shorter latency. Simultaneously, the RRC connection recovery process offers better security.

[0195] Currently, UEs in the RRC_INACTIVE state need to perform periodic location updates and cross-RNA location updates at the RAN level. They also need to perform periodic location updates and cross-CN registration area location updates at the CN level. For paging monitoring, UEs in the RRC_INACTIVE state need to calculate the PF or PO for paging monitoring based on the minimum of the UE-specific DRX, cell DRX, and RAN DRX, while simultaneously monitoring paging from the CN. This process is redundant and complex for IoT devices.

[0196] It should be noted that, in the embodiments disclosed herein, the term "node" can be replaced by at least one of the terms "network element," "network function," "network device," and "terminal." The term "IoT terminal" can be replaced by "IoT device."

[0197] Based on this, the present disclosure proposes a communication method, communication device, communication system, storage medium, and program product. The first node can provide the terminal access layer context of the first terminal and act as a node to manage the terminal context in order to support communication service requirements. This eliminates the need to distinguish the context management process under different connection states, thereby simplifying RRC_INACTIVE and reducing the functional differentiation and complexity caused by different connection states.

[0198] In some embodiments, the present disclosure can be applied to the following three network architectures.

[0199] In some embodiments, the base station is deployed centrally, or the central unit (CU) and distributed unit (DU) are deployed separately. In this case, the first node 101 is deployed in the access network, and the first node 101 can be a base station, a CU, or a DU.

[0200] Under the above architecture, the first node 101 can be used for functions such as storing, managing and transmitting terminal access layer (AS) context and / or terminal security context.

[0201] In some embodiments, the first node 101 may be, for example, a base station. In this case, physical connections between base stations exist. In one embodiment, one or more other base stations may be registered on the base station, which is used to store the terminal access layer context of itself and other base stations. In one embodiment, the base station is used for I-RNTI of terminals accessing itself and other base stations. Based on this, the base station may be called an anchor base station. The dedicated next-generation (NG) connection of the terminal, that is, the connection between the anchor base station and the core network (CN), can be maintained or released.

[0202] In some embodiments, the first node 101 may be deployed on a CU or DU, for example. In this case, physical connections between CUs exist. In one embodiment, the CU or DU is used to store the terminal access layer context. In another embodiment, the CU or DU is used to allocate the terminal's I-RNTI. Based on this, the CU or DU may be referred to as an anchor CU / DU. At this time, the terminal's dedicated NG connection, that is, the connection between the anchor CU and the CN or the connection between the DU and the CN, can be maintained or released.

[0203] In some embodiments, the first node 101 may be, for example, an anchor base station, an anchor CU, or an anchor DU.

[0204] In some embodiments, the first access network node 102 may be another base station registered with the anchor base station.

[0205] In some embodiments, the first terminal 103 may be an IoT terminal that is connected to other base stations.

[0206] In some embodiments, this disclosure applies to a combination of cloud-end and TRP.

[0207] In some embodiments, multiple TRPs within the RAN area belong to different nodes under the same cloud computing architecture. In this cloud computing architecture, the cloud-end server is responsible for storing the access layer context of the terminal (UE) and assigning the terminal's unique identifier (I-RNTI). At this time, the dedicated NG interface connection of the terminal (UE), i.e., the connection between the cloud-end and the core network (CN), can either remain active or be released as needed.

[0208] In some embodiments, as shown in FIG2A, FIG2A is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure. Specifically, it shows a schematic diagram of the architecture of a cloud-terminal communication system. In the cloud-terminal communication system, one or more TRPs 2102 are registered on the cloud server 2101. The cloud server 2101 is used to store the terminal access layer context of the TRPs 2102 and to assign I-RNTIs to terminals accessing the TRPs.

[0209] It's important to note that the collaboration between TRP and Cloud-end requires optimization across multiple layers (application layer, physical layer) and multiple time scales (task offloading on a large time scale, power control on a small time scale). For example, TRP can offload some tasks to Cloud-end based on real-time data volume and computational complexity, while Cloud-end is responsible for global resource scheduling and management. This multi-layered, multi-time scale optimization strategy can effectively reduce energy consumption and data processing latency.

[0210] In some embodiments, the protocol stack included in the Cloud-end can be at least one of the following:

[0211] Scenario 1: Non-Access Stratum (NAS) NAS, Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC);

[0212] Scenario 2: NAS, RRC, PDCP, RLC, Medium Access Control (MAC) layer;

[0213] Scenario 3: NAS, RRC, PDCP, RLC, MAC, and some physical layer functions, such as baseband processing functions.

[0214] In some embodiments, the first node 101 may be, for example, a cloud server in a cloud computing architecture.

[0215] In some embodiments, the first access network node 102 may be a TRP.

[0216] In some embodiments, the first terminal 103 may be an IoT terminal that accesses the TRP.

[0217] In some embodiments, the present disclosure is applicable to communication systems with access layer center devices (e.g., AS centers) having terminals.

[0218] In some embodiments, the access layer central device is responsible for storing the terminal access layer context and allocating the terminal's identifier I-RNTI. The access layer central device stores at least the terminal's I-RNTI and the terminal's security context (e.g., keys, configured security algorithms, etc.).

[0219] In some embodiments, as shown in Figures 2B and 2C, which are schematic diagrams of another architecture of a communication system provided according to embodiments of the present disclosure, specifically illustrating an architecture of a communication system with an access layer central device. As shown in Figure 2B, in the communication system 100, each network element communicates with each other through application layer protocol signaling; or, as shown in Figure 2C, in the communication system 100, each network element communicates with each other through the Internet Protocol (IP).

[0220] In some embodiments, as shown in FIG2B, one or more access network devices 2202 (such as base stations) are registered on the access layer center (AS center) 2201. The AS center 2201 and one or more access network devices 2202 may communicate using application layer protocol signaling, such as NG Application Protocol (NGAP) signaling.

[0221] In some embodiments, the terminal access layer context of one or more access network devices 2202 (e.g., base stations) can be stored in the AS center 2201. In one embodiment, the AS center 2201 can be deployed in the core network or in the access network. Therefore, the AS center 2201 can be either an access network device or a core network device. In one embodiment, the AS center 2201 and its subordinate access network devices 2202 can communicate via application layer protocol signaling.

[0222] In some embodiments, AS center 2201 and first core network device 2203 (such as AMF) may communicate using application layer protocol signaling, such as NG Application Protocol (NGAP) signaling.

[0223] In some embodiments, referring to Figure 2C, one or more access network devices 2202 (such as base stations) are registered on the access layer center (AS center) 2201, and IP protocol signaling communication can be used between the AS center 2201 and the one or more access network devices 2202. In this case, the AS center 2201 and the access network devices 2202 have a service interface, such as Nas_center.

[0224] In some embodiments, the terminal access layer context of one or more access network devices 2202 (e.g., base stations) can be stored in the AS center 2201. In one embodiment, the AS center 2201 can be deployed in the core network or in the access network. Therefore, the AS center 2201 can be either an access network device or a core network device. In one embodiment, the AS center 2201 and its subordinate access network devices 2202 can communicate via IP protocol signaling.

[0225] In some embodiments, the AS center 2201 and the first core network device 2203 (such as AMF) may communicate using IP protocol signaling.

[0226] In some embodiments, the first node 101 may be AS center 2201.

[0227] In some embodiments, the first access network node 102 is an access network device registered with the first node 101.

[0228] In some embodiments, the first terminal 103 may be an IoT terminal that accesses the first access network node 102.

[0229] In conjunction with the three architectures described above, this disclosure also provides a communication method.

[0230] Figure 3A is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. The communication method involved in the embodiment of the present disclosure can be applied to the communication system 100. As shown in Figure 3A, the communication method of the embodiment of the present disclosure includes steps S3101 to S3105.

[0231] In step S3101, the first terminal sends the seventh information to the first access network node.

[0232] In some embodiments, the first terminal may send a seventh message. In some embodiments, the seventh message may be sent by the first terminal, but is not limited to this, and may also be sent by other entities.

[0233] In some embodiments, the first access network node may receive the seventh information. In some embodiments, the seventh information may be received by the first access network node, but is not limited thereto, and may also be received by other entities.

[0234] In some embodiments, the seventh information, in addition to triggering the RRC recovery process, can also be used to trigger other communication processes related to the terminal access layer context, such as RRC establishment, RRC reconstruction, cell handover, cell reselection in inactive state, and cell selection in idle state. This disclosure does not impose specific limitations on these embodiments. In one example, the network side storing the access layer context can be "RRC_INACTIVE".

[0235] In some embodiments, prior to step S3101, the network may also send a paging message before the RRC recovery process to trigger the first terminal to send a seventh message. In this case, the seventh message indicates a request to restore the RRC connection.

[0236] In some embodiments, the seventh information may include: a terminal identifier of the first terminal. In one example, the terminal identifier of the first terminal may include: an I-RNTI. In another example, the terminal identifier of the first terminal may include: an IMSI (International Mobile Subscriber Identity) and an I-RNTI. The IMSI is used during initial registration or when identity verification is required. In one example, in 5G communication, the terminal identifier of the first terminal may include: an I-RNTI, an IMSI, and a 5G Temporary Mobile Subscriber Identity (5G-S-TMSI). The I-RNTI may be the I-RNTI assigned by the last serving base station carried by the first terminal, used to identify itself.

[0237] In some embodiments, when the network side has downlink data or signaling that needs to be sent to the first terminal, the first terminal is triggered to restore the connection via RAN paging (using I-RNTI).

[0238] In some embodiments, when downlink data arrives at the first node, the first node may send a paging message within its registration area to page the first terminal. In one embodiment, the registration area of ​​the first node includes the radio notification areas of one or more access network nodes registered with the first node. In another embodiment, when downlink data from the first terminal arrives at the first node, the first node may send a paging message from its own registration area to page the first terminal.

[0239] In some embodiments, when downlink data reaches the first node, the first node can send fourth information to the first core network device (such as AMF) to trigger the first core network device to initiate paging on the CN side to page the first terminal. In one embodiment, when downlink data from the first terminal reaches the first node, the first node sends fourth information to the first core network device, and the first core network device sends a paging message for the first terminal within its own registration area based on the fourth information to page the first terminal.

[0240] In some embodiments, the network side may choose not to configure the RRC_INACTIVE configuration parameter in the communication system, that is, the RAN-side mobility parameters carried in the release message are not configured. Examples include RAN notification area, RAN DRX, and RAN periodic location update timer T380. In this case, the first terminal follows CN-level mobility, meaning that when moving within the CN-configured registration area, it does not need to report to the network side; however, it needs to report to the network side when the CN periodic location update timer times out, and it needs to report to the network side when crossing CN registration areas. The first terminal listens for paging from the CN.

[0241] In some embodiments, if the RRC recovery process is not triggered by a paging message from the first terminal, such as if the first terminal actively triggers the RRC recovery process, then step S3101 can be omitted.

[0242] In step S3102, the first access network node sends the first information to the first node.

[0243] In some embodiments, the first access network node may send first information. In some embodiments, the first information may be sent by the first access network node, but is not limited to this, and may also be sent by other entities.

[0244] In some embodiments, the first node may receive the first information. In some embodiments, the first information may be received by the first node, but is not limited to this, and may also be received by other entities.

[0245] In some embodiments, after the first terminal triggers the RRC recovery process, the first information can be sent by the first terminal to the first access network device, and then by the first access network device to the first node. In one example, the first terminal can send an RRC connection recovery request message to the first access network node, in which the first information is carried in the RRC connection recovery request message.

[0246] In some embodiments, the first information may indicate the terminal identifier (such as a first identifier), such as I-RNTI, of the first terminal.

[0247] In some embodiments, the first access network node and the first node can communicate via application layer protocol signaling or IP protocol signaling.

[0248] In step S3103, the first node sends the second information to the first access network node.

[0249] In some embodiments, the first node may send second information. In some embodiments, the second information may be sent by the first node, but is not limited to this, and may also be sent by other entities.

[0250] In some embodiments, the first access network node may receive the second information. In some embodiments, the second information may be received by the first access network node, but is not limited thereto, and may also be received by other entities.

[0251] In some embodiments, after receiving the first information, the first node determines the terminal access layer context (such as the first terminal access layer context) of the first terminal based on the first information, and then sends the second information to the first access network node based on the first terminal access layer context.

[0252] In some embodiments, the first node may store terminal access layer contexts of one or more access network devices. These terminal access layer contexts are generated and stored in the first node during communication between one or more terminals and these access network devices.

[0253] In some embodiments, the first identifier in the first information is used to identify the first terminal. In this way, when the first information sent by the first access network node arrives at the first node, the first node can know which terminal's access layer context the first access network node is requesting, and then send the terminal access layer context (such as the first terminal access layer context) associated with the first identifier to the first access network node in preparation for the subsequent restoration of the RRC connection.

[0254] In some embodiments, the second information includes a first terminal access layer context, which is the terminal access layer context of the first terminal.

[0255] In some embodiments, a first access network node sends first information to a first node, and the first node addresses a terminal access layer context, such as a first terminal access layer context, in the first information based on a first identifier. The first node then sends the first terminal access layer context to the first access network node.

[0256] In some embodiments, the second information may further include a second identifier of the first terminal. The second identifier is an identifier assigned by the first node to the first terminal for use in the next communication. The second identifier may be a new identifier assigned to the first terminal for use in the next communication process.

[0257] In some embodiments, the first node may also assign a new identifier to the first terminal in this communication, and the new identifier will be used for the next communication. In one embodiment, the first node sends the new identifier to the first access network node.

[0258] In some embodiments, the second identifier may be a new I-RNTI.

[0259] In some embodiments, the second information may also include the terminal security context (e.g., UE Security Context) of the first terminal.

[0260] In some embodiments, after receiving the first information, the first node may further configure a terminal security context for the first terminal in this communication to restore the RRC connection. In one embodiment, the first node determines the terminal security context of the first terminal and sends the terminal security context to the first access network node.

[0261] In some embodiments, the terminal security context of the first terminal can be used for security and integrity protection.

[0262] In some embodiments, the terminal security context may include an NCC (Non-Containment Code). The NCC is a key derivation-related counter used to identify key sequences derived from a base key (such as K_AMF or NH). The NCC is part of the terminal security context and is used to manage encryption and integrity protection keys between the terminal and the network. This ensures that the terminal and the network can correctly recognize and use the latest key each time it is updated, thereby guaranteeing the security of communication.

[0263] In step S3104, the first access network node sends the eighth information to the first terminal.

[0264] In some embodiments, the first access network node may send the eighth information. In some embodiments, the eighth information may be sent by the first access network node, but is not limited to this, and may also be sent by other entities.

[0265] In some embodiments, the first terminal may receive the eighth information. In some embodiments, the eighth information may be received by the first terminal, but is not limited thereto, and may also be received by other entities.

[0266] In some embodiments, after obtaining the second information, the first access network node can continue to communicate with the first terminal. The first node initiates a communication response to the first terminal, thereby realizing communication with the first terminal.

[0267] In some embodiments, the first access network node sends an RRC connection restoration message to the first terminal to restore the RRC connection and establish radio bearers such as SRB1, SRB2, and DRB. SRB1 and SRB2 are used for signaling transmission, while DRB is used for user data transmission, ensuring that the terminal can communicate efficiently with the network.

[0268] In some embodiments, the eighth information may include: radio bearer configuration and terminal security context, such as reactivating or configuring SRB1, SRB2 and DRB (data radio bearer).

[0269] In some embodiments, the first access network node sends an eighth message based on the terminal security context to protect the integrity of the communication between the first access network node and the first terminal.

[0270] In some embodiments, the eighth information may further include a second identifier of the first terminal for use by the first terminal in the next instance.

[0271] In step S3105, the first terminal sends the ninth information to the first access network node.

[0272] In some embodiments, the first terminal may send a ninth message. In some embodiments, the ninth message may be sent by the first terminal, but is not limited thereto, and may also be sent by other entities.

[0273] In some embodiments, the first access network node may receive the ninth information. In some embodiments, the ninth information may be received by the first access network node, but is not limited thereto, and may also be received by other entities.

[0274] In some embodiments, the first terminal responds to the eighth message received from the first access network node by sending a ninth message to the first access network node. In one embodiment, the ninth message is used to indicate that RRC recovery is complete. In one example, the ninth message can be "RRC Resume Complete".

[0275] In some embodiments, the first terminal activates the radio bearer according to the eighth information, restores the configuration of SRB1, SRB2, and DRB, and completes the recovery process. At this time, the first terminal sends the ninth information to the first access network node and enters the connected state to prepare for data transmission. In one embodiment, after restoring the terminal security context (including encryption and integrity protection keys) and reactivating the radio bearer, the first terminal sends an RRC Resume Complete message.

[0276] In some embodiments, the first terminal sends the ninth information based on the terminal security context in the eighth information to protect the security and integrity of the communication between the first access network node and the first terminal.

[0277] In some embodiments, the ninth information may include: the first identifier of the first terminal.

[0278] Thus, steps S3101 to S3105 above complete the RRC connection recovery process.

[0279] Figure 3B is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. The communication method involved in this embodiment can be applied to a communication system 100. As shown in Figure 3B, the communication method of this embodiment includes steps S3201 to S3202.

[0280] In step S3201, the first access network node sends the fifth information to the first node.

[0281] In some embodiments, the first access network node may send the fifth information. In some embodiments, the fifth information may be sent by the first access network node, but is not limited thereto, and may also be sent by other entities.

[0282] In some embodiments, the first node may receive the fifth information. In some embodiments, the fifth information may be received by the first node, but is not limited thereto, and may also be received by other entities.

[0283] In some embodiments, when a first access network node determines that it is releasing the RRC connection with a first terminal, the first access network node may send a fifth message to the first node to instruct the first node to store the context of the first terminal.

[0284] In some embodiments, the fifth information includes a first identifier of the first terminal, a second terminal access layer context, and a first terminal security context of the first terminal.

[0285] In some embodiments, the second terminal access layer context is the latest terminal access layer context of the first terminal in the first access network node. The first access network node sends the second terminal access layer context to the first node for storage, so that the first terminal can subsequently restore the RRC connection based on the latest terminal access layer context.

[0286] In some embodiments, the fifth information is used to trigger the first node to associate and store the first identifier, the second terminal access layer context, and the first terminal security context of the first terminal. In one embodiment, after receiving the fifth information, the first node can associate and store the first identifier, the second terminal access layer context, and the first terminal security context.

[0287] In step S3202, the first access network node sends the tenth information to the first terminal.

[0288] In some embodiments, the first access network node may send tenth information. In some embodiments, the tenth information may be sent by the first access network node, but is not limited thereto, and may also be sent by other entities.

[0289] In some embodiments, the first terminal may receive the tenth information. In some embodiments, the tenth information may be received by the first terminal, but is not limited thereto, and may also be received by other entities.

[0290] In some embodiments, after the first node associates and stores the first identifier of the first terminal, the access layer context of the second terminal, and the first terminal security context of the first terminal, the first access node sends a tenth message to the first terminal. In one embodiment, the tenth message indicates the release of the RRC connection. In one example, the tenth message may be RRCRelease.

[0291] In some embodiments, the tenth information may further include: a second identifier of the first terminal, such as a new I-RNTI. In this case, the second identifier is included in the second information sent by a node to the first access network node.

[0292] In some embodiments, the first access network node provides a second identifier to the first terminal via tenth information, for the first terminal to use when it needs to look up the terminal access layer context later. In one example, the second identifier can be used by the first terminal to initiate RRC recovery.

[0293] Thus, steps S3201 to S3202 above complete the RRC connection release process.

[0294] In some embodiments, steps S3201 and S3202 may be performed in an alternate order or simultaneously.

[0295] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0296] Figure 3C is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. The communication method involved in the embodiment of the present disclosure can be applied to the communication system 100. As shown in Figure 3C, the communication method of the embodiment of the present disclosure includes steps S3301 to S3303.

[0297] In some embodiments,

[0298] In step S3301, the first access network node sends the fifth information to the first node.

[0299] In some embodiments, the first access network node may send the fifth information. In some embodiments, the fifth information may be sent by the first access network node, but is not limited thereto, and may also be sent by other entities.

[0300] In some embodiments, the first node may receive the fifth information. In some embodiments, the fifth information may be received by the first node, but is not limited thereto, and may also be received by other entities.

[0301] In some embodiments, when a first access network node determines that it is releasing the RRC connection with a first terminal, the first access network node may send a fifth message to the first node to instruct the first node to store the context of the first terminal.

[0302] In some embodiments, the fifth information includes a first identifier of the first terminal, a second terminal access layer context, and a first terminal security context of the first terminal.

[0303] In some embodiments, the second terminal access layer context is the latest terminal access layer context of the first terminal in the first access network node. The first access network node sends the second terminal access layer context to the first node for storage, so that the first terminal can subsequently restore the RRC connection based on the latest terminal access layer context.

[0304] In some embodiments, the fifth information is used to trigger the first node to associate and store the first identifier, the second terminal access layer context, and the first terminal security context of the first terminal. In one embodiment, after receiving the fifth information, the first node can associate and store the first identifier, the second terminal access layer context, and the first terminal security context.

[0305] In step S3302, the first node sends the sixth information to the first access network.

[0306] In some embodiments, the first node may send a sixth message. In some embodiments, the sixth message may be sent by the first node, but is not limited to this, and may also be sent by other entities.

[0307] In some embodiments, the first access network node may receive the sixth information. In some embodiments, the sixth information may be received by the first access network node, but is not limited thereto, and may also be received by other entities.

[0308] In some embodiments, the sixth information includes a second identifier of the first terminal. In one embodiment, after receiving the fifth information, the first node assigns a new terminal identifier, such as the second identifier, to the first terminal and sends it to the first access network node via the sixth information.

[0309] In some embodiments, the sixth information may further include the second terminal security context of the first terminal. Here, the second terminal security context is the latest terminal security context of the first terminal on the network side. In one example, the second terminal security context includes the latest NCC of the first terminal.

[0310] In some embodiments, the terminal security context of the first terminal can be provided by the first node. Then, after receiving the fifth information, the first node determines the latest terminal security context for the first terminal, such as the second terminal security context, and sends it to the first access network node through the sixth information.

[0311] In some embodiments, the terminal security context of the first terminal can be provided by the first core network device. Then, after receiving the fifth information, the first node requests the terminal security context of the first terminal from the first core network device. The first core network device determines the latest terminal security context (such as the second terminal security context) for the first terminal and sends it to the first node. The first node sends the latest terminal security context of the first terminal from the first core network device to the first access network node through the sixth information.

[0312] In step S3303, the first access network node sends the tenth information to the first terminal.

[0313] In some embodiments, the first access network node may send tenth information. In some embodiments, the tenth information may be sent by the first access network node, but is not limited thereto, and may also be sent by other entities.

[0314] In some embodiments, the first terminal may receive the tenth information. In some embodiments, the tenth information may be received by the first terminal, but is not limited thereto, and may also be received by other entities.

[0315] In some embodiments, after the first node associates and stores the first identifier of the first terminal, the access layer context of the second terminal, and the first terminal security context of the first terminal, the first access node sends a tenth message to the first terminal. In one embodiment, the tenth message indicates the release of the RRC connection. In one example, the tenth message may be RRCRelease.

[0316] In some embodiments, the tenth information may include: a second identifier of the first terminal, such as a new I-RNTI.

[0317] In some embodiments, the first access network node provides a second identifier to the first terminal via tenth information, for the first terminal to use when it needs to look up the terminal access layer context later. In one example, the second identifier can be used by the first terminal to initiate RRC recovery.

[0318] Thus, steps S3301 to S3303 above complete the RRC connection release process.

[0319] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0320] Figure 3D is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. The communication method involved in the embodiment of the present disclosure can be applied to the communication system 100. As shown in Figure 3D, the communication method of the embodiment of the present disclosure includes steps S3401 to S3402.

[0321] In some embodiments, the first node is a network node in the storage terminal access layer context. In one embodiment, the first node may be deployed in the core network. In one example, the first node may be a first core network device. In some embodiments, the first node may be deployed in the access network. In one example, the first node may be a first access network node.

[0322] In some embodiments, the first node may be the first node 101 shown in Figures 2A to 2C.

[0323] In step S3401, the first terminal sends the first information to the first node.

[0324] In some embodiments, the first terminal may send first information. In some embodiments, the first information may be sent by the first terminal, but is not limited to this, and may also be sent by other entities.

[0325] In some embodiments, the first node may receive the first information. In some embodiments, the first information may be received by the first node, but is not limited to this, and may also be received by other entities.

[0326] In some embodiments, the first information is used to request a first terminal access layer context. In one embodiment, the first terminal may send the first information to the first node during the initial access process to request the network side to establish a first terminal access layer context for the first terminal. In one example, the first information may be carried in a random access message sent to the first node. For example, Msg1 (such as PRACH Preamble), Msg3 (such as RRC Connection Request), Msg5 (such as RRC Setup Complete), etc.

[0327] In some embodiments, for an IoT terminal, multiple terminal access layer contexts can be predefined, and these terminal access layer contexts can be referred to as default terminal access layer contexts. The first terminal access layer context requested by the first information can be one of the multiple default terminal access layer contexts.

[0328] In some embodiments, the default terminal access layer context may include, but is not limited to: packet data unit (PDU) session, radio bearer configuration, physical channel configuration, MAC configuration, etc.

[0329] In some embodiments, the first information is further used to indicate the first terminal access layer context. In one embodiment, the first information indicates at least one of the following: the context index of the first terminal; the device type of the first terminal; the service type of the first terminal; the network slice associated with the first terminal; and the terminal identifier of the first terminal. Thus, the first node can determine the first terminal access layer context based on the first information. In one example, the first information may include at least one of the following: the index of the default terminal access layer context, the device type of the first terminal (e.g., IoT device type), the service type (the service type of the first terminal), the terminal identifier of the first terminal, or information about the network slice to which the first terminal is located.

[0330] In one example, the device type of the first terminal may include: sensor device, control device, positioning device, security device, etc.

[0331] In one example, the service type of the first terminal may include: smart home, smart transportation, smart healthcare, industrial IoT, smart agriculture, etc.

[0332] In one example, the terminal identifier of the first terminal can be I-RNTI.

[0333] In one example, the network slice associated with the first terminal can be a single network slice selection assistance information (S-NSSAI).

[0334] In some embodiments, the first terminal may also send the first information to the first access network node, and request the second information from the first node through the first access network node. The first node may be the first node 101 in the above embodiments.

[0335] In some embodiments, the first information may also be carried in the connection restoration request (access restoration process), and this disclosure does not impose any limitations.

[0336] In step S3402, the first node sends the second information.

[0337] In some embodiments, the first node may send second information. In some embodiments, the second information may be sent by the first node, but is not limited to this, and may also be sent by other entities.

[0338] In some embodiments, the first access network node may receive the second information. In some embodiments, the second information may be received by the first access network node, but is not limited thereto, and may also be received by other entities.

[0339] In some embodiments, the first terminal may receive the second information. In some embodiments, the second information may be received by the first terminal, but is not limited thereto, and may also be received by other entities.

[0340] In some embodiments, the first node may determine a first terminal access layer context from multiple terminal access layer contexts according to the indication of the first information, and send second information to the first access network node and / or the first terminal according to the first terminal access layer context.

[0341] In some embodiments, the second information includes a first terminal access layer context, which is a terminal access layer context determined by the network for the first terminal from a plurality of default terminal access layer contexts.

[0342] In some embodiments, the second information further includes a second terminal security context, which is a terminal security context determined by the network for the first terminal. In one embodiment, the second terminal security context may be provided by the access network and / or the core network.

[0343] In some embodiments, after receiving the second information, the first terminal can communicate with the network based on the second information.

[0344] In some embodiments, after the first terminal access layer context, during the RRC connection recovery process of the first terminal, the first node may also send a second terminal security context to the first terminal and / or the first access network node.

[0345] In some embodiments, the terminal security context of the second terminal may be provided by the first node. Then, after receiving the first information, the first node determines the latest terminal security context for the first terminal, such as the second terminal security context, and sends it to the first access network node through the second information.

[0346] In some embodiments, the terminal security context of the first terminal can be provided by the first core network device. Then, after receiving the first information, the first node requests the terminal security context of the first terminal from the first core network device. The first core network device determines the latest terminal security context for the first terminal, such as the second terminal security context, and sends it to the first node. The first node sends the latest terminal security context of the first terminal from the first core network device to the first access network node through the second information.

[0347] In some embodiments, the second information further includes a second identifier of the first terminal. The second identifier is used for the first terminal's next communication.

[0348] In some embodiments, after the first terminal completes the initial access procedure, the first node may also update the access layer context of the first terminal based on third information. In one embodiment, the third information may be sent by the first terminal. In another embodiment, the third information may be determined by the first node based on QoS.

[0349] In some embodiments, the above process is not limited to the application of RRC recovery and release processes. Any process that uses context can be applied, such as cell handover, cell reselection in inactive state, cell selection in idle state, etc. The embodiments disclosed herein are not limited.

[0350] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0351] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0352] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0353] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0354] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0355] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0356] In some embodiments, the terms "service", "business", and "traffic" can be used interchangeably.

[0357] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0358] In the following, the technical solutions of the embodiments of this disclosure will be described by way of specific implementation.

[0359] In some embodiments, the communication method provided in this disclosure can be applied to communication systems in the following three situations.

[0360] In one example, the architecture of the first communication system is described. Embodiments of this disclosure are applicable to gNB, or CU, DU separated architectures.

[0361] In a base station architecture, physical connections exist between base stations. One base station stores the terminal's Access Stratum (AS) context and assigns the terminal's Inactive Radio Network Temporary Identifier (I-RNTI). This base station can be called the anchor base station. At this point, the terminal's dedicated NG link, i.e., the connection between the anchor base station and the core network (CN), can be maintained or released.

[0362] In the CU-DU architecture, physical connections exist between CUs. One CU and / or DU is used to store the terminal access layer context and allocate the terminal's I-RNTI; this CU and / or DU can be called the anchor CU / DU. At this point, the terminal's dedicated NG connection, i.e., the link between the anchor CU / DU and the CN, can be maintained or released.

[0363] In some embodiments, the second communication system architecture is "Cloud-end" + TRP. In this architecture, the RAN area belongs to different TRPs within the same "Cloud-end". The "Cloud-end" is responsible for storing the UE access layer context and allocating the UE identifier I-RNTI. At this time, the UE's dedicated NG link, i.e., the link between the cloud end and the CN, can be maintained or released. The protocol stack included in the "Cloud-end" may be:

[0364] Option 1: NAS, RRC, PDCP, RLC;

[0365] Option 2: NAS, RRC, PDCP, RLC, MAC;

[0366] Option 2: NAS, RRC, PDCP, RLC, MAC, and some physical layer functions, such as baseband processing functions.

[0367] In some embodiments, a third communication system architecture is described. This disclosure defines a UE AS center, which stores the UE access layer context. At least one AS center can be deployed on the network side. The AS center is responsible for storing the UE access layer context and assigning the UE identifier (I-RNTI). The AS center stores at least the UE's I-RNTI and UE security context (e.g., keys, configured security algorithms, etc.). The AS center can also be a base station. The location and link relationships of the AS on the network side can be as follows:

[0368] In architecture 1, the AS center can belong to either a node in the RAN or a node in the CN. The AS center manages the UE access layer context of at least one base station. The base station and the AS center are connected via NGAP-like signaling.

[0369] In architecture 2, the AS center can belong to either a node in the RAN or a node in the CN. The AS center manages the UE access layer context of at least one base station. The base station and the AS center are connected via IP.

[0370] In some embodiments, the communication methods provided in this disclosure include Scheme 1 and Scheme 2.

[0371] Option 1 assumes that the network side stores the UE access layer context, named "RRC_INACTIVE". Then:

[0372] The network side can choose not to configure the RRC_INACTIVE configuration parameters in NR, such as RAN notification area, RAN DRX, and RAN periodic location update timer T380. In this case, the UE follows CN-level mobility rules; that is, when moving within the CN-configured registration area, it does not need to report to the network side, but it must report to the network side when the CN periodic location update timer times out, and it must report to the network side when crossing CN registration areas. The UE listens for paging from the CN.

[0373] In some embodiments, paging includes at least one of the following:

[0374] If the DL data reaches the CN, the CN will initiate a CN paging process.

[0375] When DL data reaches the anchor base station or cloud end, the base station or cloud end initiates a paging process for the registered area.

[0376] When DL data reaches the anchor base station or cloud end, the base station or cloud end notifies the CN to initiate a CN-level paging.

[0377] In some embodiments, for an AS center network architecture (i.e., the architecture of a third communication system).

[0378] In some embodiments, when the UE needs to restore the RRC connection, the following is included:

[0379] 1. The UE initiates an RRC connection restoration request to the base station. The RRC connection restoration request must carry at least the UE's identification information or the terminal identification.

[0380] 2. The serving base station addresses the AS center based on the UE's identification information and obtains the UE's access layer context information. Simultaneously, the AS center can also provide a new I-RNTI (new UE identifier) ​​for the next use.

[0381] 3. The base station initiates an RRC connection restoration message to the UE. The RRC connection restoration message can also carry the newly allocated I-RNTI mentioned above, restore the RRC connection, and establish SRB1 / 2 and DRB, etc.

[0382] In some embodiments, when the UE needs to release the RRC connection, the following is included:

[0383] 1. The serving base station requests the AS center to store the UE context, carrying the newly allocated I-RNTI and AS security context, such as NCC.

[0384] In this embodiment, newly allocated I-RNTs may also be allocated after a request for release, and this disclosure does not impose any restrictions.

[0385] In some embodiments, the newly assigned AS security context can be obtained by the AS center from the AMF requesting a new NCC, or it can be generated by the AS center itself.

[0386] 2. The serving base station sends an RRC connection release message to the UE. The RRC connection release message contains I-RNTI and AS security context, such as NCC.

[0387] Option 2: The network side or system predefines multiple UE access layer contexts, and each UE access layer context is associated with an index, IoT device type, service type, or slice.

[0388] In some embodiments, during the initial access process, the UE indicates to the network side the default context index, IoT device type, service type, or slice that the UE needs to establish. This can be indicated, for example, through RO and / or preamble, or through indication information in MSG3 or MSG5. Based on the terminal's indication information, the UE requests the network side for the default access layer context. The network side configures the access layer context for the UE and restores the RRC connection based on the default UE access layer context (without needing to obtain UE capability information).

[0389] In some embodiments, the UE can only perform the most basic communication. Subsequently, the UE access layer context can be adjusted based on the UE's instructions or by the network side according to the service QOs.

[0390] In some embodiments, the base station, based on the UE context requested by the UE, may request specific configuration information of the context from a node in the access network or a node in the CN, based on an index, IoT device type, service type, or slice, i.e., update the UE's default access stratum context. After obtaining the updated specific context information, the base station restores the RRC connection to the UE.

[0391] In some embodiments, while obtaining the UE's default access layer context, terminal security context such as keys and security algorithms can also be obtained simultaneously. The above implementation is not limited to processes such as RRC recovery and release; it can be applied to any process that uses context, such as cell handover, cell reselection in inactive state, and cell selection in idle state.

[0392] In some embodiments, the default access layer context of a UE includes, but is not limited to: PDU session, radio bearer configuration, physical channel configuration, MAC configuration, etc.

[0393] In one example, the RRC recovery process is used as an example:

[0394] (1) The UE carries the association information of the UE identifier and the UEAS default context, such as the context index, through the RRRCResumerequest message.

[0395] (2) The network side requests the core network's network side for context configuration information through the UE identifier and context association information.

[0396] (3) The core network provides context configuration information (UE default access layer context), and optional information includes UE capability information, key information, and supported security algorithms.

[0397] (4) The network side sends an RRCresume to the UE, indicating that the UE's default access layer context is activated. The RRCresume can be integrity protected, but it is not encrypted.

[0398] (5) The UE performs integrity protection verification on the cell. If it passes, it sends an RRCResumeComplete message, which is both encrypted and performs integrity protection.

[0399] In some embodiments, the functionality of RRC_INACTIVE is simplified by enhancing it and merging it with the RRC_IDLE feature, avoiding functional complexity and fragmentation. Simultaneously, to quickly establish services, a default UE access layer context can be defined for specific IoT devices to achieve rapid UE establishment and data transmission.

[0400] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, this disclosure proposes an apparatus that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0401] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0402] In this disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a central processing unit (CPU), microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented as an application-specific integrated circuit (ASIC) or a programmable logic device (FPGA). In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), etc.

[0403] Figure 4 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. As shown in Figure 4, the communication device 400 may include at least one of the following: a transceiver module 401, a processing module 402, and a storage module 403.

[0404] In some embodiments, the communication device 400 may be a first node 101. In some embodiments, the processing module 402 is configured as a transceiver module, configured to receive first information and, based on the first information, send second information, the second information including a first terminal access layer context, the first terminal access layer context being the terminal access layer context of the first terminal. Optionally, the transceiver module 401 may be used to perform at least one of the communication steps, such as sending and / or receiving, performed by the first node 101 in any of the above methods, which will not be elaborated here. Optionally, the transceiver module 401 may be used to perform at least one of the other steps performed by the first node 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module 402 may be used to perform at least one of the other steps performed by the first node 101 in any of the above methods, which will not be elaborated here. Optionally, the storage module 403 may be used to perform at least one of the other steps, such as storage, performed by the first node 101 in any of the above methods, which will not be elaborated here.

[0405] In some embodiments, the communication device 400 may be a first access network node 102. In some embodiments, the transceiver module 401 may be configured to send first information to the first node, the first information being used to instruct the first node to send second information, the second information including a first terminal access layer context, the first terminal access layer context being the terminal access layer context of the first terminal, and the first access network node being the serving node of the first terminal. Optionally, the transceiver module 401 may be used to perform at least one of the communication steps such as sending and / or receiving performed by the first access network node 102 in any of the above methods, which will not be elaborated here.

[0406] In some embodiments, the communication device 400 may be a first terminal 103. In some embodiments, the transceiver module 401 may be configured to send first information to a first node, the first information being used to instruct the first node to send second information, the second information including a first terminal access layer context, which is a terminal access layer context associated with the first information among a plurality of terminal access layer contexts. Optionally, the transceiver module 401 may be used to perform at least one of the communication steps such as sending and / or receiving performed by the first terminal 103 in any of the above methods, which will not be elaborated here.

[0407] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting and receiving modules may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0408] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0409] In some embodiments, the storage module may optionally be interchanged with the memory.

[0410] Figure 5A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. The communication device 5100 may be at least one of a first node, a first access network node, and a first terminal, or it may be a chip, chip system, or processor that supports at least one of the first node, the first access network node, and the first terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0411] As shown in Figure 5A, the communication device 5100 includes one or more processors 5101. The processor 5101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 can be used to execute any of the above methods. Optionally, one or more processors 5101 can be used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0412] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above-described method, and the processor 5101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0413] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data. Optionally, all or part of the memories 5103 may be located outside the communication device 5100. In optional embodiments, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuits 5104 are connected to the memories 5103 and can be used to receive data from the memories 5103 or other devices, and to send data to the memories 5103 or other devices. For example, the interface circuits 5104 can read data stored in the memories 5103 and send the data to the processor 5101.

[0414] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0415] Figure 5B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of the chip 5200 shown in Figure 5B, but it is not limited thereto.

[0416] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0417] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, interface circuit 5202 is connected to memory 5203, and interface circuit 5202 can be used to receive data from memory 5203 or other devices, and interface circuit 5202 can be used to send data to memory 5203 or other devices. For example, interface circuit 5202 can read data stored in memory 5203 and send the data to processor 5201.

[0418] In some embodiments, the interface circuit 5202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 5202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 5202 performs data interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of the other steps.

[0419] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0420] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 5100, cause the communication device 5100 to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0421] This disclosure also provides a program product that, when executed by a communication device 5100, causes the communication device 5100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0422] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0423] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are considered as one example only.

[0424] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A communication method, executed by a first node, the method comprising: Receive the first message; Based on the first information, second information is sent, the second information including a first terminal access layer context, the first terminal access layer context being the terminal access layer context of the first terminal.

2. The method according to claim 1, wherein, The first information is sent by the first terminal, and the first information indicates at least one of the following: The context index of the first terminal; The device type of the first terminal; The service type of the first terminal; The network slice associated with the first terminal; The terminal identifier of the first terminal.

3. The method according to claim 2, wherein, The first terminal access layer context is the terminal access layer context associated with the first information among multiple terminal access layer contexts.

4. The method according to any one of claims 1 to 3, wherein, The first information is received by the first node during the initial access process of the first terminal.

5. The method according to claim 4, wherein, The method further includes: The first terminal access layer context is updated based on the third information, which is sent by the first terminal and / or determined by the first node based on the Quality of Service (QoS).

6. The method according to claim 1, wherein, One or more access network nodes are registered on the first node, and the terminal access layer context of the one or more access network nodes is stored in the first node; The first information is sent by a first access network node among the one or more access network nodes. The first access network node is the service node of the first terminal. The first information includes a first identifier of the first terminal, and the access layer context of the first terminal is associated with the first identifier.

7. The method according to claim 6, wherein, The first node is deployed in one of the following: core network, access network, or cloud.

8. The method according to claim 6 or 7, wherein, The first node communicates with the one or more access network nodes via application layer protocol signaling; or, the first node communicates with the one or more access network nodes via Internet Protocol.

9. The method according to any one of claims 6 to 8, wherein, The method also includes one of the following: Send a paging message within the registration area of ​​the first node, wherein the registration area includes the wireless notification area of ​​the one or more access network nodes; A fourth message is sent to the first core network device, the fourth message being used to trigger the first core network device to send a paging message.

10. The method according to any one of claims 6 to 9, wherein, The method further includes: The system receives fifth information sent by the first access network node, the fifth information including the first identifier, the second terminal access layer context, and the first terminal security context of the first terminal. The first identifier, the second terminal access layer context, and the first terminal security context of the first terminal are associated and stored.

11. The method according to claim 10, wherein, The method further includes: A sixth message is sent to the first access network node. The sixth message includes a second identifier of the first terminal, which is an identifier assigned by the first node for the first terminal for the next use.

12. The method according to any one of claims 6 to 10, wherein, The second information also includes a second identifier of the first terminal, which is an identifier assigned by the first node for the first terminal for the next use.

13. The method according to any one of claims 1 to 12, wherein, The second information also includes the second terminal security context of the first terminal.

14. A communication method, executed by a first access network node, the method comprising: Send first information to the first node, the first information being used to instruct the first node to send second information, the second information including a first terminal access layer context, the first terminal access layer context being the terminal access layer context of the first terminal, and the first access network node being the service node of the first terminal.

15. The method according to claim 14, wherein, One or more access network nodes are registered on the first node, and the terminal access layer context of the one or more access network nodes is stored in the first node. The first information includes a first identifier of the first terminal, and the first terminal access layer context is associated with the first identifier.

16. The method according to claim 15, wherein, The first node is deployed in one of the following: core network, access network, or cloud.

17. The method according to claim 15 or 16, wherein, The first node communicates with the one or more access network nodes via application layer protocol signaling; or, the first node communicates with the one or more access network nodes via Internet Protocol.

18. The method according to any one of claims 15 to 17, wherein, The method further includes: Send a fifth message to the first node. The fifth message includes the first identifier, the second terminal access layer context, and the first terminal security context of the first terminal. The fifth message is used to trigger the first node to associate and store the first identifier, the second terminal access layer context, and the first terminal security context of the first terminal.

19. The method according to claim 18, wherein, The method further includes: The system receives a sixth message sent by the first node, the sixth message including a second identifier of the first terminal, the second identifier being an identifier assigned by the first node for the first terminal for the next use.

20. The method according to any one of claims 15 to 18, wherein, The second information also includes a second identifier of the first terminal, which is an identifier assigned by the first node for the first terminal for the next use.

21. The method according to any one of claims 14 to 20, wherein, The second information also includes the second terminal security context of the first terminal.

22. A communication method, executed by a first terminal, the method comprising: Send first information to the first node, the first information being used to instruct the first node to send second information, the second information including a first terminal access layer context, the first terminal access layer context being a terminal access layer context associated with the first information among a plurality of terminal access layer contexts.

23. The method according to claim 22, wherein, The first information indicates at least one of the following: The context index of the first terminal; The device type of the first terminal; The service type of the first terminal; The network slice associated with the first terminal; The terminal identifier of the first terminal.

24. The method according to any one of claims 22 to 23, wherein, The first information is received by the first node during the initial access process of the first terminal.

25. The method according to claim 24, wherein, The method further includes: A third message is sent to the first node, the third message being used to trigger the first node to update the first terminal access layer context.

26. A communication device, wherein, The communication device is used to perform the communication method as described in any one of claims 1 to 13, 14 to 21, and 22 to 25.

27. A communication system, comprising a first node, a first access network node, and a first terminal, wherein, The first node is configured to implement the communication method as described in any one of claims 1 to 13, the first access network node is configured to implement the communication method as described in any one of claims 14 to 21, and the first terminal is configured to implement the communication method as described in any one of claims 22 to 25.

28. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the communication method as described in any one of claims 1 to 13, 14 to 21, and 22 to 25.

29. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the communication method as described in any one of claims 1 to 13, 14 to 21, and 22 to 25.

Images