Communication method, apparatus and system

Abstract

The embodiment of the application provides a communication method, which comprises the following steps: an access and mobility management function network element receives tracking area information of a first device from a first network device; the access and mobility management function network element saves the association relationship between the tracking area information of the first device and the first network device; and in the case that a second network device serves the first device, the access and mobility management function network element deletes the association relationship between the tracking area information of the first device and the first network device. The first device can be a vehicle-mounted relay device (VMR), and therefore, the technical scheme of the application proposes a mobility management scheme for the first device (VMR), so as to more accurately perform mobility management on a UE.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to the design of a communication method, apparatus, and system. Background Technology

[0002] To meet the ultra-high capacity requirements of 5G mobile communication systems, high-frequency small cell networks have become the mainstream. High-frequency carriers have poor propagation characteristics, suffer severe attenuation due to obstruction, and have limited coverage, thus requiring a large-scale, dense deployment of small cells. Correspondingly, providing fiber optic backhaul for these densely deployed small cells is costly and difficult to implement, necessitating an economical and convenient backhaul solution. Furthermore, from the perspective of wide coverage requirements, providing network coverage in remote areas presents significant challenges and high costs associated with fiber optic deployment, necessitating the design of flexible and convenient access and backhaul solutions. Integrated access and backhaul (IAB) technology offers a solution to these problems.

[0003] Vehicle-mounted relays (VMRs) support wireless relay-related functions. Compared to existing IAB mechanisms, VMRs offer mobility, while existing IAB nodes are fixed relays on the ground. Therefore, the VMR in this application can also be understood as a mobile IAB node. In mobile VMR scenarios, the network side may be unable to obtain the correspondence between user equipment (UE) and base stations, meaning the network side cannot accurately manage UE mobility.

[0004] Based on this, this application proposes a mobility management scheme for the first device VMR, so as to more accurately manage the mobility of the UE. Summary of the Invention

[0005] This application proposes a mobility management scheme for a first device's VMR, so that the network side can more accurately manage the mobility of the UE.

[0006] In a first aspect, a communication method is provided, comprising: an access and mobility management function (AMU) network element receiving tracking area information of a first device from a first network device; the AMU network element storing the tracking area information of the first device and the association relationship between the first network device and the first network device; and, when a second network device serves the first device, the AMU network element deleting the tracking area information of the first device and the association relationship between the first network device.

[0007] It should be understood that the first device can be a vehicle-mounted relay (VMR) or a UE serving a VMR service; this application embodiment does not limit this.

[0008] Based on the above technical solution, when the first device accesses the first network device, the access and mobility management function network element saves the tracking area information of the first device and its association with the first network device. When the first device switches from the first network device to the second network device, the mobility management function network element saves the tracking area information of the first device and its association with the second network device, and deletes the previously saved tracking area information and association with the first network device. This allows the network side to promptly know that the network device associated with the first device has changed from the first device to the second network device. Consequently, when the network side needs to page the first device and / or a UE served by the first device, it can accurately locate the second network device. This avoids a situation where the network side instructs the first network device to send a paging message when it pages the first device and / or a UE served by the first device. This enables the network side to perform more accurate mobility management of the UE and avoids wasting resources.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the access and mobility management function (AMU) network element connects the first network device and the second network device. The method further includes: the AMU network element receiving tracking area information of the first device from the second network device; and the AMU network element storing the association between the tracking area information of the first device and the second network device. Based on the above technical solution, the network side can promptly obtain information about the network devices associated with the first device, thereby enabling the network side to perform more accurate mobility management of the UE.

[0010] In conjunction with the first aspect, in certain implementations of the first aspect, the access and mobility management function network element deletes the association between the tracking area information of the first device and the first network device, including: the access and mobility management function network element, in response to receiving the tracking area information of the first device from the second network device, deletes the association between the tracking area information of the first device and the first network device. Based on the above technical solution, the network side can promptly obtain information about the network devices associated with the first device, thereby enabling the network side to perform more accurate mobility management of the UE.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the access and mobility management function (AMU) network element receiving first indication information from the first network device; the AMU network element deleting the association between the tracking area information of the first device and the first network device, including: the AMU network element deleting the association between the tracking area information of the first device and the first network device according to the first indication information. Based on the above technical solution, the network side can promptly obtain information about the network devices associated with the first device, thereby enabling the network side to perform more accurate mobility management of the UE.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the first indication information includes the identification information of the second network device. Based on the above technical solution, the network side can promptly obtain information about the network devices associated with the first device, thereby enabling the network side to perform more accurate mobility management of the UE.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the access and mobility management function network element connects to the first network device. The method further includes: the access and mobility management function network element sending first registration information to a unified database network element. The first registration information is used to register the tracking area information of the first device and the association relationship of the first network device with the unified database network element. Based on the above technical solution, the network side can promptly obtain information about the network devices associated with the first device, thereby enabling the network side to perform more accurate mobility management of the UE.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the access and mobility management function network element sending a first request message to the unified database network element, the first request message being used to request the unified database network element to delete the tracking area information of the first device and the association relationship of the first network device. Based on the above technical solution, the network side can promptly obtain information about the network devices associated with the first device, thereby enabling the network side to perform mobility management of the UE more accurately.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the access and mobility management function network element sending first query information to the unified database network element, the first query information being used to query the unified database network element for network devices associated with the tracking area information of the first device; the access and mobility management function network element receiving first response information sent by the unified database network element, the first response information including the identification information of the second network device. Based on the above technical solution, the network side can promptly obtain information about the network devices associated with the first device, thereby enabling the network side to perform more accurate mobility management of the UE.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the first device includes a vehicle-mounted relay device (VMR).

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the tracking area information of the first device does not change with the access location of the first device.

[0018] In a second aspect, a communication method is provided, comprising: an access and mobility management function (AMU) network element receiving tracking area information of a first device from a second network device; the AMU network element storing the association between the tracking area information of the first device and the second network device; and the AMU network element sending second registration information to a unified database network element, the second registration information being used to register the tracking area information of the first device and the association between the second network device with the unified database network element.

[0019] It should be understood that the first device can be a vehicle-mounted relay (VMR) or a UE serving a VMR service; this application embodiment does not limit this.

[0020] Based on the above technical solution, when the first device switches from the first network device to the second network device, the mobility management function network element saves the tracking area information of the first device and the association relationship between the second network device, and registers the tracking area information of the first device and the association relationship between the second network device with the unified database network element. This enables the network side to promptly know that the network device associated with the first device has changed from the first device to the second network device. Consequently, when the network side needs to page the first device and / or the UE served by the first device, it can accurately locate the second network device. This avoids the situation where the network side instructs the first network device to send a paging message when it pages the first device and / or the UE served by the first device. As a result, the network side can more accurately manage the mobility of the UE and avoid wasting resources.

[0021] In conjunction with the second aspect, in some implementations of the second aspect, the first device includes a vehicle-mounted relay device (VMR).

[0022] In conjunction with the second aspect, in some implementations of the second aspect, the tracking area information of the first device does not change with the access location of the first device.

[0023] Thirdly, a communication method is provided, the method comprising: a network device obtaining tracking area information of a first device from a first device; and the network device sending the tracking area information of the first device to a connected access and mobility management function network element.

[0024] It should be noted that the network device can be either a first network device or a second network device. When the first device connects to the first network device, the first network device sends its tracking area information to the access and mobility management function (AM) network element connected to it, thereby the AM network element connected to the first network device stores the association between the tracking area information of the first device and the first network device; when the first device connects to the second network device, the second network device sends its tracking area information to the AM network element connected to it, thereby the AM network element connected to the second network device stores the association between the tracking area information of the first device and the second network device.

[0025] It should be understood that the first device can be a vehicle-mounted relay (VMR) or a UE serving a VMR service; this application embodiment does not limit this.

[0026] Based on the above technical solution, the network side can promptly learn that the network device associated with the first device has changed from the first device to the second network device. Therefore, when the network side needs to page the first device and / or the UE served by the first device, it can accurately locate the second network device. This avoids the situation where the network side instructs the first network device to send a paging message when it pages the first device and / or the UE served by the first device. As a result, the network side can more accurately manage the mobility of the UE and avoid wasting resources.

[0027] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the network device sending first indication information to a connected access and mobility management function network element, the first indication information being used to instruct the deletion of the tracking area information of the first device and the association relationship of the network device. Based on the above technical solution, the network side can promptly obtain information about the network devices associated with the first device, thereby enabling the network side to perform more accurate mobility management of the UE.

[0028] In conjunction with the third aspect, in some implementations of the third aspect, the first device includes a vehicle-mounted relay device (VMR).

[0029] In conjunction with the third aspect, in some implementations of the third aspect, the tracking area information of the first device does not change with the access location of the first device.

[0030] Fourthly, a communication method is provided, comprising: a unified database network element receiving second registration information from a first access and mobility management function network element, the second registration information being used to register the tracking area information of a first device and the association relationship of a second network device; the unified database network element storing the tracking area information of the first device and the association relationship of the second network device based on the second registration information; the unified database network element receiving first query information from a second access and mobility management function network element, the first query information being used to query the network device associated with the tracking area information of the first device; and the unified database network element sending first response information to the second access and mobility management function network element, the first response information including the identification information of the second network device.

[0031] It should be noted that the first access and mobility management function network element can be a VMR AMF network element registered by the VMR, and the second access and mobility management function network element can be a UE AMF network element registered by the UE.

[0032] It should be understood that the first device can be a vehicle-mounted relay (VMR) or a UE serving a VMR service; this application embodiment does not limit this.

[0033] Based on the above technical solution, the unified database network element can promptly inform the second access and mobility management function network element of the network device associated with the first device. This enables the network side to promptly know that the network device associated with the first device has changed from the first device to the second network device. Consequently, when the network side needs to page the first device and / or a UE served by the first device, it can accurately locate the second network device. This avoids the situation where the network side instructs the first network device to send a paging message when it pages the first device and / or a UE served by the first device. As a result, the network side can more accurately manage the mobility of the UE and avoid wasting resources.

[0034] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: the unified database network element receiving first registration information from the first access and mobility management function network element, the first registration information being used to register the tracking area information of the first device and the association relationship of the first network device; and saving the tracking area information of the first device and the association relationship of the first network device based on the first registration information. Based on the above technical solution, the network side can promptly obtain information about the network devices associated with the first device, thereby enabling the network side to perform more accurate mobility management of the UE.

[0035] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: the unified database network element receiving first request information from the first access and mobility management function network element, the first request information being used to request the deletion of the tracking area information of the first device and the association relationship of the first network device. Based on the above technical solution, the network side can promptly obtain information about the network devices associated with the first device, thereby enabling the network side to perform more accurate mobility management of the UE.

[0036] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first device includes a vehicle-mounted relay device (VMR).

[0037] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the tracking area information of the first device does not change with the access location of the first device.

[0038] Fifthly, an access and mobility management function network element is provided, comprising: a receiving unit for receiving tracking area information of a first device from a first network device; a processing unit for storing the tracking area information of the first device and the association relationship between the first network device and the first network device; and, when a second network device serves the first device, the processing unit deletes the tracking area information of the first device and the association relationship between the first network device and the first network device.

[0039] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the access and mobility management function network element connects the first network device and the second network device, and the receiving unit is further configured to: receive tracking area information of the first device from the second network device; the processing unit is further configured to: store the tracking area information of the first device and the association relationship between the second network device.

[0040] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the processing unit is specifically used to: delete the association between the tracking area information of the first device and the first network device based on the tracking area information of the first device received from the second network device.

[0041] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the receiving unit is further configured to: respond to receiving first indication information from the first network device; the processing unit is specifically configured to: delete the tracking area information of the first device and the association relationship of the first network device according to the first indication information.

[0042] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first indication information includes the identification information of the second network device.

[0043] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the access and mobility management function network element is connected to the first network device, and the access and mobility management function network element further includes: a sending unit, used to send first registration information to a unified database network element, the first registration information being used to register the tracking area information of the first device and the association relationship of the first network device with the unified database network element.

[0044] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the sending unit is further configured to: send a first request message to the unified database network element, the first request message being used to request the unified database network element to delete the tracking area information of the first device and the association relationship of the first network device.

[0045] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the sending unit is further configured to: send first query information to the unified database network element, the first query information being used to query the unified database network element for network devices associated with the tracking area information of the first device; the receiving unit is further configured to: receive first response information sent by the unified database network element, the first response information including the identification information of the second network device.

[0046] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first device includes a vehicle-mounted relay device (VMR).

[0047] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the tracking area information of the first device does not change with the access location of the first device.

[0048] A sixth aspect provides an access and mobility management function network element, comprising: a receiving unit for receiving tracking area information of a first device from a second network device; a processing unit for storing the tracking area information of the first device and the association relationship between the second network device; and a sending unit for sending second registration information to a unified database network element, the second registration information being used to register the tracking area information of the first device and the association relationship between the second network device with the unified database network element.

[0049] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the first device includes a vehicle-mounted relay device (VMR).

[0050] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the tracking area information of the first device does not change with the access location of the first device.

[0051] In a seventh aspect, a network device is provided, comprising: a receiving unit for obtaining tracking area information of the first device from a first device; and a sending unit for sending the tracking area information of the first device to a connected access and mobility management function network element.

[0052] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the sending unit is further configured to: send first indication information to the connected access and mobility management function network element, the first indication information being used to indicate the deletion of the tracking area information of the first device and the association relationship of the network device.

[0053] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the first device includes a vehicle-mounted relay device (VMR).

[0054] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the tracking area information of the first device does not change with the access location of the first device.

[0055] Eighthly, a unified database network element is provided, comprising: a receiving unit, configured to receive second registration information from a first access and mobility management function network element, the second registration information being used to register the tracking area information of a first device and the association relationship of a second network device; a processing unit, configured to save the tracking area information of the first device and the association relationship of the second network device according to the second registration information. The receiving unit is further configured to receive first query information from the second access and mobility management function network element, the first query information being used to query the network device associated with the tracking area information of the first device; and a sending unit, configured to send first response information to the second access and mobility management function network element, the first response information including the identification information of the second network device.

