WO2023138452A1

WO2023138452A1 - Communication method, apparatus, and system

Info

Publication number: WO2023138452A1
Application number: PCT/CN2023/071715
Authority: WO
Inventors: 赵鹏涛; 李岩; 朱方园
Original assignee: 华为技术有限公司
Priority date: 2022-01-19
Filing date: 2023-01-10
Publication date: 2023-07-27
Also published as: CN116506826A

Abstract

Provided in the embodiments of the present application is a communication method. The method comprises: an access and mobility management function network element receives, from a first network device, tracking area information of a first device; the access and mobility management function network element stores an association relationship between the tracking area information of the first device and the first network device; and when 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, wherein the first device may be a vehicle mounted relay (VMR). Therefore, according to the technical solution of the present application, a mobility management solution to the first device VMR is provided, so as to more accurately perform mobility management on a UE.

Description

Communication method, device and system

This application claims the priority of the Chinese patent application with the application number 202210057946.6 and the application name "Communication Method, Device and System" submitted to the China Patent Office on January 19, 2022, the entire contents of which are incorporated in this application by reference.

technical field

The embodiments of the present application relate to the communication field, and more specifically, a communication method, device, and system are designed.

Background technique

In order to meet the ultra-high capacity requirements of the 5th generation (5G) mobile communication system, high-frequency small cell networking has become the mainstream. The propagation characteristics of high-frequency carriers are poor, the attenuation is serious due to occlusion, and the coverage area is not wide, so a large number of densely deployed small stations are required. Correspondingly, the cost of providing optical fiber backhaul for these densely deployed small cells is high, and the construction is difficult. Therefore, an economical and convenient backhaul solution is required. In addition, from the perspective of wide coverage requirements, it is difficult and costly to deploy optical fibers to provide network coverage in some remote areas, and it is also necessary to design flexible and convenient access and backhaul solutions. Integrated access and backhaul (IAB) technology provides a way to solve the above problems.

Vehicle mounted relay (VMR) supports wireless relay-related functions. Compared with the existing IAB mechanism, VMR has mobility, and the existing IAB nodes are fixed relays on the ground, so the VMR in this application can also be understood as a mobile (mobile) IAB node. In the mobility scenario of VMR, the network side may not be able to obtain the corresponding relationship between the user equipment (user equipment, UE) and the base station, that is, the network side cannot perform mobility management on the UE more accurately.

Based on this, the present application proposes a mobility management solution for the first device VMR, so as to perform mobility management on the UE more accurately.

Contents of the invention

The embodiment of the present application proposes a mobility management solution for the first device VMR, so that the network side can more accurately manage the mobility of the UE.

In a first aspect, a communication method is provided, and the method includes: 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 tracking area information of the first device and an association relationship with the first network device; when a 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 with the first network device.

It should be understood that the first device may be a vehicle-mounted relay VMR, or may be a UE served by the VMR, which is not limited in this embodiment of the present application.

Based on the above technical solution, when the first device accesses 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 between the first network device. When the first device is handed over 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 deletes the previously saved tracking area information of the first device and the association relationship between the first network device, so that the network side can know in time that the network device associated with the first device has changed from the first device to the second network device, and then 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, and the network side will not page the first device and/or the service of the first device When the UE is connected to the UE, the network side instructs the first network device to send the paging message, so that the network side can perform mobility management on the UE more accurately and avoid waste of resources.

With reference to the first aspect, in some implementation manners of the first aspect, 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 the tracking area information of 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 an association relationship between the second network device. Based on the above technical solution, the network side can be made to know the network device associated with the first device in time, so that the network side can more accurately perform mobility management on the UE.

With reference to the first aspect, in some implementation manners of the first aspect, the access and mobility management function network element deleting the association relationship between the tracking area information of the first device and the first network device includes: the access and mobility management function network element responding to the tracking area information of the first device received from the second network device, deleting the association relationship between the tracking area information of the first device and the first network device. Based on the above technical solution, the network side can be made to know the network device associated with the first device in time, so that the network side can more accurately perform mobility management on the UE.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: the access and mobility management functional network element receiving first indication information from the first network device; the access and mobility management functional network element deleting the association relationship between the tracking area information of the first device and the first network device, including: the access and mobility management functional network element deleting the association relationship 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 be made to know the network device associated with the first device in time, so that the network side can more accurately perform mobility management on the UE.

With reference to the first aspect, in some implementation manners of the first aspect, the first indication information includes identification information of the second network device. Based on the above technical solution, the network side can be made to know the network device associated with the first device in time, so that the network side can more accurately perform mobility management on the UE.

With reference to the first aspect, in some implementation manners of the first aspect, the network element with the access and mobility management function is connected to the first network device, and the method further includes: the network element with the access and mobility management function sends first registration information to the unified database network element, and the first registration information is used to register with the unified database network element the tracking area information of the first device and the association relationship between the first network device. Based on the above technical solution, the network side can be made to know the network device associated with the first device in time, so that the network side can more accurately perform mobility management on the UE.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: the access and mobility management functional network element sending first request information to the unified database network element, where the first request information is used to request the unified database network element to delete the association relationship between the tracking area information of the first device and the first network device. Based on the above technical solution, the network side can be made to know the network device associated with the first device in time, so that the network side can more accurately perform mobility management on the UE.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: the access and mobility management function network element sends first query information to the unified database network element, and the first query information is used to query the unified database network element for a network device associated with the tracking area information of the first device; the access and mobility management function network element receives first response information sent by the unified database network element, and the first response information includes identification information of the second network device. Based on the above technical solution, the network side can be made to know the network device associated with the first device in time, so that the network side can more accurately perform mobility management on the UE.

With reference to the first aspect, in some implementation manners of the first aspect, the first device includes a vehicle-mounted relay device VMR.

With reference to the first aspect, in some implementation manners of the first aspect, the tracking area information of the first device does not change as the access location of the first device changes.

In a second aspect, a communication method is provided, and the method includes: an access and mobility management function network element receives tracking area information of a first device from a second network device; the access and mobility management function network element root stores the tracking area information of the first device and an association relationship between the second network device; the access and mobility management function network element sends second registration information to a unified database network element, and the second registration information is used to register with the unified database network element The tracking area information of the first device and the association relationship between the second network device.

Based on the above technical solution, when the first device is switched 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, so that the network side can know in time that the network device associated with the first device has changed from the first device to the second network device, and then 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, and the network side will not page the first device. And/or when the UE is served by the first device, the network side instructs the first network device to send a paging message, so that the network side can more accurately perform mobility management on the UE and avoid waste of resources.

With reference to the second aspect, in some implementation manners of the second aspect, the first device includes a vehicle-mounted relay device VMR.

With reference to the second aspect, in some implementation manners of the second aspect, the tracking area information of the first device does not change as the access location of the first device changes.

In a third aspect, a communication method is provided, and the method includes: a network device obtains tracking area information of the first device from a first device; the network device sends the tracking area information of the first device to a connected access and mobility management functional network element.

It should be noted that the network device may be the first network device or the second network device. When the first device accesses the first network device, the first network device sends the tracking area information of the first device to the access and mobility management function network element connected to it, so that the access and mobility management function network element connected to the first network device saves the tracking area information of the first device and the association relationship of the first network device; The association relationship with the second network device.

Based on the above technical solution, the network side can be informed in time that the network device associated with the first device has changed from the first device to the second network device, and then 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, and 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, so that the network side can more accurately perform mobility management on the UE and avoid waste of resources.

With reference to the third aspect, in some implementation manners of the third aspect, the method further includes: the network device sending first indication information to the connected access and mobility management function network element, where the first indication information is used to instruct deletion of the association relationship between the tracking area information of the first device and the network device. Based on the above technical solution, the network side can be made to know the network device associated with the first device in time, so that the network side can more accurately perform mobility management on the UE.

With reference to the third aspect, in some implementation manners of the third aspect, the first device includes a vehicle-mounted relay device VMR.

With reference to the third aspect, in some implementation manners of the third aspect, the tracking area information of the first device does not change as the access location of the first device changes.

In a fourth aspect, a communication method is provided, and the method includes: a unified database network element receives second registration information from a first access and mobility management function network element, and 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 between 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, and the first query information is used to query the network device associated with the tracking area information of the first device; the unified database network element sends first response information to the second access and mobility management function network element, and the first response information includes identification information of the second network device.

It should be noted that the first access and mobility management functional network element may be a VMR AMF network element registered with the VMR, and the second access and mobility management functional network element may be a UE AMF network element registered with the UE.

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, enabling the network side to know in a timely manner that the network device associated with the first device has changed from the first device to the second network device, and then 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, and 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, so that the network side can more accurately respond The UE performs mobility management and avoids waste of resources.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the method further includes: the unified database network element receives first registration information from the first access and mobility management functional network element, the first registration information is used to register the tracking area information of the first device and the association relationship between the first network device; and save the tracking area information of the first device and the association relationship between the first network device according to the first registration information. Based on the above technical solution, the network side can be made to know the network device associated with the first device in time, so that the network side can more accurately perform mobility management on the UE.

With reference to the fourth aspect, in some implementation manners 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, where the first request information is used to request deletion of the tracking area information of the first device and the association relationship between the first network device. Based on the above technical solution, the network side can be made to know the network device associated with the first device in time, so that the network side can more accurately perform mobility management on the UE.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the first device includes a vehicle-mounted relay device VMR.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the tracking area information of the first device does not change as the access location of the first device changes.

In a fifth aspect, an access and mobility management functional network element is provided, including: a receiving unit, configured to receive tracking area information of the first device from a first network device; a processing unit, configured to save the tracking area information of the first device and an 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 of the first network device.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the access and mobility management functional network element is connected to the first network device and the second network device, and the receiving unit is further configured to: receive the tracking area information of the first device from the second network device; the processing unit is further configured to: save an association relationship between the tracking area information of the first device and the second network device.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the processing unit is specifically configured to: delete the association relationship between the tracking area information of the first device and the first network device according to the tracking area information of the first device received from the second network device.

With reference to the fifth aspect, in some implementation manners 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 association relationship between the tracking area information of the first device and the first network device according to the first indication information.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the first indication information includes identification information of the second network device.

With reference to the fifth aspect, in some implementation manners 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, configured to send first registration information to a unified database network element, and the first registration information is used to register the association relationship between the tracking area information of the first device and the first network device with the unified database network element.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the sending unit is further configured to: send first request information to the unified database network element, where the first request information is used to request the unified database network element to delete the association relationship between the tracking area information of the first device and the first network device.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the sending unit is further configured to: send first query information to the network element of the unified database, where the first query information is used to query the network element of the unified database for a network device associated with the tracking area information of the first device; the receiving unit is also used to: receive first response information sent by the network element of the unified database, where the first response information includes identification information of the second network device.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the first device includes a vehicle-mounted relay device VMR.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the tracking area information of the first device does not change as the access location of the first device changes.

According to a sixth aspect, an access and mobility management function network element is provided, including: a receiving unit, configured to receive tracking area information of a first device from a second network device; a processing unit, configured to save an association relationship between the tracking area information of the first device and the second network device; a sending unit, configured to send second registration information to a unified database network element, and 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 with the unified database network element.

With reference to the sixth aspect, in some implementation manners of the sixth aspect, the first device includes a vehicle-mounted relay device VMR.

With reference to the sixth aspect, in some implementation manners of the sixth aspect, the tracking area information of the first device does not change as the access location of the first device changes.

In a seventh aspect, a network device is provided, including: a receiving unit, configured to obtain the tracking area information of the first device from the first device; a sending unit, configured to send the tracking area information of the first device to a connected access and mobility management functional network element.

With reference to the seventh aspect, in some implementation manners 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, where the first indication information is used to indicate to delete the association relationship between the tracking area information of the first device and the network device.

With reference to the seventh aspect, in some implementation manners of the seventh aspect, the first device includes a vehicle-mounted relay device VMR.

