Data transmission method, apparatus and system

Abstract

The present application provides a data transmission method, apparatus and system, applied to the technical field of communications. The data transmission method provided by the present application comprises: a terminal device receives a connection release message sent by a first network device, wherein the connection release message comprises first information, the first information is used for indicating the terminal device, and the first information is used for identifying the first network device within a first range; and the terminal device transmits a connection establishment request message to a second network device, wherein the connection establishment request message comprises second information, the second information is used for identifying the first network device within a second range, and the second range is smaller than the first range.

Description

Data transmission method, device and system Technical Field

[0001] The present application relates to the field of communication technologies, and in particular to data transmission methods, devices, and systems. Background Art

[0002] In NR (New Radio) technology, the access network manages device context and is responsible for some mobility management. For example, in NR technology, the RRC_INACTIVE state (Radio Resource Control - Inactive state) transitions from the RRC_CONNECTED state (Radio Resource Control - Connected state) via an RRC release message. When the device is released from the RRC_CONNECTED state to the RRC_INACTIVE state, the network device assigns the device an identifier, an I-RNTI (Inactive Radio Network Temporary Identifier), and uses this identifier to store the device context. This network device is also called the UE's last serving gNB (sometimes referred to as the anchor gNB). When a device requests to resume a previously suspended Radio Resource Control (RRC) connection or perform a RAN Notification Area (RNA) update, it sends an RRCResumeRequest message to the current network device. For example, the I-RNTI is used in RRC signaling for the network device to address the device. The I-RNTI consists of a portion that identifies the device and a portion that identifies the network device. With existing technologies, in mobility management, it is difficult to use an identifier sent by a network device to a terminal device to uniquely identify a network device in the entire network.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a data transmission method, apparatus, and system for solving the problem that it is difficult to use an identifier sent by a network device to a terminal device to identify a unique network device in the entire network during mobility management.

[0005] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0006] In the first aspect, a data transmission method is provided, which can be executed by a terminal device, or by a component of the terminal device (such as a processor, chip, or chip system, etc.), or by a logic module or software that can realize all or part of the functions of the terminal device. The following is an illustration of the method using a terminal device as an example of the execution subject, and the method includes: the terminal device receives a connection release message sent by a first network device, the connection release message includes first information, the first information is used to indicate the terminal device, and the first information is used to identify the first network device within a first range; the terminal device sends a connection establishment request message to a second network device, the connection establishment request message includes second information, the second information is used to identify the first network device within a second range, and the second range is smaller than the first range.

[0007] Through the above method, the terminal device receives the first information sent from the first network device, and the first information can be used to identify the first network device globally. Part or all of the above first information can be used by the terminal device when it subsequently establishes a connection with other network devices (such as the second network device). It can retrieve the terminal device identification of a unique UE in the entire network, so that other network devices (such as the second network device) can accurately identify and find the terminal device in the entire network.

[0008] In one possible implementation, the terminal device receives a connection establishment response message, which instructs the terminal device to send information used to identify the first network device within the first range; the terminal device sends a connection establishment completion message, which includes third information, and the third information is used to identify the first network device within the first range.

[0009] In a possible implementation manner, the terminal device receives a connection establishment permission message.

[0010] In a possible implementation, the first information and the second information are further used to identify a terminal device context (UE Context).

[0011] In a possible implementation, the first information includes one of the following:

[0012] Enhanced Inactive Radio Network Temporary Identity (eI-RNTI);

[0013] The first part of the network device identifier, the second part of the network device identifier, and the terminal device context identifier (UE context ID);

[0014] Inactive Radio Network Temporary Identifier (I-RNTI) and network device identifier;

[0015] I-RNTI and the first part of the network device identifier;

[0016] The first part of the network device identifier and the second part of the network device identifier are used to identify the first network device within the first range, and the second part of the network device identifier is used to identify the first network device within the second range.

[0017] In a possible implementation, the second information includes one of the following:

[0018] I-RNTI;

[0019] The second part of the network equipment identifier and the UE context ID;

[0020] a first part of first information, where the first part of the first information is used to identify the terminal device within the second range;

[0021] The second part of the network device identifier is used to identify the first network device within the second range.

[0022] In a possible implementation, the third information includes one of the following:

[0023] a portion of the first information other than the first portion, the first portion of the first information being used to identify the first network device within the second range;

[0024] The first part of the network device identification;

[0025] First information,

[0026] The first part of the network device identifier and the second part of the network device identifier are used to identify the first network device within the first range.

[0027] In a second aspect, a data transmission method is provided, which can be executed by a terminal device, or by a component of the terminal device (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can realize all or part of the functions of the terminal device. The following is an example of an execution subject of the method using a terminal device as an example, and the method includes: the terminal device receives a connection release message sent by a first network device, the connection release message includes fourth information, the fourth information is used to indicate the terminal device, and the fourth information is used to identify the first network device within a first range; the terminal device sends a connection establishment request message to a second network device, the connection establishment request message includes fifth information, the fifth information includes the first part of the terminal device context identifier (UE context ID), and the fifth information is used to identify the first network device within the first range.

[0028] Through the above method, the terminal device receives the fourth information sent from the first network device, and the fourth information can be used to identify the first network device globally. Part or all of the above fourth information can be used by the terminal device when establishing a connection with other network devices (such as the second network device) in the future. It can retrieve the first network device identification in the entire network, so that other network devices (such as the second network device) can accurately identify and find the first network device in the entire network.

[0029] In one possible implementation, the method further includes: receiving a connection establishment response message, wherein the connection establishment response message instructs the terminal device to send information including the second part of the UE context ID; and sending a connection establishment completion message, wherein the connection establishment completion message includes sixth information, and the sixth information includes the second part of the UE ID.

[0030] In a possible implementation manner, the method further includes: receiving a connection establishment permission message.

[0031] In a possible implementation, the fourth information includes one of the following:

[0032] Enhanced Inactive Radio Network Temporary Identity (eI-RNTI);

[0033] Network equipment identifier, the first part of the UE context ID, and the second part of the UE context ID;

[0034] Inactive Radio Network Temporary Identity (I-RNTI) and UE context ID.

[0035] In a possible implementation, the fifth information includes one of the following:

[0036] Network equipment identifier and the first part of UE context ID;

[0037] The first part of the fourth information includes the first part of the UE context ID.

[0038] In a possible implementation, the sixth information includes one of the following:

[0039] a second part of the fourth information, the second part of the fourth information including a second part of the UE context ID;

[0040] The second part of the UE context ID;

[0041] Fourth information.

[0042] In a third aspect, a data transmission method is provided, which can be executed by a first network device, or by a component of the first network device (such as a processor, chip, or chip system, etc.), or by a logic module or software that can implement all or part of the terminal device functions. The following is an example of the first network device as the execution subject of the method, and the method includes: the first network device sends a connection release message, the connection release message includes first information, and the first information is used to identify the first network device within a first range; the first network device receives a request message for querying the terminal device context (UE context) sent by the second network device through a service interface; the first network device sends the UE context of the terminal device to the second network device.

[0043] In a possible implementation, the request message for querying the terminal device context includes one of the following:

[0044] A terminal device context identifier (UE context ID) of the terminal device;

[0045] Inactive Radio Network Temporary Identity (I-RNTI);

[0046] Enhanced Inactive Radio Network Temporary Identity (eI-RNTI).

[0047] In a fourth aspect, a data transmission method is provided, which can be executed by a first network device, or by a component of the first network device (such as a processor, chip, or chip system, etc.), or by a logic module or software that can realize all or part of the terminal device functions. The following is an example of the execution subject of the method, which includes: the first network device sends a connection release message, the connection release message includes fourth information, and the fourth information is used to identify the first network device within a first range; the first network device receives a request message for querying the terminal device context (UE context) sent by the second network device through a service interface; when the first network device queries the UE context, it sends a message to the second network device to indicate that the query is successful; when the first network device cannot query the UE context, it sends a message to the second network device to indicate that the query failed.

[0048] In a possible implementation, the request message for querying the terminal device context includes one of the following:

[0049] The first part of the terminal device context identifier (UE context ID) of the terminal device;

[0050] Inactive Radio Network Temporary Identity (I-RNTI);

[0051] Enhanced Inactive Radio Network Temporary Identity (eI-RNTI).

[0052] In a fifth aspect, a data transmission method is provided, which can be executed by a second network device, or by a component of the second network device (such as a processor, chip, or chip system, etc.), or by a logic module or software that can implement all or part of the functions of the terminal device. The following is an illustration of the method using the second network device as the execution subject, and the method includes: the second network device receives an access request message, the access request message includes second information, and the second information is used to identify the first network device within a second range; when the second network device obtains the network device identification according to the second information, the second network device sends a connection establishment permission message; when the second network device cannot obtain the network device identification according to the second information, the second network device sends a connection establishment response message, and the connection establishment response message instructs the terminal device to send information used to identify the first network device within a first range, and the second range is smaller than the first range.

[0053] In one possible implementation, when the second network device cannot obtain the network device identifier (gNB ID) based on the second information, the method further includes: the second network device receives a connection establishment completion message, the connection establishment completion message includes third information, and the third information is used to identify the first network device within the first range.

[0054] In a possible implementation, the method further includes: the second network device sending a request message for querying a terminal device context (UE context) to the first network device through a service-based interface; and the second network device receiving the UE context sent by the first network device.

[0055] In a possible implementation, the request message for querying the UE context includes one of the following:

[0056] UE context ID of the terminal device;

[0057] Inactive Radio Network Temporary Identity (I-RNTI);

[0058] Enhanced Inactive Radio Network Temporary Identity (eI-RNTI).

[0059] In a sixth aspect, a data transmission method is provided, which can be executed by a second network device, or by a component of the second network device (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can realize all or part of the terminal device functions. The following is an example of the execution subject of the method, the method comprising: the second network device receives a connection establishment request message, the connection establishment request message includes fifth information, the fifth information includes the first part of the terminal device identifier (UE ID), and the fifth information is used to identify the first network device within a first range; the second network device sends a request message for querying the terminal device context (UE context) to the first network device through a service interface; when the message received from the first network device indicates that the query is successful, the second network device sends a connection establishment completion message to the terminal device; when the message received from the first network device indicates that the query fails, the second network device sends a connection establishment response message to the terminal device, the connection establishment response message instructing the terminal device to send information including the second part of the UE ID.

[0060] In a possible implementation, when receiving a message from the first network device indicating that the query fails, the method further includes: the second network device receiving a connection establishment completion message, the connection establishment completion message including sixth information, and the sixth information including the second part of the UE ID.

[0061] In one possible implementation,

[0062] In the seventh aspect, a communication device is provided, which may be a terminal device, comprising: a processor, the processor being coupled to a memory, the memory being used to store computer execution instructions, the processor being used to execute the instructions stored in the memory; when the instructions are executed by the processor, the communication device executes the method described in the first aspect or the second aspect.

[0063] In an eighth aspect, a communication device is provided, which may be a first network device, and the communication device includes: a processor, the processor is coupled to a memory, the memory is used to store computer execution instructions, and the processor is used to execute the instructions stored in the memory; when the instructions are executed by the processor, the communication device executes the method described in the third aspect or the fourth aspect.

[0064] In the ninth aspect, a communication device is provided, which may be a second network device, and the communication device includes: a processor, the processor is coupled to a memory, the memory is used to store computer execution instructions, and the processor is used to execute the instructions stored in the memory; when the instructions are executed by the processor, the communication device executes the method described in the fifth aspect or the sixth aspect.

[0065] In a tenth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a computer, the method described in the first aspect or the second aspect is executed.

[0066] In an eleventh aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a computer, the method described in the third aspect or the fourth aspect is executed.

[0067] In a twelfth aspect, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a computer, the method described in the fifth aspect or the sixth aspect is executed.

[0068] In the thirteenth aspect, a communication system is provided, which includes a terminal device, a first network device and a second network device; the terminal device is used for the method described in the first aspect; the first network device is used for executing the method described in the third aspect; and the second network device is used for executing the method described in the fifth aspect.

[0069] In the fourteenth aspect, a communication system is provided, which includes a terminal device, a first network device and a second network device; the terminal device is used for the method described in the second aspect; the first network device is used for executing the method described in the fourth aspect; and the second network device is used for executing the method described in the sixth aspect.

[0070] It should be understood that the description of technical features, technical solutions, beneficial effects or similar language in this application does not imply that all features and advantages can be realized in any single embodiment. On the contrary, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution or beneficial effect is included in at least one embodiment. Therefore, the description of a technical feature, technical solution or beneficial effect in this specification does not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions and beneficial effects described in the present embodiment can also be combined in any appropriate manner. Those skilled in the art will understand that the embodiment can be implemented without one or more specific technical features, technical solutions or beneficial effects of a specific embodiment. In other embodiments, additional technical features and beneficial effects can also be identified in specific embodiments that do not embody all embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] FIG1 is a schematic diagram of a network system architecture provided by an embodiment of the present application;

[0072] FIG2 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0073] FIG3a is an interactive diagram of a data transmission method provided in an embodiment of the present application;