[0056] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the receiving unit is further configured to: the unified database network element receive first registration information from the first access and mobility management function network element, the first registration information being used to register the tracking area information of the first device and the association relationship of the first network device; the processing unit is further configured to: save the tracking area information of the first device and the association relationship of the first network device according to the first registration information.

[0057] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the receiving unit is further configured to: receive first request information from the first access and mobility management function network element, the first request information being used to request the deletion of the tracking area information of the first device and the association relationship of the first network device.

[0058] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the first device includes a vehicle-mounted relay device (VMR).

[0059] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the tracking area information of the first device does not change with the access location of the first device.

[0060] A ninth aspect provides an access and mobility management function network element, comprising: at least one processor, a memory, and a transceiver, the memory for storing instructions, the transceiver for communicating between the access and mobility management function network element and other devices, the stored instructions being executed directly or indirectly by the at least one processor, such that the access and mobility management function network element can perform the methods of the first aspect, the second aspect, or any optional implementation of the first aspect.

[0061] A tenth aspect provides a network device comprising: at least one processor, a memory, and a transceiver, the memory for storing instructions, the transceiver for communicating between the network device and other devices, the stored instructions being executed directly or indirectly by the at least one processor, such that the network device can perform the methods of the third aspect or any optional implementation thereof.

[0062] Eleventhly, a unified database network element is provided, comprising: at least one processor, a memory, and a transceiver, wherein the memory is used to store instructions, the transceiver is used for the unified database network element to communicate with other devices, and the stored instructions are executed directly or indirectly by the at least one processor, such that the unified database network element can perform the methods in the fourth aspect or any optional implementation of the fourth aspect.

[0063] In a twelfth aspect, a chip system is provided, comprising: at least one processor for executing stored instructions such that an access and mobility management function network element can perform the methods of the first aspect, the second aspect, or any optional implementation of the first aspect.

[0064] In a thirteenth aspect, a chip system is provided, comprising: at least one processor for executing stored instructions such that a network device can execute the methods of the third aspect or any optional implementation thereof.

[0065] In a fourteenth aspect, a chip system is provided, comprising: at least one processor for executing stored instructions such that a unified database network element can perform the methods of the fourth aspect or any optional implementation thereof.

[0066] In a fifteenth aspect, a computer storage medium is provided that stores program instructions, which, when executed, cause an access and mobility management function network element to perform the methods of the first aspect, the second aspect, or any optional implementation of the first aspect.

[0067] In a sixteenth aspect, a computer storage medium is provided that stores program instructions, when executed, causing a network device to perform the methods of the third aspect or any optional implementation thereof.

[0068] In a seventeenth aspect, a computer storage medium is provided that stores program instructions, which, when executed, enable a unified database network element to perform the methods of the fourth aspect or any optional implementation thereof.

[0069] Eighteenth aspect, a computer program product is provided, the computer program product including instructions that, when executed, cause an access and mobility management function network element to perform the method in the first aspect, the second aspect, or any optional implementation of the first aspect.

[0070] Nineteenthly, a computer program product is provided, the computer program product including instructions that, when executed, cause a network device to perform the method in the third aspect or any optional implementation of the third aspect.

[0071] In a twentieth aspect, a computer program product is provided, the computer program product including instructions that, when executed, cause the method in the fourth aspect or any optional implementation of the fourth aspect to be performed using a unified database network element.

[0072] In a twenty-first aspect, a system is provided, comprising an access and mobility management function network element as described in the first aspect, the second aspect, or any optional implementation of the first aspect; and / or a network device as described in the third aspect or any optional implementation of the third aspect; and / or a unified database network element as described in the fourth aspect or any optional implementation of the fourth aspect. Attached Figure Description

[0073] Figure 1 A basic architecture diagram of a 5G system 200 is shown.

[0074] Figure 2 A schematic diagram of an architecture based on service-oriented interfaces is shown.

[0075] Figure 3 A schematic diagram of the gNB structure with CU-DU separation is shown.

[0076] Figure 4 This diagram illustrates how terminal devices transmit data via two-hop data backhaul (BH).

[0077] Figure 5A schematic flowchart of a communication method 500 adapted to scenario one, provided by an embodiment of this application, is shown.

[0078] Figure 6 A schematic flowchart of a communication method 600 adapted to scenario two, provided by an embodiment of this application, is shown.

[0079] Figure 7 A schematic flowchart of a communication method 700 provided in another embodiment of this application is shown.

[0080] Figure 8 A schematic flowchart of a communication method 800 provided in another embodiment of this application is shown.

[0081] Figure 9 A schematic flowchart of a communication method 900 provided in another embodiment of this application is shown.

[0082] Figure 10 This is a schematic block diagram of an apparatus provided in an embodiment of this application.

[0083] Figure 11 This is another schematic diagram of a device provided in the embodiments of this application.

[0084] Figure 12 This is another schematic diagram of a device provided in the embodiments of this application.

[0085] Figure 13 This is another schematic diagram of a device provided in the embodiments of this application.

[0086] Figure 14 This is a schematic structural diagram of the device provided in the embodiments of this application. Detailed Implementation

[0087] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0088] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, future 5th Generation (5G) system, or New Radio (NR), etc.

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

[0090] The network device in this application embodiment can be a device for communicating with terminal devices. The network device can be a base station (BTS) in a Global System of Mobile communication (GSM) system or Code Division Multiple Access (CDMA), a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, an evolved NodeB (eNB or eNodeB) in an LTE system, a radio controller in a Cloud Radio Access Network (CRAN) scenario, or a relay station, access point, vehicle-mounted device, wearable device, or a network device in a future 5G network or a network device in a future evolved PLMN network, etc. The embodiments of this application are not limited.

[0091] Figure 1 A basic architecture diagram of a 5G system 100 is shown. (For example...) Figure 1 As shown, system 100 includes: PCF, AMF, session management function (SMF), radio access network (RAN), unified data management (UDM), data network (DN), user plane function (UPF), UE, application function (AF), and / or unified data repository (UDR). Optionally, Figure 1 It can also include the following functions ( Figure 1 (Not shown in the image): Network Slice Selection Function (NSSF), Authentication Server Function (AUSF), Network Exposure Function (NEF), or Network Repository Function (NRF).

[0092] The main functions of each network element are described below:

[0093] 1. Terminal equipment

[0094] The terminal device in this application embodiment may be: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

[0095] Terminal devices can be devices that provide voice / data connectivity to users, such as handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving or autopilot systems, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks, or future public land mobile communication networks. Terminal devices in a mobile network (PLMN), etc., are not limited to this in the embodiments of this application.

[0096] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring. Furthermore, in this embodiment, the terminal device can also be a terminal device in an Internet of Things (IoT) system.

[0097] 2. Wireless access network

[0098] A radio access network (RAN) is an access network that implements network access functions based on wireless communication technology. RAN manages radio resources, provides wireless or air interface access services to terminals, and facilitates the forwarding of control signals and user data between terminals and the core network.

[0099] As an example and not a limitation, the radio access network can be an evolved NodeB (eNB or eNodeB) in an LTE system, a radio controller in a cloud radio access network (CRAN) scenario, or the access device can be a relay station, access point, vehicle-mounted equipment, wearable device, or access device in a 5G network or an access device in a future evolved PLMN network, etc. It can be an access point (AP) in a WLAN, or a gNB in ​​an NR system. This application embodiment is not limited.

[0100] 3. Access and mobility management function network elements

[0101] Access and mobility management function (MME) network elements are mainly used for mobility management and access management. They can be used to implement other functions of the mobility management entity (MME) besides session management, such as lawful detection or access authorization (or authentication). They are also used to transmit user policies between the UE and the PCF. In the embodiments of this application, they can be used to implement the functions of access and mobility management network elements.

[0102] 4. Session Management Function Network Element

[0103] The session management function network element is mainly used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection of manageable user plane function (UPF) network elements, endpoints for policy control and charging function interfaces, and downlink data notification. In the embodiments of this application, it can be used to implement the functions of the session management network element.

[0104] 5. User plane function network elements

[0105] User plane function network elements can be used for packet routing and forwarding, or QoS parameter processing of user plane data, etc. User data can access the data network (DN) through this network element. In the embodiments of this application, it can be used to implement the functions of user plane network elements. For example, when establishing a session on different UPFs, the UE's service experience will be different. Therefore, the aforementioned SMF needs to select a suitable UPF for the UE's session.

[0106] 6. Strategy control network element

[0107] Policy control network elements provide a unified policy framework to guide network behavior, offering policy rule information to control plane functional network elements (such as AMF and SMF elements). They are primarily responsible for policy control functions such as billing at the session and service flow levels, QoS bandwidth assurance and mobility management, and UE policy decisions. In this embodiment, the PCFs connected to the AMF and SMF correspond to the AM PCF (PCF for Access and Mobility Control) and SM PCF (PCF for Session Management), respectively. In actual deployment scenarios, these can be the same PCF entity or two different PCF entities.

[0108] 7. Network Capability Open Function Network Elements

[0109] Network capability opening function network elements are used to open up service and network capability information (such as terminal location, session reachability, etc.) provided by 3GPP network functions to the outside world.

[0110] 8. Application Functional Network Elements

[0111] Application function network elements (AFs) are primarily used to convey application-side requests to the network side, such as QoS requirements or user state event subscriptions. AFs can be third-party functional entities or application services deployed by operators, such as IMS voice call services. For third-party application functional entities, authorization processing can also be performed through the NEF when interacting with the core network. For example, a third-party application function might directly send a request message to the NEF. The NEF determines whether the AF is allowed to send the request message. If the verification is successful, the request message will be forwarded to the corresponding PCF or unified data management (UDM).

[0112] 9. Unified data management network element

[0113] The unified data management network element is mainly used for unified data management, supporting authentication trust status processing, user identity processing, access authorization, registration and mobility management, subscription management, and short message management in the 3GPP authentication and key negotiation mechanism.

[0114] 10. Unified data storage network element

[0115] The unified data storage network element is mainly used for storing and retrieving data of various types, such as contract data, strategy data, and application data.

[0116] 11. Data Network

[0117] A data network refers to a specific data service network that a UE accesses. For example, typical data networks include the Internet and the IP Multimedia Subsystem (IPMS).

[0118] In the above architecture, the functions of each interface are described as follows:

[0119] N7: The interface between PCF and SMF, used to issue PDU session granularity and business data flow granularity control policies.

[0120] N15: The interface between PCF and AMF, used to issue UE policies and access control related policies.

[0121] N5: The interface between AF and PCF, used for issuing application service requests and reporting network events.

[0122] N4: The interface between SMF and UPF, used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0123] N11: The interface between SMF and AMF, used to transmit PDU session tunnel information between RAN and UPF, transmit control messages sent to UE, and transmit radio resource control information sent to RAN, etc.

[0124] N2: The interface between AMF and RAN, used to transmit radio bearer control information from the core network side to the RAN.

[0125] N1: The interface between AMF and UE, access-independent, used to transmit QoS control rules to UE, etc.

[0126] N8: The interface between AMF and UDM, used by AMF to obtain access and mobility management related subscription data and authentication data from UDM, as well as by AMF to register UE's current mobility management information with UDM.

[0127] N10: The interface between SMF and UDM, used by SMF to obtain session management-related subscription data from UDM, and by SMF to register UE current session-related information with UDM.

[0128] N35: The interface between UDM and UDR, used by UDM to obtain user subscription data information from UDR.

[0129] N36: The interface between PCF and UDR, used by PCF to obtain policy-related contract data and application data related information from UDR.

[0130] N52: The interface between UDM and NEF, used by NEF to open network capabilities to third-party application functions, such as third-party application functions subscribing to reachability events of all users in a specific group through NEF to UDM.

[0131] In addition, NEF has direct interfaces with AMF and SMF, corresponding to the N29 interface and N51 interface respectively (not shown in the diagram above for simplification). These interfaces are used to open up operator network capabilities to third-party application function entities. The former can be used by NEF to directly subscribe to corresponding network events and update user configuration information from AMF, while the latter can be used to update application configuration data on SMF / UPF, such as packet flow description (PFD) information corresponding to the Application ID.

[0132] It should be understood that the network architecture described above in the embodiments of this application is merely an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture. The network architecture applicable to the embodiments of this application is not limited to this, and any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0133] It should be understood that Figure 1The interface names between the various network elements are merely examples; in actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0134] It should be noted that the aforementioned network element may also be referred to as an entity, device, apparatus, or module, etc., and this application does not specifically limit it. Furthermore, in this application, for ease of understanding and explanation, the description of network element is omitted in some descriptions. For example, the SMF network element is abbreviated as SMF. In this case, "SMF" should be understood as the SMF network element. The following descriptions of the same or similar cases are omitted.

[0135] It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network element or function can be implemented by one device, multiple devices working together, or a functional module within a single device; this application embodiment does not specifically limit this.

[0136] It should also be understood that, Figure 1 In the communication system shown, the functions of each component network element are merely exemplary. Not all functions of each component network element are required when applied to the embodiments of this application.

[0137] In addition, such as Figure 1 The names of the various network elements included (such as PCF, AMF, etc.) are merely names and do not limit the function of the network element itself. In 5G networks and other future networks, the aforementioned network elements may also have other names, and this application embodiment does not specifically limit this. For example, in 6G networks, some or all of the aforementioned network elements may use the terminology from 5G, or they may have other names, etc. This is uniformly explained here and will not be elaborated further below.

[0138] It should also be noted that, Figure 1 The communication between various network elements in the control plane function is described using a non-service interface as an example, but this does not limit the scope of protection of the embodiments in this application. Those skilled in the art will understand that... Figure 1 The various network elements in the control plane can also communicate through service-oriented interfaces. For example, the service-oriented interface provided by the AMF can be Namf; the service-oriented interface provided by the SMF can be Nsmf; the service-oriented interface provided by the UDM can be Nudm; the service-oriented interface provided by the AF can be Naf; the service-oriented interface provided by the PCF can be Npcf, and so on.

[0139] The above Figure 1 The network elements in the reference point architecture are not intended to limit the embodiments of this application.