With reference to the seventh aspect, in some implementation manners of the seventh aspect, the tracking area information of the first device does not change as the access location of the first device changes.

In an eighth aspect, a unified database network element is provided, including: a receiving unit, configured to receive second registration information from a first access and mobility management functional network element, the second registration information being used to register an association relationship between the tracking area information of the first device and the second network device; a processing unit, configured to save the tracking area information of the first device and the association relationship between 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, where 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, where the first response information includes identification information of the second network device.

With reference to the eighth aspect, in some implementation manners of the eighth aspect, the receiving unit is further configured to: the unified database network element receives first registration information from the first access and mobility management functional network element, the first registration information is used to register the tracking area information of the first device and the association relationship between the first network device; the processing unit is further configured to: save the tracking area information of the first device and the association relationship between the first network device according to the first registration information.

With reference to the eighth aspect, in some implementation manners of the eighth aspect, the receiving unit is further configured to: receive first request information from the first access and mobility management functional network element, where the first request information is used to request deletion of the association relationship between the tracking area information of the first device and the first network device.

With reference to the eighth aspect, in some implementation manners of the eighth aspect, the first device includes a vehicle-mounted relay device VMR.

With reference to the eighth aspect, in some implementation manners of the eighth aspect, the tracking area information of the first device does not change as the access location of the first device changes.

A ninth aspect provides an access and mobility management functional network element, including: at least one processor, a memory, and a transceiver. The memory is used to store instructions, and the transceiver is used for the access and mobility management functional network element to communicate with other devices. The stored instructions are directly or indirectly executed by the at least one processor, so that the access and mobility management functional network element can execute the method in the first aspect, the second aspect, or any optional implementation manner of the first aspect.

In a tenth aspect, a network device is provided, including: at least one processor, a memory, and a transceiver, where the memory is used to store instructions, and the transceiver is used for the network device to communicate with other devices, and the stored instructions are directly or indirectly executed by the at least one processor, so that the network device can execute the method in the third aspect or any optional implementation manner of the third aspect.

In an eleventh aspect, a unified database network element is provided, including: at least one processor, a memory, and a transceiver, where the memory is used to store instructions, and the transceiver is used for the unified database network element to communicate with other devices, and the stored instructions are directly or indirectly executed by the at least one processor, so that the unified database network element can execute the method in the fourth aspect or any optional implementation manner of the fourth aspect.

In a twelfth aspect, a chip system is provided, including: at least one processor, and the at least one processor is configured to execute stored instructions, so that an access and mobility management function network element can execute the method in the first aspect, the second aspect, or any optional implementation manner of the first aspect.

In a thirteenth aspect, a chip system is provided, including: at least one processor, and the at least one processor is configured to execute stored instructions, so that the network device can execute the method in the third aspect or any optional implementation manner of the third aspect.

In a fourteenth aspect, a chip system is provided, including: at least one processor, and the at least one processor is configured to execute stored instructions, so that a unified database network element can execute the method in the fourth aspect or any optional implementation manner of the fourth aspect.

A fifteenth aspect provides a computer storage medium. The computer storage medium stores program instructions. When the instructions are executed, the access and mobility management functional network element can execute the method in the first aspect, the second aspect, or any optional implementation manner of the first aspect.

In a sixteenth aspect, a computer storage medium is provided, and the computer storage medium stores program instructions. When the instructions are executed, the network device can execute the method in the third aspect or any optional implementation manner of the third aspect.

In a seventeenth aspect, a computer storage medium is provided. The computer storage medium stores program instructions. When the instructions are executed, the unified database network element can execute the method in the fourth aspect or any optional implementation manner of the fourth aspect.

In an eighteenth aspect, a computer program product is provided, and the computer program product includes an instruction. When the instruction is executed, the access and mobility management functional network element can execute the method in the first aspect, the second aspect, or any optional implementation manner of the first aspect.

A nineteenth aspect provides a computer program product, where the computer program product includes instructions, and when the instructions are executed, the network device can execute the method in the third aspect or any optional implementation manner of the third aspect.

In a twentieth aspect, a computer program product is provided, and the computer program product includes an instruction. When the instruction is executed, the unified database network element can execute the method in the fourth aspect or any optional implementation manner of the fourth aspect.

A twenty-first aspect provides a system, where the system includes the access and mobility management function network element as described in the first aspect, the second aspect, or any optional implementation manner of the first aspect; and/or the network device as described in the third aspect or any optional implementation manner of the third aspect; and/or the unified database network element as described in the fourth aspect or any optional implementation manner of the fourth aspect.

Description of drawings

FIG. 1 shows a schematic diagram of a basic 5G system 200 architecture.

Fig. 2 shows a schematic diagram of an architecture based on a service-based interface.

Fig. 3 shows a schematic diagram of a gNB adopting CU-DU separation.

FIG. 4 shows a schematic diagram of data transmission performed by a terminal device through two-hop data backhaul (backhaul, BH).

FIG. 5 shows a schematic flowchart of a communication method 500 adapted to scenario 1 provided by an embodiment of the present application.

FIG. 6 shows a schematic flowchart of a communication method 600 adapted to scenario 2 provided by an embodiment of the present application.

FIG. 7 shows a schematic flow chart of a communication method 700 provided by another embodiment of the present application.

FIG. 8 shows a schematic flow chart of a communication method 800 provided by another embodiment of the present application.

FIG. 9 shows a schematic flow chart of a communication method 900 provided by another embodiment of the present application.

Fig. 10 is a schematic block diagram of a device provided by an embodiment of the present application.

Fig. 11 is a schematic diagram of another device provided by the embodiment of the present application.

Fig. 12 is a schematic diagram of another device provided by the embodiment of the present application.

Fig. 13 is a schematic diagram of another device provided by the embodiment of the present application.

Fig. 14 is a schematic structural diagram of a device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (code division multiple access, CDMA) system, wideband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), long-term evolution Long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunications system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system , the future fifth generation (5th generation, 5G) system or new radio (new radio, NR), etc.

The terminal equipment in this embodiment of the present application may refer to user equipment, access terminal, subscriber unit, subscriber 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, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network, or a future evolved public land mobile communication The terminal devices in the network (public land mobile network, PLMN), etc., are not limited in this embodiment of the present application.

The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may be a base transceiver station (BTS) in a global system of mobile communication (GSM) system or a code division multiple access (CDMA), or a wideband code division multiple access (WC The base station (nodeB, NB) in the DMA) system can also be an evolved base station (evolutional nodeB, eNB or eNodeB) in the LTE system, or a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario, or the network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network. Limited.

FIG. 1 shows a schematic architecture diagram of a basic 5G system 100 . As shown in FIG. 1 , the system 100 includes: PCF, AMF, session management function (session management function, SMF), radio access network (radio access network, RAN), unified data management (unified data management, UDM), data network (data network, DN), user plane function (user plane function, UPF), UE, application function (application function, AF), and/or Unified data storage (unified data repository, UDR). Optionally, the following functions may also be included in FIG. 1 (not shown in FIG. 1 ): network slice selection function (network slice selection function, NSSF), authentication server function (authentication server function, AUSF), capability exposure function (network exposure function, NEF), or network storage function (NF repository function, NRF).

Among them, the main functions of each network element are described as follows:

1. Terminal equipment

The terminal equipment in the embodiment of the present application may be: user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

A terminal device may be a device that provides voice/data connectivity to users, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like. At present, examples of some terminals are: mobile phone (mobile phone), tablet computer, notebook computer, palmtop computer, mobile Internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) device, augmented reality (augmented reality, AR) device, industrial control (industrial control) in the wireless terminal, unmanned (self-driving or autopilot) in the wireless terminal, Wireless terminals in remote medical surgery, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol (session initiation protocol, SIP) phones, wireless local loop (wireless local loop, W LL) stations, personal digital assistants (personal digital assistant, PDA), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in the future 5G network or terminal devices in the future evolving public land mobile network (public land mobile network, PLMN), etc., the embodiments of the present application are not limited to this.

As an example but not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction. Wearable smart devices in a broad sense include full-featured, large-sized devices that do not rely on smartphones to achieve complete or partial functions, such as smart watches or smart glasses, etc., and only focus on a certain type of application function, and need to be used in conjunction with other devices such as smart phones, such as smart bracelets and smart jewelry for physical signs monitoring. In addition, in the embodiment of the present application, the terminal device may also be a terminal device in an Internet of Things (Internet of Things, IoT) system.

2. Wireless access network

The wireless access network is an access network that realizes access network functions based on wireless communication technology. The wireless access network can manage wireless resources, provide wireless access or air interface access services for terminals, and then complete the forwarding of control signals and user data between terminals and the core network.

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

3. Network elements with access and mobility management functions

Access and mobility management function network elements are mainly used for mobility management and access management, etc., and can be used to implement functions other than session management in the mobility management entity (mobility management entity, MME) function, for example, functions such as lawful interception, or access authorization (or authentication), and are also used to transfer user policies between UE and PCF. In the embodiment of the present application, it can be used to implement functions of access and mobility management network elements.

4. Network element with session management function

The session management function network element is mainly used for session management, network interconnection protocol (internet protocol, IP) address allocation and management of terminal equipment, selection and management of user plane function (user plane function, UPF) network element, policy control and termination point of charging function interface, and downlink data notification, etc. In the embodiment of the present application, it can be used to realize the function of the session management network element.

5. User plane functional network element

The user plane functional network element can be used for packet routing and forwarding, or QoS parameter processing of user plane data, etc. User data can be accessed to a data network (data network, DN) through this network element. In the embodiment of this application, it can be used to implement the functions of the user plane network element. For example, when a session is established on different UPFs, the service experience of the UE will be different. Therefore, the above SMF needs to select an appropriate UPF for the session of the UE.

6. Policy control network element

The policy control network element is used to guide the unified policy framework of network behavior, and provide policy rule information, etc. for the control plane functional network elements (such as AMF, SMF network elements, etc.). It is mainly responsible for policy control functions such as charging for sessions and service flow levels, QoS bandwidth guarantee, mobility management, and UE policy decision-making. In this embodiment of the application, the PCFs connected to the AMF and the SMF correspond to AM PCF (PCF for Access and Mobility Control) and SM PCF (PCF for Session Management), respectively, and may be the same PCF entity or two different PCF entities in the actual deployment scenario.

7. Network element with network capability opening function

The network capability opening function network element is used to open the service and network capability information provided by the 3GPP network function to the outside (such as the location of the terminal, whether the session is reachable), etc.

8. Application function network element

The application function network element is mainly used to transmit the requirements from the application side to the network side, for example, QoS requirements or user status event subscription. The AF may be a third-party functional entity, or an application service deployed by an operator, such as an IMS voice call service. For the application function entity of the third-party application, it can also perform authorization processing through NEF when interacting with the core network. For example, the third-party application function directly sends a request message to the NEF, and the NEF judges whether the AF is allowed to send the request message. If the verification is passed, the request message will be forwarded to the corresponding PCF or unified data management (UDM).

9. Unified data management network elements

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

10. Unified data storage network element

The unified data storage network element is mainly used for the access function of contract data, policy data, application data and other types of data.

11. Data network

The data network refers to a specific data service network accessed by the UE. For example, a typical DN includes the Internet and an IP multimedia subsystem (IP multimedia subsystem, IPMS).

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

N7: The interface between PCF and SMF, which is used to deliver PDU session granularity and service data flow granularity control policies.

N15: the interface between the PCF and the AMF, used to issue UE policies and access control related policies.

N5: The interface between the AF and the PCF, used for delivering application service requests and reporting network events.

N4: The interface between SMF and UPF, which is used to transmit information between the control plane and the user plane, including controlling the distribution of forwarding rules, QoS control rules, and traffic statistics rules for the user plane, as well as the information reporting of the user plane.

N11: The interface between the SMF and the AMF, used to transfer the PDU session tunnel information between the RAN and the UPF, the control message sent to the UE, the radio resource control information sent to the RAN, etc.

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