[0074] FIG3 b is an interactive diagram of another data transmission method provided in an embodiment of the present application;

[0075] FIG3c is an interactive diagram of yet another data transmission method provided in an embodiment of the present application;

[0076] FIG4a is an interactive diagram of a data transmission method provided in an embodiment of the present application;

[0077] FIG4 b is an interactive diagram of another data transmission method provided in an embodiment of the present application;

[0078] FIG4c is an interactive diagram of yet another data transmission method provided in an embodiment of the present application;

[0079] FIG5 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application;

[0080] FIG6 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0081] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship. For example, A / B can represent A or B; "and / or" in the present application is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In addition, in the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences. At the same time, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way for easy understanding.

[0082] The resource allocation method provided in the embodiment of the present application can be applicable to various communication systems. For example, the resource allocation method provided in the embodiment of the present application can be applied to a third generation partnership project (3GPP) communication system, for example, a long term evolution (LTE) system, a fifth generation (5G) system, a vehicle to everything (V2X) system, a system of LTE and NR hybrid networking, or a device to device (D2D) system, a machine to machine (M2M) communication system, an Internet of Things (IoT), or the communication system can also be a non-3GPP communication system, or other similar new communication systems for the future, such as a sixth generation (6G) system, which is not specifically limited in the embodiment of the present application. In addition, the term "system" can be interchangeable with "network".

[0083] The terminal device in the embodiment of the present application can be referred to as a UE, and the network device can be referred to as a base station or gNB.

[0084] It should be noted that the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0085] Optionally, the network device in the embodiment of the present application is a device that connects a terminal device to a wireless network. The network devices in the embodiments of the present application may include various forms of base stations, for example, a macro base station, a micro base station (also known as a small station), a relay station, an access point, a transmitting point (TP), an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5G mobile communication system, a device that implements base station functions in a communication system evolved after 5G, a mobile switching center, and a device that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications; it may also be a network device in an NTN communication system, that is, it may be deployed on a high-altitude platform or a satellite; it may also be a module or unit that performs part of the functions of a base station, for example, it may be a centralized unit (CU) in a cloud radio access network (C-RAN) system, it may also be a distributed unit (DU), or it may be a radio unit ( Unit, RU), for example, it can be CU, DU or RU under the O-RAN architecture. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device. All or part of the functions of the network device can also be implemented by software functions running on hardware, or by virtualization functions or service functions instantiated on a platform (such as a cloud platform).

[0086] In another possible scenario, multiple network devices collaborate to assist the terminal in achieving wireless access, and different network devices respectively implement part of the functions of the access network. For example, the network device in this application can be composed of multiple network devices and is not limited to a single network device. The functions implemented by the network device in this application can also be implemented by multiple network devices, or through parts of multiple network devices. For example, the network device can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0087] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0088] Optionally, the terminal device in the embodiments of the present application may be a device with wireless transceiver functions, which may also be referred to as a terminal. The terminal device may specifically refer to user equipment, access terminal, subscriber unit, user station, mobile station, customer-premises equipment (CPE), remote station, remote terminal, mobile device, mobile terminal, user terminal, wireless communication device, user agent, or user device. The terminal device may also be a satellite phone, a cellular phone, a smart phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless data card, a wireless modem, a tablet computer, a computer with wireless transceiver function, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a communication device carried on a high-altitude aircraft, a wearable device, a drone, a robot, a smart point of sale (POS) machine, a machine type communication device, a terminal device in D2D, a terminal device in V2X, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, or a wireless terminal in a smart city. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device. All or part of the functions of the terminal device can also be implemented by software functions running on hardware, or by virtualization functions or service functions instantiated on a platform (such as a cloud platform).

[0089] Figure 1 shows the 5G network architecture diagram. The following is a detailed description of the 5G network structure based on Figure 1.

[0090] The 5G system architecture is divided into two parts: the access network and the core network. The access network is used to implement functions related to wireless access. The core network mainly includes the following key logical network elements: Radio Access Network 102 (RAN), Access and Mobility Management Function 105 (AMF), Session Management Function 106 (SMF), User Plane Function 103 (UPF), Policy Control Function 107 (Policy Control Function), and Unified Data Management 108 (UDM) network elements.

[0091] UE 101 refers to a network terminal device, such as a mobile phone, an Internet of Things terminal device, etc.

[0092] RAN 102 provides wireless access devices for terminal devices, including but not limited to eNodeB, WiFi AP, WiMAX BS, etc.

[0093] AMF 105 is mainly responsible for mobility management in the mobile network, such as user location update, user registration network, user switching, etc.

[0094] The SMF 106 is primarily responsible for session management in the mobile network, such as session establishment, modification, and release. Specific functions include allocating IP addresses to users and selecting the UPF 103 that provides packet forwarding capabilities.

[0095] PCF 107 is responsible for providing policies to AMF and SMF, such as QoS policy, slice selection policy, etc.

[0096] The UDM 108 is used to store user data, such as contract information and authentication / authorization information.

[0097] AF (Application Function) is responsible for providing services to the 3GPP network, such as influencing service routing and interacting with the PCF for policy control.

[0098] UPF 103 is mainly responsible for processing user messages, such as forwarding and billing.