[0140] Figure 2 A schematic diagram of an architecture based on service-oriented interfaces is provided. For example... Figure 2 As shown, the architecture includes: NSSF, AUSF, UDM, NEF, NRF, PCF, AF, AMF, SMF, UE, RAN, UPF, and DN. Figure 2 In this architecture, the service interface provided by the NSSF can be Nnssf, the NEF can be Nnef, the NRF can be Nnrf, the AMF can be Namf, the SMF can be Nsmf, the UDM can be Nudm, the AF can be Naf, the PCF can be Npcf, the AUSF can be Nausf, and the CHF can be Nchf. The interfaces between the control plane functions and the RAN and UPF are non-service interfaces. The UE connects to the AMF via the N1 interface and to the RAN via the radio resource control (RRC) protocol. The RAN connects to the AMF via the N2 interface and to the UPF via the N3 interface. The UPF connects to the DN via the N6 interface and to the SMF via the N4 interface. For further details, please refer to the 5G system architecture in the standard. For simplicity, the connection relationships in Architecture 300 will not be elaborated here.

[0141] To facilitate understanding of the embodiments of this application, the process of UE establishing PDU session connection and PDU session management will be briefly explained first, taking a 5G network as an example.

[0142] In 5G networks, the 5G network provides data exchange services between the UE and the DN network, a service known as PDU connectivity service. The UE obtains PDU connectivity service by initiating a PDU session establishment request to the mobile network. The network side provides PDU connectivity service by maintaining PDU sessions for the UE.

[0143] To enable data exchange between the UE and the DN network, the UE needs to use the PDU connection service provided by the mobile network to establish a DNN-based PDU session (signaling plane procedure). The establishment of a PDU session includes two basic processes: the UE registers with the mobile network and the UE requests the network to establish a PDU session. These two processes belong to the signaling plane interaction process between the UE and the mobile network.

[0144] The general UE registration and network access process can be simply described as follows: The UE sends a registration request to the AMF via (R)AN. The AMF obtains subscription data from a specific UDM based on the user identifier. After a series of authentication and authorization operations, the network side finally confirms that the UE is allowed to access the network. At this point, the AMF responds to the UE's registration request and sends relevant policy information to the UE, and the UE completes network registration and residency. The network-side AMF maintains the UE's registration and network access information and performs mobility management for the UE.

[0145] After a UE completes registration and network access, it can initiate a PDU session establishment request to obtain PDU connection services from the network. The general PDU session establishment process can be simply described as follows: The UE sends a PDU session establishment request to the AMF through the RAN. The AMF selects the SMF to provide session services for the UE, saves the mapping relationship between the SMF and the PDU session, and sends the session establishment request to the SMF. The SMF selects the corresponding UPF for the UE to establish a user plane transmission path and assigns an IP address to it.

[0146] During UE PDU session management, the SMF interacts with the UPF through the N4 interface to control the UPF in creating, modifying, and deleting corresponding UE N4 sessions (N4 Session / PFCP Session), thereby controlling the UPF's data packet processing. The SMF issues various data packet processing rules to the UE N4 sessions within the UPF to control the UPF's data packet processing. Upon receiving an external data packet, the UPF performs packet matching according to the data packet matching rules issued by the SMF and forwards the packet according to the forwarding rules.

[0147] In NR technology, an access network device (e.g., a gNB) can consist of one gNB Centralized Unit (CU) and one or more gNB Distributed Units (DUs). The gNB-CU and gNB-DU are different logical nodes and can be deployed on different physical devices or on the same physical device.

[0148] gNB adopts a CU-DU separated structure, such as Figure 3As shown, the gNB-CU and gNB-DU are connected via the F1 interface, the gNB-CU and the 5G core network are connected via the NG interface, and gNBs are connected to each other via the Xn interface. The Xn interface includes the Xn-C interface and the Xn-U interface. The Xn-C interface is used for the transmission of control plane signaling between the two gNBs, and the Xn-U interface is used for the transmission of user plane data between the two gNBs. The interface between the gNB and the UE is called the Uu interface (i.e., the interface between the UE and the gNB-DU). The terminal device accesses the gNB-CU through the gNB-DU. The physical (PHY) layer / medium access control (MAC) layer / radio link control (RLC) layer, which are equivalent to the terminal device, are located on the gNB-DU, while the packet data convergence protocol (PDCP) layer / radio resource control (RRC) layer / service data adaptation protocol (SDAP) layer, which are equivalent to the terminal device, are located on the gNB-CU.

[0149] It should be understood that the protocol layers existing on the gNB-DU and gNB-CU mentioned above are only one possibility, and other possibilities may also exist. For example, the PHY layer / MAC layer corresponding to the terminal device may be located on the gNB-DU, the PDCP layer / RRC layer / SDAP layer corresponding to the terminal device may be located on the gNB-CU, and the RLC layer corresponding to the terminal device may also be located on the gNB-CU. All of these are within the scope of protection of this application, and this application does not limit them here.

[0150] From the control plane perspective, in the uplink (UL) direction, the gNB-DU encapsulates the RRC message generated by the terminal device in an F1 Application Protocol (F1AP) message on the F1 interface and sends it to the gNB-CU. In the downlink (DL) direction, the gNB-CU encapsulates the RRC message in an F1AP message and sends it to the gNB-DU. The gNB-DU extracts the RRC message from the F1AP message and maps it to the corresponding Signalalling Radio Bearer (SRB) on the Uu interface before sending it to the terminal device.

[0151] For the user plane, in the UL direction, the gNB-DU maps data packets received from the terminal device on the Data Radio Bearer (DRB) of the Uu interface to the corresponding General Packet Radio Service Tunneling Protocol (GTP) tunnel before sending them to the gNB-CU. In the DL direction, the gNB-CU maps data packets from the terminal device to the corresponding GTP tunnel before sending them to the gNB-DU. The gNB-DU extracts the data packets from the terminal device from the GTP tunnel and maps these packets to the DRB corresponding to the Uu interface before sending them to the terminal device.

[0152] 5G communication systems impose more stringent requirements on all aspects of network performance. For example, they demand a 1000-fold increase in capacity, wider coverage, and ultra-high reliability and ultra-low latency. Therefore, Integrated Access and Backhaul (IAB) technology has been introduced.

[0153] In IAB networks, such as Figure 4 As shown, a relay node (RN), also known as an IAB node, provides wireless access and wireless backhaul services to user equipment. Specifically, the user equipment's service data is connected from the IAB node to the IAB donor via a wireless backhaul link. The IAB donor can also be called a host IAB node (donor IAB) or an IAB donor base station. In NR systems, the IAB donor base station can be a host next-generation base station (donor gNodeB, DgNB), while in LTE systems (or 4G systems), it can be a host evolved NodeB (donor eNodeB, DeNB). Of course, the IAB donor node can also be simply referred to as gNB, eNB, or IAB donor.

[0154] The IAB donor can also adopt a CU-DU separation architecture, such as Figure 4As shown, the IAB donor consists of two parts: the IAB donor CU (or donor CU) and the IAB donor DU (or donor DU). The interface between the IAB donor CU and the IAB donor DU is the F1 interface. An IAB node can consist of a mobile terminal (MT) unit and a distributed unit (DU). The IAB-MT, also known as the IAB-UE, has the functions of a terminal device and mainly performs operations similar to those of a terminal device. The IAB-DU has some of the functions of a base station and mainly performs operations similar to those of a base station.

[0155] For IAB donors, the function of donor DU is similar to that of gNB-DU in NR, and the function of donor CU is similar to that of gNB-CU in NR.

[0156] For IAB nodes, the IAB-DU functions similarly to the gNB-DU in NR, providing access services to the nodes it connects to. The nodes connected to the IAB-DU can be terminal devices or other IAB nodes. The IAB-MT is similar to a terminal device, used to provide data backhaul. The IAB node to which the terminal device connects can be called the access IAB node, and the IAB nodes on the path between the access IAB node and the IABdonor are called intermediate IAB nodes. For example, if the terminal device connects to IAB node 2 (IABnode2), then IAB node2 is called the access IAB node, and IAB node1 is called the intermediate IAB node.

[0157] Figure 5 and Figure 6 This is a schematic flowchart illustrating a communication method provided in an embodiment of this application. It should be noted that during the movement of the first device, when the first device switches from a first network device to a second network device, the following two scenarios may occur. Among them, Figure 5 Corresponding to scenario one described below, Figure 6 This corresponds to scenario two described below.

[0158] Scenario 1: During the process of the first device switching from the first network device to the second network device, the access and mobility management function network elements are not changed, such as... Figure 5 As shown, the access and mobility management function network element 1 (UE AMF1, VMRAMF1) is connected to the first network device and the second network device.

[0159] Scenario 2: During the process of the first device switching from the first network device to the second network device, the access and mobility management function network elements are replaced, such as... Figure 6 As shown, the access and mobility management function (AM) network element 1 is replaced by access and mobility management (AM) network element 2. In other words, AM1 (e.g., UE AMF1, VMR AMF1) is connected to the first network device, and the replaced AM2 (e.g., UE AMF2, VMR AMF2) is connected to the second network device.

[0160] Figure 5 This is a schematic flowchart of a communication method 500 adapted to scenario one provided in an embodiment of this application. The method includes at least the following steps.

[0161] S510, the first network device sends the tracking area information of the first device to the access and mobility management function network element 1, and correspondingly, the access and mobility management function network element 1 receives the tracking area information of the first device from the first network device.

[0162] For example, the first network device can be a donor gNB1, or a CU located in the first network device (e.g., donorgNB1). The first device can be a vehicle-mounted relay (VMR) or a UE serving a VMR. This application embodiment does not limit this.

[0163] Taking the first network device as donor gNB1 and the first device as VMR as an example, VMR obtains its tracking area information by interacting with OAM through the user plane. Subsequently, the DU part (or as a DU) in VMR interacts with the CU of donor gNB1. Through the F1 setup process, the tracking area information of VMR is registered to the CU of donor gNB1. At this time, the CU of donor gNB1 updates its corresponding tracking area information list.

[0164] The Tracking Area Information (S-TAI) is specific to the first device. This can be understood as the Tracking Area Information broadcast by the first device to the UEs it serves remaining constant during the device's movement. That is, even if the first device switches from a first network device to a second network device (e.g., to another donor gNB2), the Tracking Area Information broadcast by the first device to the UEs it serves remains unchanged, i.e., it is the S-TAI. In other words, the S-TAI can only be assigned to UEs served by a VMR. When assigning a TAI to a UE not served by a VMR, no S-TAI is assigned. Therefore, the S-TAI is VMR-specific, or VMR-exclusive. Furthermore, the S-TAIs corresponding to different VMRs may be the same or different. For example, different VMRs in different regions may have the same S-TAI, while different VMRs within the same region may have different S-TAIs. For ease of description, S-TAI will be used consistently to refer to the Tracking Area Information of the first device in the following description.

[0165] It should be noted that, in this embodiment of the application, the UE served by the first device is an idle UE.

[0166] In one possible implementation, the tracking area information (S-TAI) of the first device may be carried in an update configuration message or in other messages. It should be understood that the embodiments of this application are not limited herein.

[0167] Optionally, in one possible implementation, the update configuration message may include indication information indicating that the tracking area information is the tracking area information of the first device. For example, this indication information may be VMR-specific TA indication information, used to indicate that the S-TAI is specific tracking area information of the VMR.

[0168] In one possible implementation, the indication information can be represented using a shorter field. For example, when the field is 1 bit, if the field is "1", it indicates that the indication information indicates that the S-TAI is the tracking area information of the VMR; if the field is "0", it indicates that the indication information indicates that the S-TAI is not the tracking area information of the VMR.

[0169] In one possible implementation, the indication information can also be implicit in the tracking area information S-TAI. For example, when the network side (CN) divides the TAI, it uses a specific range of TAIs as the S-TAI of the dedicated VMR. That is, when the S-TAI belongs to the specific range of TAIs, it indicates that the S-TAI is the tracking area information of the VMR.

[0170] It should be noted that the first device can be a vehicle-mounted relay (VMR) or a terminal device carried on a movable object (e.g., a UE on a moving vehicle). The access and mobility management function network element 1 can be the first AMF network element (UE AMF1) registered by the UE or the second AMF network element (VMR AMF1) registered by the first device. It should be understood that the embodiments of this application do not impose any limitations on this.

[0171] S520, Access and Mobility Management Function Network Element 1 stores the tracking area information of the first device and the association relationship of the first network device.

[0172] For example, after the access and mobility management function network element 1 receives the tracking area information (S-TAI) of the first device sent by the first network device, that is, after the first network device informs all the access and mobility management function network elements 1 connected to it that there is a first device within its jurisdiction and the tracking area information (S-TAI) of the first device, the access and mobility management function network element 1 saves the association relationship between the S-TAI of the first device and the first network device.

[0173] It should be understood that the association between the S-TAI of the first device and the first network device can be the association between the S-TAI and gNB1. For example, the association between the S-TAI of the first device and the identification information (RAN ID1) of the first network device (gNB1) can be the association between the S-TAI and the CU1 located in gNB1. This application embodiment does not limit this.

[0174] S530, when the second network device serves the first device, the access and mobility management function network element 1 deletes the tracking area information of the first device and the association relationship of the first network device.

[0175] For example, during the movement of the first device, the first device switches from the first network device to the second network device. That is, at this time, the serving network device of the first device changes from the first network device to the second network device. When the second network device serves the first device, the access and mobility management function network element 1 deletes the tracking area information (S-TAI) of the first device and the association relationship between the first device and the first device.

[0176] It should be noted that, Figure 5 Corresponding to Scenario 1 mentioned above, during the process of the first device switching from the first network device to the second network device, the access and mobility management function network element is not changed, that is, the access and mobility management function network element 1 (UE AMF1, VMR AMF1) is connected to the first network device and the second network device.

[0177] Optionally, prior to S530, the method may further include: S521, the second network device sends the tracking area information (S-TAI) of the first device to the access and mobility management function network element 1, and correspondingly, the access and mobility management function network element 1 receives the tracking area information (S-TAI) of the first device from the second network device.

[0178] S522, Access and Mobility Management Function Network Element 1 stores the Tracking Area Information (S-TAI) of the first device and the association relationship between the second network device.

[0179] It should be understood that the second network device can be the donor gNB2 or the CU2 located in the second network device (donorgNB2), and the first device can be a vehicle-mounted relay (VMR) or a UE serving VMR. This application embodiment does not limit this.