N1: The interface between the AMF and the UE, which has nothing to do with access, and is used to deliver QoS control rules to the UE.

N8: The interface between AMF and UDM, which is used for AMF to obtain subscription data and authentication data related to access and mobility management from UDM, and for AMF to register UE current mobility management related information with UDM.

N10: The interface between SMF and UDM, which is used for SMF to obtain session management-related subscription data from UDM, and for SMF to register UE current session-related information with UDM.

N35: interface between UDM and UDR, used for UDM to obtain user subscription data information from UDR.

N36: the interface between PCF and UDR, used for PCF to obtain policy-related subscription data and application data-related information from UDR.

N52: The interface between UDM and NEF, which is used for NEF to open network capabilities to third-party application functions. For example, third-party application functions subscribe to UDM through NEF to reachability events of all users in a specific group.

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

It should be understood that the above-mentioned network architecture applied to the embodiment of the present application is only 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 embodiment of the present application is not limited thereto. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiment of the present application.

It should be understood that the name of the interface between network elements in FIG. 1 is just an example, and the name of the interface in a specific implementation may be another name, which is not specifically limited in this application. In addition, the name of the message (or signaling) transmitted between the above network elements is only an example, and does not constitute any limitation on the function of the message itself.

It should be noted that the foregoing network element may also be called an entity, device, device, or module, which is not specifically limited in this application. Moreover, in this application, for the sake of easy understanding and description, the description of the network element is omitted in some descriptions. For example, the SMF network element is referred to as SMF.

It can be understood that the above-mentioned network element or function may be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform). Optionally, the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.

It should also be understood that in the communication system shown in FIG. 1 , the functions of each component network element are only exemplary, and not all functions of each component network element are required when applied in the embodiment of the present application.

In addition, the naming of each network element (such as PCF, AMF, etc.) included in FIG. 1 is only a name, and the name does not limit the function of the network element itself. In the 5G network and other networks in the future, the above-mentioned network elements may also have other names, which are not specifically limited in this embodiment of the present application. For example, in a 6G network, some or all of the above-mentioned network elements may use the terms in 5G, or may be named by other names, etc., which will be described in a unified manner here, and will not be described in detail below.

It should also be noted that, in FIG. 1 , the communication between various network elements of the control plane function is described using a non-service interface as an example, but this does not limit the protection scope of the embodiment of the present application. Those skilled in the art can understand that each network element of the control plane function in FIG. 1 can also communicate through a service interface. For example, the service interface provided by AMF can be Namf; the service interface provided by SMF can be Nsmf; the service interface provided by UDM can be Nudm; the service interface provided by AF can be Naf;

The above network elements in FIG. 1 are architectures based on reference points, which do not limit this embodiment of the present application.

Figure 2 shows a schematic diagram of the architecture based on the service interface. As shown in Figure 2, the structure includes: NSSF, AUSF, UDM, NEF, NRF, PCF, AF, AMF, SMF, UE, RAN, UPF, DN. In Figure 2, the service interface provided by NSSF can be Nnssf, the service interface provided by NEF can be Nnef, the service interface provided by NRF can be Nnrf, the service interface provided by AMF can be Namf; the service interface provided by SMF can be Nsmf; the service interface provided by UDM can be Nudm, the service interface provided by AF can be Naf; the service interface provided by PCF can be Npcf, and the service interface provided by AUSF The service interface provided by CHF can be Nausf, and the service interface provided by CHF can be Nchf; the interface between the control plane function and RAN and UPF is a non-service interface. UE is connected to AMF through N1 interface, UE is connected to RAN through radio resource control (RRC) protocol; RAN is connected to AMF through N2 interface, RAN is connected to UPF through N3 interface; UPF is connected to DN through N6 interface, and UPF is connected to SMF through N4 interface. For related descriptions, please refer to the 5G system architecture in the standard. For the sake of brevity, the connection relationship of the architecture 300 will not be repeated here.

In order to facilitate the understanding of the embodiments of the present application, a 5G network is taken as an example to briefly describe the process of establishing a PDU session connection and PDU session management for a UE.

In 5G network, 5G network provides data exchange service for UE and DN network, which is called PDU connection service. The UE obtains the PDU connection service by initiating a PDU session establishment request to the mobile network. The network side provides the PDU connection service by maintaining the PDU session for the UE.

In order to realize data exchange between UE and DN network, UE needs to use the PDU connection service provided by the mobile network to establish a DNN-based PDU session (signaling plane process). The establishment of a PDU session includes two basic processes: the UE registers with the mobile network to access the 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.

The general UE registration and network access process can be simply described as: UE sends a registration request to AMF through (R)AN, and AMF obtains subscription data from a specific UDM according to the user ID. After a series of authentication and authorization operations, the network side finally confirms that the UE is allowed to access the network. At this time, the AMF responds to the UE registration request and sends relevant policy information to the UE, and the UE completes network registration and camping. The AMF on the network side maintains the registration information of the UE and performs mobility management on the UE.

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

In the process of PDU session management for UE, SMF interacts with UPF through N4 interface, and controls UPF to create, modify, and delete corresponding UE N4 sessions (N4Session/PFCP Session) to realize the control of UPF processing data packets. SMF sends various data packet processing rules to UE N4 sessions in UPF to complete the control of UPF processing data packets. After the UPF receives the external data packet, it performs packet matching according to the data packet matching rules delivered by the SMF, and forwards the packets according to the forwarding rules.

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

The structure of gNB using CU-DU separation is shown in Figure 3. The gNB-CU and gNB-DU are connected through the F1 interface, the gNB-CU and the 5G core network are connected through the NG interface, and the gNB and gNB are connected through the Xn interface. The Xn interface includes an Xn-C interface and an Xn-U interface. The Xn-C interface is used for transmission of control plane signaling between two gNBs, and the Xn-U interface is used for transmission of user plane data between two gNBs. The interface between gNB and UE is called Uu interface (that is, the interface between UE and gNB-DU). The terminal device accesses the gNB-CU through the gNB-DU. The physical (physics, PHY) layer/media access control (MAC) layer/radio link control (radio link control, RLC) layer equivalent to the terminal device is located on the gNB-DU, and the packet data convergence protocol (PDCP) layer/radio resource control (radio resource control, RRC) layer/service data adaptation protocol (Service The Data Adaptation Protocol (SDAP) layer is located on the gNB-CU.

It should be understood that the above-mentioned protocol layers on the gNB-DU and gNB-CU are only one possibility, and there may be other possibilities. For example, the PHY layer/MAC layer equivalent to the terminal device is located on the gNB-DU, the PDCP layer/RRC layer/SDAP layer equivalent to the terminal device is located on the gNB-CU, and at the same time, the RLC layer equivalent to the terminal device is also located on the gNB-CU.

For the control plane, in the uplink (uplink, UL) direction, the gNB-DU encapsulates the RRC message generated by the terminal device in the F1 Application Protocol (F1Application Protocol, F1AP) message of the F1 interface and sends it to the gNB-CU. In the downlink (downlink, DL) direction, the gNB-CU encapsulates the RRC message in the F1AP message and sends it to the gNB-DU, and the gNB-DU extracts the RRC message from the F1AP message and maps it to the signaling radio bearer (Signalling Radio Bearer, SRB) corresponding to the Uu interface and sends it to the terminal device.

For the user plane, in the UL direction, the gNB-DU maps the data packet of the terminal device received from the Data Radio Bearer (DRB) of the Uu interface to the corresponding General Packet Radio Service Tunneling Protocol (GTP) tunnel and sends it to the gNB-CU. In the DL direction, the gNB-CU maps the data packet of the terminal device to the corresponding GTP tunnel and sends it to the gNB-DU. The gNB-DU extracts the data packet of the terminal device from the GTP tunnel, and maps the data packet to the DRB corresponding to the Uu interface and sends it to the terminal device.

The 5G communication system puts forward more stringent requirements for various performance indicators of the network. For example, the capacity index has been increased by 1000 times, wider coverage requirements, ultra-high reliability and ultra-low latency, etc. Therefore, the Integrated Access And Backhaul (IAB) technology is introduced.

In the IAB network, as shown in FIG. 4, a relay node (Relay Node, RN), or also called an IAB node (IAB node), can provide wireless access and wireless backhaul services for user equipment. Specifically, the service data of the user equipment is connected to the IAB donor node (IAB donor) by the IAB node through a wireless backhaul link, and the IAB donor node (IAB donor) may also be called a donor IAB node (donor IAB) or an IAB donor base station. In the NR system, the IAB donor base station may be a donor next-generation base station (donor gNodeB, DgNB), and in the LTE system (or 4G system), the IAB donor base station may be a donor evolved base station (donor eNodeB, DeNB). Of course, the IAB host node can also be referred to as: gNB, eNB or IAB donor.

IAB donor can also adopt CU-DU separation architecture, as shown in Figure 4, namely: IAB donor is composed of two parts: IAB donor CU (or can also be called donor CU) and IAB donor DU (or can also be called donor DU), and the interface between IAB donor CU and IAB donor DU is F1 interface. The IAB node may be composed of a mobile terminal (mobile terminal, MT) unit and a distributed unit (distributed unit, DU). The IAB-MT can also be called the IAB-UE, which has the function of a terminal device and mainly performs operations similar to the terminal device. The IAB-DU has some functions of the base station, and mainly completes operations similar to the base station.

For IAB donor, 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.

For an IAB node, the IAB-DU has a similar function to the gNB-DU in NR, providing access services to nodes connected to it, where the node connected to the IAB-DU can be a terminal device or other IAB nodes. IAB-MT is similar to terminal equipment and is used to provide data backhaul. The IAB node accessed by the terminal device may be called an access IAB node, and the IAB node on the path between the access IAB node and the IAB donor is called an intermediate IAB node. For example, if a terminal device accesses IAB node 2 (IAB node2), then IAB node2 is called an access IAB node, and IAB node1 is called an intermediate IAB node.

Figure 5 and Figure 6 are schematic flowcharts of a communication method provided by an embodiment of the present application. It should be noted that during the movement of the first device, the first device switches from the first network device to the second network device, and the following two scenarios may exist. Wherein, FIG. 5 corresponds to Scenario 1 described below, and FIG. 6 corresponds to Scenario 2 described below.

Scenario 1: During the movement of the first device from the first network device to the second network device, the access and mobility management function network element is not replaced, as shown in FIG. 5, 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.

Scenario 2: During the movement of the first device from the first network device to the second network device, the access and mobility management function network element is replaced. As shown in FIG. 6, the access and mobility management function network element 1 is replaced with the access and mobility management function network element 2. In other words, the access and mobility management function network element 1 (such as UE AMF1, VMR AMF1) is connected to the first network device, and the replaced access and mobility management function network element 2 (such as UE AMF2, VMR AMF2) is connected to the second network device.

FIG. 5 is a schematic flowchart of a communication method 500 adapted to scenario 1 provided by an embodiment of the present application, and the method includes at least the following steps.

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.

For example, the first network device may be a donor gNB1, or may be a CU located in the first network device (for example, donor gNB1), and the first device may be a vehicle-mounted relay VMR, or may be a UE served by the VMR, which is not limited in this embodiment of the present application.

The first network device is donor gNB1, and the first device is VMR as an example. The VMR interacts with the OAM to obtain the tracking area information of the VMR. Then, the DU part (or as a DU) in the VMR interacts with the CU of donor gNB 1, and registers the tracking area information of the VMR to the CU of donor gNB 1 through the F1setup process. At this time, the CU of donor gNB 1 updates its corresponding tracking area information list .

Wherein, the tracking area information is the specific tracking area information (S-TAI) of the first device. It can be understood that, during the moving process of the first device, the tracking area information broadcast by the first device to the UE served by it is fixed, that is, even if the first device switches from the first network device to the second network device (for example, switching to another donor gNB2), the tracking area information broadcast by the first device to the UE it serves is also fixed, that is, S-TAI. To put it another way, the S-TAI can only be allocated to the UE served by the VMR, and when the TAI is allocated to the UE not served by the VMR, the S-TAI will not be allocated. Therefore, the S-TAI is VMR-specific, or called VMR-specific. In addition, the S-TAIs corresponding to different VMRs may be the same or different. For example, the S-TAIs corresponding to different VMRs in different regions are the same, but the S-TAIs corresponding to different VMRs in the same region are different. For ease of description, in the following description, the S-TAI is uniformly used to replace the tracking area information of the first device.

It should be noted that, in the embodiment of the present application, the UE served by the first device is a UE in an idle state.

In a possible implementation manner, the tracking area information S-TAI of the first device may be carried in an update configuration message, or may also be carried in other messages. It should be understood that this embodiment of the present application makes no limitation here.

Optionally, in a possible implementation manner, the update configuration message may include indication information, where the indication information is used to indicate that the tracking area information is the tracking area information of the first device. Exemplarily, the indication information may be VMR specific TA indication information, which is used to indicate that the S-TAI is specific tracking area information of the VMR.

In a possible implementation manner, the indication information may be represented by a shorter field. For example, when the field is 1 bit, when the field is "1", it means that the indication information indicates that the S-TAI is the tracking area information of the VMR; when the field is "0", it means that the indication information indicates that the S-TAI is not the tracking area information of the VMR.

In a possible implementation manner, the indication information may also be implicit in the tracking area information S-TAI. For example, when the network side (CN) divides the TAI, the TAI of a specific range is used as the S-TAI dedicated to the VMR, that is, when the S-TAI belongs to the TAI of the specific range, it indicates that the S-TAI is the tracking area information of the VMR.

It should be noted that the first device may be a vehicle-mounted relay VMR, or may be a terminal device carried on a movable object (for example, a UE on a moving vehicle), and the access and mobility management function network element 1 may be a first AMF network element (UE AMF1) registered with the UE, or a second AMF network element (VMR AMF1) registered with the first device. It should be understood that this embodiment of the present application does not limit it.

S520, the access and mobility management function network element 1 saves the tracking area information of the first device and the association relationship between the first network device.

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 notifies all the access and mobility management function network elements 1 connected to it that there is a first device and the tracking area information (S-TAI) of the first device within its jurisdiction, 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.

It should be understood that the association relationship between the S-TAI of the first device and the first network device may be the association relationship between the S-TAI and gNB1, for example, the association relationship between the S-TAI of the first device and the identification information (RAN ID1) of the first network device (gNB1), or the association relationship between the S-TAI and the CU1 located in the gNB1, which is not limited in this embodiment of the present application.

S530, in the case that the second network device serves the first device, the access and mobility management functional network element 1 deletes the association relationship between the tracking area information of the first device and the first network device.

For example, during the moving process 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 is changed from the first network device to the second network device, and when the second network device serves the first device, the access and mobility management functional network element 1 deletes the association relationship between the tracking area information (S-TAI) of the first device and the first device.

It should be noted that FIG. 5 corresponds to scenario 1 described above, that is, during the movement of the first device from the first network device to the second network device, the access and mobility management function network element is not replaced, 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.

Optionally, before 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.

S522. The access and mobility management function network element 1 saves the tracking area information (S-TAI) of the first device and the association relationship between the second network device.

It should be understood that the second network device may be donor NB2, or CU2 located in the second network device (donor gNB2), and the first device may be a vehicle-mounted relay VMR, or a UE served by the VMR, which is not limited in this embodiment of the present application.

The second network device is donor gNB2, and the first device is VMR as an example. The VMR interacts with the OAM on the user plane to obtain the tracking area information of the VMR. Then, the DU in the VMR (or as a DU) interacts with the CU of the donor gNB 2, and registers the tracking area information of the VMR to the CU of the donor gNB 2 through the F1setup process. At this time, the CU of the donor gNB 2 updates its corresponding tracking area information list ( TAI list).

For example, in Scenario 1, when the access and mobility management function network element 1 (for example, 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, VMR AMF1) receives the S-TAI of the first device from the second network device. It can be understood that the second network device notifies all the access and mobility management function network elements 1 (for example, UE AMF1 and VMR AMF1) The TAI list associated with itself includes tracking area information (S-TAI) of the first device. At this time, the access and mobility management function network element 1 (UE AMF1, VMR AMF1) stores the association relationship between the S-TAI of the first device and the second network device.

It should be understood that the association relationship between the S-TAI of the first device and the second network device may be the association relationship between the S-TAI and gNB2, for example, the association relationship between the S-TAI of the first device and the identification information (RAN ID2) of the second network device (gNB2), or the association relationship between the S-TAI and the CU2 located in the gNB2, which is not limited in this embodiment of the present application.

Optionally, in a possible implementation, in scenario one, that is, when the access and mobility management function network element 1 is connected to the first network device and the second network device, after the access and mobility management function network element 1 receives the S-TAI of the first device from the second network device, the access and mobility management function network element 1 learns that the serving network device of the first device is handed over from the first network device to the second network device according to the identifier (such as RAN ID2) contained in the S-TAI received from the second network device. The mobility management function network element 1 deletes the association relationship between the S-TAI of the first device and the first network device by using the S-TAI as an index.

Optionally, in a possible implementation manner, 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, where the first indication information is used to indicate deletion of the association relationship between the tracking area information of the first device and the first network device.

For example, in Scenario 1, that is, when 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, VMR AMF1) deletes the association relationship between the S-TAI of the first device and the first network device according to the received first indication information, which includes an identifier (such as RAN ID1).