[0099] DN 104 refers to a carrier network that provides data transmission services to users, such as IMS (IP Multi-media Service) and the Internet.

[0100] The UE accesses the data network (DN) by establishing a PDU session (PDU session) between the UE, the RAN, the UPF, and the DN.

[0101] In current public discussions on network architecture evolution, it has been proposed that the next step in the evolution of wireless network architecture is to introduce an SBA network architecture, also known as RAN service-based architecture, or the introduction of service-based interfaces for network devices. The RAN service-based architecture has the following advantages:

[0102] Service-based RAN architecture enables end-to-end unified orchestration, such as unified service discovery and service invocation. This reduces functional coupling between network elements and accelerates feature rollout. From a performance perspective, the RAN service-based architecture can reduce signaling hops and enable rapid connection establishment. One current technical approach within the RAN service-based architecture involves the RAN storing user context and not releasing it until the UE registers. This architecture simplifies downlink signaling addressing (core network elements interact directly with network equipment), avoiding the circuitous paths caused by downlink signaling and the asymmetric uplink and downlink processes. In this network architecture, since base stations can directly connect to all CN network elements, UE mobility and context management no longer rely on centralized AMF management. The RAN manages UE context, eliminating the need for message relay through the AMF. This technology allows direct interaction between the RAN and 5GC NFs without the AMF. Currently, in NR technology, the RAN manages UE context and also handles some mobility management, such as inactive terminal management. With this technology, UE context management and migration between RANs is transparent to the 5GC.

[0103] Optionally, the network devices, terminal devices, or core network devices in the embodiments of the present application can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the surface of water; and can also be deployed in the air on aircraft, balloons, and artificial satellites. The embodiments of the present application do not limit the application scenarios of the network devices, terminal devices, or core network devices.

[0104] Optionally, the network device and the terminal device in the embodiments of the present application can communicate through an authorized spectrum, or can communicate through an unlicensed spectrum, or can communicate through both an authorized spectrum and an unlicensed spectrum. The network device and the terminal device can communicate through a spectrum below 6 gigahertz (GHz), or can communicate through a spectrum above 6 GHz, or can communicate using a spectrum below 6 GHz and a spectrum above 6 GHz at the same time. The embodiments of the present application do not limit the spectrum resources used between the network device and the terminal device.

[0105] Optionally, the network device, terminal device or core network device in the embodiment of the present application can also be referred to as a communication device, which can be a general device or a dedicated device, and the embodiment of the present application does not make specific limitations on this.

[0106] [Corrected 05.07.2024 according to Rule 91] Optionally, in a specific implementation, a terminal device, a network device, or a core network device may adopt the structure shown in Figure 2, or include the components shown in Figure 2. Figure 2 is a schematic diagram of the structure of a communication device 200 provided in this application. The communication device 200 may be a terminal device or a chip or system-on-chip in a terminal device; or a network device or a module or chip or system-on-chip in a network device; or a core network device or a module or chip or system-on-chip in a core network device.

[0107] [Corrected 05.07.2024 in accordance with Rule 91] As shown in FIG2 , the communication device 200 includes at least one processor 201 and at least one communication interface ( FIG2 is merely illustrative, illustrating the communication device 200 as including a communication interface 204 and a processor 201). Optionally, the communication device 200 may further include a communication bus 202 and a memory 203.

[0108] The processor 201 may be a general-purpose central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor 701 may also be other devices with processing capabilities, such as circuits, devices, or software modules, without limitation.

[0109] Communication bus 202 is used to connect the various components in communication device 200, enabling communication between them. Communication bus 202 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, for example. This bus can be categorized as an address bus, a data bus, a control bus, and so on. For ease of illustration, FIG2 shows a single thick line, but this does not necessarily indicate that there is only one bus or only one type of bus.

[0110] Communication interface 204 is used to communicate with other devices or communication networks. Exemplarily, communication interface 204 can be a module, circuit, transceiver, or any other device capable of communication. Optionally, communication interface 204 can also be an input / output interface within processor 201, used to implement signal input and output to the processor.

[0111] The memory 203 may be a device with a storage function, used to store instructions and / or data, wherein the instructions may be computer programs.

[0112] Exemplarily, the memory 203 may be a read-only memory (ROM) or other types of static storage devices that can store static information and / or instructions, or a random access memory (RAM) or other types of dynamic storage devices that can store information and / or instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., without limitation.

[0113] It should be noted that the memory 203 can exist independently of the processor 201 or can be integrated with the processor 201. The memory 203 can be located within the communication device 200 or outside the communication device 200, without limitation. The processor 201 can be used to execute instructions stored in the memory 203 to implement the methods provided in the following embodiments of the present application.

[0114] As an optional implementation, the communication device 200 may further include an output device 205 and an input device 206. The output device 205 communicates with the processor 201 and can display information in a variety of ways. For example, the output device 205 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 206 communicates with the processor 201 and can receive user input in a variety of ways. For example, the input device 206 can be a mouse, a keyboard, a touch screen device, or a sensor device.

[0115] It should be noted that the structure shown in FIG2 does not constitute a specific limitation on the network device or terminal device. For example, in other embodiments of the present application, the network device or terminal device may include more or fewer components than shown in the figure, or combine or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0116] In NR technology, the RAN manages UE context and is responsible for some mobility management, including RRC_inactive state terminal mobility management. The RRC_INACTIVE (Radio Resource Control - Inactive) state can only be transitioned from RRC_CONNECTED (Radio Resource Control - Connected) via an RRC release message. When the UE releases from RRC_CONNECTED to RRC_INACTIVE, the base station assigns the UE an I-RNTI (Inactive Radio Network Temporary Identity) and uses this to manage the UE's context. This base station is also called the UE's last serving gNB (sometimes referred to as the anchor gNB). When a UE requests to resume a previously suspended RRC connection or perform an RNA update, it sends an RRCResumeRequest message to the current base station. Inactive UEs support the RRC Resume procedure, which can be used for the following: when the UE has data or signaling to transmit, when the UE needs to send a Management Area Update (including periodic updates, such as when moving out of a Location Management Area), or when the UE receives a paging message. When the network equipment controls the UE to enter the INACTIVE state, it will configure a UE Context ID (I-RNTI) for the UE. This UE Context ID is used to identify the UE. In 5G, the paging identifier can be 5G-S-TMSI (for idle UE) or I-RNTI. The role of 5G-S-TMSI is similar to that of S-TMSI in LTE, and is used for paging on the core network side (5GC paging). The gNodeB will not save the 5G-S-TMSI information. In order to perform RAN paging, a new paging identifier is required, so I-RNTI is introduced. When the RAN side wants to page a UE, it will send a paging message containing the I-RNTI of the UE in all cells in the RNA where the UE is located. After receiving this paging message, if the UE finds that the I-RNTI matches, it will initiate the RRC Resume process to migrate to the RRC connected state.

[0117] The RRC Resume process is as follows:

[0118] 1. The UE sends an RRC connection recovery request to the network device, which carries the UE context ID;

[0119] 2. After receiving the UE context ID, the network device determines the network device where the UE context is located based on the context ID, sends a UE context acquisition request to the network device to obtain the UE context from the network device, and restores the connection for the UE based on the UE context;

[0120] 3. The network device sends a connection restoration message to the UE. The restoration message is encrypted and secured using the key passed by the old network device. The old network device may also be referred to as the last serving cell, anchor base station, or base station where the UE context is located.

[0121] 4. When the UE receives the resume, it uses the deduced key for integrity verification and decryption.

[0122] The following describes the design of I-RNTI. The current protocol specifies two types of I-RNTI: long I-RNTI (Full I-RNTI) and short I-RNTI (Short I-RNTI). The I-RNTI carried in the current air interface RRC Resume is 40 bits or 24 bits long, of which 16 to 20 bits or 6 / 8 / 12 / 15 / 18 / 21 bits are used to identify the NG-RAN address. The current standard recommends two required I-RNTI formats:

[0123] Table 1 I-RNTI reference configuration

[0124] Table 2 Full I-RNTI configuration

[0125] Table 3 Short I-RNTI configuration

[0126] The I-RNTI structure that can be used by base stations in R17 and later versions is as follows:

[0127] -the first part(starting from the MSB of the I-RNTI)identifies the I-RNTI profile. It is 2 bits long for a Full I-RNTI or 1 bit long for a short I-RNTI, and it indicates the length of a Local NG-RAN Node Identifier of the NG-RAN Node that allocated the I-RNTI;

[0128] -the second part,immediately following the first part,is a Local NG-RAN Node Identifier;

[0129] -the third part,immediately following the second part,identifies the UE context stored in the NG-RAN node that allocated the I-RNTI.

[0130] The I-RNTI is only applicable in the RRC inactive state. Unlike other RNTIs, the I-RNTI is not used for CRC scrambling. The I-RNTI is used in RRC signaling for base stations to address UEs. The I-RNTI uniquely identifies a UE only within the RNA range. If a UE changes its RNA, it must re-acquire the I-RNTI. The Release 17 protocol defines that the gNB ID portion of the I-RNTI can be exchanged over the Xn interface. This specifies whether the gNB ID length in the I-RNTI generated by each gNB is 6 / 8 / 12 / 15 / 18 / 21 bits, and the corresponding gNB ID, for example, 110101. Through Xn interaction, gNBs can clearly identify the gNB ID in the I-RNTI generated by each gNB, allowing them to index the corresponding gNB when searching for the context of a specific terminal device.