[0180] Taking the second network device as donor gNB2 and the first device as VMR as an example, VMR obtains its tracking area information by interacting with OAM through the user plane. Subsequently, the DU part (or as a DU) in VMR interacts with the CU of donor gNB2. Through the F1 setup process, the tracking area information of VMR is registered to the CU of donor gNB2. At this time, the CU of donor gNB2 updates its corresponding tracking area information list (TAI list).

[0181] For example, in Scenario 1, when Access and Mobility Management Function (AMF) element 1 (e.g., UE AMF1, VMR AMF1) is connected to a first network device and a second network device, AMF1 (UE AMF1, VMR AMF1) receives the S-TAI of the first device from the second network device. This can be understood as the second network device informing all AMF1 elements 1 connected to it (e.g., UE AMF1 and VMR AMF1) that its associated TAI list includes the tracking area information (S-TAI) of the first device. At this time, AMF1 (UE AMF1, VMR AMF1) stores the association between the S-TAI of the first device and the second network device.

[0182] It should be understood that the association between the S-TAI of the first device and the second network device can be the association between the S-TAI and gNB2. For example, the association between the S-TAI of the first device and the identification information (RAN ID2) of the second network device (gNB2) can be the association between the S-TAI and the CU2 located in gNB2. This application embodiment does not limit this.

[0183] Optionally, in one possible implementation, in scenario one, i.e., when access and mobility management function network element 1 connects to the first network device and the second network device, after access and mobility management function network element 1 receives the S-TAI of the first device from the second network device, access and mobility management function network element 1 learns from the identifier (e.g., RAN ID2) contained in the S-TAI of the first device received from the second network device that the serving network device of the first device has switched from the first network device to the second network device. At this time, access and mobility management function network element 1 deletes the association between the S-TAI of the first device and the first network device by using the S-TAI as an index.

[0184] Optionally, in one possible implementation, the method may further include: S523, the first network device sends first indication information to the access and mobility management function network element 1, and correspondingly, the access and mobility management function network element 1 receives the first indication information from the first network device, the first indication information being used to indicate the deletion of the tracking area information of the first device and the association relationship of the first network device.

[0185] For example, in scenario one, where the access and mobility management function network element 1 (UE AMF1, VMR AMF1) is connected to the first network device and the second network device, the access and mobility management function network element 1 (UE AMF1, VMRAMF1) deletes the association between the S-TAI of the first device and the first network device according to the received first indication information, which contains an identifier (e.g., RAN ID1).

[0186] It should be noted that S523 can be executed before or after S521 and S522. It should be understood that the embodiments of this application do not limit the specific execution order.

[0187] For example, in one possible implementation, step S523 can be triggered by the action of the first device switching from the first network device to the second network device. That is, when the first device switches from the first network device to the second network device, the first network device is triggered to send a first instruction message to the access and mobility management function network element 1, instructing to delete the association between the first device's S-TAI and the first network device.

[0188] In the technical solution of this application embodiment, when the first device accesses the first network device, the access and mobility management function network element 1 saves the tracking area information of the first device and the association relationship of the first network device. When the first device switches from the first network device to the second network device, the mobility management function network element 1 saves the tracking area information of the first device and the association relationship of the second network device, and deletes the previously saved tracking area information of the first device and the association relationship of the first network device. This enables the network side to promptly know that the network device associated with the first device has changed from the first device to the second network device. Consequently, when the network side needs to page the first device and / or the UE served by the first device, it can accurately locate the second network device. This avoids the situation where the network side instructs the first network device to send a paging message when it pages the first device and / or the UE served by the first device. This allows the network side to more accurately manage the mobility of the UE and avoids wasting resources.

[0189] Figure 6 This is a schematic flowchart of a communication method 600 adapted to scenario two, provided in an embodiment of this application. The method includes at least the following steps.

[0190] S610, the first network device sends the tracking area information of the first device to the access and mobility management function network element 1, and correspondingly, the access and mobility management function network element 1 receives the tracking area information of the first device from the first network device.

[0191] S620, the access and mobility management function network element 1 stores the tracking area information of the first device and the association relationship of the first network device.

[0192] It should be noted that S610-S620 are similar to S510-S520, but for the sake of simplicity, this application will not elaborate further.

[0193] Optionally, after S620, the method may further include S621, in which the access and mobility management function network element 1 sends first registration information to the unified database network element, and correspondingly, the unified database network element receives the first registration information from the access and mobility management function network element 1. The first registration information is used to register the tracking area information (S-TAI) of the first device and the association relationship of the first network device with the unified database.

[0194] For example, the access and mobility management function network element 1 can be the access and mobility management function network element 1 registered by the first device (e.g., VMR AMF1). VMR AMF1 is connected to the first network device. VMR AMF1 sends first registration information to the unified database network element. The first registration information includes the identification information of the first network device (e.g., donor gNB1 ID or RAN1 ID). The unified database network element registers the tracking area information (S-TAI) of the first device and the association relationship of the first network device in the unified database according to the first registration information.

[0195] It should be noted that, Figure 6 Corresponding to scenario two described above, that is, during the process of the first device switching from the first network device to the second network device, the access and mobility management function network elements are replaced, such as... Figure 6 As shown, the access and mobility management function (AM) network element 1 is replaced by access and mobility management (AM) network element 2. In other words, AM1 (e.g., UE AMF1, VMR AMF1) is connected to the first network device, and the replaced AM2 (e.g., UE AMF2, VMR AMF2) is connected to the second network device.

[0196] S630, the second network device sends the tracking area information (S-TAI) of the first device to the access and mobility management function network element 2, and correspondingly, the access and mobility management function network element 2 receives the tracking area information (S-TAI) of the first device from the second network device.

[0197] S640, Access and Mobility Management Function Network Element 2 stores the Tracking Area Information (S-TAI) of the first device and the association relationship between the second network device.

[0198] It should be understood that the second network device can be the donor gNB2 or the CU2 located in the second network device (donorgNB2), and the first device can be a vehicle-mounted relay (VMR) or a UE serving VMR. This application embodiment does not limit this.

[0199] Taking the second network device as donor gNB2 and the first device as VMR as an example, the DU part in VMR (or as a DU) interacts with the CU of donor gNB2. Through the F1 setup process, the tracking area information of VMR is registered to the CU of donor gNB2. At this time, the CU of donor gNB2 updates its corresponding tracking area information list (TAI list).

[0200] In Scenario 2, where Access and Mobility Management Function (AMF) element 1 (e.g., UE AMF1, VMR AMF1) is connected to the first network device, and the replaced AMF network element 2 (e.g., UE AMF2, VMR AMF2) is connected to the second network device, the replaced AMF network element 2 (UE AMF2, VMR AMF2) receives the Tracking Area Information (S-TAI) of the first device from the second network device. This can be understood as the second network device informing all connected AMF network elements 2 (e.g., UE AMF2, VMR AMF2) that its associated TAI list includes the Tracking Area Information (S-TAI) of the first device. At this time, AMF network element 2 (UE AMF2, VMR AMF2) stores the association between the Tracking Area Information (S-TAI) of the first device and the second network device.

[0201] Optionally, after S640, the method may further include S641, in which the access and mobility management function network element 2 sends second registration information to the unified database network element, and correspondingly, the unified database network element receives the second registration information from the access and mobility management function network element 2, the second registration information being used to register the tracking area information (S-TAI) of the first device and the association relationship of the second network device with the unified database.

[0202] For example, the access and mobility management function network element 2 at this time can be the access and mobility management function network element 2 registered by the first device (e.g., VMR AMF2). The VMR AMF2 is connected to the second network device. The VMR AMF2 sends second registration information to the unified database network element. The second registration information includes the identification information of the second network device (e.g., donor gNB2ID or RAN2 ID). The unified database network element registers the tracking area information of the first device and the association relationship of the second network device into the unified database according to the second registration information.

[0203] S650, the first network device sends a first instruction information to the access and mobility management function network element 1. Correspondingly, the access and mobility management function network element 1 receives the first instruction information from the first network device. The first instruction information is used to indicate the deletion of the tracking area information of the first device and the association relationship of the first network device.

[0204] For example, in scenario two, when the access and mobility management function network element 1 (UE AMF1, VMR AMF1) is connected to the first network device, the access and mobility management function network element 1 (UE AMF1, VMR AMF1) deletes the association between the S-TAI of the first device and the first network device according to the received first indication information, which contains the identifier of the first network device (e.g., RAN ID1).

[0205] It should be noted that S650 can be executed before or after S630 and S640. It should be understood that the embodiments of this application do not limit the specific execution order.

[0206] For example, in one possible implementation, step S650 can be triggered by the action of the first device switching from the first network device to the second network device. That is, when the first device switches from the first network device to the second network device, the first network device is triggered to send a first instruction message to the access and mobility management function network element 1, instructing to delete the association between the first device's S-TAI and the first network device.

[0207] Optionally, in one possible implementation, the first indication information may further include the identification information of the second network device. For example, in scenario two, access and mobility management function network element 1 (e.g., UE AMF1, VMR AMF1) receives first indication information from the first network device, which also includes the identification information of the second network device (e.g., donor gNB2 ID or RAN2 ID). That is, the first network device informs access and mobility management function network element 1 (UE AMF1, VMR AMF1) that the target network device for the first device handover is the second network device. At this time, the access and mobility management function network element (UE AMF1) registered by the UE will determine UE AMF2 connected to the second network device to provide services to the UE based on the identification information of the second network device in the received first indication information. Subsequently, UE AMF1 and UE AMF2 will perform UE context migration.

[0208] Optionally, in scenario two, the method may further include S660, whereby the access and mobility management function network element 1 sends a first request information to the unified database, and the unified database receives the first request information, which is used to request the unified database to delete the tracking area information (S-TAI) of the first device and the association relationship of the first network device.

[0209] For example, the access and mobility management function network element 1 can be an access and mobility management function network element registered by VMR (e.g., VMR AMF1). VMR AMF1 is connected to the first network device. VMR AMF1 sends a first request information to the unified database. The unified database deletes the tracking area information (S-TAI) of the first device and the association relationship between the first network device based on the received first request information.

[0210] It should be noted that step S650 can be used to trigger step S660. In step S650, the donor gNB1 sends a first indication information to VMRAMF1 and UE AMF1. The first indication information is used to indicate the deletion of the association between the first network device and S-TAI. Optionally, in a possible implementation, the first indication information may also include VMR identification information (e.g., VMR ID1). VMR AMF1 determines that it serves a VMR based on the VMR identification information (e.g., VMR ID1), thereby triggering VMR AMF1 to send a first request message to the unified database, requesting the unified database to delete the association between the first network device and S-TAI.

[0211] It should be understood that step S660 can also be an optional step, that is, the access and mobility management function network element 1 may not send a request message to the unified database to request the deletion of the association between the first network device and the S-TAI information. In one possible implementation, S641 can be used to trigger the unified database to delete the association between the first network device and the S-TAI information. In other words, when VMR AMF2 registers the association between the second network device and the S-TAI with the unified database, the unified database will then delete the association between the first network device and the S-TAI.

[0212] Optionally, in scenario two, the method may further include: S670, the access and mobility management function network element 1 sends a first query information to the unified database, and correspondingly, the unified database receives the first query information, which is used to query the unified database for network devices associated with the tracking area information (S-TAI) of the first device.

[0213] For example, the access and mobility management function network element 1 can be an access and mobility management function network element registered by the UE (e.g., UE AMF1). UE AMF1 is connected to the first network device. UE AMF1 sends the first query information to the unified database. The unified database determines that the network device associated with the tracking area information (S-TAI) of the first device is the second network device based on the S-TAI carried in the received first query information.

[0214] For example, UE AMF1 uses the general query service of the unified database. UE AMF1 carries the query target type as gNB (or RAN) and the query index as S-TAI in the first query information, so that the unified database determines that the network device associated with the tracking area information (S-TAI) of the first device is the second network device.

[0215] It should be noted that step S670 can be triggered by step S650. That is, after UE AMF1 deletes the association between the tracking area information of the first device and the first network device according to the received first instruction information, it can determine that the first device corresponding to the tracking area information has left the first network device. At this time, UE AMF1 needs to know the new network device associated with the tracking area information of the first device. Then, UE AMF1 will send the first query information to the unified database to query which new network device is associated with the tracking area information of the first device.

[0216] S680, the unified database sends a first response information to the access and mobility management function network element, and the access and mobility management function network element receives the first response information, which includes the identification information of the second network device.

[0217] In scenario two, the access and mobility management function network element 1 can be an access and mobility management function network element registered by the UE (e.g., UE AMF1), and UE AMF1 is connected to the first network device.

[0218] After the unified database determines that the network device associated with the tracking area information (S-TAI) of the first device is the second network device, the unified database sends a first response message to UE AMF1. The first response message contains the identification information of the second network device (e.g., donor gNB2 ID or RAN2 ID). That is, the unified database informs UE AMF1 that the network device associated with the tracking area information (S-TAI) of the first device is the second network device.

[0219] It should be noted that S670 is an optional step, that is, the access and mobility management function network element (e.g., UEAMF1) can subscribe in advance to the unified database for changes in the network devices associated with the tracking area information (S-TAI) of the first device. Once the network device associated with the tracking area information (S-TAI) of the first device changes, for example, from the first network device to the second network device, the unified database directly sends the first response information to UEAMF1, that is, informs that the network device associated with the S-TAI of the first device has changed to the second network device.

[0220] In the technical solution of this application embodiment, when the first device accesses the first network device, the access and mobility management function network element 1 saves the tracking area information of the first device and the association relationship of the first network device. When the first device switches from the first network device to the second network device, the mobility management function network element 2 saves the tracking area information of the first device and the association relationship of the second network device, the mobility management function network element 1 deletes the previously saved tracking area information of the first device and the association relationship of the first network device, and obtains the identification information of the second network device from the first network device. Through the above technical solution, the network side can promptly know that the network device associated with the first device has changed from the first device to the second network device. Therefore, when the network side needs to page the first device and / or the UE served by the first device, it can accurately locate the second network device. There will be no situation where the network side instructs the first network device to send a paging message when the network side pages the first device and / or the UE served by the first device. This enables the network side to perform more accurate mobility management of the UE and avoids wasting resources.