It should be noted that S523 may be executed before S521 and S522, or may be executed after S521 and S522. It should be understood that the specific execution order is not limited in this embodiment of the present application.

Exemplarily, in a possible implementation manner, step S523 may be triggered by the handover of the first device from the first network device to the second network device, that is, when the first device is handed over from the first network device to the second network device, the first network device is triggered to send the first indication information to the access and mobility management function network element 1, indicating to delete the association relationship between the S-TAI of the first device and the first network device.

In the technical solution of the embodiment of the present application, when the first device accesses the first network device, the access and mobility management functional network element 1 saves the tracking area information of the first device and the association relationship between the first network device. When the first device is handed over 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 between the second network device, and deletes the previously saved tracking area information of the first device and the association relationship between the first network device, so that the network side can know in time that the network device associated with the first device has changed from the first device to the second network device, and then 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, and the network side does not paging the first device and/or the first device service. When the UE is at the UE, the network side instructs the first network device to send the paging message, so that the network side can more accurately perform mobility management on the UE and avoid waste of resources.

Fig. 6 is a schematic flowchart of a communication method 600 adapted to scenario 2 provided by an embodiment of the present application, and the method includes at least the following steps.

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.

S620, the access and mobility management functional network element 1 saves the tracking area information of the first device and the association relationship between the first network device.

It should be noted that S610-S620 are similar to S510-S520, and for the sake of brevity, the present application will not repeat them here.

Optionally, after S620, the method may further include S621, 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, and the first registration information is used to register the tracking area information (S-TAI) of the first device and the association relationship between the first network device with the unified database.

For example, the access and mobility management function network element 1 may be the access and mobility management function network element 1 (such as VMR AMF1) registered by the first device. The VMR AMF1 is connected to the first network device. The VMR AMF1 sends the first registration information to the network element of the unified database. The first registration information includes the identification information of the first network device (such as donor NB1ID or RAN1ID). Relationships are registered with the consolidated database.

It should be noted that FIG. 6 corresponds to scenario 2 described above, that is, during the moving 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 replaced. As shown in FIG. 6 , the access and mobility management function network element 1 is replaced with the access and mobility management function network element 2. In other words, the access and mobility management function network element 1 (such as UE AMF1, VMR AMF1) is connected to the first network device, and the replaced access and mobility management function network element 2 (such as UE AMF2, VMR AMF2) is connected to the second network device.

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.

S640, the access and mobility management functional network element 2 saves the association relationship between the tracking area information (S-TAI) of the first device and the second network device.

Taking the second network device as donor gNB2 and the first device as VMR as an example, the DU part of the VMR (or as a DU) interacts with the CU of donor gNB 2, and registers the tracking area information of the VMR to the CU of donor gNB 2 through the F1setup process. At this time, the CU of donor gNB 2 updates its corresponding tracking area information list (TAI list).

In the second scenario, that is, when the access and mobility management function network element 1 (such as UE AMF1, VMR AMF1) is connected to the first network device, and the replaced access and mobility management function network element 2 (such as UE AMF2, VMR AMF2) is connected to the second network device, the replaced access and mobility management function network element 2 (UE AMF2, VMMR AMF2) receives the tracking area information (S-TAI) of the first device from the second network device, it can be understood For, the second network device notifies all access and mobility management function network elements 2 (for example, UE AMF2, VMR AMF2) connected to it that its associated TAI list includes the tracking area information (S-TAI) of the first device. At this time, the access and mobility management function network element 2 (UE AMF2, VMR AMF2) saves the association relationship between the tracking area information (S-TAI) of the first device and the second network device.

Optionally, after S640, the method may further include S641, 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, and the second registration information is used to register the association relationship between the tracking area information (S-TAI) of the first device and the second network device with the unified database.

For example, at this time, the access and mobility management function network element 2 may be the access and mobility management function network element 2 (such as VMR AMF2) registered by the first device, and the VMR AMF2 is connected to the second network device, and the VMR AMF2 sends the second registration information to the network element of the unified database. in the consolidated database.

S650, 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, where the first indication information is used to instruct deletion of the association relationship between the tracking area information of the first device and the first network device.

For example, in Scenario 2, that is, 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 relationship between the S-TAI of the first device and the first network device according to the received first indication information, which includes the identifier of the first network device (such as RAN ID1).

It should be noted that S650 may be executed before S630 and S640, or may be executed after S630 and S640. It should be understood that the specific execution sequence is not limited in this embodiment of the present application.

Exemplarily, in a possible implementation manner, step S650 may be triggered by the handover of the first device from the first network device to the second network device, that is, when the first device is handed over from the first network device to the second network device, the first network device is triggered to send first instruction information to the access and mobility management function network element 1, indicating to delete the association relationship between the S-TAI of the first device and the first network device.

Optionally, in a possible implementation manner, the first indication information may further include identification information of the second network device. For example, in Scenario 2, the access and mobility management function network element 1 (such as UE AMF1, VMRAMF1) receives first indication information from the first network device, and the first indication information also includes identification information of the second network device (such as donor NB2 ID or RAN2 ID). That is, the first network device notifies the access and mobility management function network element 1 (UE AMF1, VMR AMF1) that the target network device for the handover of the first device is the second network device. At this time, the access and mobility management function network element (UE AMF1) registered by the UE will determine the UE AMF2 connected to the second network device to provide services for the UE according to the identification information of the second network device in the received first indication information, and subsequently perform UE context migration between UE AMF1 and UE AMF2.

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

For example, the access and mobility management function network element 1 may be a VMR-registered access and mobility management function network element (such as VMR AMF1), the VMR AMF1 is connected to the first network device, and the VMR AMF1 sends the first request information to the unified database, and the unified database deletes the tracking area information (S-TAI) of the first device and the association relationship between the first network device according to the received first request information.

It should be noted that step S650 may be used to trigger step S660. In step S650, donor NB1 sends first indication information to VMR AMF1 and UE AMF1, and the first indication information is used to indicate to delete the association relationship between the first network device and S-TAI. Optionally, in a possible implementation manner, the first indication information may also include VMR identification information (such as VMR ID1), and VMR AMF1 judges according to the VMR identification information (such as VMR ID1) out to serve the VMR, thereby triggering the VMR AMF1 to send a first request message to the unified database, requesting the unified database to delete the association relationship between the first network device and the S-TAI.

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

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

For example, the access and mobility management function network element 1 may be a UE registered access and mobility management function network element (such as UE AMF1), UE AMF1 is connected to the first network device, UE AMF1 sends the first query information to the unified database, and 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 according to the S-TAI carried in the received first query information.