[0131] The RRC Resume Request is transmitted during the RACH process, carried in Message 3 (MSG 3), which is sent over SRB 0. Because MSG 3 cannot be segmented, it must be transmitted using a single transport block. For this reason, the message size needs to be kept relatively small to ensure reliable reception when the UE is at the cell edge. According to the current protocol design, the RRC Resume Request message is 48 bits when using a short I-RNTI, allowing it to be transmitted using a single transport block.

[0132] According to the current protocol design, the RRC Resume Request1 message containing the full I-RNTI is 64 bits in size, so it requires relatively good coverage for reliable reception. The full I-RNTI is generally used for indoor or small cell deployments where coverage conditions are generally good.

[0133] In the current NR design, the UE is not aware of which bits in the I-RNTI are the gNB ID and which are the UE context ID. The specific division is only known between e-stations. The UE only knows its own I-RNTI, such as 110101010001010010010100 and 110101011101010101000110110101010001100100. The UE can only report either the long or short I-RNTI in MSG 3.

[0134] The UE context to be queried is mainly involved in the UE resume scenario: Retrieve UE Context. The process is used after the UE resumes at the new base station. The new base station determines who the old base station is based on the I-RNTI, and sends the I-RNTI bearer and the RETRIEVE UE CONTEXT REQUEST to the old base station for the old base station to query the corresponding UE context and feedback the UE context in the RETRIEVE UE CONTEXT RESPONSE.

[0135] In the current NR design, the gNB ID in the I-RNTI identifies only base stations with Xn connections and has a maximum length of 21 bits. However, the global gNB ID ranges from 22 to 32 bits. This means that the gNB ID in the I-RNTI in the current NR design is insufficient to identify base stations without Xn connections. Furthermore, as base stations are added in the future, the number of global gNB ID bits is likely to increase further, making it even more difficult to uniquely identify a base station using the base station ID in the I-RNTI. Furthermore, due to coverage issues, the length of the MSG3 sent by the UE is limited, making it difficult to increase the length of the I-RNTI and MSG3.

[0136] The post-SBA network architecture described above may adopt a similar mobility management approach for inactive terminal devices. This is because base stations can access service-based interfaces or service-based buses, allowing them to communicate with each other based on these service-based interfaces and address each other. Therefore, an identifier is required to enable base stations to locate the UE context at any base station in the entire network. Based on this identifier, when a UE enters a connected state at any base station, the base station can directly locate the base station where the UE context resides, eliminating the need to determine whether it is within the RNA range or consider the existence of an Xn interface between the two base stations.

[0137] An exemplary method is that when the UE accesses a new base station (or called a target base station), the new base station triggers a query or request for UE context information from the old base station. The message may be sent directly to the old base station (such as RETRIEVE UE CONTEXT REQUEST or a new message in NR), or the message may be forwarded through an intermediate network element (such as first sending a message to the network element that assists in managing the UE context, and the network element forwards the message of the new base station, or first querying the auxiliary management network element (such as NRF) for the information of the old base station and then the new base station sends a message to the old base station). After that, the old base station identifies the UE's identification information and sends the corresponding UE context to the new base station.

[0138] However, the above solutions are all based on the premise that UE identification information can uniquely indicate a terminal in the network. This is inconsistent with the current I-RNTI in inactive state mobility management, which only uniquely identifies a terminal within a station or RNA. If you want to design an identifier that can index a unique UE in the entire network, one solution is to extend the UE identification information, such as the length of the I-RNTI, to fully reflect the identification information of the gNB. This will also cause the newly designed identification information to exceed the maximum 40-bit I-RNTI length supported by the existing NR.

[0139] The present application proposes a terminal device identification method, in which a first network device sends a unique terminal device identification for retrieving the terminal device in the entire network to the terminal device. The terminal device identification can be called an enhanced non-activated radio network temporary identification (eI-RNTI). After the terminal device receives the unique terminal device identification for retrieving the terminal device in the entire network, it can send different parts or information of the above-mentioned terminal device identification at different stages when establishing a connection with a second network device in a subsequent manner, so that the network can accurately identify and find the terminal device in the entire network.

[0140] An embodiment of the present invention is described below with reference to FIG. 3 a to FIG. 3 c .

[0141] FIG3a is a terminal device identification method provided by the present invention, comprising the following steps:

[0142] S401: A first network device sends a connection release message to a terminal device, where the connection release message includes first information, where the first information is used to indicate the terminal device and where the first information is used to identify the first network device within a first range.

[0143] Specifically, the connection release message may be an RRC release message or other types of connection release messages. The name of the message is also not limited, for example, it may also be a reconfiguration message or a configuration message.

[0144] Specifically, the first information is used to indicate the terminal device, including: the first information is used to identify the terminal device, or the first information is used to address the terminal device.

[0145] Specifically, the first information includes information for identifying the network device and information for identifying the terminal device. The information for identifying the network device may further include information for identifying the network device within the first range and information for identifying the network device within the second range. In some embodiments, the information for identifying the network device may be 32 bits, of which the first 21 bits may be used to identify the network device within the second range, and the last 22 to 32 bits are used to identify the network device within the first range. In other embodiments, the information for identifying the network device may be 32 bits, of which the first 21 bits may be used to identify the network device within the second range, and the last 22 to 32 bits and the first 21 bits are used together to identify the network device within the first range.

[0146] It should be noted that the first range is larger than the second range. For example, the first range can be a global range or a network-wide range, and the global range or network-wide range can be the range of a public land mobile network (PLMN) or an operator's network; the second range is a local range, and the local range can be a local RNA area, such as a collection of several base stations. For example, the first range includes base stations 1, 2, 3, and 4, and the second range only includes base stations 1 and 2. The fact that the first range is larger than the second range can be understood as the first range including the second range, or the first range including the second range.

[0147] In some embodiments, the first information may be described as an enhanced inactive radio network temporary identifier (eI-RNTI), and the first information may be composed in the following ways:

[0148] 1. The first part of the network device identifier, the second part of the network device identifier, and the terminal context identifier (UE context ID);

[0149] The network device identifier may be a gNB ID or an eNB ID. The first part of the network device identifier may be the global part of the network device identifier or the part of the network device identifier excluding the second part, and the second part of the network device identifier may be the local part of the network device identifier. The first part of the network device identifier may be used to identify the network device in a first scope, or the first part of the network device identifier and the second part of the network device identifier may be used to identify the network device in a first scope; the second part of the network device identifier may be used to identify the network device in a second scope. The UE context ID may be used to identify or index a terminal device.

[0150] The first part of the network device identifier, the second part of the network device identifier, and the terminal context identifier (UE context ID) may be sent using different information elements (IEs), respectively. The specific formats are as follows:

[0151] 2. Complete network device identification and UE context ID;

[0152] The network device identifier can be a gNB ID or an eNB ID. The complete network device identifier can be used to identify the network device within the first range. The UE context ID can be used to identify the terminal device. The specific format is as follows:

[0153] 3. Use a profile ID to indicate the first information format and the corresponding network device identifier and UE context ID;

[0154] Profile ID can be used to indicate different first information formation forms and corresponding network device identification parts. For example, as shown in the first row of the Full I-RNTI configuration shown in Table 2, when the value of Profile ID is 0b00, the network device identification is 21 bits. Profile ID can be used to indicate the complete network device identification, or it can indicate the first part of the network device identification and the second part of the network device identification respectively. The specific Profile ID can be placed in the front part of all bits, such as the first 4 bits of 50 bits, or the first 4 bits of the last 40 bits of 50 bits. Its format can be