[0221] For ease of understanding, in the embodiments described below, the term "vehicle-mounted relay (VMR)" will be used to refer to the first device.

[0222] Figure 7 This is a schematic flowchart of a communication method 700 provided in an embodiment of this application. It should be noted that method 700 mainly corresponds to scenario one described above, namely, during the VMR's handover from donor gNB1 to donor gNB2, the access and mobility management function (AMF) network elements are not changed. That is, the AMF network elements (e.g., UE AMF, VMR AMF) are connected to donor gNB1 and donor gNB2. The UE AMF and VMR AMF can be the same AMF (i.e., interaction between these two AMFs can be achieved through internal interaction), or they can be different AMFs. The following description assumes that the UE AMF and VMR AMF are different AMFs. The method includes at least the following steps.

[0223] It should be noted that, in this embodiment of the application, the UE providing the VMR service is an idle UE.

[0224] The S710 VMR registers with the network (CN) and establishes a PDU session.

[0225] For example, when a VMR registers with the network, the Access and Mobility Management Function (VMR AMF) provides services to the VMR. The VMR establishes a PDU session, allowing it to communicate with the OAM system via the user plane. The OAM system then returns the VMR's specific Tracking Area Information (S-TAI) via the user plane. Subsequently, the VMR interacts with the CU in the donor gNB1, registering the S-TAI with the CU of donor gNB1 through the F1 setup procedure. At this point, CU1 of donor gNB1 updates the corresponding TAI list.

[0226] S720, the donor gNB1 sends the S-TAI of VMR to the UE AMF network element and the VMR AMF network element, and correspondingly, the UE AMF network element and the VMR AMF network element receive the S-TAI of VMR.

[0227] For example, since the current VMR communicates through the donor gNB1, the donor gNB1 sends the S-TAI of the VMR to the AMFs that have established a connection with it. The AMFs that have established a connection with the donor gNB1 include the UE AMF and the VMR AMF. Therefore, it can be understood that the donor gNB1 sends the S-TAI of the VMR to both the UE AMF and the VMR AMF network elements. The S-TAI of the VMR can be found in [reference needed]. Figure 5 The description will not be repeated here.

[0228] For example, the donor gNB1 can send the VMR S-TAI to the UE AMF network element and the VMR AMF network element through configuration update message 1. That is, configuration update message 1 includes the VMR S-TAI.