For another example, UE AMF1 utilizes the general query service of the unified database, UE AMF1 carries the query target type as gNB (or RAN) in the first query information, and the query index is S-TAI, 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.

It should be noted that step S670 can be triggered by step S650, that is, after UE AMF1 deletes the association relationship between the tracking area information of the first device and the first network device according to the received first indication information, it can be judged 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. one.

S680. The unified database sends first response information to the access and mobility management functional network element, and correspondingly, the access and mobility management functional network element receives the first response information, where the first response information includes the identification information of the second network device.

In Scenario 2, the access and mobility management function network element 1 may be a UE-registered access and mobility management function network element (for example, UE AMF1), and UE AMF1 is connected to the first network device.

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 the first response information to UE AMF1, and the first response information includes the identification information of the second network device (such as donor NB2 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.

It should be noted that S670 is an optional step, that is, the access and mobility management function network element (such as UE AMF1) can subscribe to the unified database in advance for the change of the network device associated with the tracking area information (S-TAI) of the first device. The network device is changed to a second network device.

In the technical solution of the embodiment of the present application, when the first device accesses the first network device, the access and mobility management functional network element 1 saves the tracking area information of the first device and the association relationship between the first network device. When the first device is handed over 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 between the second network device, and the mobility management function network element 1 deletes the previously saved association relationship between the tracking area information of the first device and 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 be informed in time that the network device associated with the first device has been changed from the first device to the second network device, and then 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, and 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, so that the network side can more accurately perform mobility management on the UE and avoid waste of resources.

To facilitate understanding of the present application, in the following embodiments, a vehicle-mounted relay VMR is used instead of the first device for description.

7 is a schematic flowchart of a communication method 700 provided by the embodiment of the present application. It should be noted that the method 700 mainly corresponds to the first scenario described above, that is, during the movement of the VMR from donor gNB1 to donor gNB2, the access and mobility management function network element is not replaced, that is, the access and mobility management function network element (such as UE AMF, VMR AMF) is connected to donor gNB1 and donor gNB2 . Wherein, the UE AMF and the VMRAMF can be the same AMF (that is, the interaction between the two AMFs can be realized through internal interaction), or they can be different AMFs. The UE AMF and the VMMR AMF are different AMFs as an example for description below. The method at least includes the following steps.

It should be noted that, in the embodiment of the present application, the UE served by the VMR is a UE in an idle state.

S710, the VMR registers with the network (CN), and establishes a PDU session.

For example, the VMR is registered in the network, and the access and mobility management function network element VMR AMF provides services for the VMR. The VMR establishes a PDU session, so that the VMR communicates with the OAM system through the user plane, and the OAM system returns specific tracking area information (S-TAI) of the VMR to the VMR through the user. Then the VMR interacts with the CU in donor gNB1, and the VMR registers the S-TAI to the CU in donor gNB 1 through the F1setup process. At this time, CU1 of donor gNB 1 updates the corresponding TAI list.

S720, the donor gNB1 sends the S-TAI of the 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 the VMR.

For example, since the current VMR communicates through the donor gNB1, the donor gNB1 sends the S-TAI of the VMR to the AMF that has established a connection with it. The AMF that has established a connection with the donor gNB1 includes the UE AMF and the VMRAMF. Therefore, it can be understood that the donor gNB1 sends the S-TAI of the VMR to the UE AMF network element and the VMR AMF network element. For the S-TAI of the VMR, reference may be made to the description in FIG. 5 , which will not be repeated here.

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

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

Optionally, in a possible implementation manner, the configuration update message 1 may only include the S-TAI information of the VMR, that is, not include the VMR indication information. Wherein, the S-TAI includes specific information, and through the specific information, the UE AMF network element and the VMMR AMF network element can identify that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR.

Optionally, in a possible implementation manner, the network side (CN) defines a VMR-specific TAI list for the VMR, then the UE AMF network element and the VMR AMF network element belong to the TAI list according to the S-TAI, thereby identifying that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR.

It should be noted that during the moving process of the VMR, the tracking area information broadcast by the VMR to the UE it serves is constant, that is, the S-TAI. That is to say, even if the VMR is switched from donor gNB1 to donor gNB2, the tracking area information (S-TAI) of the VMR is fixed.

S730, the UE registers in the network through the VMR, and the UE AMF performs access and mobility management on the UE. The UE AMF locates the UE in the area where the S-TAI information is located according to the location information of the UE, and learns that the UE is served by the VMR. At this time, the UE AMF assigns the S-TAI as the TAI List of the UE. On the contrary, the UE AMF knows that the UE is not served by the VMR according to the location information of the UE is not located in the area where the S-TAI information is located, then when the UE AMF allocates a TAI List for the UE not served by the VMR, the TAI List does not include S-TAI.

S740, VMR switches from donor gNB1 to donor gNB2.

For example, corresponding to scenario 1 mentioned above, during the process of VMR switching from donor gNB1 to donor gNB2, the UE AMF network element and VMR AMF network element are not replaced. 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 is connected to UE AMF1 and VMRAMF1, and donor gNB1 is also connected to UE AMF1 and VMR AMF1.

S750. The VMR registers the S-TAI obtained from the OAM system into the donor gNB2.

For example, VMR exchanges information with CU in donor gNB2, and VMR registers S-TAI to CU2 in donor gNB 2 through the F1setup process. At this time, CU2 of donor gNB 2 updates the corresponding TAI list.

S760, the donor gNB2 sends the S-TAI of the 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 the VMR.

For example, since the current VMR communicates through the donor gNB2, the donor gNB2 sends the S-TAI of the VMR to the AMF that has established a connection with it. The AMF that has established a connection with donor gNB1 includes UE AMF and VMR AMF. Therefore, it can be understood that donor gNB2 has sent the S-TAI of VMR to the UE AMF network element and the VMR AMF network element. For the S-TAI of the VMR, reference may be made to the description in FIG. 5 , which will not be repeated here.

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

Optionally, in a possible implementation manner, the configuration update message 2 includes the S-TAI of the VMR and the VMR indication information, and the VMR indication information is used to indicate the UE AMF network element and the VMMR AMF network element that the S-TAI is specific tracking area information of the VMR. Donor gNB2 informs all AMFs connected to donor gNB2 (including UE AMF and VMR AMF) that there is a VMR within its jurisdiction and the tracking area information (S-TAI) of the VMR through the configuration update message 2 (Ran configuration update2).

Optionally, in a possible implementation manner, the configuration update message 2 may only include the S-TAI information of the VMR, that is, not include the VMR indication information. Wherein, the S-TAI includes specific information, and through the specific information, the UE AMF network element and the VMMR AMF network element can identify that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR. Or, in another possible implementation, the network side (CN) defines a VMR-specific TAI list for the VMR, then the UE AMF network element and the VMR AMF network element belong to the TAI list according to the S-TAI, thereby identifying that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR.

S770, the donor gNB1 sends a configuration update message 3 to the UE AMF network element and the VMR AMF network element.

For example, the configuration update message 3 is used to instruct all AMFs (UE AMF network elements and VMR AMF network elements) connected to the donor gNB1 to delete the S-TAI, or it can also be said that the configuration update message 3 is used to instruct all AMFs connected to the donor gNB1 to delete the association between the S-TAI and the donor gNB1 or CU1 in the donor gNB1. At this point, the VMR AMF1 and the UE AMF1 delete the association between the S-TAI of the VMR and the donor gNB1 according to the received configuration update message 3, which contains the identifier of the donor gNB1 (eg gNB ID1). It can be understood that the donor gNB1 notifies all AMFs connected to it that a VMR is left under the jurisdiction of the donor gNB1, and the tracking area information of the VMR is S-TAI. Then it means that all AMFs (UE AMF network elements and VMR AMF network elements) connected to the donor gNB1 will not go to the donor gNB1 for the subsequent processing of the VMR and UE corresponding to the S-TAI.

For example, when the network needs to page the VMR and/or the UE served by the VMR, the VMR AMF and/or the UE AMF network element can accurately locate the donor gNB 2, and when the network paging the UE served by the VMR, the VMR AMF and/or the UE AMF instruct the donor gNB 1 to send a paging message, thereby avoiding waste of resources.

It should be noted that step S770 can also be performed after step S740. It can be understood that the VMR in step S740 is switched from donor gNB1 to donor gNB2, which can trigger the donor gNB1 in step S770 to send a configuration update message 3 to the UE AMF network element and the VMR AMF network element. The configuration update message 3 is used to indicate the deletion of the association relationship between the donor gNB1 and the S-TAI. It should be understood that the embodiment of the present application does not limit the execution sequence here.

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

In the technical solution of the embodiment of the present application, when the VMR accesses the donor gNB1, the AMF (such as VMR AMF, UE AMF) saves the association relationship between the VMR's S-TAI and the donor gNB1. When the VMR is switched from donor gNB1 to donor gNB2, the AMF (such as VMR AMF, UE AMF) deletes the previously saved association between the S-TAI of the VMR and the donor gNB1. Through this technical solution, the network side can be informed in time that the network device associated with the VMR is changed to donor gNB2, and then when the network side needs to page the VMR and/or the UE served by the VMR, the donor gNB2 associated with the VMR can be accurately located, and there will be no situation where the network side instructs other network devices (such as donor gNB1) to send paging messages when the network side pages the VMR and/or the UE served by the VMR, so that the network side can more accurately respond to the UE. Carry out mobility management and avoid resource waste.

8 is a schematic flowchart of a communication method 800 provided by the embodiment of the present application. It should be noted that the method 800 mainly corresponds to the second scenario described above, that is, during the moving process of VMR switching from donor gNB1 to donor gNB2, the access and mobility management function network element is replaced, that is, the access and mobility management function network element (such as UE AMF1, VMR AMF1) is connected to the donor gNB1, and the access and mobility management function network Elements (such as UE AMF2, VMR AMF2) are connected to donor NB2, where UE AMF1 and VMR AMF1 can be the same AMF, UE AMF2 and VMR AMF2 can be the same AMF (that is, the interaction between the two AMFs can be realized through internal interaction), or they can be different AMFs. The UE AMF and the VMMR AMF are different AMFs as an example for description below. The method at least includes the following steps.

S810, the VMR registers with the network (CN), and establishes a PDU session.

For example, the VMR is registered in the network, and the access and mobility management function network element VMR AMF1 provides services for the VMR. The VMR establishes a PDU session, so that the VMR communicates with the OAM system through the user plane, and the OAM system returns specific tracking area information (S-TAI) of the VMR to the VMR through the user. Then VMR interacts with CU1 in donor gNB1, and VMR registers S-TAI to CU1 in donor gNB 1 through the F1setup process. At this time, CU1 of donor gNB 1 updates the corresponding TAI list.

S820, the donor gNB1 sends the S-TAI of the 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 the VMR.

For example, since the current VMR communicates through the donor gNB1, the donor gNB1 sends the S-TAI of the VMR to the AMF that has established a connection with it. The AMFs that have established a connection with donor gNB1 include UE AMF1 and VMR AMF1. Therefore, it can be understood that donor gNB1 sends the S-TAI of VMR to UE AMF1 network element and VMR AMF1 network element. For the S-TAI of the VMR, reference may be made to the description in FIG. 5 , which will not be repeated here.

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

Optionally, in a possible implementation, the configuration update message 1 includes the S-TAI of the VMR and the VMR indication information, where the VMR indication information is used to indicate the UE AMF1 network element and the VMR AMF1 network element that the S-TAI is specific tracking area information of the VMR. Donor gNB1 notifies 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 the VMR through configuration update message 1 (Ran configuration update1).

Optionally, in a possible implementation manner, the configuration update message 1 may only include the S-TAI information of the VMR, that is, not include the VMR indication information. Wherein, the S-TAI includes specific information, and through the specific information, the UE AMF1 network element and the VMR AMF1 network element can identify that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR. Or, in another possible implementation, the network side (CN) defines a VMR-specific TAI list for the VMR, then the UE AMF1 network element and the VMR AMF1 network element belong to the TAI list according to the S-TAI, thereby identifying that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR.

S830, the UE registers in the network through the VMR, and the UE AMF1 performs access and mobility management on the VMR. The UE AMF1 locates within the area where the S-TAI information is located according to the location information of the UE, and learns that the UE is served by the VMR. At this time, the UE AMF1 allocates the S-TAI as the TAI List of the UE. On the contrary, UE AMF1 knows that the UE is not served by the VMR according to the location information of the UE is not located in the area where the S-TAI information is located, then when UE AMF1 allocates a TAI List for a UE not served by the VMR, the TAI List does not include S-TAI.

S840, the VMR is switched from donor gNB1 to donor gNB2.

For example, during the process of VMR switching from donor gNB1 to donor gNB2, the UE AMF network element and VMR AMF 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 is connected to UE AMF1 and VMRAMF1, and donor gNB2 is connected to UE AMF2 and VMR AMF2 .

S850. The VMR registers the S-TAI obtained from the OAM system into the donor gNB2. It should be noted that the S850 is similar to the S750, and for the sake of brevity, the present application will not repeat them here.

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

For example, since the current VMR communicates through the donor gNB2, the donor gNB2 sends the S-TAI of the VMR to the AMF that has 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 VMR to the UE AMF2 network element and the VMR AMF2 network element. For the S-TAI of the VMR, reference may be made to the description in FIG. 5 , which will not be repeated here.

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

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

Optionally, in a possible implementation manner, the configuration update message 2 may only include the S-TAI information of the VMR, that is, not include the VMR indication information. Wherein, the S-TAI includes specific information, and through the specific information, the UE AMF2 network element and the VMR AMF2 network element can identify that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR. Or, in another possible implementation, the network side (CN) defines a VMR-specific TAI list for the VMR, then the UE AMF2 network element and the VMR AMF2 network element belong to the TAI list according to the S-TAI, thereby identifying that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR.

S870. Donor gNB1 sends configuration update message 3 to VMR AMF1 and UE AMF1. Correspondingly, VMR AMF1 and UE AMF1 receive configuration update message 3 sent by donor gNB1.

For example, the configuration update message 3 is used to instruct all AMFs (UE AMF1 network element and VMR AMF1 network element) connected to the donor gNB1 to delete the S-TAI, or it can also be said that the configuration update message 3 is used to instruct all AMFs connected to the donor gNB1 to delete the association relationship between the S-TAI and the donor gNB1 or CU1 in the donor gNB1. At this point, the VMR AMF1 and the UE AMF1 delete the association between the S-TAI of the VMR and the donor gNB1 according to the received configuration update message 3, which contains the identifier of the donor gNB1 (eg gNB ID1). It can be understood that the donor gNB1 notifies all AMFs connected to it that a VMR is left under the jurisdiction of the donor gNB1, and the tracking area information of the VMR is S-TAI. Then it means that all AMFs (UE AMF1 and VMR AMF1) connected to donor gNB1 will not go to donor gNB1 for the subsequent processing of the VMR and UE corresponding to the S-TAI.

In a possible implementation, the configuration update message 3 includes the identification information (such as donor gNB2 ID) of the second network device, for example, the donor gNB1 notifies all AMFs connected to it (such as UE AMF1, VMR AMF1) that the target network device of the VMR handover is donor gNB2.

It should be noted that step S870 can also be executed after step S840. It can be understood that the VMR in step S840 is switched from donor gNB1 to donor gNB2, which can trigger donor gNB1 in step S870 to send a configuration update message 3 to the UE AMF1 network element and the VMR AMF1 network element. It should be understood that the embodiment of the present application does not limit the execution sequence here.

S880, UE AMF 1 selects UE AMF 2 connected to donor gNB 2 to provide services for the UE according to the identification information of the second network device included in the received configuration update message 3.

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

S890, UE AMF1 and UE AMF2 perform context migration.

In a possible implementation, the UE AMF 1 requests the UE AMF 2 to establish a UE context through the Namf_Communication_Create UE Context service, where the UE context includes indication information that the UE is served by the VMR, specifically, the indication information may be a direct indication identification information.

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

As another example, when the network side (CN) divides the TAI, the specific TAI is used as the TAI dedicated to the VMR. It can be understood that when the TAI belongs to a specific S-TAI, it indicates that the S-TAI is the tracking area information of the VMR, that is, the UE is served by the VMR. Then the AMF network element can judge that the UE is served by the VMR according to the S-TAI of the UE.

Or, in a possible implementation, the UE AMF 1 instructs the UE AMF 2 to obtain the UE context from the UE AMF 1 through the Namf_Communication_UE Context Transfer service. Wherein, the UE context includes indication information that the UE is served by the VMR. And the indication information that UE AMF 1 instructs UE AMF 2 to obtain the UE context may also include the identification information of the target AMF (for example, UE AMF 1).

It should be noted that the indication information may be direct indication identification information. For example, if the indication information is set to "1" or "TRUE", it means that the UE is served by the VMR; if the indication information is set to "0" or "FALSE", it means that the UE is not served by the VMR.

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 in step S870, it recognizes that donor gNB 1 no longer provides services for the VMR corresponding to the S-TAI, and donor gNB2 provides services for the VMR. Since UE AMF 1 and donor gNB2 cannot be connected (perhaps due to load balancing considerations), UE AMF1 selects the target UE AMF, namely UE AMF 2, according to donor gNB2 to provide services for UE. Subsequently, since UE AMF1 deduces that the UE corresponding to the S-TAI has moved out of its service range, UE AMF1 needs to migrate the context of the corresponding UE to UE AMF 2.

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

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

S8110. The UE AMF 2 allocates a temporary number (5G-globally unique temporary identifier, 5G-GUTI) for the UE to identify the user identity globally, initiates a 5G-GUTI update process, and registers with the UDM.

In the technical solution of the embodiment of this application, when the VMR accesses the donor gNB1, the VMR AMF and the UE AMF1 connected to the donor gNB1 save the association relationship between the VMR's S-TAI and the donor gNB1. When the VMR is switched from donor gNB1 to donor gNB2, VMR AMF1 and UE AMF1 delete the previously saved association between the S-TAI of VMR and donor gNB1, and obtain the identification information (ID) of donor gNB2 from donor gNB1. Through this technical solution, the network side can be informed in time that the network device associated with the VMR has been changed to donor gNB2, and then when the network side needs to page the VMR and/or the UE served by the VMR, it can accurately locate the donor gNB2 associated with the VMR, and when the network side pages the VMR and/or the UE served by the VMR, the network side instructs other network devices (such as donor gNB1) to send paging messages, so that the network side can more accurately respond The UE performs mobility management and avoids waste of resources.

9 is a schematic flowchart of a communication method 900 provided by the embodiment of the present application. It should be noted that the method 900 mainly corresponds to the second scenario described above, that is, during the moving process of the VMR switching from donor gNB1 to donor gNB2, the access and mobility management function network element is replaced, that is, the access and mobility management function network element (such as UE AMF1, VMR AMF1) is connected to the donor gNB1, and the access and mobility management function network Elements (such as UE AMF2, VMR AMF2) are connected to donor NB2, where UE AMF1 and VMR AMF1 can be the same AMF, UE AMF2 and VMR AMF2 can be the same AMF (that is, the interaction between the two AMFs can be realized through internal interaction), or they can be different AMFs. The UE AMF and the VMMR AMF are different AMFs as an example for description below. The method at least includes the following steps.

S910, the VMR registers with the network (CN), and establishes a PDU session.

It should be noted that S910 is similar to S810, and for the sake of brevity, the present application will not repeat them here.

S920, donor gNB1 sends the S-TAI and VMR identification information (for example, VMR ID1) of the 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 and VMR identification information (for example, VMR ID1) of the VMR.

For example, since the current VMR communicates through the donor gNB1, the donor gNB1 sends the S-TAI of the VMR to the AMF that has established a connection with it. The AMF that has established a connection with the donor gNB1 includes UE AMF1 and VMR AMF1. Therefore, it can be understood that the donor gNB1 has sent the S-TAI and VMR identification information (such as VMR ID1) of the VMR to the UE AMF1 network element and the VMR AMF1 network element. For the S-TAI of the VMR, reference may be made to the description in FIG. 5 , which will not be repeated here.

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

Optionally, in a possible implementation manner, the configuration update message 1 includes the S-TAI of the VMR, VMR indication information, and VMR identification information (such as VMR ID1), the VMR indication information is used to indicate the UE AMF1 network element and the VMR AMF1 network element. The S-TAI is specific tracking area information of the VMR. Donor gNB1 notifies 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 the VMR through configuration update message 1 (Ran configuration update1).

Optionally, in a possible implementation manner, the configuration update message 1 may also only include the S-TAI information of the VMR and the VMR identification information (such as VMR ID1), that is, no VMR indication information. Wherein, the S-TAI includes specific information, and through the specific information, the UE AMF1 network element and the VMR AMF1 network element can identify that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR. Or, in another possible implementation, the network side (CN) defines a VMR-specific TAI list for the VMR, then the UE AMF1 network element and the VMR AMF1 network element belong to the TAI list according to the S-TAI, thereby identifying that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR.

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

For example, the VMR AMF1 determines that it serves the VMR according to the VMR identification information (such as the VMR ID1) in the S920, so that the VMR AMF 1 registers the association relationship between the donor NB 1 and the S-TAI in the UDR. The registration message includes donor gNB1ID (or RAN1ID) and S-TAI. However, other AMFs that receive the message in step S920 judge that they do not serve the VMR, and may not need to register the association relationship with the UDR.

It should be noted that the above registration message may not include the VMR ID.

It should be understood that the association relationship may be the association relationship between the donor gNB1 and the S-TAI of the VMR, or the association relationship between the CU1 located in the donor gNB1 and the S-TAI of the VMR, which is not limited in this embodiment of the present application.

S940, the UE registers in the network through the VMR, and the UE AMF1 performs access and mobility management on the VMR. The UE AMF1 locates within the area where the S-TAI information is located according to the location information of the UE, and learns that the UE is served by the VMR. At this time, the UE AMF1 allocates the S-TAI as the TAI List of the UE. On the contrary, UE AMF1 learns that the UE is not served by the VMR according to the fact that the location information of the UE is not located within the area where the S-TAI information is located. Then, when UE AMF1 allocates a TAI List for a UE not served by the VMR, the TAI List does not include S-TAI.

S950, VMR switches from donor gNB1 to donor gNB2.

S960. The VMR registers the S-TAI obtained from the OAM system into the donor gNB2.

It should be noted that S940-S960 is similar to S840-S860, and for the sake of brevity, the present application will not repeat them here.

S970, the donor NB2 sends the S-TAI and VMR identification information (for example, VMR ID1) of the VMR to the UE AMF2 network element and the VMR AMF2 network element, and correspondingly, the UE AMF2 network element and the VMR AMF2 network element receive the S-TAI and VMR identification information (for example, VMR ID1) of the VMR.

For example, since the current VMR communicates through the donor gNB2, the donor gNB2 sends the S-TAI of the VMR to the AMF that has established a connection with it. The AMF that has established a connection with the donor gNB2 includes UE AMF2 and VMR AMF2. Therefore, it can be understood that the donor gNB2 has sent the S-TAI of the VMR and the VMR identification information (such as VMR ID1) to the UE AMF2 network element and the VMR AMF2 network element. For the S-TAI of the VMR, reference may be made to the description in FIG. 5 , which will not be repeated here.

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

Optionally, in a possible implementation manner, the configuration update message 2 includes the S-TAI of the VMR, VMR indication information, and VMR identification information (such as VMR ID1), the VMR indication information is used to indicate the UE AMF2 network element and the VMR AMF2 network element. The S-TAI is specific tracking area information of the VMR. Donor gNB2 informs all AMFs connected to donor gNB2 (including UE AMF2 and VMR AMF2) that there is a VMR within its jurisdiction and the tracking area information (S-TAI) of the VMR through the configuration update message 2 (Ran configuration update2).

Optionally, in a possible implementation manner, the configuration update message 2 may only include the S-TAI information of the VMR and the VMR identification information (for example, VMR ID1), that is, the VMR indication information is not included. Wherein, the S-TAI includes specific information, and through the specific information, the UE AMF2 network element and the VMR AMF2 network element can identify that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR. Or, in another possible implementation, the network side (CN) defines a VMR-specific TAI list for the VMR, then the UE AMF2 network element and the VMR AMF2 network element belong to the TAI list according to the S-TAI, thereby identifying that the S-TAI is specific tracking area information (S-TAI) dedicated to the VMR.

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

For example, the VMR AMF2 determines that it serves the VMR according to the VMR identification information (such as VMR ID1) in the S970, so that the VMR AMF 2 registers the association relationship between the donor NB 2 and the S-TAI in the UDR. The registration message includes donor gNB2 ID (or RAN2 ID) and S-TAI. However, other AMFs that receive the message in step S970 judge that they do not serve the VMR, and do not need to register the association relationship with the UDR.

It should be noted that the above registration message may not include VMR identification information (for example, VMR ID1).

It should be understood that the association relationship may be the association relationship between the donor NB2 and the S-TAI of the VMR, or the association relationship between the CU2 located in the donor NB2 and the S-TAI of the VMR, which is not limited in this embodiment of the present application.

S990, donor gNB1 sends configuration update message 3 to VMR AMF1 and UE AMF1, and correspondingly, VMR AMF1 and UE AMF1 receive configuration update message 3 sent by donor gNB1.

It should be noted that step S990 can also be executed after step S950, and it can be understood that the VMR in step S950 is switched from donor gNB1 to donor gNB2, which can trigger donor gNB1 in step S990 to send a configuration update message 3 to the UE AMF1 network element and the VMR AMF1 network element. It should be understood that the embodiment of the present application does not limit the execution sequence here.

S9100. The VMR AMF1 sends a request message to the UDR, where the request message is used to request the UDR to delete the association relationship between the donor gNB1 and the S-TAI information. Correspondingly, the UDR receives the request message, and deletes the association between donor gNB1 and S-TAI information according to the request message.

It should be noted that step S990 can be used to trigger step S9100. In step S990, donor gNB1 sends a configuration update message 3 to VMR AMF1 and UE AMF1, and the configuration update message 3 is used to indicate to delete the association relationship between donor gNB1 and S-TAI information. Optionally, in a possible implementation manner, the configuration update message 3 may include VMR identification information (such as VMR ID1), and the VMR AMF1 determines that it serves the VMR according to the VMR identification information (such as VMR ID1), thereby triggering the 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.

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

S9110, UE AMF1 sends a query message to the UDR, where the query message is used to query the network device associated with the S-TAI information. Correspondingly, the UDR receives the query message.

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 the VMR is donor NB2 according to the S-TAI carried in the received query message.

For another example, UE AMF1 utilizes the general query service of UDR, UE AMF 1 carries the query target type as gNB (or RAN) in the query message, and the query index is S-TAI, so that UDR determines that the network device associated with the tracking area information (S-TAI) of the VMR is donor gNB2.

It should be noted that step S9110 can be triggered by step S990, that is, after UE AMF1 deletes the association relationship between the tracking area information of the VMR and the donor NB1 according to the received configuration update message 3, it can be judged 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 tracking area information of the VMR. Then, UE AMF1 will send a query message to the UDR to query the VMR. Which one is the tracking area information associated with the new network device.

S9120, the UDR sends a response message to the UE AMF1, and the response message includes the identification information of the second network device (for example, donor NB2 ID), and correspondingly, the UE AMF1 receives the response message sent by the UDR.

S9130, UE AMF 1 determines that the network device associated with the S-TAI is donor gNB2 according to the received response message, and further selects UE AMF2 connected to donor gNB2 to provide services for the UE.

After the UDR determines that the network device associated with the tracking area information (S-TAI) of the VMR is donor gNB2, the UDR sends a response message to the UE AMF1, and the response message includes the identification information of the donor gNB2 (such as donor gNB2 ID or RAN2 ID), that is, the UDR informs the UE AMF1 that the network device associated with the tracking area information (S-TAI) of the VMR is donor gNB2.

It should be noted that before S9130, donor gNB2 interacts with all connected AMF network elements, including UE AMF2 mentioned above, but it should be noted that before S9130, no specific AMF is determined to provide services for UE to replace UE AMF1, that is, before S9130, it is not determined that UE AMF2 provides services for UE.

S9140, UE AMF1 and UE AMF2 perform context migration. It should be noted that the S9140 is similar to the S890, and for the sake of brevity, the present application will not repeat them here.

It should also be noted that step S9140 may be triggered by steps S990 and S9120, that is, after UE AMF 1 receives the configuration update message 3 in step S990, it recognizes that donor gNB 1 no longer provides services for the VMR corresponding to the S-TAI. According to the identification information of donor gNB2 contained in the response message in step 9120, UE AMF1 determines that donor gNB2 will provide services for VMR at this time. Since UE AMF 1 and donor gNB2 cannot be connected (perhaps due to load balancing considerations), donor gNB2 selects the target UE AMF, that is, UE AMF 2, to provide services for UE. Subsequently, since UE AMF1 deduces that the UE corresponding to the S-TAI has moved out of its service range, UE AMF1 needs to migrate the context of the corresponding UE to UE AMF 2.

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

For example, UE AMF 2 requests the corresponding SMF network element to update the SM context of the PDU session according to the PDU session identifier and SMF information in the context information in S9140, and the SMF replaces UE AMF 1 with UE AMF2.

S9160, UE AMF 2 allocates 5G-GUTI for UE, initiates 5G-GUTI update process, and registers to UDM.

In the technical solution of the embodiment of this application, when the VMR switches from donor gNB1 to donor gNB2, the AMF (UE AMF2, VMR AMF2) connected to donor gNB2 registers the association relationship between donor gNB2 and S-TAI with UDR, but the VMR AMF1 connected to donor gNB1 requests UDR to delete the saved relationship between donor gNB1 and S-TAI Then the UE AMF1 connected to donor gNB1 will learn from UDR that the donor gNB2 is associated with S-TAI. Through this technical solution, the network side can be informed in a timely manner that the network device associated with the S-TAI of the VMR has been changed to donor gNB2, and then when the network side needs to page the VMR and/or the UE served by the VMR, it can accurately locate the donor gNB2 associated with the VMR, and there will be no situation where the network side instructs other network devices (such as donor gNB1) to send paging messages when the network side pages the VMR and/or the UE served by the VMR. The side performs mobility management on the UE more accurately, and avoids waste of resources.

The various embodiments described herein may be independent solutions, or may be combined according to internal logic, and these solutions all fall within the protection scope of the present application.

It can be understood that, in the foregoing method embodiments, the methods and operations implemented by each device or network element may also be implemented by components (such as chips or circuits) of the corresponding device or network element.

The foregoing mainly introduces the solutions provided by the embodiments of the present application from the perspectives of various interactions. It can be understood that each network element, such as a transmitting end device or a receiving end device, includes a corresponding hardware structure and/or software module for performing each function in order to realize the above functions. Those skilled in the art should be aware that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

The embodiment of the present application can divide the function modules of the sending end device or the receiving end device according to the above method example, for example, each function module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation. In the following, the description will be made by taking the division of each functional module corresponding to each function as an example.

It should be understood that the specific examples in the embodiments of the present application are only for helping those skilled in the art to better understand the embodiments of the present application, rather than limiting the scope of the embodiments of the present application.

It should be understood that in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Above, the method provided by the embodiment of the present application is described in detail with reference to FIG. 5 to FIG. 9 . Hereinafter, the device provided by the embodiment of the present application will be described in detail with reference to FIG. 10 to FIG. 13 . It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments. Therefore, for details that are not described in detail, reference may be made to the method embodiments above. For brevity, details are not repeated here.

Fig. 10 shows a schematic block diagram of an access and mobility management functional network element 1000 according to an embodiment of the present application. It should be understood that the access and mobility management functional network element 1000 includes a receiving unit 1010 , a processing unit 1020 and a sending unit 1030 .

The receiving unit 1010 is configured to receive the tracking area information of the first device from the first network device; the processing unit 1020 is configured 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.

In a possible implementation manner, the access and mobility management functional network element is connected to the first network device and the second network device, and 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: store the tracking area information of the first device and an association relationship between the second network device.

In a possible implementation manner, the processing unit 1020 is specifically configured to: delete the association relationship between the tracking area information of the first device and the first network device according to the tracking area information of the first device received from the second network device.

In a possible implementation manner, 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 association relationship between the tracking area information of the first device and the first network device according to the first indication information.

In a possible implementation manner, the first indication information includes identification information of the second network device.

In a possible implementation manner, 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 1030, configured to send first registration information to a unified database network element, where the first registration information is used to register with the unified database network element the tracking area information of the first device and the association relationship between the first network device.

In a possible implementation manner, the sending unit 1030 is further configured to: send first request information to the unified database network element, where the first request information is used to request the unified database network element to delete the tracking area information of the first device and the association relationship between the first network device.

In a possible implementation manner, the sending unit 1030 is further configured to: send first query information to the unified database network element, where the first query information is used to query the unified database network element for a network device associated with the tracking area information of the first device; the receiving unit is also configured to: receive first response information sent by the unified database network element, where the first response information includes identification information of the second network device.

Fig. 11 shows a schematic block diagram of an access and mobility management functional network element 1100 according to an embodiment of the present application. It should be understood that the access and mobility management functional network element 1100 includes a receiving unit 1110 , a processing unit 1120 , and a sending unit 1130 .

The receiving unit 1110 is configured to receive the tracking area information of the first device from the second network device; the processing unit 1120 is configured to store the tracking area information of the first device and the association relationship between the second network device; the sending unit 1130 is configured to send second registration information to a unified database network element, and 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 with the unified database network element.

Fig. 12 shows a schematic block diagram of a network device 1200 according to an embodiment of the present application. It should be understood that the network device 1200 includes a receiving unit 1210 and a sending unit 1220 .

The receiving unit 1210 is configured to obtain the tracking area information of the first device from the first device; the sending unit 1220 is configured to send the tracking area information of the first device to a connected access and mobility management functional network element.

In a possible implementation manner, the sending unit 1220 is further configured to: send first indication information to the connected access and mobility management function network element, where the first indication information is used to indicate to delete the association relationship between the tracking area information of the first device and the network device.

Fig. 13 shows a schematic block diagram of a unified database network element 1300 according to an embodiment of the present application. 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 .

The receiving unit 1310 is configured to receive second registration information from the first access and mobility management functional 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 processing unit 1320 is configured to save the tracking area information of the first device and the association relationship between 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 access and mobility management function network element, where the first query information is 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 access and mobility management function network element, where the first response information includes identification information of the second network device.

In a possible implementation manner, the receiving unit 1310 is further configured to: the unified database network element receives first registration information from the first access and mobility management functional network element, where the first registration information is used to register the tracking area information of the first device and the association relationship between 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 between the first network device according to the first registration information.

In a possible implementation manner, the receiving unit 1310 is further configured to: receive first request information from the first access and mobility management functional network element, where the first request information is used to request deletion of the tracking area information of the first device and the association relationship between the first network device.

It should be understood that the above division of units in the communication device is only a division of logical functions, and may be fully or partially integrated into a physical entity or physically separated during actual implementation. In addition, the units in the communication device can be implemented in the form of software calling through the processing elements; they can also be implemented in the form of hardware; some units can also be implemented in the form of software calling through the processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separate processing element, or can be integrated into a certain chip of the communication device, and can also be stored in the memory in the form of a program, and the function of the module can be called and executed by a certain processing element of the communication device. In addition, all or part of these units can be integrated together, or implemented independently. The processing element mentioned here may also be a processor, which may be an integrated circuit with signal processing capabilities. In the process of implementation, each step of the above method or each unit above may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software called by the processing element.

In one example, the unit in any communication device or network element can be configured to be configured to implement one or more integrated circuits that implement the above methods, such as: one or more specific integrated circuits (Application SPECIFICIFIC Integrated Circuit, ASIC), or one or more microprocessors (Digital Singna) l Processor, DSP), or one or more on -site programming door array (FPGA), or at least two combinations of these integrated circuits. For another example, when the unit in the communication device or network element can be implemented in the form of a processing element scheduler, the processing element can be a general processor, such as a central processing unit (central processing unit, CPU) or other processors that can call programs. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