[0155] UE-Identity::=BIT STRING(SIZE(XX)

[0156] In the text description of the protocol, indicate that the first X bits are the Profile ID;

[0157] or

[0158] UE-Identity::=BIT STRING(SIZE(XX)

[0159] Profile-Identity::=ENUMERATED{p0,p1,p2,spare5,spare4,spare3,spare2,spare1}

[0160] The configuration form of the first information is indicated by an independent information element.

[0161] 4. The first part of the network device identifier and I-RNTI.

[0162] The network device identifier may be a gNB ID or an eNB ID. The first part of the network device identifier may be a global part of the network device identifier. The I-RNTI may include the second part of the network identifier and the UE context ID. The first part of the network device identifier may be used to identify the network device in a first range, or the first part of the network device identifier and the second part of the network device identifier may be used to identify the network device in a first range; the second part of the network device identifier may be used to identify the network device in a second range. The UE context ID may be used to identify the terminal device. The specific format is as follows:

[0163] In some embodiments, the information included in the above four methods may be included in the first information, but the name of the information included in the above four methods is not limited. The name may be other names except eI-RNTI, which is not limited in the present invention.

[0164] In some embodiments, the UE context ID may also be a terminal identifier or a terminal index.

[0165] S402: The terminal device sends a connection establishment request message to the second network device. The connection establishment request message includes second information, where the second information is used to identify the first network device within a second range, where the second range is smaller than the first range. The fact that the second range is smaller than the first range can be understood as meaning that the first range includes the second range, or that the first range contains the second range.

[0166] Specifically, the connection establishment request message may be an RRC resume request message, or other types of connection establishment messages, or other messages are not limited thereto.

[0167] Specifically, the second information includes information for identifying the network device and information for identifying the terminal device. The information for identifying the network device may further include information for identifying the network device within the second range. In some embodiments, the information for identifying the network device may be 21 bits, and the 21 bits may be used to identify the network device within the second range.

[0168] It should be noted that the first scope is larger than the second scope. For example, the first scope may be a global scope or a network-wide scope, or a global scope. The global scope or network-wide scope may be the scope of a public land mobile network (PLMN), a group of PLMNs, or a network of an operator. The second scope may be a local scope, which may be a local RNA area or a collection of multiple base stations.

[0169] In some embodiments, the second information may be one of the following:

[0170] 1. Inactive Radio Network Temporary Identifier (I-RNTI);

[0171] The I-RNTI may include the second part of the network device identifier and the UE context ID. The network device identifier may be a gNB ID or an eNB ID. The second part of the network device identifier may be a local part of the network device identifier, and the second part of the network device identifier may be used to identify the network device in a second range. The UE context ID may be used to identify the terminal device. The I-RNTI may be 40 bits. The above identifier may also be an identifier with another name having the same format, content, or information as the I-RNTI. The I-RNTI mentioned in the present invention may be an identifier with another name having the same format, content, or information as the I-RNTI.

[0172] 2. The second part of the network equipment identifier and the UE context ID;

[0173] The network device identifier may be a gNB ID or an eNB ID. The second portion of the network device identifier may be a local portion of the network device identifier, and the second portion of the network device identifier may be used to identify the network device in a second range. The UE context ID may be used to identify the terminal device.

[0174] 3. The first part of the first message.

[0175] The first part of the first information is used to identify the terminal device within the second range. The first part of the first information may include the second part of the network device identifier and the UE context ID. The network device identifier may be a gNB ID or an eNB ID. The second part of the network device identifier may be a local part of the network device identifier, which may be used to identify the network device within the second range. The UE context ID may be used to identify the terminal device.

[0176] In some embodiments, after receiving the first information from the first network device, the terminal device can obtain the second information based on the first information. Specifically, the terminal device can identify the first information and obtain the second information therefrom, or can generate the second information based on the first information. For example, if the first information is an eI-RNTI with different parts sent through different information elements, the UE can identify the first part of the network device identifier, the second part of the network device and the UE context ID based on each received information element, thereby sending the second part of the network device and the UE context ID as the second information to the second network device. In another example, if the first information is a configuration identifier (Profile ID) indicating the RNTI composition form and the corresponding part of the network device identifier and the UE context ID, the terminal device can find the second part of the network device identifier and the UE context ID in the first information through the Profile ID, thereby sending the second part of the network device identifier and the UE context ID as the second information to the second network device.

[0177] In some embodiments, the type, method, content, or format of the second information in the second message sent by the terminal device to the second network device can be generated based on indication information of a system message. For example, the system message instructs the terminal device to send the second information in the form of the second part of the network device identifier and the UE context ID. The system message can be a message such as SIB 1 or MIB.

[0178] Through the above method, the terminal device receives the first information sent from the first network device, and the first information can be used to identify the first network device globally. Part or all of the above first information can be used by the terminal device when it subsequently establishes a connection with other network devices (such as the second network device). It can retrieve the terminal device identification of a unique UE in the entire network, so that other network devices (such as the second network device) can accurately identify and find the terminal device in the entire network.

[0179] FIG3b is another terminal device identification method provided by the present invention, comprising the following steps:

[0180] S401: A first network device sends a connection release message to a terminal device, where the connection release message includes first information, where the first information is used to indicate the terminal device and where the first information is used to identify the first network device within a first range.

[0181] S402: The terminal device sends a connection establishment request message to the second network device, where the connection establishment request message includes second information, and the second information is used to identify the first network device within a second range, where the second range is smaller than the first range.

[0182] For the related description of S401 and S402, please refer to FIG. 3a and the related paragraphs, which will not be repeated here.

[0183] S403: The second network device receives a connection establishment request message including second information, which is used to identify the first network device within a second range. The second network device obtains a network device identifier based on the second information, and sends a connection establishment permission message to the terminal device.

[0184] Specifically, the second network device can find the first network device within the second range according to the second information. For example, the second network device can restore the network device identifier of the I-RNTI contained in the second information, and then send a connection establishment permission message to the terminal device.

[0185] Specifically, the second network device queries or requests the context of the terminal device from the first network. After the request is successful, the second network device sends a connection establishment permission message to the terminal device. More specifically, the second network device can obtain the context of the terminal device from the first network based on an Xn interface or a service-based interface, or query the first network device from other network elements or devices and then send signaling to the first network device, or forward the information based on other network devices or devices.

[0186] Specifically, the connection establishment permission message may be an RRC resume message.

[0187] FIG3c shows another terminal device identification method provided by the present invention, comprising the following steps:

[0188] S401: A first network device sends a connection release message to a terminal device, where the connection release message includes first information, where the first information is used to indicate the terminal device and where the first information is used to identify the first network device within a first range.

[0189] S402: The terminal device sends a connection establishment request message to the second network device, where the connection establishment request message includes second information, and the second information is used to identify the first network device within a second range, where the second range is smaller than the first range.

[0190] For the relevant description of S401 and S402, please refer to the relevant paragraphs of FIG3a, which will not be repeated here.

[0191] S404: The second network device receives an access request message including second information, where the second information is used to identify the first network device within a second range. The second network device cannot obtain the network device identification according to the second information or fails to address the second network device. The second network device sends a connection establishment response message to the terminal device, where the connection establishment response message instructs the terminal device to send information used to identify the first network device within the first range, where the second range is smaller than the first range.

[0192] Specifically, if the second network device cannot find the first network device within the second range based on the second information, for example, if the second network device cannot recover the network device identifier of the I-RNTI contained in the second information, then the second network device sends a connection establishment response message to the terminal device. The connection establishment response message instructs the terminal device to send information used to identify the first network device within the first range, and the second range is smaller than the first range. Since the second network device cannot find the first network device within the second range, for example, the second network device cannot find the first network device within the local range, the second network device may send a connection establishment response message to the terminal device, which may instruct the terminal device to send information used to identify the first network device within the first range to the second network device, for example, the first range may be a global range.

[0193] Specifically, the connection establishment response message may be an RRC setup message. In some embodiments, the connection establishment response message may indicate that the access is successful but still requires the terminal device to additionally report other parts of the network device identifier.

[0194] S405: The terminal device receives the connection establishment response message and sends a connection establishment completion message to the second network device, the connection establishment completion message including third information, the third information being used to identify the first network device within the first range.

[0195] Specifically, the third information is used to globally identify the first network device. Specifically, the third information may be one of the following:

[0196] 1. the portion of the first information other than the first portion;

[0197] The first part of the first information can be used to identify the first network device within the second range. Since the second network device has already obtained the first part of the first information from the second information, after obtaining the portion of the eI-RNTI excluding the first part using the third information, the complete first information can be obtained. The complete first information can be used to identify the first network device within the first range.

[0198] 2. The first part of the network device identifier;

[0199] The network device identifier may be a gNB ID or an eNB ID. The first part of the network device identifier may be a global part of the network device identifier. The first part of the network device identifier may be used to identify the network device within a first scope, or the first part of the network device identifier and the second part of the network device identifier may be used to identify the network device within a first scope. Alternatively, the first part of the network device identifier may be a part of the network device identifier other than the second part of the network device identifier.

[0200] 3. First information.

[0201] Since the number of bits that can be sent in the connection establishment completion message is no longer limited, the third information can also be the complete first information, and the complete first information can be used to identify the first network device within the first range.

[0202] Specifically, the connection establishment completion message may be an RRC setup complete message, and the connection establishment completion message may be carried in message 5 (Msg5).

[0203] S406: The second network device receives the connection establishment response message and sends a request message for querying the terminal context (UE context) to the first network device through the service-based interface;

[0204] Specifically, the service-based interface can be an interface between the second network device and the first network device and other network elements, such as NgNB (Service-based interface exhibited by gNB).

[0205] Specifically, the request message for querying the UE context may include one or more of the UE context ID, I-RNTI and eI-RNTI of the terminal device.

[0206] S407: The first network device receives the request message for querying the UE context, and sends the UE context of the terminal device to the second network device.

[0207] Specifically, the first network device receives one or more of the UE context ID, I-RNTI, and eI-RNTI carried in the request message for querying the UE context sent by the second network device, thereby querying the UE context of the terminal device. After querying the UE context of the terminal device, the UE context of the terminal device can be sent to the second network device.

[0208] It should be noted that the information contained in the above-mentioned first message, second message and third message can be arbitrarily combined. For example, when the first message is a complete network device identifier and UE context ID, the second message can be an I-RNTI, or the second part of the network device identifier and the UE context ID. The third message can be the part of the eI-RNTI excluding the first part, or the first part of the network device identifier. In different combinations, the terminal device can report part of the network device identifier in the second message, and then report another part or all of the network device identifier in the third message, that is, the terminal device sends a part of the network device identifier through the second message and sends another part of the network device identifier through the third message. Finally, the second network device can combine the network device identifiers in the second and third messages to obtain a complete network device identifier.

[0209] It should be noted that, among any of the above combinations, some combinations require the terminal device to perceive the bit division and usage in the eI-RNTI, such as when the first information is a complete network device identifier and UE context ID or the first part of the network device identifier and I-RNTI; some combinations do not require the terminal device to perceive the bit division and usage in the eI-RNTI, such as when the first information is a configuration identifier indicating the RNTI composition form and the corresponding part of the network device identifier and UE context ID, the terminal device can obtain the content in the first information based on the number of intercepted bits.

[0210] Through the above method, the terminal device receives the first information sent from the first network device, and the first information can be used to identify the first network device globally. When the terminal device and the second network device establish a connection, the second information used to identify the first network device locally can be sent first. If the second network device can obtain the first network identifier, the connection is successful; if the second network device cannot obtain the first network identifier, the terminal device sends the third information used to identify the first network device globally to the second network device, so that the second network device can accurately address the context of the terminal device within the entire network, or obtain the context of the terminal device.

[0211] Another embodiment of the present invention will be described below with reference to FIG. 4 a - FIG. 4 c .

[0212] S501: A first network device sends a connection release message to a terminal device, where the connection release message includes fourth information, where the fourth information is used to indicate the terminal device and to identify the first network device within a first range.

[0213] Specifically, the connection release message may be an RRC release message or other types of connection release messages. The name of the message is also not limited, for example, it may also be a reconfiguration message or a configuration message.

[0214] Specifically, the fourth information is used to indicate the terminal device, including: the fourth information is used to identify the terminal device, and the first information is used to address the terminal device.

[0215] Specifically, the fourth information includes information for identifying the network device and information for identifying the terminal device. The information for identifying the network device may further include information for identifying the network device within the first range and information for identifying the network device within the second range. In some embodiments, the information for identifying the network device may be 32 bits, of which the first 21 bits may be used to identify the network device within the second range, and the last 22 to 32 bits are used to identify the network device within the first range. In other embodiments, the information for identifying the network device may be 32 bits, of which the first 21 bits may be used to identify the network device within the second range, and the last 22 to 32 bits and the first 21 bits are used together to identify the network device within the first range.

[0216] It should be noted that the first range is larger than the second range. For example, the first range can be a global range or a network-wide range, and the global range or network-wide range can be the range of a public land mobile network (PLMN) or an operator's network; the second range is a local range, and the local range can be a local RNA area, such as a collection of several base stations. For example, the first range includes base stations 1, 2, 3, and 4, and the second range only includes base stations 1 and 2. The fact that the first range is larger than the second range can be understood as the first range including the second range, or the first range including the second range.

[0217] In some embodiments, the fourth information may be described as an enhanced inactive radio network temporary identifier (eI-RNTI), and the fourth information may be composed in the following ways:

[0218] 1. Network equipment identifier, the first part of the terminal context identifier (UE context ID), and the second part of the UE context ID;

[0219] The network device identifier may be a gNB ID or an eNB ID. The network device identifier may be used to identify the network device in a first scope. The UE context ID may be used to identify or index a terminal device.

[0220] 2. The network equipment identifier, the first part of the UE context ID and the second part of the UE context ID can be used in different ways.

[0221] The specific format can refer to the relevant description of the first information above.

[0222] Network device identification and complete UE context ID;

[0223] The network device identifier may be a gNB ID or an eNB ID. The network device identifier may be used to identify the network device within the first range. The complete UE context ID may be used to identify the terminal device.

[0224] 3. Use the profile ID to indicate the RNTI configuration and the corresponding UE context ID and network device ID;

[0225] Profile ID can be used to indicate different RNTI structures and the corresponding terminal device identification parts. For example, as shown in the first row of the Full I-RNTI configuration shown in Table 2, when the Profile ID value is 0b00, the terminal device identification is 21 bits. Profile ID can be used to indicate the complete terminal device identification, or to indicate the first part of the terminal device identification and the second part of the terminal device identification respectively. The specific Profile ID can be placed at the front of all bits, such as the first 4 bits of 50 bits, or the first 4 bits of the last 40 bits of 50 bits.

[0226] 4.UE context ID and I-RNTI.

[0227] It should be noted that the I-RNTI here only includes the first part of the UE context ID and the network device identifier.

[0228] 5. I-RNTI and the second part of the UE context ID;

[0229] In some embodiments, the information included in the above five methods may be included in the fourth information, but the name of the information included in the above four methods is not limited. The name may be any name other than eI-RNTI, which is not limited in the present invention.

[0230] In some embodiments, the UE context ID may also be a terminal identifier or a terminal index.

[0231] S502: The terminal device sends a connection establishment request message to the second network device, where the connection establishment request message includes fifth information, where the fifth information includes a first part of a terminal device context identifier (UE context ID), and the fifth information is used to identify the first network device within a first range.

[0232] Specifically, the connection establishment request message may be an RRC resume request message, or a release message of another type of connection.

[0233] Specifically, the fifth information includes information for identifying the network device and information for identifying the terminal device. The information for identifying the network device may further include information for identifying the network device within the first range. In some embodiments, the information for identifying the network device may be 32 bits, and the 32 bits may be used to identify the network device within the first range.

[0234] It should be noted that the first scope is larger than the second scope. For example, the first scope may be a global scope or a network-wide scope, or a global scope. The global scope or network-wide scope may be the scope of a public land mobile network (PLMN), a group of PLMNs, or a network of an operator. The second scope may be a local scope, which may be a local RNA area or a collection of multiple base stations.

[0235] The information identifying the terminal device included in the fifth information is the first part of the terminal device context identifier (UE context ID), that is, the information identifying the terminal device included in the fifth information is an incomplete UE context ID.

[0236] In some embodiments, the fifth information may be one of the following:

[0237] 1. Network equipment identifier and the first part of the UE context ID;

[0238] The network device identifier may be a gNB ID or an eNB ID. The network device identifier is used to identify the network device within the first range.

[0239] 2. The first part of the fourth information, the first part of the eI-RNTI includes the first part of the UE context ID.

[0240] The first part of the fourth information also includes a complete network device identifier, where the network device identifier is used to identify the network device within the first range. It should be noted that the first part of the fourth information includes the first part of the UE context ID and does not include the second part of the UE context ID, that is, the first part of the fourth information includes an incomplete UE context ID.

[0241] In some embodiments, after receiving the fourth information from the first network device, the terminal device can obtain the fifth information based on the fourth information. Specifically, the terminal device can identify the fourth information and obtain the fifth information therefrom, or can generate the fifth information based on the fourth information. For example, if the fourth information is an eI-RNTI with different parts sent through different information elements, the UE can identify the network device identifier, the first part of the UE context ID and the second part of the UE context ID based on each received information element, thereby sending the network device identifier and the first part of the UE context ID as the fifth information to the second network device. In another example, if the fourth information is a part that indicates the RNTI composition form and the network device identifier and the corresponding UE context ID using a configuration identifier (Profile ID), the terminal device can find the network device identifier and the first part of the UE context ID in the fourth information through the Profile ID, thereby sending the network device identifier and the first part of the UE context ID as the fifth information to the second network device.

[0242] In some embodiments, the identification format in the second message sent by the terminal device to the second network device can be generated based on indication information in a system message. For example, the system message instructs the terminal device to send the fifth information in the form of a network device identifier and the first part of the UE context ID. The system message can be a message such as SIB 1, MIB, etc.

[0243] Through the above method, the terminal device receives the fourth information sent from the first network device, and the fourth information can be used to identify the first network device globally. Part or all of the above fourth information can be used by the terminal device when establishing a connection with other network devices (such as the second network device) in the future. It can retrieve the first network device identification in the entire network, so that other network devices (such as the second network device) can accurately identify and find the first network device in the entire network.

[0244] FIG4b is another terminal device identification method provided by the present invention, comprising the following steps:

[0245] S501: A first network device sends a connection release message to a terminal device, where the connection release message includes fourth information, where the fourth information is used to indicate the terminal device and to identify the first network device within a first range.

[0246] S502: The terminal device sends a connection establishment request message to the second network device, where the connection establishment request message includes fifth information, where the fifth information includes a first part of a terminal device context identifier (UE context ID), and the fifth information is used to identify the first network device within a first range.

[0247] For the related description of S501 and S502, please refer to FIG4a and the related paragraphs, which will not be repeated here.

[0248] S503: The second network device receives an access request message, where the connection establishment request message includes fifth information, the fifth information including a first part of a terminal device identifier (UE ID), and the fifth information is used to identify the first network device within a first range. The second network device obtains the network device identifier based on the fifth information, and sends a request message to the first network device to query a terminal device context. Querying the terminal device context may also be referred to as obtaining a terminal device context, migrating a terminal device context, or requesting a terminal device context.

[0249] Specifically, the request message for querying the terminal device context includes one of the following:

[0250] 1. The first part of the UE context ID;

[0251] 2. Inactive Radio Network Temporary Identifier (I-RNTI);

[0252] 3. Enhanced Inactive Radio Network Temporary Identity (eI-RNTI).

[0253] It should be noted that the above-mentioned I-RNTI and eI-RNTI only include the first part of the UE context ID, that is, the request message for querying the terminal device context only includes part of the UE context ID.

[0254] S504a: The first network device receives a request message for querying the terminal device context, obtains the terminal device context, and sends a message to the second network device indicating that the query is successful.

[0255] Specifically, the first network device can recover or retrieve the terminal device identifier in the I-RNTI or index the unique terminal device context based on the partial UE context ID in the request message for querying the terminal device context, and then send a message to the second network device to indicate that the query is successful. Optionally, the first network device sends the unique terminal device context to the second network device.

[0256] In some embodiments, the first network device may receive a request message for querying the terminal device context through a service-based interface.

[0257] S505a: In response to the first network device sending a message indicating that the query is successful, the second network device sends a connection establishment permission message to the terminal device

[0258] Specifically, the connection establishment permission message may be an RRC resume message.

[0259] FIG4c shows another terminal device identification method provided by the present invention, comprising the following steps:

[0260] S501: A first network device sends a connection release message to a terminal device, where the connection release message includes fourth information, where the fourth information is used to indicate the terminal device and to identify the first network device within a first range.

[0261] S502: The terminal device sends a connection establishment request message to the second network device, where the connection establishment request message includes fifth information, where the fifth information includes a first part of a terminal device context identifier (UE context ID), and the fifth information is used to identify the first network device within a first range.

[0262] S503: The second network device receives an access request message, where the connection establishment request message includes fifth information, where the fifth information includes a first part of a terminal device identifier (UE ID), and where the fifth information is used to identify the first network device within a first range. The second network device obtains the network device identifier based on the fifth information, and the second network device sends a context migration request message to the first network device, where the context migration message includes the fifth message.

[0263] For the related descriptions of S501, S502 and S503, please refer to FIG. 4a and FIG. 4b and the related paragraphs, which will not be repeated here.

[0264] S504b: The first network device receives a request message for querying the terminal device context, but cannot obtain the terminal device context. The first network device sends a message to the second network device indicating that the query has failed.

[0265] Specifically, if the first network device cannot recover or retrieve the terminal device identifier in the I-RNTI or index the unique terminal device context based on the partial UE context ID in the request message for querying the terminal device context, it sends a message to the second network device to indicate the query failure.

[0266] Optionally, the first network device may match multiple terminal device contexts based on a portion of the UE context ID in the request message for querying the terminal device context, thereby sending the multiple terminal device contexts to the second network device.

[0267] In some embodiments, the first network device may receive a request message for the terminal device context through a service-based interface.

[0268] S505b: In response to the first network device sending a message indicating that the query fails, the second network device sends a connection establishment response message to the terminal device, where the connection establishment response message instructs the terminal device to send information including the second part of the UE context ID.

[0269] Specifically, the connection establishment response message may be an RRC Setup message. In some embodiments, the connection establishment response message may indicate that the access is successful but still requires the terminal device to additionally report other parts of the UE context ID, such as the second part of the UE context ID.

[0270] S506: In response to the received connection establishment response message, the terminal device sends a connection establishment completion message to the second network device, where the connection establishment completion message includes the sixth information, and the sixth information includes the second part of the UE context ID.

[0271] Specifically, the sixth information includes one of the following:

[0272] 1. The second part of the fourth information, wherein the second part of the fourth information includes the second part of the UE context ID;

[0273] 2. The second part of the UE context ID;

[0274] 3. The fourth message.

[0275] It should be noted that the second part of the UE context ID included in the sixth message and the second part of the UE context ID included in the fourth message or the fifth message are combined to form a complete UE context ID.

[0276] Optionally, after the terminal device sends a connection establishment completion message to the second network device, the second network device may again send a request message to query the terminal device context to the first network device. The request message to query the terminal device context includes a complete UE context ID, so that the first network device can recover or retrieve the terminal device identifier in the I-RNTI based on the complete UE context ID or index a unique terminal device context, and then send it to the second network device.

[0277] Optionally, when the first network device sends multiple terminal device contexts to the second network device, a unique terminal device context can be obtained by matching the complete UE context ID with the multiple terminal device contexts. Optionally, the second network device can instruct the first network device to delete the unique terminal device context local to the first network device or migrate the unique terminal device context local to the first network device, and the first network device can continue to store other terminal device contexts.

[0278] Through the above method, the terminal device receives the fourth information sent from the first network device, and the fourth information can be used to identify the first network device globally. When the terminal device and the second network device establish a connection, the second information used to identify the first network device globally can be sent first, but the second information only contains a partial UE context ID. If the second network device can obtain the terminal device context through the partial UE context ID, the connection is successful; if the second network device cannot obtain the terminal device context, the terminal device sends the third information including the complete UE context ID to the second network device, so that the second network device can obtain the terminal device context.

[0279] It is understood that in each of the above embodiments, the methods and / or steps implemented by a network device (including the first network device or the second network device) may also be implemented by components (such as chips or circuits) applicable to network devices. The methods and / or steps implemented by a terminal device may also be implemented by components (such as chips or circuits) applicable to terminal devices. The methods and / or steps implemented by a core network device may also be implemented by components (such as chips or circuits) applicable to core network devices.

[0280] The above description primarily describes the solutions provided by the embodiments of the present application from the perspective of interaction between various devices. Accordingly, the embodiments of the present application also provide a communication device for implementing the various methods described above. The communication device may be a network device in the method embodiments described above, or a device comprising such a network device, or a component usable in a network device. Alternatively, the communication device may be a terminal device in the method embodiments described above, or a device comprising such a terminal device, or a component usable in a terminal device. Alternatively, the communication device may be a core network device in the method embodiments described above, or a device comprising such a core network device, or a component usable in a core network device. It will be understood that, to implement the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the respective functions. Those skilled in the art will readily appreciate that, in conjunction with the various exemplary units and algorithm steps described in the embodiments disclosed herein, the present application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Professionals skilled in the art may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of the present application.

[0281] In the embodiment of the present application, the functional modules of the communication device can be divided according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0282] 5 shows a schematic structural diagram of a communication device 1200. The communication device 1200 includes a receiving module 1201 and a processing module 1202. The receiving module, also called a receiving unit, is used to implement a receiving function, and may be, for example, a receiving circuit, a receiver, a receiver, or a communication interface.

[0283] Taking the communication device 1200 as an example of the terminal device in the above method embodiment, in one possible design, the receiving module 1201 is used to receive the first data of the first broadcast service from the first network device through the first broadcast session; the receiving module 1201 is also used to receive the second data of the first broadcast service from the second network device through the first multicast session; the processing module 1202 is used to determine the final data of the first broadcast service based on the first data and the second data.

[0284] Optionally, the communication device 1200 may further include a sending module 1203. The sending module may also be referred to as a sending unit. The sending module 1203 is used to implement a sending function, and may be, for example, a transmitting circuit, a transmitter, a transmitter, or a communication interface.

[0285] In this embodiment, the communication device 1200 is presented in the form of various functional modules divided in an integrated manner. Here, "module" can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions.

[0286] 6 shows a schematic structural diagram of another communication device 1300. The communication device 1300 includes a sending module 1301 and a processing module 1302. The sending module, also called a sending unit, is used to implement a sending function, and may be, for example, a transmitting circuit, a transmitter, a transmitter, or a communication interface.

[0287] Taking the communication device 1300 as the second network device in the above method embodiment as an example, in one possible design, the processing module 1302 is used to establish a first multicast session; the first multicast session is associated with the first broadcast service; and the sending module 1301 is used to transmit the second data of the first broadcast service to the terminal device through the first multicast session.

[0288] Optionally, the communication device 1300 may further include a receiving module 1303. The receiving module may also be referred to as a receiving unit, and the receiving module 1303 is used to implement a receiving function, and may be, for example, a receiving circuit, a receiver, a receiver, or a communication interface.

[0289] In this embodiment, the communication device 1300 is presented in the form of various functional modules divided in an integrated manner. The "module" here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions.

[0290] It should be noted that one or more of the above modules or units can be implemented by software, hardware, or a combination of the two. When any of the above modules or units is implemented by software, the software exists in the form of computer program instructions and is stored in a memory, and a processor can be used to execute the program instructions and implement the above method flow. The processor can be built into an SoC (system on chip) or an ASIC, or it can be an independent semiconductor chip. In addition to the core used to execute software instructions to perform calculations or processing within the processor, it can further include necessary hardware accelerators, such as a field programmable gate array (FPGA), a programmable logic device (PLD), or a logic circuit that implements dedicated logic operations.

[0291] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a DSP chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.

[0292] Optionally, an embodiment of the present application further provides a chip system, comprising: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instruction in the memory, the method in any of the above method embodiments is executed. In one possible implementation, the communication device also includes a memory. Optionally, the chip system can be composed of a chip, or can include a chip and other discrete devices, which is not specifically limited in the embodiment of the present application.

[0293] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software programs, all or part of the embodiments may be implemented in the form of computer program products.

[0294] The present application provides a computer program product comprising one or more computer instructions, which, when executed on a communication device, enables any method of the embodiments of the present application to be executed.

[0295] When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.

[0296] The computer instructions may be stored in a computer-readable storage medium. The embodiment of the present application provides a computer-readable storage medium having instructions stored therein, which, when executed on a communication device, enables any method of the embodiment of the present application to be executed.

[0297] Computer instructions can be transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. A computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media. Available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital versatile discs (DVDs)), or semiconductor media (e.g., solid state drives (SSDs)).