[0229] Optionally, in one possible implementation, the configuration update message 1 includes the S-TAI of the VMR and VMR indication information. The VMR indication information is used to indicate to the UE AMF network element and the VMR AMF network element that the S-TAI is specific tracking area information for the VMR. The donor gNB1 uses configuration update message 1 ( Ran configuration update1 It informs all AMFs (including UE AMF and VMR AMF) connected to the donor gNB1 that there is a VMR within its jurisdiction and the tracking area information (S-TAI) of that VMR.

[0230] Optionally, in one possible implementation, the configuration update message 1 may only contain the S-TAI information of the VMR, that is, it may not contain the VMR indication information. The S-TAI includes specific information that allows the UE AMF network element and the VMR AMF network element to identify that the S-TAI is specific tracking area information (S-TAI) specific to the VMR.

[0231] Alternatively, in one possible implementation, the network side (CN) defines a TAI list specific to the VMR. Then, the UE AMF network element and the VMR AMF network element can identify that the S-TAI is specific tracking area information (S-TAI) exclusive to the VMR based on whether the S-TAI belongs to the TAI list.

[0232] It should be noted that during the VMR's movement, the tracking area information (S-TAI) broadcast by the VMR to the UE it serves remains constant. In other words, even if the VMR switches from donor gNB1 to donor gNB2, the VMR's tracking area information (S-TAI) remains unchanged.

[0233] In S730, the UE registers with the network via VMR. The UE AMF performs access and mobility management on the UE. If the UE's location information is within the area specified by the S-TAI information, the UE AMF determines that the UE is being served by a VMR. In this case, the UE AMF assigns the S-TAI as part of the UE's TAI List. Conversely, if the UE's location information is not within the area specified by the S-TAI information, the UE AMF determines that the UE is not being served by a VMR. Therefore, when assigning a TAI List to a UE not served by that VMR, the UE AMF will not include the S-TAI in that TAI List.

[0234] S740, VMR switches from donor gNB1 to donor gNB2.

[0235] For example, corresponding to Scenario 1 mentioned above, during the VMR switch from donor gNB1 to donor gNB2, the UE AMF network element and the VMR AMF network element are not changed. In other words, the AMF network element connected to donor gNB1 is the same as the AMF network element connected to donor gNB2. For example, donor gNB1 connects to UE AMF1 and VMRAMF1, and donor gNB1 also connects to UE AMF1 and VMR AMF1.

[0236] S750, VMR will register the S-TAI obtained from the OAM system into the donor gNB2.

[0237] For example, the VMR exchanges information with the CU in the donor gNB2. The VMR registers the S-TAI to the CU2 of the donor gNB2 through the F1 setup process. At this time, the CU2 of the donor gNB2 updates the corresponding TAI list.

[0238] S760, the donor gNB2 sends the S-TAI of VMR to the UE AMF network element and the VMR AMF network element, and correspondingly, the UE AMF network element and the VMR AMF network element receive the S-TAI of VMR.

[0239] For example, since the current VMR communicates through donor gNB2, donor gNB2 sends the S-TAI of the VMR to the AMFs that have established a connection with it. The AMFs that have established a connection with donor gNB1 include the UE AMF and the VMR AMF. Therefore, it can be understood that donor gNB2 sends the S-TAI of the VMR to both the UE AMF and VMR AMF network elements. The S-TAI of the VMR can be found in [reference needed]. Figure 5 The description will not be repeated here.

[0240] For example, the donor gNB2 can send the VMR S-TAI to the UE AMF network element and the VMR AMF network element through configuration update message 2. That is, configuration update message 2 includes the VMR S-TAI.

[0241] Optionally, in one possible implementation, the configuration update message 2 includes the S-TAI of the VMR and VMR indication information. The VMR indication information is used to indicate to the UE AMF network element and the VMR AMF network element that the S-TAI is specific tracking area information for the VMR. The donor gNB2 uses configuration update message 2 ( Ran configuration update2 It informs all AMFs (including UE AMF and VMR AMF) connected to the donor gNB2 of the existence of a VMR within its jurisdiction and the tracking area information (S-TAI) of that VMR.

[0242] Optionally, in one possible implementation, the configuration update message 2 may only contain the S-TAI information of the VMR, i.e., it may not contain VMR indication information. This S-TAI includes specific information that allows the UE AMF network element and the VMR AMF network element to identify that the S-TAI is specific tracking area information (S-TAI) specific to the VMR. Alternatively, in another possible implementation, the network side (CN) defines a list of TAIs specific to the VMR. Then, the UE AMF network element and the VMR AMF network element can identify that the S-TAI is specific tracking area information (S-TAI) specific to the VMR based on whether the S-TAI belongs to this TAI list.

[0243] S770, donor gNB1 sends configuration update message 3 to UE AMF network element and VMR AMF network element.

[0244] For example, configuration update message 3 instructs all AMFs (UE AMF and VMRAMF elements) connected to the donor gNB1 to delete the S-TAI. Alternatively, configuration update message 3 can be described as instructing all AMFs connected to the donor gNB1 to delete the association between the S-TAI and the donor gNB1 or CU1 within the donor gNB1. In this case, VMR AMF1 and UE AMF1, based on the received configuration update message 3 (which contains the identifier of the donor gNB1, such as gNB ID1), delete the association between the VMR's S-TAI and the donor gNB1. This can be understood as the donor gNB1 informing all AMFs connected to it that a VMR with an S-TAI has left its jurisdiction. Therefore, all AMFs (UE AMF and VMR AMF elements) connected to the donor gNB1 will not seek out the donor gNB1 in subsequent processing of the VMR and UE corresponding to this S-TAI.

[0245] For example, when the network needs to page the VMR and / or the UE served by the VMR, the VMR AMF and / or UE AMF network elements can accurately locate the donor gNB 2, and there will be no situation where the VMR AMF and / or UE AMF instruct the donor gNB 1 to send a paging message when the network pages the UE served by the VMR, thereby avoiding the waste of resources.

[0246] It should be noted that step S770 can also be executed after step S740. This can be understood as follows: the VMR switching from donor gNB1 to donor gNB2 in step S740 can trigger donor gNB1 to send configuration update message 3 to the UE AMF network element and VMRAMF network element in step S770. This configuration update message 3 is used to indicate the deletion of the association between donor gNB1 and S-TAI. It should be understood that the execution order is not limited in this embodiment.

[0247] It should be understood that this application may also use other messages / information to indicate the deletion of the association between donor gNB1 and S-TAI information. Configuration update message 3 is only an example, and this application embodiment does not limit this.

[0248] In the technical solution of this application embodiment, when a VMR accesses donor gNB1, the AMF (e.g., VMR AMF, UE AMF) stores the association between the VMR's S-TAI and donor gNB1. When the VMR switches from donor gNB1 to donor gNB2, the AMF (e.g., VMR AMF, UE AMF) deletes the previously stored association between the VMR's S-TAI and donor gNB1. This technical solution enables the network side to promptly learn that the network device associated with the VMR has changed to donor gNB2. Therefore, when the network side needs to page the VMR and / or a UE serving the VMR, it can accurately locate the donorgNB2 associated with the VMR. This prevents the network side from instructing other network devices (e.g., donorgNB1) to send paging messages when paging a UE serving the VMR, thus enabling the network side to more accurately manage UE mobility and avoid resource waste.

[0249] Figure 8This is a schematic flowchart of a communication method 800 provided in an embodiment of this application. It should be noted that method 800 mainly corresponds to scenario two described above, namely, during the VMR's handover from donor gNB1 to donor gNB2, the access and mobility management function (AMF) network elements are changed. Specifically, the AMF network elements (e.g., UE AMF1, VMRAMF1) are connected to donor gNB1, and the AMF network elements (e.g., UE AMF2, VMR AMF2) are connected to donor gNB2. UE AMF1 and VMR AMF1 can be the same AMF, and UE AMF2 and VMR AMF2 can be the same AMF (i.e., interaction between the two AMFs can be achieved through internal interaction), or they can be different AMFs. The following description assumes that UE AMF and VMR AMF are different AMFs. This method includes at least the following steps.

[0250] It should be noted that, in this embodiment of the application, the UE providing the VMR service is an idle UE.

[0251] The S810 VMR registers with the network (CN) and establishes a PDU session.

[0252] For example, when a VMR registers with the network, the Access and Mobility Management Function (VMR) network element AMF1 provides services to the VMR. The VMR establishes a PDU session, allowing it to communicate with the OAM system via the user plane. The OAM system then returns the VMR's specific Tracking Area Information (S-TAI) via the user plane. Subsequently, the VMR interacts with the CU1 in the donor gNB1, registering the S-TAI with the donor gNB1's CU1 through the F1 setup procedure. At this point, the donor gNB1's CU1 updates its corresponding TAI list.

[0253] S820, the donor gNB1 sends the S-TAI of VMR to the UE AMF1 network element and the VMR AMF1 network element, and correspondingly, the UE AMF1 network element and the VMR AMF1 network element receive the S-TAI of VMR.

[0254] For example, since the current VMR communicates through the donor gNB1, the donor gNB1 sends the S-TAI of the VMR to the AMFs that have established a connection with it. The AMFs that have established a connection with the donor gNB1 include UE AMF1 and VMR AMF1. Therefore, it can be understood that the donor gNB1 sends the S-TAI of the VMR to both the UE AMF1 network element and the VMR AMF1 network element. The S-TAI of the VMR can be found in [reference needed]. Figure 5The description will not be repeated here.

[0255] For example, the donor gNB1 can send the VMR S-TAI to the UE AMF1 network element and the VMR AMF1 network element through configuration update message 1. That is, configuration update message 1 includes the VMR S-TAI.

[0256] Optionally, in one possible implementation, the configuration update message 1 includes the S-TAI of the VMR and VMR indication information. The VMR indication information is used to indicate to the UE AMF1 network element and the VMR AMF1 network element that the S-TAI is specific tracking area information for the VMR. The donor gNB1 uses configuration update message 1 ( Ran configuration update1 It informs all AMFs connected to donor gNB1 (including UE AMF1 and VMR AMF1) that there is a VMR within its jurisdiction and the tracking area information (S-TAI) of that VMR.

[0257] Optionally, in one possible implementation, the configuration update message 1 may only contain the S-TAI information of the VMR, i.e., it may not contain VMR indication information. This S-TAI includes specific information that allows the UE AMF1 network element and the VMR AMF1 network element to identify that the S-TAI is specific tracking area information (S-TAI) specific to the VMR. Alternatively, in another possible implementation, the network side (CN) defines a list of TAIs specific to the VMR. The UE AMF1 network element and the VMR AMF1 network element can then identify that the S-TAI belongs to this TAI list, thus recognizing that the S-TAI is specific tracking area information (S-TAI) specific to the VMR.

[0258] It should be noted that during the VMR's movement, the tracking area information (S-TAI) broadcast by the VMR to the UE it serves remains constant. In other words, even if the VMR switches from donor gNB1 to donor gNB2, the VMR's tracking area information (S-TAI) remains unchanged.

[0259] In S830, the UE registers with the network via VMR. UE AMF1 performs access and mobility management for the VMR. If the UE's location information is within the area specified by the S-TAI information, UE AMF1 determines that the UE is being served by the VMR. In this case, UE AMF1 assigns the S-TAI as part of the UE's TAI List. Conversely, if the UE's location information is not within the area specified by the S-TAI information, UE AMF1 determines that the UE is not being served by the VMR. Therefore, when assigning a TAI List to a UE not served by that VMR, UE AMF1 will not include the S-TAI in that TAI List.

[0260] S840, VMR switches from donor gNB1 to donor gNB2.

[0261] For example, during the VMR switch from donor gNB1 to donor gNB2, the UE AMF network element and VMRAMF network element are replaced. In other words, the AMF network element connected to donor gNB1 is different from the AMF network element connected to donor gNB2. For example, donor gNB1 connects UE AMF1 and VMRAMF1, and donor gNB2 connects UE AMF2 and VMR AMF2.

[0262] In S850, VMR registers the S-TAI obtained from the OAM system to the donor gNB2. It should be noted that S850 is similar to S750; for simplicity, this application will not elaborate further.

[0263] S860, the donor gNB2 sends the S-TAI to the UE AMF2 network element and the VMR AMF2 network element VMR, and correspondingly, the UE AMF2 network element and the VMR AMF2 network element receive the S-TAI of the VMR.

[0264] For example, since the current VMR communicates through donor gNB2, donor gNB2 sends the S-TAI of the VMR to the AMFs that have established a connection with it. The AMFs that have established a connection with donor gNB1 include UE AMF2 and VMR AMF2. Therefore, it can be understood that donor gNB2 sends the S-TAI of the VMR to both the UE AMF2 network element and the VMR AMF2 network element. The S-TAI of the VMR can be found in [reference needed]. Figure 5 The description will not be repeated here.

[0265] For example, the donor gNB2 can send the VMR S-TAI to the UE AMF2 network element and the VMR AMF2 network element through configuration update message 2. That is, configuration update message 2 includes the VMR S-TAI.

[0266] Optionally, in one possible implementation, the configuration update message 2 includes the S-TAI of the VMR and VMR indication information. The VMR indication information is used to indicate to the UE AMF2 network element and the VMR AMF2 network element that the S-TAI is specific tracking area information for the VMR. For example, the donor gNB2 uses configuration update message 2 ( Ran configuration update2 It informs all AMFs connected to donorgNB2 (including UE AMF2 and VMR AMF2) that there is a VMR within its jurisdiction and the tracking area information (S-TAI) of that VMR.

[0267] Optionally, in one possible implementation, the configuration update message 2 may only contain the S-TAI information of the VMR, i.e., it may not contain VMR indication information. This S-TAI includes specific information that allows the UE AMF2 network element and the VMR AMF2 network element to identify that the S-TAI is specific tracking area information (S-TAI) specific to the VMR. Alternatively, in another possible implementation, the network side (CN) defines a list of TAIs specific to the VMR. The UE AMF2 network element and the VMR AMF2 network element can then identify that the S-TAI belongs to this TAI list, thus recognizing that the S-TAI is specific tracking area information (S-TAI) specific to the VMR.

[0268] S870, the donor gNB1 sends configuration update message 3 to VMR AMF1 and UE AMF1, and accordingly, VMR AMF1 and UE AMF1 receive the configuration update message 3 sent by the donor gNB1.

[0269] For example, configuration update message 3 instructs all AMFs (UE AMF1 and VMRAMF1) connected to the donor gNB1 to delete the S-TAI. Alternatively, configuration update message 3 can be described as instructing all AMFs connected to the donor gNB1 to delete the association between the S-TAI and the donor gNB1 or CU1 within the donor gNB1. In this case, VMR AMF1 and UE AMF1, based on the received configuration update message 3 (which contains the identifier of the donor gNB1, such as gNB ID1), delete the association between the VMR's S-TAI and the donor gNB1. This can be understood as the donor gNB1 informing all AMFs connected to it that a VMR with an S-TAI has left its jurisdiction. Therefore, all AMFs connected to the donor gNB1 (UE AMF1 and VMR AMF1) will not seek out the donor gNB1 in subsequent processing of the VMR and UE corresponding to this S-TAI.

[0270] In one possible implementation, the configuration update message 3 includes the identification information of the second network device (e.g., the donor gNB2 ID). For example, the donor gNB1 notifies all AMFs (e.g., UE AMF1, VMR AMF1) connected to it that the target network device for VMR handover is the donor gNB2.

[0271] It should be noted that step S870 can also be executed after step S840. This can be understood as the VMR switching from donor gNB1 to donor gNB2 in step S840 triggering the sending of configuration update message 3 from donor gNB1 to the UE AMF1 network element and VMRAMF1 network element in step S870. It should be understood that the execution order is not limited in this embodiment.

[0272] S880, UE AMF1 selects UE AMF2 connected to donor gNB2 to provide services to UE based on the identification information of the second network device included in the received configuration update message 3.

[0273] It should be noted that before S880, the donor gNB2 interacts with all connected AMF network elements, including UE AMF2 mentioned above. However, it is important to note that before S880, it is not determined which specific AMF will replace UE AMF1 to provide services to the UE; that is, before S880, it is not determined which AMF2 will provide services to the UE. However, because UE AMF2 has established a connection with the donor gNB2, the AMF that is subsequently determined for the UE is included in the VMR S-TAI received by the donor gNB2 in step S860.

[0274] It should be understood that this application may also use other messages / information to indicate the deletion of the association between donor gNB1 and S-TAI information. Configuration update message 3 is only an example, and this application embodiment does not limit this.

[0275] S890, UE AMF1 and UE AMF2 perform context migration.

[0276] In one possible implementation, UE AMF 1 via Namf_Communication_Create UE Context The service requests UE AMF 2 to establish a UE context, where the UE context contains indication information that the UE is being served by VMR. Specifically, this indication information can be a direct indication identifier.

[0277] As an example, if the indication information is set to "1" or "TRUE", it means that the UE is being served by VMR; if the indication information is set to "0" or "FALSE", it means that the UE is not being served by VMR.

[0278] As another example, when the network (CN) allocates TAIs, it designates specific TAIs as dedicated VMR TAIs. This can be understood as follows: when a TAI belongs to a specific S-TAI, it indicates that the S-TAI is VMR tracking area information, meaning the UE is being served by VMR. Therefore, the AMF network element can determine whether the UE is being served by VMR based on the UE's S-TAI.

[0279] Alternatively, in one possible implementation, UE AMF 1 instructs UE AMF 2 to... Namf_ Communication_UE Context Transfer The service obtains the UE context from UE AMF 1. The UE context contains indication information that the UE is being served by VMR. Furthermore, the indication information from UE AMF 1 to UE AMF 2 to obtain the UE context may also include the identification information of the target AMF (e.g., UE AMF 1).

[0280] It should be noted that this indication information can be a direct indication identifier. For example, if the indication identifier is set to "1" or "TRUE", it means that the UE is being served by VMR; if the indication identifier is set to "0" or "FALSE", it means that the UE is not being served by VMR.

[0281] It should also be noted that step S890 is triggered by step S870. That is, after UE AMF 1 receives the configuration update message 3 from step S870, it recognizes that donor gNB 1 no longer provides services for the VMR corresponding to S-TAI, and that donor gNB 2 will provide services for the VMR instead. Since UE AMF 1 and donor gNB 2 cannot be connected (perhaps for load balancing considerations), UE AMF 1 selects the target UE AMF, namely UE AMF 2, based on donor gNB 2 to provide services to the UE. Subsequently, since UE AMF 1 infers that the UE corresponding to S-TAI has moved out of its service range, UE AMF 1 needs to migrate the context of the corresponding UE to UE AMF 2.

[0282] S8100, UE AMF 2 requests SMF to update the corresponding SM context.

[0283] For example, UE AMF 2 requests the corresponding SMF network element to update the SM context of the PDU session based on the PDU session identifier and SMF information in the context information in S890, and the SMF replaces UE AMF 1 with UE AMF 2.

[0284] S8110, UE AMF 2 assigns a globally unique temporary identifier (5G-GUTI) to the UE, initiates a 5G-GUTI update process, and registers it with UDM.

[0285] In the technical solution of this application embodiment, when a VMR accesses donor gNB1, the VMR AMF and UE AMF1 connected to donor gNB1 store the S-TAI of the VMR and the association relationship with donor gNB1. When the VMR switches from donor gNB1 to donor gNB2, VMR AMF1 and UE AMF1 delete the previously stored S-TAI of the VMR and the association relationship with donor gNB1, and obtain the identification information (ID) of donor gNB2 from donor gNB1. Through this technical solution, the network side can promptly know that the network device associated with the VMR has changed to donor gNB2. Therefore, when the network side needs to page the VMR and / or the UE serving the VMR, it can accurately locate the donor gNB2 associated with the VMR. This avoids the situation where the network side instructs other network devices (such as donor gNB1) to send paging messages when paging the VMR and / or the UE serving the VMR. This enables the network side to perform more accurate mobility management of the UE and avoids wasting resources.

[0286] Figure 9 This is a schematic flowchart of a communication method 900 provided in an embodiment of this application. It should be noted that method 900 mainly corresponds to scenario two described above, namely, during the VMR's handover from donor gNB1 to donor gNB2, the access and mobility management function (AMF) network elements are changed. Specifically, the AMF network elements (e.g., UE AMF1, VMRAMF1) are connected to donor gNB1, and the AMF network elements (e.g., UE AMF2, VMR AMF2) are connected to donor gNB2. UE AMF1 and VMR AMF1 can be the same AMF, and UE AMF2 and VMR AMF2 can be the same AMF (i.e., interaction between the two AMFs can be achieved through internal interaction), or they can be different AMFs. The following description assumes that UE AMF and VMR AMF are different AMFs. This method includes at least the following steps.

[0287] It should be noted that, in this embodiment of the application, the UE providing the VMR service is an idle UE.

[0288] The S910 VMR registers with the network (CN) and establishes a PDU session.

[0289] It should be noted that S910 is similar to S810, but for the sake of simplicity, this application will not elaborate further.

[0290] S920, the donor gNB1 sends the S-TAI and VMR identification information (e.g., VMR ID1) of the VMR to the UE AMF1 network element and the VMR AMF1 network element. Correspondingly, the UE AMF1 network element and the VMR AMF1 network element receive the S-TAI and VMR identification information (e.g., VMR ID1) of the VMR.

[0291] For example, since the current VMR communicates through the donor gNB1, the donor gNB1 sends the VMR's S-TAI to the AMFs that have established a connection with it. The AMFs that have established a connection with the donor gNB1 include UE AMF1 and VMR AMF1. Therefore, it can be understood that the donor gNB1 sends the VMR's S-TAI and VMR identification information (e.g., VMR ID1) to both the UE AMF1 and VMR AMF1 network elements. The VMR's S-TAI can be found at [reference needed]. Figure 5 The description will not be repeated here.

[0292] For example, the donor gNB1 can send the S-TAI and VMR identification information (e.g., VMR ID1) of the VMR to the UE AMF1 network element and the VMR AMF1 network element through configuration update message 1. That is, configuration update message 1 includes the S-TAI and VMR identification information (e.g., VMR ID1) of the VMR.

[0293] Optionally, in one possible implementation, the configuration update message 1 includes the S-TAI of the VMR, VMR indication information, and VMR identification information (e.g., VMR ID1). The VMR indication information is used to indicate to the UE AMF1 network element and the VMR AMF1 network element that the S-TAI is specific tracking area information for the VMR. The donor gNB1 uses configuration update message 1 ( Ran configuration update1 It informs all AMFs connected to donor gNB1 (including UE AMF1 and VMR AMF1) that there is a VMR within its jurisdiction and the tracking area information (S-TAI) of that VMR.

[0294] Optionally, in one possible implementation, the configuration update message 1 may only contain the VMR's S-TAI information and VMR identification information (e.g., VMR ID1), i.e., it may not contain VMR indication information. The S-TAI includes specific information that allows the UE AMF1 network element and the VMR AMF1 network element to identify that the S-TAI is specific tracking area information (S-TAI) specific to the VMR. Alternatively, in another possible implementation, the network side (CN) defines a list of TAIs specific to the VMR. The UE AMF1 network element and the VMR AMF1 network element can then identify that the S-TAI belongs to this TAI list, thus recognizing that the S-TAI is specific tracking area information (S-TAI) specific to the VMR.

[0295] It should be noted that during the VMR's movement, the tracking area information (S-TAI) broadcast by the VMR to the UE it serves remains constant. In other words, even if the VMR switches from donor gNB1 to donor gNB2, the VMR's tracking area information (S-TAI) remains unchanged.

[0296] S930, VMR AMF1 registers the association between donor gNB1 and S-TAI with UDR, and correspondingly, UDR stores the association between donor gNB1 and S-TAI.

[0297] For example, VMR AMF1 determines that it serves this VMR based on the VMR identification information (e.g., VMR ID1) in S920, and thus registers the association between donor gNB1 and S-TAI with the UDR. This registration message includes the donor gNB1 ID (or RAN1 ID) and S-TAI. Other AMFs that receive the message in step S920 determine that they do not serve this VMR and do not need to register the association with the UDR.

[0298] It should be noted that the VMR ID may not be included in the registration message mentioned above.

[0299] It should be understood that the association can be the association between donor gNB1 and VMR's S-TAI, or the association between CU1 located in donor gNB1 and VMR's S-TAI. This application embodiment does not impose any limitations on this.

[0300] In S940, the UE registers with the network via VMR. UE AMF1 performs access and mobility management for the VMR. If the UE's location information is within the area specified by the S-TAI information, UE AMF1 determines that the UE is being served by the VMR. In this case, UE AMF1 assigns the S-TAI as part of the UE's TAI List. Conversely, if the UE's location information is not within the area specified by the S-TAI information, UE AMF1 determines that the UE is not being served by the VMR. Therefore, when assigning a TAI List to a UE not served by that VMR, UE AMF1 will not include the S-TAI in that TAI List.

[0301] S950, VMR switched from donor gNB1 to donor gNB2.

[0302] S960, VMR will register the S-TAI obtained from the OAM system into the donor gNB2.

[0303] It should be noted that S940-S960 are similar to S840-S860, but for the sake of simplicity, this application will not elaborate further.

[0304] S970, the donor gNB2 sends the S-TAI and VMR identification information (e.g., VMR ID1) of the VMR to the UE AMF2 network element and the VMR AMF2 network element. Correspondingly, the UE AMF2 network element and the VMR AMF2 network element receive the S-TAI and VMR identification information (e.g., VMR ID1) of the VMR.

[0305] For example, since the current VMR communicates through the donor gNB2, the donor gNB2 sends the VMR's S-TAI to the AMFs that have established a connection with it. The AMFs that have established a connection with the donor gNB2 include UE AMF2 and VMR AMF2. Therefore, it can be understood that the donor gNB2 sends the VMR's S-TAI and VMR identification information (e.g., VMR ID1) to both the UE AMF2 and VMR AMF2 network elements. The VMR's S-TAI can be found at [reference needed]. Figure 5 The description will not be repeated here.

[0306] For example, the donor gNB2 can send the S-TAI and VMR identification information (e.g., VMR ID1) of the VMR to the UE AMF2 network element and the VMR AMF2 network element through configuration update message 2. That is, configuration update message 2 includes the S-TAI and VMR identification information (e.g., VMR ID1) of the VMR.

[0307] Optionally, in one possible implementation, the configuration update message 2 includes the VMR's S-TAI, VMR indication information, and VMR identification information (e.g., VMR ID1). The VMR indication information is used to indicate to the UE AMF2 network element and the VMR AMF2 network element that the S-TAI is specific tracking area information for the VMR. The donor gNB2 informs all AMFs connected to the donor gNB2 (including UE AMF2 and VMR AMF2) via configuration update message 2 that there is a VMR within its jurisdiction and the tracking area information (S-TAI) of that VMR.

[0308] Optionally, in one possible implementation, the configuration update message 2 may only contain the VMR's S-TAI information and VMR identification information (e.g., VMR ID1), i.e., it may not contain VMR indication information. The S-TAI includes specific information that allows the UE AMF2 network element and the VMR AMF2 network element to identify that the S-TAI is specific tracking area information (S-TAI) belonging to the VMR. Alternatively, in another possible implementation, the network side (CN) defines a list of TAIs specific to the VMR. The UE AMF2 network element and the VMR AMF2 network element can then identify that the S-TAI belongs to this TAI list, thus recognizing that the S-TAI is specific tracking area information (S-TAI) belonging to the VMR.

[0309] S980, VMR AMF2 registers the association between donor gNB2 and S-TAI with UDR, and correspondingly, UDR stores the association between donor gNB2 and S-TAI.

[0310] For example, VMR AMF2 determines that it serves a VMR based on the VMR identification information (e.g., VMR ID1) in S970, and thus registers the association between donor gNB2 and S-TAI with the UDR. This registration message includes the donorgNB2 ID (or RAN2 ID) and S-TAI. Other AMFs that receive the message in step S970 determine that they do not serve this VMR and do not need to register the association with the UDR.

[0311] It should be noted that the above registration message may also omit VMR identification information (e.g., VMR ID1).

[0312] It should be understood that the association can be the association between donor gNB2 and VMR's S-TAI, or the association between CU2 located in donor gNB2 and VMR's S-TAI. This application embodiment does not limit this.

[0313] S990, the donor gNB1 sends configuration update message 3 to VMR AMF1 and UE AMF1, and accordingly, VMR AMF1 and UE AMF1 receive configuration update message 3 sent by the donor gNB1.

[0314] For example, configuration update message 3 instructs all AMFs (UE AMF1 and VMRAMF1) connected to the donor gNB1 to delete the S-TAI. Alternatively, configuration update message 3 can be described as instructing all AMFs connected to the donor gNB1 to delete the association between the S-TAI and the donor gNB1 or CU1 within the donor gNB1. In this case, VMR AMF1 and UE AMF1, based on the received configuration update message 3 (which contains the identifier of the donor gNB1, such as gNB ID1), delete the association between the VMR's S-TAI and the donor gNB1. This can be understood as the donor gNB1 informing all AMFs connected to it that a VMR with an S-TAI has left its jurisdiction. Therefore, all AMFs connected to the donor gNB1 (UE AMF1 and VMR AMF1) will not seek out the donor gNB1 in subsequent processing of the VMR and UE corresponding to this S-TAI.

[0315] It should be noted that step S990 can also be executed after step S950. This can be understood as the VMR switching from donor gNB1 to donor gNB2 in step S950 triggering the sending of configuration update message 3 from donor gNB1 to the UE AMF1 and VMRAMF1 network elements in step S990. It should be understood that the execution order is not limited in this embodiment.

[0316] In S9100, VMR AMF1 sends a request message to UDR, requesting UDR to delete the association between donor gNB1 and S-TAI information. Accordingly, UDR receives the request message and deletes the association between donor gNB1 and S-TAI information based on the request message.

[0317] It should be noted that step S990 can be used to trigger step S9100. In step S990, the donor gNB1 sends a configuration update message 3 to VMRAMF1 and UE AMF1. The configuration update message 3 is used to indicate the deletion of the association between the donor gNB1 and the S-TAI information. Optionally, in one possible implementation, the configuration update message 3 may include VMR identification information (e.g., VMR ID1). VMR AMF1 determines that it serves a VMR based on the VMR identification information (e.g., VMR ID1), thereby triggering VMR AMF1 to send a request message to the UDR, requesting the UDR to delete the association between the donor gNB1 and the S-TAI information.

[0318] It should be understood that this application may also use other messages / information to indicate the deletion of the association between donor gNB1 and S-TAI information. Configuration update message 3 is only an example, and this application embodiment does not limit this.

[0319] It should be understood that step S9100 can also be an optional step, meaning that VMR AMF1 may not send a request message to the UDR to request the UDR to delete the association between donor gNB1 and S-TAI information. In one possible implementation, S980 can be used to trigger the UDR to delete the association between donor gNB1 and S-TAI information. In other words, when VMR AMF2 registers the association between donor gNB2 and S-TAI with the UDR, then the UDR will delete the association between donor gNB1 and S-TAI information.

[0320] In step S9110, UE AMF1 sends a query message to UDR, which is used to query the network device associated with the S-TAI information. Correspondingly, UDR receives the query message.

[0321] For example, UE AMF1 sends a query message to UDR, and UDR determines that the network device associated with the tracking area information (S-TAI) of VMR is donor gNB2 based on the S-TAI carried in the received query message.

[0322] For example, UE AMF1 uses the UDR's general query service. UE AMF1 carries the query target type as gNB (or RAN) and the query index as S-TAI in the query message. UDR then determines that the network device associated with the VMR's tracking area information (S-TAI) is the donor gNB2.

[0323] It should be noted that step S9110 can be triggered by step S990. That is, after UE AMF1 deletes the association between the VMR's tracking area information and the donor gNB1 according to the received configuration update message 3, it can determine that the VMR corresponding to the S-TAI has left the donor gNB1. At this time, UE AMF1 needs to know the new network device associated with the VMR's tracking area information. Therefore, UE AMF1 will send a query message to UDR to query which new network device is associated with the VMR's tracking area information.

[0324] S9120, the UDR sends a response message to the UE AMF1, which includes the identification information of the second network device (e.g., the donor gNB2 ID). Accordingly, the UE AMF1 receives the response message sent by the UDR.

[0325] S9130, UE AMF 1 determines that the network device associated with S-TAI is donorgNB2 based on the received response message, and further selects UE AMF2 connected to donor gNB2 to provide services to the UE.

[0326] After the UDR determines that the network device associated with the VMR's Tracking Area Information (S-TAI) is the donor gNB2, the UDR sends a response message to the UE AMF1. The response message contains the identification information of the donor gNB2 (such as the donor gNB2 ID or RAN2 ID). In other words, the UDR informs the UE AMF1 that the network device associated with the VMR's Tracking Area Information (S-TAI) is the donor gNB2.

[0327] It should be noted that before S9130, the donor gNB2 interacts with all connected AMF network elements, including UE AMF2 mentioned above. However, it should be noted that before S9130, it was not determined which specific AMF would provide services to the UE to replace UE AMF1. That is, before S9130, it was not determined that UE AMF2 would provide services to the UE.

[0328] In S9140, UE AMF1 and UE AMF2 perform context migration. It should be noted that S9140 is similar to S890, but for simplicity, it will not be described in detail here.

[0329] It should also be noted that step S9140 can be triggered by steps S990 and 9120. That is, after UE AMF 1 receives the configuration update message 3 from step S990, it identifies that donor gNB 1 no longer provides services for the VMR corresponding to S-TAI. Based on the identifier information of donor gNB2 contained in the response message in step 9120, UE AMF 1 determines that donor gNB2 should provide services for VMR at this time. Since UE AMF 1 and donor gNB2 cannot be connected (perhaps for load balancing considerations), donor gNB2 selects the target UE AMF, namely UE AMF 2, to provide services for the UE. Subsequently, since UE AMF 1 infers that the UE corresponding to S-TAI has moved out of its service range, UE AMF 1 needs to migrate the context of the corresponding UE to UE AMF 2.

[0330] S9150, UE AMF 2 requests SMF to update the corresponding SM context.

[0331] For example, UE AMF 2 requests an update to the SM context of the PDU session from the corresponding SMF network element based on the PDU session identifier and SMF information in the context information in S9140. The SMF then replaces UE AMF 1 with UE AMF 2.

[0332] S9160, UE AMF 2 assigns 5G-GUTI to UE, initiates 5G-GUTI update process, and registers with UDM.

[0333] In the technical solution of this application embodiment, when the VMR switches from donor gNB1 to donor gNB2, the AMF (UE AMF2, VMR AMF2) connected to donor gNB2 registers the association between donor gNB2 and S-TAI with the UDR. However, the VMR AMF1 connected to donor gNB1 requests the UDR to delete the saved association between donor gNB1 and S-TAI. Subsequently, the UE AMF1 connected to donor gNB1 will learn from the UDR that the S-TAI is associated with donor gNB2. This technical solution enables the network side to promptly learn that the network device associated with the VMR's S-TAI has been changed to donor gNB2. Consequently, when the network side needs to page a UE serving VMR and / or VMR services, it can accurately locate the donor gNB2 associated with VMR. This prevents the network side from instructing other network devices (such as donor gNB1) to send paging messages when paging a UE serving VMR and / or VMR services. As a result, the network side can more accurately manage UE mobility and avoid wasting resources.

[0334] The various embodiments described herein can be independent solutions or combinations thereof based on their inherent logic, and all such solutions fall within the protection scope of this application.

[0335] It is understood that the methods and operations implemented by each device or network element in the above method embodiments can also be implemented by components (such as chips or circuits) of the corresponding device or network element.

[0336] The foregoing mainly describes the solutions provided by the embodiments of this application from the perspective of various interactions. It is understood that each network element, such as a transmitting or receiving device, includes corresponding hardware structures and / or software modules to perform the aforementioned functions. Those skilled in the art should recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0337] This application embodiment can divide the transmitting or receiving device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or software. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the division of functional modules according to each function as an example.

[0338] It should be understood that the specific examples in the embodiments of this application are only for the purpose of helping those skilled in the art to better understand the embodiments of this application, and are not intended to limit the scope of the embodiments of this application.

[0339] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0340] The above, combined with Figures 5 to 9 The methods provided in the embodiments of this application are described in detail below. Figures 10 to 13 The apparatus provided in the embodiments of this application is described in detail. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, for content not described in detail, please refer to the method embodiments above. For the sake of brevity, it will not be repeated here.

[0341] Figure 10 A schematic block diagram of an access and mobility management function network element 1000 according to an embodiment of this application is shown. It should be understood that the access and mobility management function network element 1000 includes a receiving unit 1010, a processing unit 1020, and a transmitting unit 1030.

[0342] The receiving unit 1010 is used to receive tracking area information of the first device from the first network device; the processing unit 1020 is used to save the tracking area information of the first device and the association relationship of the first network device; when the second network device serves the first device, the processing unit 1020 deletes the tracking area information of the first device and the association relationship of the first network device.

[0343] In one possible implementation, the access and mobility management function network element connects the first network device and the second network device. The receiving unit 1010 is further configured to: receive the tracking area information of the first device from the second network device; the processing unit 1020 is further configured to: save the tracking area information of the first device and the association relationship between the second network device.

[0344] In one possible implementation, the processing unit 1020 is specifically used to: delete the association between the tracking area information of the first device and the first network device based on the tracking area information of the first device received from the second network device.

[0345] In one possible implementation, the receiving unit 1010 is further configured to: receive first indication information from the first network device; the processing unit 1020 is specifically configured to: delete the tracking area information of the first device and the association relationship of the first network device according to the first indication information.

[0346] In one possible implementation, the first indication information includes the identification information of the second network device.

[0347] In one possible implementation, the access and mobility management function network element is connected to the first network device. The access and mobility management function network element further includes a sending unit 1030, which is used to send first registration information to a unified database network element. The first registration information is used to register the tracking area information of the first device and the association relationship of the first network device with the unified database network element.

[0348] In one possible implementation, the sending unit 1030 is further configured to: send a first request message to the unified database network element, the first request message being used to request the unified database network element to delete the tracking area information of the first device and the association relationship of the first network device.

[0349] In one possible implementation, the sending unit 1030 is further configured to: send first query information to the unified database network element, the first query information being used to query the unified database network element for network devices associated with the tracking area information of the first device; the receiving unit is further configured to: receive first response information sent by the unified database network element, the first response information including the identification information of the second network device.

[0350] Figure 11 A schematic block diagram of an access and mobility management function network element 1100 according to an embodiment of this application is shown. It should be understood that the access and mobility management function network element 1100 includes a receiving unit 1110, a processing unit 1120, and a transmitting unit 1130.

[0351] The receiving unit 1110 is used to receive tracking area information of the first device from the second network device; the processing unit 1120 is used to store the tracking area information of the first device and the association relationship of the second network device; the sending unit 1130 is used to send second registration information to the unified database network element, the second registration information being used to register the tracking area information of the first device and the association relationship of the second network device with the unified database network element.

[0352] Figure 12 A schematic block diagram of a network device 1200 according to an embodiment of this application is shown. It should be understood that the network device 1200 includes a receiving unit 1210 and a transmitting unit 1220.

[0353] The receiving unit 1210 is used to obtain the tracking area information of the first device from the first device; the sending unit 1220 is used to send the tracking area information of the first device to the connected access and mobility management function network element.

[0354] In one possible implementation, the sending unit 1220 is further configured to: send first indication information to the connected access and mobility management function network element, the first indication information being used to indicate the deletion of the tracking area information of the first device and the association relationship of the network device.

[0355] Figure 13 A schematic block diagram of a unified database network element 1300 according to an embodiment of this application is shown. It should be understood that the unified database network element 1300 includes a receiving unit 1310, a processing unit 1320, and a sending unit 1330.

[0356] The receiving unit 1310 is configured to receive second registration information from the first access and mobility management function (AM) network element, the second registration information being used to register the tracking area information of the first device and the association relationship of the second network device; the processing unit 1320 is configured to save the tracking area information of the first device and the association relationship of the second network device according to the second registration information. The receiving unit 1310 is further configured to receive first query information from the second AM network element, the first query information being used to query the network device associated with the tracking area information of the first device; the sending unit 1330 is configured to send first response information to the second AM network element, the first response information including the identification information of the second network device.

[0357] In one possible implementation, the receiving unit 1310 is further configured to: receive first registration information from the first access and mobility management function network element, the first registration information being used to register the tracking area information of the first device and the association relationship of the first network device; the processing unit 1320 is further configured to: save the tracking area information of the first device and the association relationship of the first network device according to the first registration information.

[0358] In one possible implementation, the receiving unit 1310 is further configured to: receive first request information from the first access and mobility management function network element, the first request information being used to request the deletion of the tracking area information of the first device and the association relationship of the first network device.

[0359] It should be understood that the division of units in the above communication device is merely a logical functional division. In actual implementation, all or part of them can be integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the communication device can be implemented entirely through software calls from processing elements; all can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, and others in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the communication device. Alternatively, it can be stored as a program in memory, called and executed by a processing element of the communication device. Moreover, these units can be integrated together or implemented independently. The processing element mentioned here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0360] In one example, a unit in any of the above communication devices or network elements can be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. As another example, when a unit in a communication device or network element can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling programs. Furthermore, these units can be integrated together and implemented as a system-on-a-chip (SOC).

[0361] refer to Figure 14 This is a schematic diagram of a communication device provided in an embodiment of this application, used to implement the operations of the access and mobility management function network elements, network devices, and unified database network elements in the above embodiments. Figure 14As shown, the communication device includes a processor 1410 and an interface 1430, with the processor 1410 coupled to the interface 1430. The interface 1430 is used to enable communication with other devices. The interface 1430 can be a transceiver or an input / output interface. The interface 1430 can be, for example, an interface circuit. Optionally, the communication device also includes a memory 1420 for storing instructions executed by the processor 1410, or storing input data required by the processor 1410 to execute instructions, or storing data generated after the processor 1410 executes instructions.

[0362] The methods executed by the access and mobility management function network element, network device, and unified database network element in the above embodiments can be implemented by the processor 1410 calling a program stored in memory (which can be memory 1220 in the access and mobility management function network element, network device, and unified database network element, or external memory). That is, the access and mobility management function network element, network device, and unified database network element can include the processor 1410, which executes the methods executed by the access and mobility management function network element, network device, and unified database network element in the above method embodiments by calling a program in memory. The processor here can be an integrated circuit with signal processing capabilities, such as a CPU. The access and mobility management function network element, network device, and unified database network element can be implemented by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or one or more microprocessors (DSPs), or one or more FPGAs, or a combination of at least two of these integrated circuit forms. Alternatively, the above implementation methods can be combined.

[0363] Specifically, Figures 10 to 13 The functions / implementation processes of each unit can be accessed through... Figure 14 The processor 1410 in the communication device 1400 shown calls computer-executable instructions stored in memory 1420 to implement the communication. Alternatively, Figures 10 to 13 The function / implementation process of the processing unit in the middle can be obtained through Figure 14 The processor 1410 in the communication device 1400 shown calls computer execution instructions stored in the memory 1420 to implement this. Figures 10 to 13 The function / implementation process of the receiving unit or transmitting unit in the middle can be obtained through Figure 14 This is implemented using interface 1430 in the communication device 1400 shown.

[0364] It should be understood that the processing unit in the above-described apparatus includes a processor coupled to a memory for storing computer programs or instructions and / or data, and the processor for executing the computer programs or instructions and / or data stored in the memory, so that the method in the above-described method embodiments is executed.

[0365] It should also be understood that the division of units in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, while others are implemented in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, and its function can be called and executed by a processing element within the device. Here, the processing element can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0366] This application also provides a communication system, which includes: the aforementioned access and mobility management function network element, network equipment, and unified database network element.

[0367] This application also provides a computer-readable medium for storing computer program code, the computer program including instructions for executing the communication method described in the embodiments of this application. The readable medium may be a read-only memory (ROM) or a random access memory (RAM), and this application does not impose any limitations on this.

[0368] This application also provides a computer program product including instructions that, when executed, cause access and mobility management function network elements, network devices, and unified database network elements to perform operations corresponding to the methods described above.

[0369] This application also provides a system-on-a-chip (SoC) comprising a processing unit and a communication unit. The processing unit may be, for example, a processor, and the communication unit may be, for example, an input / output interface, pins, or circuitry. The processing unit can execute computer instructions to cause the chip within the communication device to perform any of the communication methods provided in the embodiments of this application.

[0370] Optionally, the computer instructions are stored in a storage unit.

[0371] Optionally, the storage unit can be an internal storage unit within the chip, such as a register or cache. Alternatively, it can be an external storage unit located within the terminal, such as ROM or other types of static storage devices capable of storing static information and instructions, like RAM. The processor mentioned above can be a CPU, microprocessor, ASIC, or one or more integrated circuits used to control the execution of a program for transmitting the aforementioned feedback information. The processing unit and the storage unit can be decoupled and located on different physical devices, connected via wired or wireless means to implement their respective functions, thus supporting the system chip in implementing the various functions described in the above embodiments. Alternatively, the processing unit and the memory can also be coupled to the same device.

[0372] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be RAM, which is used as an external cache. RAM has various different types, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM).