Referring to FIG. 14 , it is a schematic diagram of a communication device provided by the embodiment of the present application, which is used to realize the operation of the access and mobility management function network element, network equipment, and unified database network element in the above embodiment. As shown in FIG. 14 , the communication device includes: a processor 1410 and an interface 1430 , and the processor 1410 is coupled to the interface 1430 . The interface 1430 is used to communicate with other devices. Interface 1430 may be a transceiver or an input-output interface. Interface 1430 may be, for example, an interface circuit. Optionally, the communication device further includes a memory 1420 for storing instructions executed by the processor 1410 or storing input data required by the processor 1410 to execute the instructions or storing data generated after the processor 1410 executes the instructions.

The method performed by the access and mobility management function network element, the network device, and the unified database network element in the above embodiments may be implemented by the processor 1410 calling a program stored in a memory (which may be the memory 1220 in the access and mobility management function network element, network device, and unified database network element, or may be an external memory). That is, the access and mobility management function network element, network device, and unified database network element may include a processor 1410, and the processor 1410 executes the method performed 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 the memory. The processor here may be an integrated circuit with signal processing capabilities, such as a CPU. Access and mobility management functional network elements, network devices, and unified database network elements can be realized by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or one or more microprocessors DSP, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Alternatively, the above implementation manners may be combined.