[0298] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and implement other changes to the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0299] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations thereof may be made without departing from the scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Provided that such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations.

Claims

1. A data transmission method, characterized in that: The method comprises: The terminal device receives a connection release message sent by the first network device, where the connection release message includes first information, where the first information is used to indicate the terminal device, and the first information is used to identify the first network device within a first range; The terminal device sends a connection establishment request message to the second network device, where the connection establishment request message includes second information, where the second information is used to identify the first network device within a second range, where the second range is smaller than the first range.

2. The method according to claim 1, characterized in that The method further comprises: The terminal device receives a connection establishment response message, where the connection establishment response message instructs the terminal device to send information for identifying the first network device within the first range; The terminal device sends a connection establishment completion message, where the connection establishment completion message includes third information, and the third information is used to identify the first network device within the first range.

3. The method according to claim 1, characterized in that The method further comprises: The terminal device receives a connection establishment permission message.

4. The method according to any one of claims 1 to 3, characterized in that: The first information and the second information are also used to identify a terminal device context (UE Context).

5. The method according to any one of claims 1 to 4, characterized in that: The first information includes one of the following: Enhanced Inactive Radio Network Temporary Identity (eI-RNTI); The first part of the network device identifier, the second part of the network device identifier and the terminal device context identifier (UE context ID); Inactive Radio Network Temporary Identifier (I-RNTI) and network device identifier; I-RNTI and the first part of the network equipment identity; The first part of the network device identifier and the second part of the network device identifier are used to identify the first network device within the first range, and the second part of the network device identifier is used to identify the first network device within the second range.