[0373] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0374] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0375] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0376] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0377] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0378] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0379] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: The access and mobility management function network element receives tracking area information from the first network device; The access and mobility management function network element stores the tracking area information of the first device and the association relationship of the first network device; When the second network device serves the first device, the access and mobility management function network element deletes the tracking area information of the first device and the association relationship between the first network device and the first network device.

2. The method according to claim 1, characterized in that, The access and mobility management function network element connects the first network device and the second network device, and the method further includes: The access and mobility management function network element receives tracking area information from the first device from the second network device; The access and mobility management function network element stores the tracking area information of the first device and the association relationship of the second network device.

3. The method according to claim 2, characterized in that, The access and mobility management function network element deletes the tracking area information of the first device and the association relationship of the first network device, including: The access and mobility management function network element, in response to the tracking area information of the first device received from the second network device, deletes the association between the tracking area information of the first device and the first network device.

4. The method according to claim 1 or 2, characterized in that, The method further includes: The access and mobility management function network element receives first indication information from the first network device; The access and mobility management function network element deletes the tracking area information of the first device and the association relationship of the first network device, including: The access and mobility management function network element deletes the tracking area information of the first device and the association relationship of the first network device according to the first instruction information.

5. The method according to claim 4, characterized in that, The first indication information includes the identification information of the second network device.