Specifically, the functions/implementation process of each unit in FIG. 10 to FIG. 13 can be implemented by calling the computer-executable instructions stored in the memory 1420 by the processor 1410 in the communication device 1400 shown in FIG. 14 . Alternatively, the function/implementation process of the processing unit in FIG. 10 to FIG. 13 can be realized by the processor 1410 in the communication device 1400 shown in FIG.

It should be understood that the processing unit in the above device includes a processor, the processor is coupled with the memory, the memory is used to store computer programs or instructions and/or data, and the processor is used to execute the computer programs or instructions and/or data stored in the memory, so that the methods in the above method embodiments are executed.

It should also be understood that the division of units in the above device is only a division of logical functions, and may be fully or partially integrated into a physical entity or physically separated during actual implementation. And the units in the device can all be implemented in the form of software called by the processing element; they can also be implemented in the form of hardware; some units can also be implemented in the form of software called by the processing element, and some units can be implemented in the form of hardware. For example, each unit may be an independently established processing element, or may be integrated into a certain chip of the device. In addition, it may also be stored in the memory in the form of a program, and the function of the unit may be invoked and executed by a certain processing element of the device. Here, the processing element may also be referred to as a processor, which may be an integrated circuit with signal processing capability. In the process of implementation, each step of the above method or each unit above may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software called by the processing element.