6. The method according to claims 1-4, characterized in that: The second information includes one of the following: I-RNTI; The second part of the network equipment identifier and the UE context ID; a first part of first information, where the first part of the first information is used to identify the terminal device within the second range; The second part of the network device identifier is used to identify the first network device within the second range.

7. The method according to claim 2, characterized in that The third information includes one of the following: a portion of the first information other than the first portion, the first portion of the first information being used to identify the first network device within the second range; The first part of the network device identification; First information, The first part of the network device identifier and the second part of the network device identifier are used to identify the first network device within the first range.

8. A data transmission method, characterized in that: The method comprises: The terminal device receives a connection release message sent by the first network device, where the connection release message includes fourth information, where the fourth information is used to indicate the terminal device, and the fourth information is used to identify the first network device within a first range; The terminal device sends a connection establishment request message to the second network device, and the connection establishment request message includes fifth information, and the fifth information includes the first part of the terminal device context identifier (UE context ID), and the fifth information is used to identify the first network device within a first range.

9. The method according to claim 8, characterized in that The method further comprises: receiving a connection establishment response message, wherein the connection establishment response message instructs the terminal device to send information including the second part of the UE context ID; A connection establishment complete message is sent, where the connection establishment complete message includes sixth information, and the sixth information includes the second part of the UEID.