6. The method according to claim 1, characterized in that, The access and mobility management function network element is connected to the first network device, and the method further includes: The access and mobility management function network element sends first registration information to the unified database network element. The first registration information is used to register the tracking area information of the first device and the association relationship of the first network device with the unified database network element.

7. The method according to claim 6, characterized in that, The method further includes: The access and mobility management function network element sends a first request message to the unified database network element. The first request message is used to request the unified database network element to delete the tracking area information of the first device and the association relationship of the first network device.

8. The method according to claim 6 or 7, characterized in that, The method further includes: The access and mobility management function network element sends a first query information to the unified database network element. The first query information is used to query the unified database network element for network devices associated with the tracking area information of the first device. The access and mobility management function network element receives a first response information sent by the unified database network element, the first response information including the identification information of the second network device.

9. The method according to any one of claims 1 to 3, characterized in that, The first device includes a vehicle-mounted relay device (VMR).

10. The method according to any one of claims 1 to 3, characterized in that, The tracking area information of the first device does not change with the access location of the first device.

11. A communication method, characterized in that, include: The network device obtains the tracking area information of the first device from the first device; The network device sends the tracking area information of the first device to the connected access and mobility management function network element, so that the access and mobility management function network element can save the association between the tracking area information of the network device and the first device.

12. The method according to claim 11, characterized in that, The method further includes: The network device sends a first instruction to the connected access and mobility management function network element, the first instruction being used to instruct the deletion of the tracking area information of the first device and the association relationship of the network device.

13. The method according to claim 11 or 12, characterized in that, The first device includes a vehicle-mounted relay device (VMR).

14. The method according to claim 11 or 12, characterized in that, The tracking area information of the first device does not change with the access location of the first device.

15. A communication method, characterized in that, include: The unified database network element receives second registration information from the first access and mobility management function network element. The second registration information is used to register the tracking area information of the first device and the association relationship between the second network device. The unified database network element saves the tracking area information of the first device and the association relationship of the second network device according to the second registration information; The unified database network element receives first query information from the second access and mobility management function network element. The first query information is used to query the network devices associated with the tracking area information of the first device. The unified database network element sends a first response information to the second access and mobility management function network element, the first response information including the identification information of the second network device; The method further includes: The unified database network element receives first registration information from the first access and mobility management function network element. The first registration information is used to register the tracking area information of the first device and the association relationship of the first network device, so that the first access and mobility management function network element can save the tracking area information of the first device and the association relationship of the first network device. Based on the first registration information, the tracking area information of the first device and the association relationship of the first network device are saved.

16. The method according to claim 15, characterized in that, The method further includes: The unified database network element receives a first request information from the first access and mobility management function network element. The first request information is used to request the deletion of the tracking area information of the first device and the association relationship of the first network device.

17. The method according to claim 15 or 16, characterized in that, The first device includes a vehicle-mounted relay device (VMR).

18. The method according to claim 15 or 16, characterized in that, The tracking area information of the first device does not change with the access location of the first device.

19. A network element for access and mobility management functions, characterized in that, include: A receiving unit is configured to receive tracking area information of a first device from a first network device; The processing unit is used to save the tracking area information of the first device and the association relationship of the first network device; When the second network device serves the first device, the processing unit deletes the tracking area information of the first device and the association relationship between the first network device and the first device.

20. The network element for access and mobility management functions according to claim 19, characterized in that, The access and mobility management function network element connects the first network device and the second network device. The receiving unit is further configured to: receive tracking area information of the first device from the second network device; The processing unit is also used to: save the tracking area information of the first device and the association relationship of the second network device.

21. The access and mobility management function network element according to claim 20, characterized in that, The processing unit is specifically used for: In response to the tracking area information of the first device received from the second network device, the association between the tracking area information of the first device and the first network device is deleted.

22. The access and mobility management function network element according to claim 19 or 20, characterized in that, The receiving unit is further configured to: receive first indication information from the first network device; The processing unit is specifically used to: delete the tracking area information of the first device and the association relationship of the first network device according to the first instruction information.

23. The network element for access and mobility management functions according to claim 22, characterized in that, The first indication information includes the identification information of the second network device.

24. The network element for access and mobility management functions according to claim 19, characterized in that, The access and mobility management function network element is connected to the first network device, and the access and mobility management function network element further includes: The sending unit is used to send first registration information to the unified database network element. The first registration information is used to register the tracking area information of the first device and the association relationship of the first network device with the unified database network element.

25. The network element for access and mobility management functions according to claim 24, characterized in that, The sending unit is further configured to: send a first request message to the unified database network element, the first request message being used to request the unified database network element to delete the tracking area information of the first device and the association relationship of the first network device.

26. The access and mobility management function network element according to claim 24 or 25, characterized in that, The sending unit is further configured to: send first query information to the unified database network element, wherein the first query information is used to query the unified database network element for network devices associated with the tracking area information of the first device; The receiving unit is further configured to: receive first response information sent by the unified database network element, wherein the first response information includes the identification information of the second network device.

27. A network device, characterized in that, include: A receiving unit is configured to obtain tracking area information of the first device from the first device; The sending unit is configured to send the tracking area information of the first device to the connected access and mobility management function network element, wherein the access and mobility management function network element stores the association relationship between the tracking area information of the network device and the first device.

28. The network device according to claim 27, characterized in that, The sending unit is further configured to: send first indication information to the connected access and mobility management function network element, the first indication information being used to indicate the deletion of the tracking area information of the first device and the association relationship of the network device.

29. A unified database network element, characterized in that, include: The receiving unit is configured to receive second registration information from the first access and mobility management function network element, wherein the second registration information is used to register the tracking area information of the first device and the association relationship between the second network device; The processing unit is configured to save the tracking area information of the first device and the association relationship between the second network device based on the second registration information; The receiving unit is further configured to receive first query information from the second access and mobility management function network element, wherein the first query information is used to query the network device associated with the tracking area information of the first device; The sending unit is configured to send first response information to the second access and mobility management function network element, wherein the first response information includes the identification information of the second network device.

30. The unified database network element according to claim 29, characterized in that, The receiving unit is further configured to: the unified database network element receive first registration information from the first access and mobility management function network element, wherein the first registration information is used to register the tracking area information of the first device and the association relationship of the first network device; The processing unit is further configured to: save the tracking area information of the first device and the association relationship of the first network device based on the first registration information.

31. The unified database network element according to claim 30, characterized in that, The receiving unit is further configured to: receive first request information received from the first access and mobility management function network element, wherein the first request information is used to request the deletion of the tracking area information of the first device and the association relationship of the first network device.

32. The unified database network element according to any one of claims 29 to 31, characterized in that, The first device includes a vehicle-mounted relay device (VMR).

33. The unified database network element according to any one of claims 29 to 31, characterized in that, The tracking area information of the first device does not change with the access location of the first device.

34. A communication device, characterized in that, This includes network elements for access and mobility management functions, network equipment, and unified database network elements. The access and mobility management function network element is used to perform the method as described in any one of claims 1 to 10; or, The network device is used to perform the method as described in any one of claims 11 to 14; or... The unified database network element is used to perform the method as described in any one of claims 15 to 18.

35. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores program instructions that, when executed, cause the access and mobility management function network element to perform the method as described in any one of claims 1 to 10; or, When the instruction is executed, it enables the network device to perform the method as described in any one of claims 11 to 14; or, When the instruction is executed, it enables the unified database network element to perform the method as described in any one of claims 15 to 18.

Images