The embodiment of the present application also provides a communication system, which includes: the above-mentioned access and mobility management function network element, network equipment, and unified database network element.

The embodiment of the present application also provides a computer-readable medium for storing computer program codes, where the computer program includes instructions for executing the communication method in the embodiment of the present application among the above methods. The readable medium may be a read-only memory (read-only memory, ROM) or a random access memory (random access memory, RAM), which is not limited in this embodiment of the present application.

The present application also provides a computer program product. The computer program product includes instructions. When the instructions are executed, the access and mobility management function network element, the network device, and the unified database network element perform operations corresponding to the access and mobility management function network element, the network device, and the unified database network element.

The embodiment of the present application also provides a system chip. The system chip includes: 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, a pin, or a circuit. The processing unit can execute computer instructions, so that the chip in the communication device executes any communication method provided by the above-mentioned embodiments of the present application.

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

Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit in the terminal located outside the chip, such as a ROM or other types of static storage devices that can store static information and instructions, RAM, etc. Wherein, the processor mentioned in any one of the above places may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for program execution for controlling the transmission method of the above feedback information. The processing unit and the storage unit can be decoupled, respectively arranged on different physical devices, and connected by wire or wirelessly to realize the respective functions of the processing unit and the storage unit, so as to support the system chip to realize various functions in the above-mentioned embodiments. Alternatively, the processing unit and the memory can also be coupled to the same device.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Wherein, the non-volatile memory may be ROM, programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory can be RAM, which acts as external cache memory. There are many different types of RAM, such as static random access memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. 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 implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or the part that contributes to the prior art or a part of the technical solution. The computer software product is stored in a storage medium and includes several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the application. The aforementioned storage medium includes: various media that can store program codes such as U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk.

The above is only a specific embodiment of the application, but the scope of protection of the application is not limited thereto. Anyone skilled in the art within the scope of the technology disclosed in this application can easily think of changes or replacements, which should be covered within the scope of protection of the application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A communication method, characterized in that, comprising:

The access and mobility management function network element receives the tracking area information of the first device from the first network device;

The access and mobility management function network element saves the tracking area information of the first device and the association relationship between the first network device;

When the 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 method according to claim 1, wherein the access and mobility management function network element connects the first network device and the second network device, and the method further comprises:

receiving, by the access and mobility management functional network element, tracking area information of the first device from a second network device;

The access and mobility management function network element saves the tracking area information of the first device and the association relationship between the second network device.
The method according to claim 2, wherein the access and mobility management functional network element deletes the association relationship between the tracking area information of the first device and the first network device, comprising:

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 in response to the tracking area information of the first device received from the second network device.
The method according to claim 1 or 2, characterized in that the method further comprises:

The access and mobility management functional network element receives first indication information from the first network device;

The access and mobility management functional network element deleting the association relationship between the tracking area information of the first device and the first network device includes:

The access and mobility management functional network element deletes the association relationship between the tracking area information of the first device and the first network device according to the first indication information.
The method according to claim 4, wherein the first indication information includes identification information of the second network device.
The method according to claim 1, wherein the access and mobility management functional network element is connected to the first network device, and the method further comprises:

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

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

The access and mobility management function network element sends first query information to the unified database network element, and the first query information is used to query the unified database network element for a network device associated with the tracking area information of the first device;

The access and mobility management function network element receives the first response information sent by the unified database network element, where the first response information includes the identification information of the second network device.
A communication method, characterized in that, comprising:

The network device obtains 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 functional network element.
The method according to claim 9, characterized in that the method further comprises:

The network device sends first indication information to the connected access and mobility management function network element, where the first indication information is used to indicate to delete the association relationship between the tracking area information of the first device and the network device.
A communication method, characterized in that, comprising:

The unified database network element receives second registration information from the first access and mobility management functional network element, where the second registration information is used to register an association relationship between the tracking area information of the first device and the second network device;

The unified database network element saves the association relationship between the tracking area information of the first device and the second network device according to the second registration information.

The unified database network element receives first query information from a second access and mobility management function network element, and the first query information is used to query the network device associated with the tracking area information of the first device;

The unified database network element sends first response information to the second access and mobility management functional network element, where the first response information includes identification information of the second network device.
The method according to claim 11, characterized in that the method further comprises:

The unified database network element receives first registration information from the first access and mobility management function network element, and the first registration information is used to register the tracking area information of the first device and the association relationship between the first network device;

The association relationship between the tracking area information of the first device and the first network device is stored according to the first registration information.
The method according to claim 12, characterized in that the method further comprises:

The unified database network element receives first request information from the first access and mobility management function network element, where the first request information is used to request to delete the association relationship between the tracking area information of the first device and the first network device.
The method according to any one of claims 1 to 13, characterized in that the first device comprises a vehicle-mounted relay device VMR.
The method according to any one of claims 1 to 13, characterized in that the tracking area information of the first device does not change as the access location of the first device changes.
An access and mobility management function network element, characterized in that it includes:

a receiving unit, configured to receive tracking area information of the first device from the first network device;

a processing unit, configured to store the tracking area information of the first device and the association relationship between the first network device;

In a case where the second network device serves the first device, the processing unit deletes the association relationship between the tracking area information of the first device and the first network device.
The access and mobility management functional network element according to claim 16, wherein the access and mobility management functional network element is connected to 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 a 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.
The access and mobility management function network element according to claim 17, wherein the processing unit is specifically used for:

In response to the tracking area information of the first device received from the second network device, delete the association relationship between the tracking area information of the first device and the first network device.
The access and mobility management function network element according to claim 16 or 17, characterized in that,

The receiving unit is further configured to: receive first indication information from the first network device;

The processing unit is specifically configured to: delete the association relationship between the tracking area information of the first device and the first network device according to the first indication information.
The access and mobility management functional network element according to claim 19, wherein the first indication information includes identification information of the second network device.
The access and mobility management function network element according to claim 16, wherein 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, configured to send first registration information to a unified database network element, where the first registration information is used to register an association relationship between the tracking area information of the first device and the first network device with the unified database network element.
The access and mobility management function network element according to claim 21, characterized in that,

The sending unit is further configured to: send first request information to the unified database network element, where the first request information is used to request the unified database network element to delete the association relationship between the tracking area information of the first device and the first network device.
The access and mobility management function network element according to claim 21 or 22, characterized in that,

The sending unit is further configured to: send first query information to the unified database network element, where the first query information is used to query the unified database network element for a network device 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, where the first response information includes identification information of the second network device.
A network device, characterized in that it includes:

a receiving unit, configured to obtain tracking area information of the first device from the first device;

A sending unit, configured to send the tracking area information of the first device to a connected access and mobility management functional network element.
The network device according to claim 24, characterized in that,

The sending unit is further configured to: send first instruction information to the connected access and mobility management functional network element, where the first instruction information is used to instruct to delete the association relationship between the tracking area information of the first device and the network device.
A unified database network element, characterized in that it includes:

A receiving unit, configured to receive second registration information from the first access and mobility management functional network element, where 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;

A processing unit, configured to save an association relationship between the tracking area information of the first device and the second network device according to the second registration information.

The receiving unit is further configured to receive first query information from a second access and mobility management functional network element, where the first query information is used to query the network device associated with the tracking area information of the first device;

A sending unit, configured to send first response information to the second access and mobility management functional network element, where the first response information includes identification information of the second network device.
The unified database network element according to claim 26, characterized in that,

The receiving unit is further configured to: the unified database network element receives first registration information from the first access and mobility management function network element, and the first registration information is used to register the tracking area information of the first device and the association relationship between the first network device;

The processing unit is further configured to: store the tracking area information of the first device and the association relationship between the first network device according to the first registration information.
The unified database network element according to claim 27, characterized in that,

The receiving unit is further configured to: receive first request information from the first access and mobility management functional network element, where the first request information is used to request deletion of the association relationship between the tracking area information of the first device and the first network device.
The apparatus according to any one of claims 16 to 28, wherein the first device comprises a vehicle-mounted relay device VMR.
The apparatus according to any one of claims 16 to 28, wherein the tracking area information of the first device does not change as the access location of the first device changes.
A communication device, characterized in that it includes an access and mobility management function network element, a network device, and a unified database network element,

The access and mobility management functional network element is used to execute the method according to any one of claims 1 to 8; or,

The network device is configured to perform the method as claimed in claim 9 or 10; or,

The unified database network element is used to execute the method according to any one of claims 11-15.
A computer-readable storage medium, wherein the computer storage medium stores program instructions, and when the instructions are executed, the access and mobility management functional network element can execute the method according to any one of claims 1 to 8; or,

When the instruction is executed, the network device can execute the method according to claim 9 or 10; or,

When the instructions are executed, the unified database network element can execute the method according to any one of claims 11-15.