10. The method according to claim 8, characterized in that The method further comprises: Receive connection establishment allowed message.

11. The method according to any one of claims 8 to 10, characterized in that: The fourth information includes one of the following: Enhanced Inactive Radio Network Temporary Identity (eI-RNTI); The network equipment identifier, the first part of the UE context ID, and the second part of the UE context ID; Inactive Radio Network Temporary Identity (I-RNTI) and UE context ID.

12. The method according to any one of claims 8 to 10, characterized in that: The fifth information includes one of the following: Network equipment identifier and the first part of UE context ID; The first part of the fourth information includes the first part of the UE context ID.

13. The method according to claim 9, characterized in that The sixth information includes one of the following: a second part of the fourth information, wherein the second part of the fourth information includes a second part of the UE context ID; The second part of the UE context ID; Fourth information.

14. A data transmission method, characterized in that: The method comprises: The first network device sends a connection release message, where the connection release message includes first information, where the first information is used to identify the first network device within a first range; The first network device receives, through the service-based interface, a request message for querying a terminal device context (UE context) sent by the second network device; The first network device sends the UE context of the terminal device to the second network device.

15. The method according to claim 14, characterized in that The request message for querying the terminal device context includes one of the following items: A terminal device context identifier (UE context ID) of the terminal device; Inactive Radio Network Temporary Identifier (I-RNTI); Enhanced Inactive Radio Network Temporary Identity (eI-RNTI).

16. A data transmission method, characterized in that: The method comprises: The first network device sends a connection release message, where the connection release message includes fourth information, where the fourth information is used to identify the first network device within a first range; The first network device receives, through the service-based interface, a request message for querying a terminal device context (UE context) sent by the second network device; When the first network device queries the UE context, sending a message to the second network device to indicate that the query is successful; When the first network device cannot query the UE context, a message is sent to the second network device to indicate that the query failed.

17. The method according to claim 16, characterized in that The request message for querying the terminal device context includes one of the following items: A first part of a terminal device context identifier (UE context ID) of the terminal device; Inactive Radio Network Temporary Identifier (I-RNTI); Enhanced Inactive Radio Network Temporary Identity (eI-RNTI).

18. A data transmission method, characterized in that: The method comprises: The second network device receives an access request message, where the access request message includes second information, where the second information is used to identify the first network device within the second range; When the second network device obtains the network device identification according to the second information, the second network device sends a connection establishment permission message; When the second network device cannot obtain the network device identification according to the second information, the second network device sends a connection establishment response message, and the connection establishment response message instructs the terminal device to send information used to identify the first network device within a first range, and the second range is smaller than the first range.

19. The method according to claim 18, characterized in that When the second network device cannot obtain the network device identifier (gNB ID) according to the second information, the method further includes: The second network device receives a connection establishment completion message, where the connection establishment completion message includes third information, where the third information is used to identify a message of the first network device within a first range.

20. The method according to claim 18 or 19, characterized in that The method further comprises: The second network device sends a request message for querying a terminal device context (UE context) to the first network device through a service-based interface; The second network device receives the UE context sent by the first network device.

21. The method according to claim 20, characterized in that The request message for querying the UE context includes one of the following items: A terminal device context identifier (UE context ID) of the terminal device; Inactive Radio Network Temporary Identifier (I-RNTI); Enhanced Inactive Radio Network Temporary Identity (eI-RNTI).

22. A data transmission method, characterized in that: The method comprises: The second network device receives a connection establishment request message, where the connection establishment request message includes fifth information, where the fifth information includes a first part of a terminal equipment identifier (UE ID), and where the fifth information is used to identify the first network device within a first range; The second network device sends a request message for querying a terminal device context (UE context) to the first network device through a service-based interface; When receiving a message from the first network device indicating that the query is successful, the second network device sends a connection establishment completion message to the terminal device; When receiving a message from the first network device indicating that the query fails, the second network device sends a connection establishment response message to the terminal device, wherein the connection establishment response message instructs the terminal device to send information including the second part of the UE ID.

23. The method according to claim 22, characterized in that When receiving a message from the first network device indicating that the query fails, the method further includes: The second network device receives a connection establishment complete message, where the connection establishment complete message includes sixth information, and the sixth information includes the second part of the UE ID.

24. A communication device, characterized in that: The communication device includes: a processor, the processor is coupled to a memory, the memory is used to store computer execution instructions, and the processor is used to execute the instructions stored in the memory; when the instructions are executed by the processor, the communication device executes the method described in any one of claims 1-7 or claims 8-12.

25. A communication device, characterized in that: The communication device includes: a processor, the processor is coupled to a memory, the memory is used to store computer execution instructions, and the processor is used to execute the instructions stored in the memory; when the instructions are executed by the processor, the communication device executes the method described in any one of claims 14-15 or claims 16-17.

26. A communication device, characterized in that: The communication device includes: a processor, the processor is coupled to a memory, the memory is used to store computer execution instructions, and the processor is used to execute the instructions stored in the memory; when the instructions are executed by the processor, the communication device executes the method described in any one of claims 18-21 or claims 22-23.

27. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a computer, the method according to any one of claims 1 to 7 is executed, or the method according to any one of claims 8 to 12 is executed.

28. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a computer, the method of any one of claims 14-15 is executed, or the method of any one of claims 16-17 is executed.

29. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a computer, the method of any one of claims 18 to 21 is executed, or the method of any one of claims 22 to 23 is executed.

30. A communication system, characterized in that: The communication system includes a terminal device, a first network device and a second network device; the terminal device is used to execute the method described in any one of claims 1-8; the first network device is used to execute the method described in any one of claims 14-15; the second network device is used to execute the method described in any one of claims 18-21.

31. A communication system, characterized in that: The communication system includes a terminal device, a first network device and a second network device; the terminal device is used to execute the method described in any one of claims 8-12; the first network device is used to execute the method described in any one of claims 16-17; the second network device is used to execute the method described in any one of claims 22-23.

Images