Method and apparatus for communicating

Abstract

The application provides a method and device for communication, the method comprising: a data analysis network element obtaining a plurality of tracking area (TA) information from a first core network element; and the data analysis network element generating network topology information according to the plurality of TA information, wherein the network topology information comprises an association relationship between the plurality of TA. By obtaining data from the data analysis network element to generate network topology information, the effect of network operation can be optimized.

Description

Technical Field

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

[0002] Network topology information is crucial for network operation, and currently, it is mostly added to interconnected network devices through configuration. However, 5G mobile communication systems have a large number of network devices and a significantly increased number of cells, resulting in a more complex network topology.

[0003] Existing methods for obtaining network topology information in 5G mobile communication network systems have limited capacity to acquire such information, which can affect the effectiveness of optimizing network operation based on the topology. Summary of the Invention

[0004] This application provides a communication method that can obtain network topology information to improve network optimization performance.

[0005] Firstly, a communication method is provided, the communication method comprising:

[0006] The data analysis network element acquires multiple tracking area (TA) information from the first core network element; the data analysis network element generates network topology information based on the multiple TA information, and the network topology information includes the correlation between the multiple TAs.

[0007] The communication method provided in this application embodiment allows data analysis network elements to obtain multiple TA information and generate network topology information based on the multiple TA information, which can optimize the network operation effect.

[0008] In conjunction with the first aspect, in certain implementations of the first aspect, the association relationships between the multiple TAs include at least one of the following: the association relationships between the frequency bands supported by the multiple TAs, the association relationships between the network slices supported by the multiple TAs, the association relationships between the geographical locations of the multiple TAs, and the adjacency relationships between the multiple TAs. Specifically, the association relationships between the frequency bands supported by the multiple TAs include: frequency bands or frequency band lists supported by each TA, a list of TAs supporting the same frequency band, inter-frequency handover relationships between TAs, and intra-frequency handover relationships between TAs. The association relationships between the network slices supported by the multiple TAs include: a list of TAs supporting the same network slice, and a list of frequency bands supported by the network slices supported by the TAs. The association relationships between the geographical locations of the multiple TAs include: a list of geographical grids for each TA, overlapping geographical areas, partially overlapping geographical areas, geographical adjacency, and geographical non-adjacency. The adjacency relationships between the multiple TAs include: non-adjacency, adjacency during connected state handover, and adjacency during idle state reselection handover.

[0009] The network topology information mentioned above includes various forms of relationships between multiple TAs, which can improve the flexibility of the solution.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the data analysis network element acquiring at least one of the following information: information of the serving cell of the terminal device, information of the neighboring cells of the serving cell, mobility information of the terminal device, and geographical location information of the terminal device.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the data analysis network element acquiring the minimized drive test (MDT) result of the terminal device, wherein the MDT result of the terminal device includes at least one of the following: information of the serving cell of the terminal device, neighboring cell information of the serving cell, mobility information of the terminal device, and geographical location information of the terminal device; the data analysis network element generating network topology information based on the plurality of TA information, including: the data analysis network element generating the network topology information based on the plurality of TA information and the MDT result of the terminal device.

[0012] The communication method provided in this application embodiment can also obtain the MDT information of the terminal device by the data analysis network element, and generate network topology information based on the multiple TA information and the MDT information of the terminal device, so that the generated network topology information is more conducive to network optimization.

[0013] In conjunction with the first aspect, in certain implementations of the first aspect, the information of the serving cell of the terminal device includes at least one of the following: the identifier of the access network equipment providing services to the terminal device, the identifier of the serving cell of the terminal device, the identifier of the TA to which the serving cell belongs, and the frequency band of the serving cell; the neighbor cell information of the serving cell includes at least one of the following: the identifier of the neighboring cell of the serving cell, the identifier of the TA to which the neighboring cell belongs, and the frequency band of the neighboring cell; the mobility information of the terminal device includes the adjacency relationship between the source cell of the terminal device before handover and the destination cell after handover and / or the type of handover.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the data analysis network element acquiring access network device-related information from the first core network element, the access network device-related information including the TA and frequency band of a first cell and the TA and frequency band of a second cell, wherein the first cell is a cell managed by the access network device, and the second cell is a cell managed by an access network device adjacent to the access network device; the data analysis network element generating network topology information based on the multiple TA information, including: the data analysis network element generating the network topology information based on the multiple TA information and the access network device-related information.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the data analysis network element acquiring access network device-related information from the access network device, the access network device-related information including at least one of the following: the geographical location of the access network device, the TA and frequency band of the first cell, the TA and frequency band of the second cell, and the network topology information of the location of the access network device, wherein the first cell is a cell managed by the access network device, the second cell is a cell managed by an adjacent access network device, and the network topology information of the location of the access network device includes the association relationship between multiple cells; the data analysis network element generating network topology information based on the multiple TA information, including: the data analysis network element generating the network topology information based on the multiple TA information and the access network device-related information.

[0016] The communication method provided in this application embodiment allows the data analysis network element to obtain information related to the access network device, and generate network topology information based on the multiple TA information and the access network device related information, making the generated network topology information more conducive to network optimization.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the network topology information includes the identifier of the TA and at least one of the following: the frequency band supported by the TA, the geographical location of the TA, or the TA adjacent to the TA.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the multiple TAs correspond to multiple cells, and the network topology information further includes the cell identifier corresponding to the cell and at least one of the following: the frequency band to which the cell belongs, the TA to which the cell belongs, the radio access network device to which the cell belongs, the cells adjacent to the cell, the first geographical location covered by the cell, the cells whose second geographical location is covered and adjacent to the first geographical location, and the cells whose third geographical location is covered and overlaps with the first geographical location.

[0019] The communication method provided in this application embodiment can include network topology information at the TA level (e.g., TA identifier, frequency bands supported by the TA, geographical location of the TA, or neighboring TAs), and can also include network topology information at the cell level (e.g., cell identifier, TA to which the cell belongs, radio access network device to which the cell belongs, neighboring cells of the cell, geographical location covered by the cell, relationship between geographical locations covered by different cells, etc.), indicating that this application can generate detailed network topology information.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the network data analysis network element performing terminal device mobility analysis or terminal device communication analysis to obtain analysis data; and the data analysis network element verifying the validity of the network topology information based on the analysis data.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, when the network topology information is invalid, the method further includes: the data analysis network element updating the network topology information.

[0022] The communication method provided in this application embodiment can verify the validity of the generated network topology information through the analysis data of the terminal device, thereby improving the accuracy of the solution.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the data analysis network element acquiring network slice information supported by each of the plurality of TAs from the first core network element; the data analysis network element generating network topology information based on the plurality of TAs information, including: the data analysis network element generating the network topology information based on the plurality of TAs information and the network slice information supported by each of the plurality of TAs.

[0024] The communication method provided in this application embodiment allows the data analysis network element to obtain network slice information supported by the TA, and generate network topology information based on multiple TA information and the network slice information supported by the TA, making the generated network topology information more conducive to network optimization.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, the network topology information further includes at least one of the following: network slices supported by the TA, frequency bands supported by the network slices supported by the TA, and network slices supported by the cell.

[0026] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the data analysis network element sending the network topology information to the second core network element, the network topology information being used by the second core network element to optimize the network.

[0027] The aforementioned network topology information can be used by the second core network elements to optimize the network and achieve the goal of network optimization.

[0028] In conjunction with the first aspect, in some implementations of the first aspect, the optimized network includes one or more of the following: the registration area of ​​the optimized terminal, the network slices allowed to be accessed, the network slices to be accessed, and the frequency band selection priority.

[0029] The optimized network involved in this application can be achieved through different technical means (such as optimizing the terminal's registration area, allowed network slices, target access network slices, frequency band selection priority, or one or more of these), thereby improving the flexibility of the solution.

[0030] Secondly, a mobile communication method is provided, the communication method comprising:

[0031] The second core network element obtains network topology information from the data analysis network element, which includes the relationships between multiple TAs; the second core network element optimizes the network based on this network topology information.

[0032] The communication method provided in this application embodiment enables the second core network element to perform network optimization based on network topology information, thereby achieving the purpose of network optimization.

[0033] In conjunction with the second aspect, in some implementations of the second aspect, the second core network element optimizes the network based on the network topology information, including: the second core network element optimizes the registration area of ​​the terminal device and / or optimizes the frequency band selection priority of the terminal device based on the network topology information.

[0034] The network optimization of the aforementioned second core network element can be achieved by optimizing the registration area of ​​the terminal device or by optimizing the frequency band selection priority of the terminal device. Different optimization methods can be used to optimize the network, thereby improving the flexibility of network optimization.

[0035] In conjunction with the second aspect, in some implementations of the second aspect, the second core network element optimizes the registration area of ​​the terminal device based on the network topology information, including: the second core network element removes TAs whose geographical locations can be contained within the geographical area formed by other TAs in the registration area based on the geographical location of the TA; and / or, the second core network element removes TAs that are not adjacent to any other TA in the registration area based on the TAs adjacent to the TA; the second core network element optimizes the frequency band selection priority of the terminal device based on the network topology information, including: the second core network element determines the frequency bands supported by as many TAs as possible in the registration area of ​​the terminal device and the corresponding frequency band selection priorities based on the frequency bands supported by the TA.

[0036] In conjunction with the second aspect, in some implementations of the second aspect, where the network topology information also includes network slice-related information, the second core network element optimizes the network based on the network topology information, including at least one of the following: the second core network element optimizes the registration area of ​​the terminal device, optimizes the list of network slices that the terminal device is allowed to access, optimizes the list of network slices that the terminal device is targeting to access, or optimizes the frequency band selection priority of the terminal device based on the network topology information.

[0037] The network optimization of the aforementioned second core network element can be achieved by optimizing the registration area of ​​the terminal device, optimizing the frequency band selection priority of the terminal device, optimizing the list of network slices that the terminal device is allowed to access, and optimizing the list of network slices that the terminal device is targeting to access. This demonstrates that different optimization methods can be used to optimize the network, thereby improving the flexibility of network optimization.

[0038] In conjunction with the second aspect, in certain implementations of the second aspect, the second core network element optimizes the registration area of ​​the terminal device based on the network topology information, including at least one of the following: the second core network element, based on the list of TAs supporting network slices and the geographical location of the TAs, forms the registration area of ​​the terminal device with TAs that are geographically consecutive and support the network slice; the second core network element, based on the list of TAs supporting network slices and the TAs adjacent to the TA, forms the registration area of ​​the terminal device with TAs that support the network slice; the second core network element, based on the list of network slices requested by the terminal and the list of TAs supporting network slices, determines the number of network slices requested by the terminal supported by the TA, and removes TAs from the registration area of ​​the terminal device whose number of TAs is different from that supported by other TAs in the registration area.

[0039] In conjunction with the second aspect, in some implementations of the second aspect, the second core network element optimizes the list of network slices that the terminal device is allowed to access based on the network topology information, including: the second core network element determines the list of network slices that the terminal is allowed to access based on the list of network slices requested by the terminal, the list of TAs supporting the network slices, and the TAs adjacent to the TAs.

[0040] In conjunction with the second aspect, in some implementations of the second aspect, the second core network element optimizes the list of network slices that the terminal device aims to access based on the network topology information, including: the second core network element determines the list of network slices that the terminal aims to access based on the list of network slices requested by the terminal, the list of TAs supporting the network slices, and the geographical location of the TAs.

[0041] In conjunction with the second aspect, in certain implementations of the second aspect, the second core network element optimizes the frequency band selection priority of the terminal device based on the network topology information, including: the second core network element determines the frequency band selection priority of the terminal based on the network slice list requested by the terminal, the TA list supporting the network slice, and the frequency bands supported by the network slices supported by the TA; and / or, the second core network element determines the frequency band selection priority of the terminal based on the network slice list requested by the terminal, the TA list supporting the network slice, the geographical location of the TA, and the frequency bands supported by the network slices supported by the TA.

[0042] Thirdly, a communication method is provided, which includes:

[0043] The access network device generates network topology information about its location based on the TA and frequency band of the first cell, the TA and frequency band of the second cell, the neighbor relationships between the first cells, and the neighbor relationships between the first and second cells. The access network device sends relevant information to the core network elements. This relevant information includes at least one of the following: the geographical location of the access network device, the TA and frequency band of the first cell, the TA and frequency band of the second cell, and the network topology information about the location of the access network device. The first cell is a cell managed by the access network device, and the second cell is a cell managed by an adjacent access network device. The network topology information includes the relationships between multiple cells.

[0044] The communication method provided in this application embodiment enables the access network device to generate network topology information of the location of the access network device based on the acquired data, thereby optimizing the network operation effect.

[0045] In conjunction with the third aspect, in some implementations of the third aspect, the network topology information of the location of the access network device includes cell-level topology information of one or more cells served by the access network device, wherein the cell-level topology information of the cell includes the cell identifier corresponding to the cell and at least one of the following: the frequency band to which the cell belongs, the TA to which the cell belongs, the radio access network device to which the cell belongs, the cells adjacent to the cell, the first geographical location covered by the cell, the cells to which the cell is covered by a second geographical location adjacent to the first geographical location, and the cells to which the cell is covered by a third geographical location overlapping the first geographical location.

[0046] In conjunction with the third aspect, in some implementations of the third aspect, the cell-level topology information of the cell also includes: the network slices supported by the cell.

[0047] Fourthly, a communication method is provided, which includes:

[0048] The first core network element acquires multiple tracking area (TA) information, which is used to generate network topology information, including the relationships between the multiple TAs; the first core network element then sends the multiple tracking area TA information to the data analysis network element.

[0049] The communication method provided in this application embodiment allows a first core network element to send multiple acquired TA information to a data analysis network element, which then generates network topology information based on the TA information, thereby optimizing network operation.

[0050] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: the first core network element acquiring information related to the access network device, the information related to the access network device being used to generate the network topology information; the first core network element sending the information related to the access network device to the data analysis network element, wherein the information related to the access network device includes the TA and frequency band to which the first cell belongs and the TA and frequency band to which the second cell belongs, the first cell being a cell managed by the access network device, and the second cell being a cell managed by an access network device adjacent to the access network device.

[0051] The communication method provided in this application embodiment allows a first core network element to send information related to the access network device to a data analysis network element. The data analysis network element then generates network topology information based on the TA information and the access network device information, making the generated network topology information more conducive to network optimization.

[0052] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: the first core network element acquiring network topology information from the data analysis network element; and the first core network element optimizing the network based on the network topology information.

[0053] The communication method provided in this application embodiment enables the first core network element to perform network optimization based on network topology information, thereby achieving the purpose of network optimization.

[0054] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first core network element optimizes the network based on the network topology information, including: the first core network element optimizes the registration area of ​​the terminal device and / or optimizes the frequency band selection priority of the terminal device based on the network topology information.

[0055] The network optimization of the first core network element mentioned above can be carried out by optimizing the registration area of ​​the terminal device or by optimizing the frequency band selection priority of the terminal device. Different optimization methods can be used to optimize the network, thereby improving the flexibility of network optimization.

[0056] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the first core network element optimizes the registration area of ​​the terminal device based on the network topology information, including: the first core network element removes TAs whose geographical locations can be contained within a geographical area formed by other TAs in the registration area based on the geographical location of the TA; and / or, the first core network element removes TAs that are not adjacent to any other TA in the registration area based on the TAs adjacent to the TA; the first core network element optimizes the frequency band selection priority of the terminal device based on the network topology information, including: the first core network element determines the frequency bands supported by as many TAs as possible in the registration area of ​​the terminal device and the corresponding frequency band selection priorities based on the frequency bands supported by the TA.

[0057] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the network topology information also includes network slice-related information. The first core network element optimizes the network based on the network topology information, including at least one of the following: the first core network element optimizes the registration area of ​​the terminal device, optimizes the list of network slices that the terminal device is allowed to access, optimizes the list of network slices that the terminal device is targeting to access, or optimizes the frequency band selection priority of the terminal device based on the network topology information.

[0058] The network optimization of the first core network element mentioned above can be achieved by optimizing the registration area of ​​the terminal device, optimizing the frequency band selection priority of the terminal device, optimizing the list of network slices that the terminal device is allowed to access, and optimizing the list of network slices that the terminal device is targeting to access. This shows that the network can be optimized through different optimization methods, thereby improving the flexibility of network optimization.

[0059] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the first core network element optimizes the registration area of ​​the terminal device based on the network topology information, including at least one of the following: the first core network element, based on the list of TAs supporting network slices and the geographical location of the TAs, forms the registration area of ​​the terminal device with TAs that are geographically consecutive and support the network slice; the first core network element, based on the list of TAs supporting network slices and the TAs adjacent to the TA, forms the registration area of ​​the terminal device with TAs that support the network slice; the first core network element, based on the list of network slices requested by the terminal and the list of TAs supporting network slices, determines the number of network slices requested by the terminal supported by the TA, and removes TAs from the registration area of ​​the terminal device whose number of TAs is different from that supported by other TAs in the registration area.

[0060] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first core network element optimizes the list of network slices that the terminal device is allowed to access based on the network topology information, including: the first core network element determines the list of network slices that the terminal is allowed to access based on the list of network slices requested by the terminal, the list of TAs that support the network slices, and the TAs adjacent to the TAs.

[0061] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second core network element optimizes the list of network slices that the terminal device aims to access based on the network topology information, including: the first core network element determines the list of network slices that the terminal aims to access based on the list of network slices requested by the terminal, the list of TAs that support the network slices, and the geographical location of the TAs.

[0062] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the first core network element optimizes the frequency band selection priority of the terminal device based on the network topology information, including: the first core network element determines the frequency band selection priority of the terminal based on the network slice list requested by the terminal, the TA list supporting the network slice, and the frequency bands supported by the network slices supported by the TA; and / or, the first core network element determines the frequency band selection priority of the terminal based on the network slice list requested by the terminal, the TA list supporting the network slice, the geographical location of the TA, and the frequency bands supported by the network slices supported by the TA.

[0063] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the network topology information includes the identifier of the TA and at least one of the following: the identifier of the TA, the frequency band supported by the TA, the geographical location of the TA, or the TA adjacent to the TA.

[0064] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the multiple TAs correspond to multiple cells, and the network topology information also includes the cell identifier corresponding to the cell and at least one of the following: the cell identifier corresponding to the cell, the frequency band to which the cell belongs, the TA to which the cell belongs, the radio access network device to which the cell belongs, the cells adjacent to the cell, the first geographical location covered by the cell, the cells whose second geographical location is covered and adjacent to the first geographical location, and the cells whose third geographical location is covered and overlaps with the first geographical location.

[0065] The communication method provided in this application embodiment can include network topology information at the TA level (e.g., TA identifier, frequency bands supported by the TA, geographical location of the TA, or neighboring TAs), and can also include network topology information at the cell level (e.g., cell identifier, TA to which the cell belongs, radio access network device to which the cell belongs, neighboring cells of the cell, geographical location covered by the cell, relationship between geographical locations covered by different cells, etc.), indicating that this application can generate detailed network topology information.

[0066] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: the first core network element sending network slice information supported by each of the multiple TAs to the data analysis network element.

[0067] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the network topology information also includes at least one of the following: network slices supported by the TA, frequency bands supported by the network slices supported by the TA, and network slices supported by the cell.

[0068] The communication method provided in this application embodiment allows the first core network element to send network slice information supported by TA to the data analysis network element, thereby enriching the network topology information generated by the data analysis network element.

[0069] Fifthly, a communication method is provided, which includes:

[0070] The first core network element obtains network topology information about the location of the access network device from the access network device. Based on the network topology information about the location of the access network device, the first core network element generates network topology information about its own location. The first core network element then sends the network topology information about its own location to the third core network element.

[0071] The communication method provided in this application embodiment enables the first core network element to generate network topology information of its location based on the network topology information of the location of the access network device, thereby optimizing the network operation effect.

[0072] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the network topology information of the location of the first core network element includes TA-level topology information of one or more TAs served by the first core network element, wherein the cell-level topology information of the TA includes the TA's identifier and at least one of the following: the frequency band supported by the TA, the geographical location of the TA, and the TA's neighboring TAs.

[0073] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the topology information of the TA at the TA level also includes: the network slices supported by the TA and the frequency bands supported by the network slices supported by the TA.

[0074] Sixthly, a communication method is provided, the communication method comprising:

[0075] The third core network element obtains network topology information from the location of the first core network element, and generates full network topology information based on the network topology information of the location of the first core network element.

[0076] The communication method provided in this application embodiment enables the third core network element to generate full network topology information based on the network topology information obtained from the location of the first core network element, thereby optimizing the network operation effect.

[0077] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the overall network topology information includes TA-level topology information of one or more TAs, wherein the cell-level topology information of the TA includes the TA's identifier and at least one of the following: the frequency band supported by the TA, the geographical location of the TA, and the TA's neighboring TAs.

[0078] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the topology information of the TA at the TA level also includes: the network slices supported by the TA and the frequency bands supported by the network slices supported by the TA.

[0079] In a seventh aspect, a communication apparatus is provided, which may be a data analysis network element, or a chip or circuit disposed in the data analysis network element. The communication apparatus includes a processor for implementing the functions of the data analysis network element in the method described in the first aspect above.

[0080] The communication device specifically includes:

[0081] The acquisition unit is used to acquire multiple tracking area (TA) information from the first core network element; the processing unit is used to generate network topology information based on the multiple TA information, the network topology information including the correlation between the multiple TAs.

[0082] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the acquiring unit is further configured to acquire at least one of the following information: information of the serving cell of the terminal device, information of the neighboring cells of the serving cell, mobility information of the terminal device, and geographical location information of the terminal device.

[0083] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the acquisition unit is further configured to acquire the MDT result of the terminal device, the MDT result of the terminal device including at least one of the following information: information of the serving cell of the terminal device, neighboring cell information of the serving cell, mobility information of the terminal device, and geographical location information of the terminal device; the processing unit generates network topology information based on the plurality of TA information, including: the processing unit generates the network topology information based on the plurality of TA information and the MDT result of the terminal device.

[0084] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the acquisition unit is further configured to acquire information related to the access network equipment from the first core network element. The information related to the access network equipment includes the TA and frequency band to which the first cell belongs, and the TA and frequency band to which the second cell belongs. The first cell is a cell managed by the access network equipment, and the second cell is a cell managed by an access network equipment adjacent to the access network equipment. The processing unit generates network topology information based on the multiple TA information, including: the processing unit generates the network topology information based on the multiple TA information and the information related to the access network equipment.

[0085] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the acquisition unit is further configured to acquire access network device-related information from the access network device. This access network device-related information includes at least one of the following: the geographical location of the access network device, the TA and frequency band of the first cell, the TA and frequency band of the second cell, and network topology information of the location of the access network device. The first cell is a cell managed by the access network device, the second cell is a cell managed by an adjacent access network device, and the network topology information of the location of the access network device includes the relationships between multiple cells. The processing unit generates network topology information based on the multiple TA information, including: the processing unit generates the network topology information based on the multiple TA information and the access network device-related information.

[0086] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the processing unit is further configured to perform terminal device mobility analysis or terminal device communication analysis to obtain analysis data; the processing unit verifies the validity of the network topology information based on the analysis data.

[0087] In conjunction with the seventh aspect, in some implementations of the seventh aspect, if the network topology information is invalid, the processing unit is also used to update the network topology information.

[0088] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the acquisition unit is further configured to acquire network slice information supported by each of the plurality of TAs from the first core network element; the processing unit generates network topology information based on the plurality of TAs information, including: the processing unit generates the network topology information based on the plurality of TAs information and the network slice information supported by each of the plurality of TAs.

[0089] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the apparatus further includes: a transmitting unit for transmitting the network topology information to a second core network element, the network topology information being used by the second core network element to optimize the network.

[0090] In one possible implementation, the communication device may further include a memory coupled to a processor for implementing the functions of the data analysis network element in the method described in the first aspect above.

[0091] In one possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, which can call and execute the program instructions stored in the memory to implement the functions of the data analysis network element in the method described in the first aspect above.

[0092] In one possible implementation, the communication device may further include a communication interface for communicating with other devices. This communication interface may be a transceiver, an input / output interface, or a circuit, etc.

[0093] In one possible design, the communication device includes: a processor and a communication interface.

[0094] The processor is used to run computer programs so that the communication device implements any of the methods described in the first aspect above;

[0095] The processor uses this communication interface to communicate with the outside world.

[0096] It is understood that the external entity can be an object outside the processor or an object outside the device.

[0097] In another possible design, the communication device is a chip or chip system. The communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be manifested as processing circuitry or logic circuitry.

[0098] Eighthly, a communication apparatus is provided, which may be a second core network element, or a chip or circuit disposed in the second core network element. The communication apparatus includes a processor for implementing the functions of the second core network element in the method described in the second aspect above.

[0099] The communication device specifically includes:

[0100] The acquisition unit is used to acquire network topology information from the data analysis network element or generate the network topology information, which includes the relationship between the multiple TAs; the processing unit is used to optimize the network based on the network topology information.

[0101] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the processing unit optimizes the network based on the network topology information, including: the processing unit optimizes the registration area of ​​the terminal device and / or optimizes the frequency band selection priority of the terminal device based on the network topology information.

[0102] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the processing unit optimizes the registration area of ​​the terminal device based on the network topology information, including: the processing unit removes TAs whose geographical locations can be contained within geographical areas formed by other TAs in the registration area based on the geographical location of the TA; and / or, the processing unit removes TAs that are not adjacent to any other TA in the registration area based on the TAs adjacent to the TA; the processing unit optimizes the frequency band selection priority of the terminal device based on the network topology information, including: the processing unit determines the frequency bands supported by as many TAs as possible in the registration area of ​​the terminal device and the corresponding frequency band selection priorities based on the frequency bands supported by the TA.

[0103] In conjunction with the eighth aspect, in some implementations of the eighth aspect, where the network topology information also includes network slice-related information, the processing unit optimizes the network based on the network topology information, including at least one of the following: the processing unit optimizes the registration area of ​​the terminal device, optimizes the list of network slices that the terminal device is allowed to access, optimizes the list of network slices that the terminal device is targeting to access, or optimizes the frequency band selection priority of the terminal device based on the network topology information.

[0104] In conjunction with the eighth aspect, in certain implementations of the eighth aspect, the processing unit optimizes the registration area of ​​the terminal device based on the network topology information, including at least one of the following: the processing unit, based on the list of TAs supporting network slices and the geographical location of the TAs, forms the registration area of ​​the terminal device with TAs that are geographically consecutive and support the network slice; the processing unit, based on the list of TAs supporting network slices and the TAs adjacent to the TA, forms the registration area of ​​the terminal device with TAs that support the network slice; the processing unit, based on the list of network slices requested by the terminal and the list of TAs supporting network slices, determines the number of network slices requested by the terminal supported by the TA, and removes TAs from the registration area of ​​the terminal device whose number of TAs is different from that supported by other TAs in the registration area.

[0105] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the processing unit optimizes the list of network slices that the terminal device is allowed to access based on the network topology information, including: the processing unit determines the list of network slices that the terminal is allowed to access based on the list of network slices requested by the terminal, the list of TAs that support the network slices, and the TAs adjacent to the TAs.

[0106] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the processing unit optimizes the list of network slices that the terminal device aims to access based on the network topology information, including: the processing unit determines the list of network slices that the terminal aims to access based on the list of network slices requested by the terminal, the list of TAs that support the network slices, and the geographical location of the TAs.

[0107] In conjunction with the eighth aspect, in certain implementations of the eighth aspect, the processing unit optimizes the frequency band selection priority of the terminal device based on the network topology information, including: the processing unit determines the frequency band selection priority of the terminal based on the network slice list requested by the terminal, the list of TAs supporting the network slice, the TAs adjacent to the TA, and the frequency bands supported by the network slices supported by the TA; and / or, the processing unit determines the frequency band selection priority of the terminal based on the network slice list requested by the terminal, the list of TAs supporting the network slice, the geographical location of the TA, and the frequency bands supported by the network slices supported by the TA. In one possible implementation, the communication apparatus may further include a memory coupled to the processor, the processor being used to implement the functions of the second core network element in the method described in the second aspect above.

[0108] In one possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, which can call and execute the program instructions stored in the memory to implement the functions of the second core network element in the method described in the second aspect above.

[0109] In one possible implementation, the communication device may further include a communication interface for communicating with other devices. This communication interface may be a transceiver, an input / output interface, or a circuit, etc.

[0110] In one possible design, the communication device includes: a processor and a communication interface.

[0111] The processor uses this communication interface to communicate with external devices;

[0112] The processor is used to run computer programs so that the communication device implements any of the methods described in the second aspect above.

[0113] It is understood that the external entity can be an object outside the processor or an object outside the device.

[0114] In another possible design, the communication device is a chip or chip system. The communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be manifested as processing circuitry or logic circuitry.

[0115] Ninthly, a communication apparatus is provided, which may be an access network device or a chip or circuit disposed in the access network device, the communication apparatus including a processor for implementing the functions of the access network device in the method described in the third aspect above.

[0116] The communication device specifically includes:

[0117] The processing unit is configured to generate network topology information of the location of the access network device based on the TA and frequency band of the first cell, the TA and frequency band of the second cell, the neighbor cell relationships between the first cells, and the neighbor cell relationships between the first cell and the second cell.

[0118] The sending unit is configured to send information related to the access network device to the core network elements, wherein the information related to the access network device includes at least one of the following:

[0119] The geographical location of the access network device, the TA and frequency band of the first cell, the TA and frequency band of the second cell, and the network topology information of the location of the access network device.

[0120] The first cell is the cell managed by the access network device, the second cell is the cell managed by the access network device adjacent to the access network device, and the network topology information of the location of the access network device includes the relationship between multiple cells.

[0121] In one possible implementation, the communication apparatus may further include a memory coupled to a processor for implementing the functions of the access network device in the method described in the third aspect above.

[0122] In one possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, which can call and execute the program instructions stored in the memory to implement the functions of the access network device in the method described in the third aspect above.

[0123] In one possible implementation, the communication device may further include a communication interface for communicating with other devices. This communication interface may be a transceiver, an input / output interface, or a circuit, etc.

[0124] In one possible design, the communication device includes: a processor and a communication interface.

[0125] The processor uses this communication interface to communicate with external devices;

[0126] The processor is used to run computer programs so that the communication device implements any of the methods described in the third aspect above.

[0127] It is understood that the external entity can be an object outside the processor or an object outside the device.

[0128] In another possible design, the communication device is a chip or chip system. The communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be manifested as processing circuitry or logic circuitry.

[0129] In a tenth aspect, a communication apparatus is provided, which may be a first core network element, or a chip or circuit disposed in the first core network element. The communication apparatus includes a processor for implementing the functions of the first core network element in the methods described in the fourth and fifth aspects above.

[0130] In one possible implementation, the communication apparatus may further include a memory coupled to a processor for implementing the functions of the first core network element in the methods described in the fourth and fifth aspects above.

[0131] In one possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, which can call and execute the program instructions stored in the memory to implement the functions of the first core network element in the methods described in the fourth and fifth aspects above.

[0132] In one possible implementation, the communication device may further include a communication interface for communicating with other devices. This communication interface may be a transceiver, an input / output interface, or a circuit, etc.

[0133] In one possible design, the communication device includes: a processor and a communication interface.

[0134] The processor uses this communication interface to communicate with external devices;

[0135] The processor is used to run computer programs so that the communication apparatus implements any of the methods described in the fourth and fifth aspects above.

[0136] It is understood that the external entity can be an object outside the processor or an object outside the device.

[0137] In another possible design, the communication device is a chip or chip system. The communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be manifested as processing circuitry or logic circuitry.

[0138] Eleventhly, a communication apparatus is provided, which may be a third core network element, or a chip or circuit disposed in the third core network element. The communication apparatus includes a processor for implementing the functions of the third core network element in the method described in the sixth aspect above.

[0139] In one possible implementation, the communication device may further include a memory coupled to the processor, which is used to implement the functions of the third core network element in the method described in the sixth aspect above.

[0140] In one possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, which can call and execute the program instructions stored in the memory to implement the functions of the third core network element in the method described in the sixth aspect above.

[0141] In one possible implementation, the communication device may further include a communication interface for communicating with other devices. This communication interface may be a transceiver, an input / output interface, or a circuit, etc.

[0142] In one possible design, the communication device includes: a processor and a communication interface.

[0143] The processor uses this communication interface to communicate with external devices;

[0144] The processor is used to run computer programs so that the communication apparatus implements any of the methods described in the sixth aspect above.

[0145] It is understood that the external entity can be an object outside the processor or an object outside the device.

[0146] In another possible design, the communication device is a chip or chip system. The communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be manifested as processing circuitry or logic circuitry.

[0147] In a twelfth aspect, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the methods described in the above aspects.

[0148] In a thirteenth aspect, this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.

[0149] In a fourteenth aspect, a communication system is provided, comprising: a core network element for sending multiple tracking area (TA) information to a data analysis network element; and the data analysis network element for performing the method described in the first aspect above.

[0150] In a fifteenth aspect, a communication system is provided, comprising: a data analysis network element for sending network topology information to a core network element, the network topology information including association relationships between multiple TAs; and the core network element for performing the method described in the second aspect above.

[0151] In a sixteenth aspect, a communication system is provided, comprising: an access network device for sending access network device-related information to a data analysis network element; the data analysis network element for performing the method described in the first aspect above; and the core network element for performing the method described in the second aspect above.

[0152] In a seventeenth aspect, a communication system is provided, comprising the communication apparatus shown in the seventh aspect and the communication apparatus shown in the ninth aspect.

[0153] Eighteenth aspect: A communication system is provided, including the communication apparatus shown in the seventh aspect to the communication apparatus shown in the eleventh aspect.

[0154] In a nineteenth aspect, a chip or chip system is provided, comprising at least one processor and a communication interface, the communication interface and the at least one processor being interconnected via a circuit, the at least one processor being configured to execute computer programs or instructions to perform the methods of any of the possible implementations of the first to sixth aspects. The communication interface in the chip may be an input / output interface, a pin, or a circuit, etc.

[0155] In one possible implementation, the chip or chip system described above in this application further includes at least one memory storing instructions. The memory can be an internal storage unit of the chip, such as a register or cache, or it can be a storage unit of the chip itself (e.g., read-only memory, random access memory, etc.). Attached Figure Description

[0156] Figure 1 This is a schematic diagram of the architecture of a communication system applicable to one embodiment of this application.

[0157] Figure 2 This is a schematic diagram for obtaining network topology information.

[0158] Figure 3 This is a schematic diagram of the movement path of a terminal device.

[0159] Figure 4 This is a schematic flowchart of a communication method provided in this application.

[0160] Figure 5 This is a schematic diagram of a network topology scenario provided in this application.

[0161] Figure 6 This is a schematic flowchart illustrating another communication method provided in an embodiment of this application.

[0162] Figure 7 This is a schematic block diagram of a communication device provided according to an embodiment of this application.

[0163] Figure 8 This is another schematic block diagram of a communication device provided according to an embodiment of this application.

[0164] Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

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

[0166] The technical solutions of this application can be applied to various communication systems, such as 5th generation (5G) systems, new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems. The technical solutions of this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0167] To facilitate understanding of the embodiments of this application, firstly, in conjunction with Figure 1 This application provides a brief description of a communication system applicable to one embodiment.

[0168] As an example, Figure 1 A schematic diagram of the architecture of a communication system to which embodiments of this application are applicable is shown. Figure 1 The communication system shown includes a 5G network architecture based on service-oriented interfaces. For example... Figure 1 As shown, the network architecture may include, but is not limited to, the following network elements (or functional network elements, functional entities, nodes, devices, etc.):

[0169] User equipment (UE), radio access network (R)AN, access and mobility management function (AMF) network elements, session management function (SMF) network elements, user plane function (UPF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, data network (DN), network slice selection function (NSSF), unified data management (UDM), unified data repository (UDR), network data analytics function (NWDAF) network elements, minimized drive test management service producer (MDT MnS Producer), trace collection entity (TCE), etc.

[0170] The following is about Figure 1 A brief introduction to each network element shown in the image:

[0171] 1. UE: A terminal that communicates with (R)AN, also known as terminal equipment, access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device. Terminal equipment can be a device that provides voice / data connectivity to the user, such as a handheld device with wireless connectivity, vehicle-mounted equipment, etc. Currently, examples of terminals include: mobile phones, tablets, computers with wireless transceiver capabilities (such as laptops and PDAs), mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc.

[0172] Furthermore, terminal devices can also be terminal devices in Internet of Things (IoT) systems. IoT is an important component of future information technology development. Its main technical characteristic is connecting objects to networks through communication technologies, thereby realizing an intelligent network that enables human-machine interconnection and machine-to-machine interconnection. IoT technology can achieve massive connectivity, deep coverage, and low power consumption at the terminal level through technologies such as narrowband (NB).

[0173] In addition, terminal devices may also include sensors such as smart printers, train detectors, and gas stations. Their main functions include collecting data (for some terminal devices), receiving control information and downlink data from network devices, and sending electromagnetic waves to transmit uplink data to network devices.

[0174] It should be understood that a terminal device can be any device capable of accessing a network. The terminal device and the access network device can communicate with each other using some form of air interface technology.

[0175] 2. (R)AN: Used to provide network access functionality for authorized user equipment in a specific area, and can use transmission tunnels with different service qualities according to the user equipment level, service requirements, etc.

[0176] (R)AN can manage radio resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between user equipment and the core network. (R)AN can also be understood as a base station in a traditional network.

[0177] For example, the access network device in this application embodiment can be any kind of communication device with wireless transceiver function for communicating with user equipment. This access network device includes, but is not limited to: evolved Node B (eNB), home evolved Node B (HeNB, or home Node B, HNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP) in a wireless fidelity (WIFI) system, etc. It can also be a gNB in ​​a 5G, such as NR, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU), etc.

[0178] In some deployments, a gNB may include a centralized unit (CU) and a distribution unit (DU). The gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), media access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered to be sent by the DU, or by the DU+AAU. It is understood that access network equipment can be devices including one or more of the following: CU nodes, DU nodes, and AAU nodes. In addition, the CU can be classified as an access network device in the radio access network (RAN) or as an access network device in the core network (CN), and this application does not limit this.

[0179] 3. User Plane Network Element: Primarily responsible for processing user packets, such as forwarding, billing, and legitimate interception. User plane network elements can also be called Protocol Data Unit (PDU) session anchors (PSA).

[0180] In 5G communication systems, user plane network elements can be UPF network elements. In future communication systems, user plane network elements can still be UPF network elements, or they can have other names; this application does not limit this.

[0181] 4. DN: A network used to provide data transmission.

[0182] In 5G communication systems, the data network can be a DN (Data Network). In future communication systems, the data network can still be a DN, or it can have other names; this application does not limit this.

[0183] 5. AMF network element: mainly used for terminal attachment, mobility management, and tracking area update processes in mobile networks. The access management network element terminates non-access stratum (NAS) messages, completes registration management, connection management, and reachability management, allocates tracking area list (TA list), and performs mobility management, and transparently routes session management (SM) messages to the session management network element.

[0184] In 5G communication systems, the access management network element can be an AMF (Access Management Function) network element. In future communication systems, the access management network element can still be an AMF network element, or it can have other names; this application does not limit this.

[0185] 6. SMF: Primarily used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection of manageable user plane functions, endpoints for policy control and billing function interfaces, and downlink data notification, etc.

[0186] In 5G communication systems, the session management network element can be an SMF network element. In future communication systems, the session management network element can still be an SMF network element, or it can have other names; this application does not limit this.

[0187] 7. PCF: Includes user subscription data management functions, policy control functions, billing policy control functions, quality of service (QoS) control, etc.

[0188] For example, PCFs may also be divided into multiple entities according to hierarchy or function, such as global PCFs and PCFs within slices, or session management PCFs (SM-PCFs) and access management PCFs (AM-PCFs).

[0189] In this embodiment, the PCFs connected to the AMF and SMF correspond to the AM PCF and SM PCF, respectively. In actual deployment scenarios, they can be the same PCF entity or two different PCF entities.

[0190] In 5G communication systems, this policy control network element can be a PCF network element. In future communication systems, the policy control network element can still be a PCF network element, or it can have other names; this application does not limit this.

[0191] 8. UDM: This can be understood as the naming of the Unified Data Management Network Element in the 5G architecture. The Unified Data Management Network Element mainly includes the following functions: unified data management, supporting authentication trust letter processing in the 3rd Generation Partnership Project (3GPP) authentication and key negotiation mechanism, user identity processing, access authorization, registration and mobility management, subscription management, and SMS management.

[0192] 9. NSSF: Main functions include: selecting a set of network slice instances for the UE, determining the allowed network slice selection assistance information (NSSAI), and determining the AMF set that can serve the UE.

[0193] 10. UDR: Primarily used for storing and retrieving data types such as contract data, strategy data, and application data.

[0194] It is understood that the aforementioned network elements or functional network elements can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0195] 11. NWDAF: It can collect data from various network functions (NFs), such as policy control network elements, session management network elements, user plane network elements, access management network elements, and application function network elements (through network capability opening function network elements), and perform analysis and prediction.

[0196] In 5G communication systems, data analysis network elements can be NWDAF network elements.

[0197] Optionally, the data analysis network element can be a separately established physical unit, or it can be a functional unit within one or more core network elements.

[0198] In future communication systems, the data analysis network element can still be an NWDAF network element, or it can have other names; this application does not limit this.

[0199] In addition to the network communication equipment mentioned above Figure 1 The communication system shown also includes the following entities related to MDT:

[0200] 12. MDT Service Entity: An entity that provides the MDT service interface, which, upon request from a service consumer, instructs core network equipment and radio network equipment to initiate MDT for a specified UE.

[0201] 13. TCE: An entity that collects MDT reports from core network equipment or wireless network equipment via file transfer protocol (FTP) or other means.

[0202] from Figure 1 It can be seen that, Figure 1 The interfaces between the various control plane network elements are service-oriented interfaces.

[0203] Figure 1 Nnssf, Nudr, Nnwdaf, Namf, Npcf, Nsmf, and Nudm are the service interfaces provided by NSSF, UDR, NWDAF, AMF, PCF, SMF, and UDM, respectively, used to invoke the corresponding service operations. N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the definitions in the 3GPP standard protocols and are not limited here.

[0204] Service-oriented architecture enables the 5G core network to form a flat architecture. Through the control plane signaling bus, network function entities in the control plane of the same network slice can discover each other through network repository function (NRF) elements, obtain each other's access address information, and then communicate directly with each other through the control plane signaling bus.

[0205] It should be noted that, Figure 1 The interfaces between the various control plane network elements can also be point-to-point interfaces, which will not be elaborated here.

[0206] It is understood that the aforementioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0207] For ease of explanation, this application will subsequently use the access management function network element (AMF) and the data analysis network element (NWDAF) as examples. Furthermore, the AMF network element will be abbreviated as AMF, and the NWDAF network element as NWDAF. That is, the AMF described below can be replaced by the access management function network element, and the NWDAF can be replaced by the data analysis function network element.

[0208] For ease of explanation, this application uses the AMF entity and NWDAF entity as examples to describe the communication method. For the implementation method of the chip in the AMF entity and the chip in the NWDAF entity, please refer to the specific description of the AMF entity and NWDAF entity respectively, and will not be repeated here.

[0209] It should be noted that, Figure 1 The names of the various network elements and communication interfaces between them are simply illustrated using examples from current protocols, but this does not limit the embodiments of this application to only known communication systems. Therefore, the standard names that appear when describing using current protocols as examples are functional descriptions. This application does not limit the specific names of network elements, interfaces, or signaling, but only indicates the function of the network element, interface, or signaling, which can be extended to other systems, such as 4G or future communication systems.

[0210] Additionally, it should be noted that in some network architectures, network function elements such as AMF, SMF, PCF, BSF, and UDM are all referred to as network function (NF) elements; or, in other network architectures, a collection of AMF, SMF, PCF, BSF, and UDM elements can be referred to as control plane function elements.

[0211] Figure 1 For the communication system applicable to the embodiments of this application, in order to facilitate understanding of the technical solutions of the embodiments of this application, before introducing the solutions of the embodiments of this application based on the 5G architecture, some terms or concepts in 5G that may be involved in the embodiments of this application will be briefly described first.

[0212] 1. Network topology.

[0213] Network topology refers to the layout of various devices interconnected by transmission media; that is, how wireless devices are connected to core network devices, and how wireless devices are connected to each other. When considering wireless links, network topology also includes how wireless devices are connected to terminal devices, such as wireless frequency bands, wireless cell coverage, cell adjacency relationships, etc.

[0214] Currently, network topology information is mostly added to interconnected network devices through configuration. This network topology information is crucial for network operation. For example, mobile networks are divided into multiple tracking areas (TAs), with geographically proximate cells and frequently moving terminal devices assigned to the same TA. Each TA uses its own tracking area identity (TAI) to distinguish itself from others. The TAI can include the mobile country code (MCC), mobile network code (MNC), and tracking area code (TAC), among other things.

[0215] 2. Registration area (RA).

[0216] After a terminal device registers with the network, the network device responsible for mobility management assigns a Location Area (RA) to the terminal device based on which radio access network devices it is connected to, which tracking areas its management range includes, and so on. The RA includes one or more Tracking Areas (TAs), and can be represented as a list of TAs. When a terminal device undergoes cell handover in idle mode, it does not notify the network. Upon arriving at a new cell, if the terminal device detects that the TA of the current cell no longer belongs to an RA, it initiates a location update procedure to notify the network device responsible for mobility management that it has left the registered area.

[0217] 3. Network slice.

[0218] Network slicing is an on-demand networking approach that allows operators to separate multiple virtual end-to-end networks on a unified infrastructure. Each network slice is logically isolated from the radio access network to the bearer network and then to the core network to adapt to various types of applications. A network slice can be divided into at least three parts: radio network sub-slices, bearer network sub-slices, and core network sub-slices.

[0219] A 5G physical network can be abstractly divided into multiple network slices. Each network slice constitutes an end-to-end logical network, which is logically isolated from each other and does not affect each other. Each network slice is identified using Single-Network Slice Selection Assistance Information (S-NSSAI).

[0220] 4. Minimization of drive test (MDT).

[0221] The main methodology of drive testing involves: first, determining the test area and designing the test route; then, collecting measurement data, including location information as well as physical layer, media access control layer, signaling information, and system information; finally, performing post-collection processing, primarily including data analysis and problem localization analysis. Minimized Drive Testing (MDT) utilizes measurement reports with latitude and longitude information from existing commercial terminals in the network to optimize the network and identify issues such as weak coverage, coverage vulnerabilities, and over-coverage. This avoids conducting actual drive tests, thus saving costs.

[0222] As the above introduction to network topology shows, network topology information is crucial for network operation. However, 5G mobile communication systems have numerous network devices and a significantly increased number of cells. Furthermore, there are scenarios where different network slices are supported on different frequency bands, making the network topology structure even more complex. How to obtain network topology information in 5G and subsequent mobile communication network systems, and how to determine the RA (Real Estate Provider) of terminal devices based on the network topology, are problems that need to be solved.

[0223] A method for obtaining network topology information, such as Figure 2 The above, Figure 2 This is a schematic diagram for obtaining network topology information. It includes:

[0224] gNB (e.g., Figure 2 The gNB#1, gNB#2, and gNB#3 shown in the diagram report to the AMF at startup the identifier (e.g., TAI) of the TA to which the cell they manage belongs, as well as the S-NSSAI of the network slices supported within that TA.

[0225] Because gNB reports TAI and S-NSSAI to AMF during startup, the relationship between TA, AMF, and S-NSSAI is shown in Table 1 below:

[0226] Tracking area Managing AMF Supported S-NSSAI list TAI#1 AMF#1 Slice #1 TAI#2 AMF#1 Slice#1, Slice#2 TAI#3 AMF#2 Slice #2 TAI#4 AMF#2 Slice #2 TAI#5 AMF#2 Slice#1, Slice#2, Slice#3 TAI#6 AMF#3 Slice #1 TAI#7 AMF#3 Slice#1, Slice#3

[0227] As shown in Table 1, when a UE initiates a network registration request via gNB within TA#1 managed by AMF#1, for example, requesting access to network slices Slice1 and Slice2, AMF#1 determines that the TA#1 currently in which the UE is located only supports Slice#1 and not Slice#2. Therefore, the NSSF or AMF ultimately determines that the list of network slices the UE is allowed to access (i.e., Allowed NSSAI) contains only Slice#1, where NSSAI is a list containing one or more S-NSSAIs. Because TA#2 managed by AMF#1 itself also supports Slice#1, AMF#1 determines the UE's registration area RA as {TA#1, TA#2}, indicating that the RA is a list of TAs including TA#1 and TA#2. Within this RA, the UE can access network slice Slice#1.

[0228] Because the AMF only has a list of tracking areas it manages and information on the network slices supported by each tracking area, it lacks detailed network topology and cannot optimize network operation based on the topology. As mentioned above, when the UE registers with TA#1, it requests simultaneous access to both Slice#1 and Slice#2. The final registration result is RA as {TA#1, TA#2}, and the S-NSSAI included in Allowed NSSAI is only Slice#1. Because TA#1, where the UE is located, does not support Slice#2, Slice#2 is sent to the UE as a rejected network slice (Rejected S-NSSAI). The UE can use Slice#1 within the RA range, but cannot use Slice#2. If the UE's movement path is as follows... Figure 3 As shown, the geographical area covered by TA#2 is also covered by another frequency band used by TA#1. When the UE moves to the area covered by TA#2, the network can actually provide Slice#2 service, but the UE cannot use it normally.

[0229] As can be seen from the above examples, if network topology information is available, the AMF can know that the two different RAs {TA#1, TA#2} and {TA#1} have the same geographical coverage. Including more TAs (i.e., adding TA#2) into the RA does not have the desired effect. Instead, it restricts the UE from using slice #2 in the geographical area covered by TA#2.

[0230] Another method to obtain network topology information is to statically configure cell adjacency relationships, and then statically configure the adjacency relationships of tracking areas according to the tracking area to which each cell belongs. For example, if cell #1 and cell #2 are two adjacent cells, cell #1 belongs to TA#1 and cell #2 belongs to TA#2, then TA#1 and TA#2 are statically configured to be adjacent on the AMF.

[0231] However, in some scenarios, two TAs that are geographically adjacent or overlap in coverage are not configured with cell adjacency relationships, which allows operators to prevent terminals from automatically switching over.

[0232] For example, Slice#1 is a public service network slice provided by a public network, and Slice#2 is a campus network slice. TA#2's coverage area is limited to the campus. To prevent ordinary users' terminals from accessing the campus network, the cell in TA#2 is not configured as a neighboring cell by the cell in TA#1; however, to allow campus terminals to use the public service network slice outside the campus, the cell in TA#2 configures the cell in TA#1 as a neighboring cell. To ensure that campus terminal devices returning from outside can access the campus network normally, the network configures specific radio access technology / frequency selection priority (RFSP) for campus terminal devices. Thus, when campus terminal devices return to the campus, they will preferentially choose to camp on the cell in TA#2, while ordinary terminal devices will camp on the cell in TA#1 in the same geographical location. This example shows that the neighbor relationship of a TA cell is not always determined by the neighbor relationship of a cell. In addition, real-world mobile networks often enable self-organization network (SON) functionality, where cell adjacency relationships are dynamically added and deleted, and topology relationships are dynamically changing. Static configuration may not be able to reflect the actual network topology in a timely manner, which will affect the effectiveness of optimizing network operation based on topology.

[0233] To avoid the drawbacks of the aforementioned methods for obtaining network topology information, this application provides a communication method that can obtain more detailed network topology information (such as frequency bands supported by TAs or cells, adjacency relationships of TAs or cells, slice support capabilities, etc.) and optimize network mobility management decisions based on the network topology information.

[0234] The embodiments shown below do not specifically limit the structure of the execution subject of the method provided in the embodiments of this application. As long as it is possible to communicate according to the method provided in the embodiments of this application by running a program that records the code of the method provided in the embodiments of this application, for example, the execution subject of the method provided in the embodiments of this application can be a terminal device or a core network device, or a functional module in the terminal device or core network device that can call and execute the program.

[0235] To facilitate understanding of the embodiments of this application, the following points are provided.

[0236] First, in this application, "for instruction" can be understood as "enabling," and "enabling" can include direct enabling and indirect enabling. When describing information for enabling A, it can include whether the information directly enables A or indirectly enables A, but does not necessarily mean that the information carries A.

[0237] The information that enables the information is called the information to be enabled. In the specific implementation process, there are many ways to enable the information to be enabled, such as, but not limited to, directly enabling the information to be enabled, such as the information to be enabled itself or its index. It can also be indirectly enabled by enabling other information, where there is a relationship between the other information and the information to be enabled. It can also enable only a part of the information to be enabled, while the other parts are known or pre-agreed upon. For example, enabling specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing enabling overhead to some extent. Simultaneously, common parts of various pieces of information can be identified and enabled uniformly to reduce the enabling overhead caused by individually enabling the same information.

[0238] Second, the first, second, and various numerical designations (e.g., "#1", "#2", etc.) shown in this application are merely for descriptive convenience and to distinguish objects, and are not intended to limit the scope of the embodiments of this application. For example, to distinguish different messages, etc., rather than to describe a specific order or sequence. It should be understood that such described objects can be interchanged where appropriate to describe solutions other than those in the embodiments of this application.

[0239] Third, in this application, "preset" may include predefined terms, such as protocol definitions. These "predefined terms" can be implemented by pre-storing corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including user equipment or core network equipment), and this application does not limit the specific implementation method.

[0240] Fourth, the term "storage" in the embodiments of this application can refer to storage in one or more memories. These memories can be separate installations or integrated into an encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others can be integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0241] Fifth, the “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communication, such as 5G protocols, new radio (NR) protocols, and related protocols applied in future communication systems. This application does not limit this.

[0242] Without loss of generality, the communication method provided in the embodiments of this application will be described in detail using the interaction between network elements as an example.

[0243] Figure 4 This is a schematic flowchart of a communication method provided in this application.

[0244] The communication method includes at least the following steps.

[0245] S410, the first core network element obtains information from the access network device from the access network device, or in other words, the access network device sends information to the first core network element.

[0246] For example, in the embodiments of this application, the access network device can be a wireless network device such as a gNB. It should be understood that the specific form of the access network device in the embodiments of this application is not limited, and other entities that can implement the access network device in this application are within the protection scope of this application.

[0247] For ease of description, the following text will use gNB as an example of a wireless network device.

[0248] For example, the first core network element involved in this application embodiment may be an access and mobility management network element. The access and mobility management network element may be an AMF, or other network elements capable of implementing access and mobility management functions. In this application embodiment, no limitation is made on the name of the network element.

[0249] For ease of description, the following text will use AMF as an example to illustrate the concept.

[0250] Specifically, the gNB is any one of at least one access network device connected to the AMF.

[0251] For example, the gNB can send gNB information to the AMF at startup by interacting with the AMF and sending gNB information to the AMF, or it can send gNB information to the AMF at other times.

[0252] Optionally, the gNB information includes: the gNB identifier (gNB ID), a list of Tracking Areas (TAs) to which the gNB-managed cells belong, and at least one item from the list of network slices supported by each TA in the TA list.

[0253] For example, the tracking area (TA) list of the cell to which the gNB belongs includes at least one TA's identifier (TAI), and each of the at least one TAI is used to identify a TA.

[0254] For example, the tracking area (TA) list of cells managed by the gNB is {TAI#1, TAI#2, TAI#3}, where TAI#1 is used to identify TA#1, TAI#2 is used to identify TA#2, and TAI#3 is used to identify TA#3, indicating that the tracking areas of cells managed by the gNB include TA#1, TA#2, and TA#3.

[0255] For example, the list of network slices supported by each TA includes at least one network slice identifier S-NSSAI, and each of the at least one S-NSSAI is used to identify a network slice.

[0256] For example, the Tracking Area (TA) list of the cell managed by the gNB is {TAI#1, TAI#2, TAI#3}, where TAI#1 is used to identify TA#1, TAI#2 is used to identify TA#2, and TAI#3 is used to identify TA#3. The list of network slices supported by TA#1 is {S-NSSAI#1, S-NSSAI#2}, where S-NSSAI#1 is used to identify network slice #1, and S-NSSAI#2 is used to identify network slice #2, indicating that TA#1 supports network slice #1 and network slice #2.

[0257] The list of network slices supported by TA#2 is {S-NSSAI#3, S-NSSAI#4}, where S-NSSAI#3 is used to identify network slice #3 and S-NSSAI#4 is used to identify network slice #4, indicating that TA#2 supports network slice #3 and network slice #4.

[0258] The list of network slices supported by TA#3 is {S-NSSAI#2, S-NSSAI#3}, which means that TA#3 supports network slice #2 and network slice #3.

[0259] Optionally, the gNB ID, TA list, and network slice list supported by each TA included in the above gNB information can be sent to the AMF in multiple messages or in a single message. This application does not limit this.

[0260] It should be noted that at least one access network device connected to the AMF can send its information to the AMF.

[0261] For example, AMF connects gNB#1 and gNB#2. gNB#1 sends gNB#1 information to AMF, and gNB#2 sends gNB#2 information to AMF.

[0262] The above description uses a specific access network device (e.g., an access network device) as an example. The process of other access network devices connected to the AMF sending information to the AMF can be referred to the above description, and will not be repeated here.

[0263] Additionally, it should be noted that there can be multiple AMFs in the network. Each AMF can obtain information about the access network devices it is connected to through the methods described above. For specific information acquisition methods, please refer to the description above, which will not be repeated here.

[0264] When the AMF (Access Provider Function) in the network obtains information about the access network devices connected to the AMF, the network data analysis element can collect network data from the AMF in the network. Figure 4 The method flow shown also includes:

[0265] S420, the data analysis network element obtains multiple tracking area TA information from the first core network element, or in other words, the first core network element sends multiple tracking area TA information to the data analysis network element.

[0266] Optionally, the multiple TA information is carried in the first information.

[0267] Data analysis network elements can be used to implement data analysis functions. Specifically, data analysis network elements have data collection, training, and inference functions. The data collection function can collect relevant data from network elements, third-party service servers, user equipment, or network management systems; the data training function is used to perform analysis and training based on relevant training data; the data inference function is used to perform analysis and inference based on relevant inference data and provide data analysis results to network elements, third-party service servers, user equipment, or network management systems. These analysis results can assist the network in selecting service quality parameters, executing traffic routing, or selecting traffic transmission strategies, etc.

[0268] This application mainly relates to the data collection function of the data analysis network element, and how the data analysis network element can perform related training and inference based on the collected data.

[0269] For example, the data analysis network element involved in the embodiments of this application may be an NWDAF network element, or other network elements that can realize data analysis functions. The names of the network elements are not limited in this embodiment of the application.

[0270] For example, the data analysis network element is a separately established core network element, or a functional unit within one or more core network elements.

[0271] For ease of description, the following text will use NWDAF as an example for the data analysis network element.

[0272] For example, multiple TA information can be a TA list, which represents the TAs supported by at least one access network device connected to the first core network element (e.g., AMF).

[0273] It should be noted that NWDAF can collect network data from multiple AMFs in the network, and different AMFs can provide NWDAF with information about the access network devices they are connected to.

[0274] For ease of description, the above example illustrates how an AMF provides information about its connected access network devices to the NWDAF. Furthermore, the NWDAF can generate network topology information based on multiple received TA (Transmission Access Frame) messages. Figure 4 The method flow shown also includes:

[0275] S430, NWDAF generates network topology information.

[0276] Specifically, the network topology information includes the relationships between the aforementioned multiple TAs.

[0277] The relationships between multiple TAs include at least one of the following:

[0278] The relationships between the frequency bands supported by the multiple TAs, the relationships between the network slices supported by the multiple TAs, the relationships between the geographical locations of the multiple TAs, and the adjacency relationships between the multiple TAs.

[0279] For example, the relationships between frequency bands supported by multiple TAs include: frequency bands or frequency band lists supported by each TA, lists of TAs supporting the same frequency band, inter-frequency switching relationships between TAs, and intra-frequency switching relationships between TAs.

[0280] For example, the relationship between network slices supported by multiple TAs includes: a list of TAs that support the same network slice (the amount of information is equivalent to the list of network slices supported by each TA), a list of frequency bands supported by the network slices supported by the TAs, etc.

[0281] For example, the relationships between multiple geographic locations include: geographic grid lists of each TA, overlapping geographic ranges (e.g., the geographic coverage area corresponding to one TA includes the geographic coverage area corresponding to another TA), partially overlapping geographic ranges, geographic adjacency, and geographic non-adjacency.

[0282] For example, the adjacency relationships between multiple TAs include: not adjacent, adjacent during connected state switching, adjacent during idle state reselection switching, etc.

[0283] For example, network topology information includes the identifier of a TA and at least one of the following: the frequency band supported by the TA, the geographical location of the TA, or the TA adjacent to the TA.

[0284] Furthermore, the multiple TAs correspond to multiple cells, and the network topology information also includes the cell identifier corresponding to the cell and at least one of the following: the frequency band to which the cell belongs, the TA to which the cell belongs, the radio access network device to which the cell belongs, the cells adjacent to the cell, the first geographical location covered by the cell, the cells whose second geographical location is adjacent to the first geographical location, and the cells whose third geographical location overlaps with the first geographical location.

[0285] Optionally, if the data collected by NWDAF from AMF includes network slice information and network topology information supported by each of the plurality of TAs, it also includes at least one of the following:

[0286] The network slices supported by the TA, the frequency bands supported by the network slices supported by the TA, and the network slices supported by the cell.

[0287] It should be noted that in the process of generating network topology information by NWDAF in this embodiment of the application, network data collected from AMF (such as the multiple TA information mentioned above) needs to be taken into account, and other information may also need to be taken into account. The information required for NWDAF to generate network topology information is described in detail below with reference to methods one to three.

[0288] Method 1: NWDAF needs to generate network topology information based on first information and at least one of the following: information of the serving cell of the terminal device, neighboring cell information of the serving cell, mobility information of the terminal device, and geographical location information of the terminal device.

[0289] Among them, at least one of the following information about the terminal device's serving cell, the serving cell's neighboring cell information, the terminal device's mobility information, and the terminal device's geographic location information can be referred to as the terminal device's MDT result.

[0290] The above-mentioned S430 can be understood as: NWDAF generates network topology information based on the first information and the MDT results of the terminal device.

[0291] The first information includes information obtained by NWDAF from AMF, such as the multiple TA information mentioned above.

[0292] Optionally, the first information may also include network slice information supported by each of the multiple TAs mentioned above, wherein the network slice information supported by each TA may be a list of network slices.

[0293] Optionally, the first information may also include the identification information of the gNB connected to the AMF (e.g., gNB ID).

[0294] In this first method, NWDAF acts as a consumer of the MDT management service, initiating MDT execution on multiple specified terminal devices by calling the MDT MnS Producer interface. NWDAF also acts as a TCE to collect MDT reports and obtain network data.

[0295] In this method one, Figure 4 The method flow shown also includes:

[0296] S431, NWDAF obtains the identifier of the terminal device.

[0297] One possible implementation is that NWDAF can obtain the terminal devices and their identifiers within the area of ​​interest (AoI) through terminal device movement analysis.

[0298] Another possible implementation is that NWDAF can obtain the terminal device and its identifier within the AoI through terminal device communication analysis.

[0299] The identifier of the terminal device can be a subscriber permanent identity (SUPI) or a generic public subscription identity (GPSI) that can be used to identify the UE. This identifier is used for subsequent execution of the MDT (Multi-Targeting Technique) for that terminal device. For ease of description, the following explanation uses SUPI as the identifier of the terminal device.

[0300] In addition, in cases where certain terminal devices are used as volunteer road testers for operators, NWDAF is equipped with SUPI for these volunteer terminal devices.

[0301] Furthermore, once NWDAF obtains the identifier of the aforementioned terminal device, NWDAF uses the SUPI of the aforementioned terminal device to call the MDT service entity, sets a certain terminal device as the target terminal device for MDT, and starts executing MDT. Figure 4 The method flow shown also includes:

[0302] S432, NWDAF calls the MDT service entity.

[0303] Optionally, NWDAF can invoke MDT on multiple terminal devices simultaneously to accelerate the measurement of the region of interest to NWDAF.

[0304] For example, the MDT service entity sets the identifier of the MDT target terminal device to the current AMF, SMF, gNB, or other network devices that provide services to the UE.

[0305] If the UE is not currently registered on the network, the MDT service entity will set the identifier of the MDT target terminal device on the UDM. After the UE registers, the UDM will notify the network devices such as AMF, SMF, and gNB that provide services to the UE to activate the MDT.

[0306] As one possible implementation, the MDT target terminal device can perform measurements and record measurements during normal cell camping or during cell selection.

[0307] For example, the measurements include measurements of the serving cell of the target terminal device, measurements of co-frequency neighboring cells, and measurements of inter-frequency neighboring cells.

[0308] In this implementation, the recorded measurement data includes the current serving cell identifier (Cell ID or global cell identifier, CGI), the latitude and longitude information measured by the UE, and the UE's barometric pressure or altimeter information.

[0309] In addition, the neighboring cell information measured by the UE can also be used to determine the UE's location, which is called radio frequency fingerprint information (RF fingerprint).

[0310] Each MDT measurement record for a target terminal device consists of a list of {time, radio frequency band measurement, optional radio fingerprint information, optional geographic location information, and optional altitude information}.

[0311] As another possible implementation, the target terminal device of MDT can also perform measurement and measurement recording during the service connection process.

[0312] In this implementation, the recorded measurement data includes connection time, connection success or failure result, available frequency band or access technology at the previous moment, serving cell identifier, TA identifier, and optional geographic location information.

[0313] As another possible implementation, the MDT target terminal device can also perform measurements and record measurements during cell handover.

[0314] In this implementation, the recorded measurement data includes handover time, handover success or failure result, selectable target frequency band or access technology, source cell identifier, target cell identifier, and selectable geographic location information.

[0315] It should be noted that the process of performing MDT on the MDT service entity is not limited in the embodiments of this application. You can refer to the description in the relevant current technology, which will not be repeated in this application.

[0316] Meanwhile, in this embodiment, NWDAF sets the TCE address to the address where it collects data. Figure 4 The method flow shown also includes:

[0317] S433, NWDAF obtains the MDT results of the terminal device.

[0318] Among them, the MDT results of terminal devices obtained by the data analysis network element can be the MDT results of one or more terminal devices.

[0319] Specifically, the aforementioned measurement records are transmitted by the UE to connected wireless devices such as gNB, and then the wireless devices transmit them to TCE (i.e., the data collection function of NWDAF) via FTP or other means.

[0320] In addition, core network devices also transmit the records they generate to TCE via FTP or other methods. For example, core network devices such as AMF, SMF, and UDM also generate corresponding records during the registration, update, session connection, and handover processes of the target terminal in the MDT, and transmit the generated records to NWDAF. This application mainly involves the MDT results of the target terminal device and does not limit the information generated in the core network, so it will not be elaborated on.

[0321] Furthermore, NWDAF summarizes and analyzes the MDT results of multiple target terminal devices to obtain wireless network information. This wireless network information includes at least one of the following: information about the serving cell of the terminal device, neighboring cell information of the serving cell, mobility information of the terminal device, and geographical location information of the terminal device.

[0322] The information of the serving cell of the terminal device includes at least one of the following: the identifier of the access network device providing services to the terminal device, the identifier of the serving cell of the terminal device, the identifier of the TA to which the serving cell belongs, and the frequency band to which the serving cell belongs.

[0323] The neighbor cell information of the serving cell includes at least one of the following: the identifiers of the serving cell's neighboring cells, the identifiers of the TAs to which the neighboring cells belong, and the frequency bands to which the neighboring cells belong.

[0324] The mobility information of the terminal device includes the adjacency relationship between the source cell before the handover (e.g., cell handover) and the destination cell after the handover, and / or the type of handover.

[0325] For example, the geographic location information of the terminal device includes at least one of the following:

[0326] The global cell identifier (CGI) of the serving cell of the terminal device, the latitude and longitude information of the terminal device, and the altitude information of the terminal device;

[0327] The type of switching includes at least one of the following:

[0328] Switching between different frequencies, switching between the same frequency, or switching between different systems.

[0329] Method 2: NWDAF needs to generate network topology information based on the first information.

[0330] The first information includes information obtained by NWDAF from AMF, such as the multiple TA information mentioned above.

[0331] In Method Two, the first information also includes information related to the access network equipment, which includes the local area coordinate (TA) and frequency band of the first cell, as well as the TA and frequency band of the second cell.

[0332] Wherein, the first cell is a cell managed by the access network device, and the second cell is a cell managed by an access network device adjacent to the access network device.

[0333] The cell managed by the access network device can be one or more of the first internal cells, and the cell managed by the access network device adjacent to the access network device can be one or more of the first external cells.

[0334] For example, a gNB knows the cells it manages and the frequency bands it supports. Through information exchange, the gNB can obtain information about external cells (i.e., cells of neighboring gNBs). When connecting with the AMF, the gNB reports its identifier, a list of supported TAs, the TAs and supported frequency bands of each cell within the gNB, the TAs and supported frequency bands of external cells, neighbor relationships between internal cells, and neighbor relationships between internal and external cells.

[0335] For example, the first cell managed by the access network device can be one or more cells. If there are multiple cells, they may belong to different TAs. This can be understood as adjacent cells within the network belonging to different TAs.

[0336] For example, the second cell managed by the access network device adjacent to the access network device can be one or more cells. If there are multiple cells, they may belong to different TAs. This can be understood as the external adjacent cells may belong to different TAs.

[0337] The above-mentioned S430 can be understood as: NWDAF generates network topology information based on the first information, which includes multiple TA information and access network device related information.

[0338] In this second method, different gNBs are configured with communication interfaces (e.g., Xn), and gNBs exchange information with each other.

[0339] In this second method, Figure 4 The method flow shown may also include:

[0340] S440, the second core network element sends a network topology analysis subscription request message to the NWDAF, or in other words, the NWDAF receives a network topology analysis subscription request message from the second core network element.

[0341] This network topology analysis subscription request message is used to request NWDAF to perform network topology analysis.

[0342] Optionally, the second core network element can be any one of the following network elements:

[0343] NSSF, AMF, or PCF.

[0344] Optionally, the second core network element may also send range indication information to the NWDAF, which is used to indicate the range for network topology analysis; or, the range indication information may not be sent, and the NWDAF may determine the range for network topology analysis on its own.

[0345] For example, the scope of the analysis can include a specified region or the entire network.

[0346] For example, the aforementioned range indication information can be carried in the network topology analysis subscription request message.

[0347] S441, NWDAF sends a network topology analysis subscription response message to the second core network element, or in other words, the second core network element receives a network topology analysis subscription response message from NWDAF.

[0348] The network topology analysis subscription response is used to indicate acceptance of the network topology analysis request.

[0349] It should be noted that steps S440 and S441 mentioned above are not mandatory. In other words, NWDAF can decide to perform network topology analysis and generate network topology information on its own, without needing to submit a subscription request based on the second core network element.

[0350] In this second method, in order to output the analysis results, NWDAF collects the first information from AMF:

[0351] The first information includes the TA list managed by the AMF (e.g., the multiple TA information mentioned above) and information related to the access network equipment (e.g., the TA and frequency band to which the first cell belongs and the TA and frequency band to which the second cell belongs).

[0352] Optionally, the first information may also include network slice information supported by each of the multiple TAs mentioned above, wherein the network slice information supported by each TA may be a list of network slices.

[0353] Optionally, the first information may also include the identification information of the gNB connected to the AMF (e.g., gNB ID). Optionally,

[0354] Method 3: NWDAF generates network topology information based on the first information and access network device-related information collected from the access network devices. In this method, NWDAF needs to collect information from the gNB.

[0355] The first information includes information obtained by NWDAF from AMF, such as the multiple TA information mentioned above.

[0356] Optionally, the first information may also include network slice information supported by each of the multiple TAs mentioned above, wherein the network slice information supported by each TA may be a list of network slices.

[0357] Optionally, the first information may also include the identification information of the gNB connected to the AMF (e.g., gNB ID).

[0358] The above-mentioned S430 can be understood as: NWDAF generates network topology information based on the first information and information related to the access network device.

[0359] In this method three, Figure 4 The method flow shown also includes:

[0360] S450, NWDAF receives access network device-related information from access network devices, or in other words, access network devices send access network device-related information to NWDAF.

[0361] Specifically, the access network equipment-related information collected from the access network equipment includes at least one of the following:

[0362] The geographical location of the access network device, the local area coordinate (TA) and frequency band of the first cell, the TA and frequency band of the second cell, and the network topology information of the location of the access network device.

[0363] Wherein, the first cell is a cell managed by the access network device, the second cell is a cell managed by an access network device adjacent to the access network device, and the network topology information of the location of the access network device includes the association relationship between multiple cells.

[0364] For example, the first cell managed by the access network device can be one or more cells. If there are multiple cells, they may belong to different TAs. This can be understood as adjacent cells within the network belonging to different TAs.

[0365] For example, the second cell managed by the access network device adjacent to the access network device can be one or more cells. If there are multiple cells, they may belong to different TAs. This can be understood as the external adjacent cells may belong to different TAs.

[0366] The network topology information of the location of the access network device is generated by the access network device based on the following information:

[0367] The TA of the first cell, the S-NSSAI and frequency band supported by the first cell, the TA of the second cell, the S-NSSAI and frequency band supported by the second cell, the neighboring cell relationships between the first and second cells, and the neighboring cell relationships between the first and second cells.

[0368] Specifically, the access network device can be any access network device. The access network device involved in this method three and the access network device involved in the above-mentioned method two can be the same access network device or different access network devices.

[0369] In this third method, the access network device (gNB) can send information in two ways:

[0370] One approach is to provide the NWDAF with the location information of the gNB, the TA and frequency band information of the internal cell to which the gNB belongs, and the TA and frequency band information of the external cell to which the gNB belongs.

[0371] In this mode, when connecting with the AMF, the gNB reports its identifier, the list of TAs supported by the gNB, and the list of S-NSSAIs supported by the TAs to the AMF.

[0372] Another approach is for the gNB to generate network topology information for its location and then send it to the NWDAF.

[0373] In this mode, the gNB obtains the TA (Target Area Code) and supported frequency bands of external cells, as well as the S-NSSAI (Side Classification and Access Control) list of supported network slices, based on information exchanged between interfaces such as Xn. The gNB then generates network topology information for its location based on the TA, supported S-NSSAI, and frequency bands of each internal cell, the TA, supported S-NSSAI, and frequency bands of external cells, neighbor relationships between internal cells, neighbor relationships between internal and external cells, and the gNB's geographical location.

[0374] NWDAF will jointly analyze the gNB ID collected from the gNB, the list of TAs supported by the gNB, the list of S-NSSAIs supported by the TAs, the TAs and supported frequency bands of each cell within the gNB, the TAs and supported frequency bands of external cells, the neighbor relationships between internal cells and between internal and external cells, and the information collected from the AMF to generate network topology information.

[0375] Alternatively, in this method three, Figure 4 The method flow shown also includes:

[0376] S451, the second core network element sends a network topology analysis subscription request message to the NWDAF, or in other words, the NWDAF receives a network topology analysis subscription request message from the second core network element.

[0377] This network topology analysis subscription request message is used to request NWDAF to perform network topology analysis.

[0378] Optionally, the second core network element can be any one of the following network elements:

[0379] NSSF, AMF, or PCF.

[0380] Optionally, the second core network element may also send range indication information to the NWDAF, which is used to indicate the range for network topology analysis; or, the range indication information may not be sent, and the NWDAF may determine the range for network topology analysis on its own.

[0381] For example, the scope of the analysis can include a specified region or the entire network.

[0382] For example, the aforementioned range indication information can be carried in the network topology analysis subscription request message.

[0383] S452, NWDAF sends a network topology analysis subscription response to the second core network element, or in other words, the second core network element receives a network topology analysis subscription response from NWDAF.

[0384] The network topology analysis subscription response is used to indicate acceptance of the network topology analysis request.

[0385] It should be noted that steps S451 and S452 mentioned above are not mandatory. In other words, NWDAF can decide to perform network topology analysis and generate network topology information on its own, without needing to submit a subscription request based on the second core network element.

[0386] In this third method, in order to output the analysis results, NWDAF collects initial information from each AMF:

[0387] The first piece of information includes the list of TAs managed by AMF (e.g., the multiple TA information mentioned above);

[0388] Optionally, the first information also includes a list of S-NSSAI supported by each TA and a list of gNBs connected to the AMF.

[0389] NWDAF collects information related to access network devices from each gNB:

[0390] NWDAF collects information related to access network devices from each gNB (e.g., the location of each gNB, and the TA and frequency band of each cell within each gNB, and the TA and frequency band of each cell outside the gNB); or,

[0391] If a gNB generates network topology information for its location, NWDAF collects the topology information for each gNB's location from the gNBs.

[0392] The above-described methods one through three detail the information that NWDAF needs to collect. After obtaining the different types of information, NWDAF can determine the network topology information based on the acquired information. The following example illustrates the process by which NWDAF generates network topology information based on the collected information.

[0393] For example, NWDAF can obtain cell-level topology information based on each cell's CGI, the radio device to which it belongs, the cell frequency band, the TA information to which the cell belongs, i.e., the S-NSSAI supported by each TA, the location information of the UEs that have successfully camped or connected to the cell, and the same-frequency or different-frequency measurement information during cell selection or cell handover.

[0394] The cell-level topology information includes the CGI of each cell and at least one of the following:

[0395] Frequency band, supported S-NSSAI list, home radio device, home TA, neighboring cells, geographical location of cell coverage area, geographically adjacent cells, geographically overlapping cells.

[0396] The specific processing procedure can be as follows: use the cell identifier CGI to associate the CGI of each cell obtained from the gNB or MDT results, the associated radio device, the cell frequency band, the TA information of the cell, and the same-frequency or different-frequency measurement information during cell selection or cell handover. Then, use the TA of the cell to further associate the S-NSSAI supported by each TA obtained from the AMF to obtain an information containing all cells as shown in Table 2 below:

[0397] Table 2

[0398]

[0399] Divide the geographical area covered by the wireless network into a grid (e.g., a square with sides of 100 meters).

[0400] By matching the locations of each UE in the location information of UEs successfully camped or connected to this cell to each grid, a list of cells that can provide service in each geographical location (i.e., grid) can be obtained. Then, based on the same-frequency or different-frequency measurement information during cell selection or cell handover and the frequency band and radio access technology of the target cell, at least one of the following information can be obtained:

[0401] Within the same grid, which cells can switch to the same frequency and which cells can switch to different frequencies.

[0402] The remaining cells are not adjacent to each other and can only change the cell they reside in through RRC idle state frequency reselection.

[0403] The following table 3 contains information on all location grids and all cells:

[0404] Table 3

[0405]

[0406] The information tables 2 and 3 mentioned above together constitute the cell-level topology information.

[0407] Optionally, NWDAF collects the first information and the MDT results of the terminal device through the above-described method one, and generates network topology information by correlation analysis of the first information and the MDT results of the terminal device, further including:

[0408] Specifically, based on the correspondence between the cell and geographical location in Information Table 3, and the TA to which the cell belongs in Information Table 1, the geographical location information covered by the TA is obtained, that is, the list of grid numbers covered by all cells of each TA, as shown in Table 4 below.

[0409] Table 4

[0410]

[0411] Specifically, based on the TA to which the cell belongs in Information Table 2, and the adjacency relationships between cells in each grid in Information Table 3 (including cell neighbor relationships, geographically adjacent or overlapping coverage relationships, whether the cell can be changed through handover, whether the cell can be changed through cell reselection, etc.), the logical adjacency relationships between TAs in each grid are obtained (i.e., two TAs can be switched in RRC connected state, or two TAs can only be switched in RRC idle state, etc.). At the same time, the adjacency relationships between TAs can be obtained based on the geographical location information of the TA coverage area (i.e., the grid list).

[0412] Specifically, based on the aforementioned TA coverage geographic location relationship information (including geographic overlap, geographic adjacency, and geographic non-adjacency), and considering the geographic location relationships between TAs, their logical adjacency relationships, and the network slices supported by each TA, the frequency bands of cells within each TA, the geographic location regions of the cells, and the slices supported by each cell as shown in Information Tables 2 and 3, TA-level network topology information is obtained. TA-level network topology information includes: TAI, TA-supported frequency bands, TA-supported slices, frequency bands supported by slices within each TA, TA geographic location regions, and TA adjacency relationships.

[0413] One possible implementation is to correlate and analyze information tables 2 and 3 above, and use the TAs to which each cell belongs and the supported S-NSSAIs to obtain a list of TAs that can provide services and a list of supported S-NSSAIs for each geographical location (i.e., grid). Further, by using the TAs to which cells belong, and the handover relationships or RRC idle-state reselection relationships between cells in each geographical location, the logical adjacency relationships between TAs (which can be switched in RRC connected state, or only switched in RRC idle-state reselection) and the geographical adjacency relationships between TAs (including geographical overlap, geographical proximity, and geographical non-adjacency) are obtained. This is the network topology information at the TA level, as shown in Table 5 below:

[0414] Table 5

[0415]

[0416] In another possible implementation, the network topology information at the TA level can also be described as: the TAs that a network slice can provide services for in each geographical location (i.e., the grid), and the logical adjacency relationships between TAs in each geographical location (because for a specific network slice, it is only necessary to focus on whether it can switch across TAs in a connected state, so the logical adjacency relationships here do not need to include the cases of non-connected state switching between TAs, but only need to retain the connected state switching between TAs), as shown in Table 6 below:

[0417] Table 6

[0418]

[0419]

[0420] Through the above steps, NWDAF obtains the cell-level topology information and the TA-level topology information of the region of interest.

[0421] Optionally, if NWDAF is also performing UE mobility analysis or UE communication analysis at the same time.

[0422] For example, NWDAF collects UE mobility data or UE communication data from AMF or SMF. This data includes the UE's location, serving cell at the time of registration, allowed NSSAI, S-NSSAI for establishing a session's home slice, source and destination cells during handover, and other information. By analyzing each UE's mobility trajectory and network registration events, as well as session handover events, NWDAF can further verify the nodes and connections in the network topology information generated in step four. NWDAF considers the portion of the network topology information verified by the UE mobility data or UE communication data as the valid network topology.

[0423] For example, if the network topology information is invalid, NWDAF updates the network topology information (e.g., regenerates the network topology information).

[0424] Furthermore, NWDAF uses the generated network topology information as an analysis result and sends it to the second core network element via an analysis notification message. Figure 4 The method flow shown also includes:

[0425] S460, NWDAF sends network topology information to the second core network element, or in other words, the second core network element receives network topology information from NWDAF.

[0426] For example, the second core network element can be an AMF, an NSSF, or a PCF.

[0427] Optionally, NWDAF can also provide verified and valid network topology information to the second core network elements.

[0428] Optionally, if a frequency band or cell is shut down due to energy conservation and emission reduction, or if the neighbor cell relationship changes, the AMF will receive updated information from the gNB regarding the TA and frequency band of each internal cell, the TA and frequency band of each external cell, and the neighbor cell relationship.

[0429] Furthermore, NWDAF will collect updated first information from AMF (e.g., the TA and frequency band of each cell within each gNB, and the TA and frequency band of each cell outside).

[0430] If the network topology information changes, NWDAF will send the updated analysis results to the second core network element.

[0431] After obtaining network topology information, the second core network elements can optimize network operation and decision-making. Figure 4 The method flow shown also includes:

[0432] S470, a network optimized by the second core network element.

[0433] Specifically, the second core network element optimizes the network based on the network topology information.

[0434] As one possible implementation, the second core network element optimizes the network based on the network topology information, including:

[0435] The second core network element optimizes the registration area of ​​the terminal device and / or optimizes the frequency band selection priority of the terminal device based on the network topology information.

[0436] For example, the second core network element removes TAs whose geographical location range can be included in the geographical area formed by other TAs in the registration area of ​​the terminal device, based on the geographical location of the TA.

[0437] For example, the second core network element removes TAs that are not adjacent to any other TAs in the registration area of ​​the terminal device based on the TAs adjacent to the TA.

[0438] For example, the second core network element determines, based on the frequency bands supported by the TA, the frequency bands supported by as many TAs as possible in the registration area of ​​the terminal device and the corresponding frequency band selection priority.

[0439] As another possible implementation, if the network topology information also includes network slice-related information, the second core network element optimizes the network based on the network topology information, including at least one of the following:

[0440] The second core network element optimizes at least one of the following based on the network topology information: the registration area of ​​the terminal device, the list of network slices that the terminal device is allowed to access, the list of network slices that the terminal device is targeting to access, or the frequency band selection priority of the terminal device.

[0441] For example, the second core network element, based on the list of TAs supporting network slicing and the geographical location of the TAs, forms the registration area of ​​the terminal device by TAs with consecutive geographical locations that support the network slicing.

[0442] For example, the second core network element, based on the list of TAs supporting network slicing and the TAs adjacent to the TAs, forms the registration area of ​​the terminal device with the adjacent TAs supporting the network slice.

[0443] For example, the second core network element determines the number of network slices supported by the TA that the terminal requests to access, based on the network slice list requested by the terminal and the TA list that supports network slices, and removes TAs from the registration area of ​​the terminal device whose number of TAs is different from that supported by other TAs in the registration area.

[0444] For example, the second core network element determines a list of network slices that the terminal is allowed to access based on the network slice list requested by the terminal, a list of TAs supporting network slices, and adjacent TAs. The list of network slices allowed to access by the terminal includes network slices that the terminal can access within its current registration area.

[0445] For example, the second core network element determines the list of network slices that the terminal aims to access based on the list of network slices requested by the terminal, the list of TAs supporting the network slices, and the geographical location of the TAs. The list of network slices that the terminal aims to access includes network slices that the terminal can access from its current geographical location through other TAs at that location; the list of network slices that the terminal aims to access is the list of network slices requested by the terminal or a subset thereof.

[0446] For example, the second core network element determines the frequency band selection priority of the terminal based on the list of network slices that the terminal is allowed to access or the list of network slices that the terminal aims to access, as well as the frequency bands supported by the network slices supported by the TA.

[0447] For ease of description, Figure 5 Using the network topology scenario shown as an example, this paper provides a detailed explanation of optimizing network operation and decision-making.

[0448] The AMF receives the UE's registration request message through the gNB, which carries one or more network slices that the UE wishes to access (i.e., Requested NSSAI), the CGI of the cell the UE is currently connected to, and the TAI of the tracking area to which the cell belongs.

[0449] Taking a UE simultaneously subscribing to enhanced mobile broadband (eMBB) network slicing and ultra-reliable low-latency communication (uRLLC) network slicing as an example, according to Figure 5 The first core network elements in the different topology scenarios shown perform different optimization processes.

[0450] Specific examples of AMF or NSSF processing UE registration requests or network slice selection requests are as follows.

[0451] Assumption Scenario 1: If the network topology information is that TA#1 and TA#2 or TA#3 have no logical adjacency relationship and are geographically overlapping in frequency range, and TA#3 only supports eMBB slicing, while TA#1 and TA#2 support both eMBB and uRLLC slicing.

[0452] Based on the topology information above, AMF or NSSF can optimize the decisions for Allowed NSSAI and RA as follows:

[0453] When the UE's Requested NSSAI only has eMBB, Allowed NSSAI = eMBB, RA = TA#1. This result optimizes mobility, as the UE does not need to re-register with the network when moving over a large area.

[0454] When a UE's Requested NSSAI includes both eMBB and uRLLC, Allowed NSSAI = {eMBB, uRLLC}, RA = {TA#2, TA#3}. This result optimizes uRLLC slice availability, ensuring that the UE can access the requested uRLLC slice within the RA.

[0455] Assume scenario 2: If the wireless topology is that TA#1, TA#2 and TA#3 are logically adjacent and geographically have overlapping frequency coverage, TA#3 only supports eMBB, while TA#1 and TA#2 support both eMBB and uRLLC.

[0456] Based on the above topology information, AMF or NSSF can optimize the decisions for Allowed NSSAI and RA; at the same time, PCF can also optimize RFSP decisions for the network slices available to the UE based on the above topology information, as follows:

[0457] When a UE's Requested NSSAI includes both eMBB and uRLLC, and the UE has no established uRLLC slice session, Allowed NSSAI = {eMBB}, Rejected S-NSSAI = {empty}, and RA = {TA#1}. This result is optimized for mobility, ensuring the UE does not need to re-register with the network when moving over a large area.

[0458] Meanwhile, when the UE can still register in the current RA using eMBB+uRLLC when needed, the PCF can determine the RFSP to redirect the UE based on the radio topology. Once the UE accesses the cell of TA#2 or TA#3, the UE can access the uRLLC slice through registration update.

[0459] When a UE's Requested NSSAI includes both eMBB and uRLLC, and the UE has already established a uRLLC slice session, Allowed NSSAI = {eMBB, uRLLC}, RA = {TA#2, TA#3}. This result optimizes for uRLLC slice availability.

[0460] PCF can determine the RFSP to redirect the UE based on the wireless topology, and redirect the UE to the TA2 or TA3 cell to access the uRLLC slice.

[0461] AMF / NSSF or PCF can also optimize the decisions of Allowed NSSAI, RA and RFSP according to different topology scenarios based on the analysis results of network topology information.

[0462] The above Figure 4 In the illustrated embodiment, NWDAF collects data and generates network topology information. This application also provides a communication method, such as... Figure 6 As shown, Figure 6 This is a schematic flowchart illustrating another communication method provided in an embodiment of this application, including the following steps:

[0463] S610, the access network device generates network topology information for the location of the access network device.

[0464] Specifically, the gNB generates network topology information for its location based on the TA, supported S-NSSAI and frequency bands of each internal cell, the TA, supported S-NSSAI and frequency bands of external cells, the neighbor relationships between internal cells, the neighbor relationships between internal and external cells, and the geographical location of the gNB.

[0465] For example, the network topology information of the location of the gNB includes cell-level topology information of one or more cells served by the gNB, wherein the cell-level topology information includes the cell identifier corresponding to the cell and at least one of the following: the frequency band to which the cell belongs, the S-NSSAI supported by the cell, the TA to which the cell belongs, the radio access network device to which the cell belongs, the cells adjacent to the cell, the first geographical location covered by the cell, the cells adjacent to the second geographical location covered by the cell, and the cells overlapping the third geographical location covered by the cell.

[0466] S620: The access network device sends network topology information of the location of the access network device to the first core network element, or in other words, the first core network element receives network topology information of the location of the access network device from the access network device.

[0467] Specifically, the AMF collects network topology information for the locations of each gNB.

[0468] S630, the first core network element generates network topology information for the location of the first core network element.

[0469] AMF generates network topology information for the AMF region by collecting the TA topology of each gNB location.

[0470] For example, the network topology information of the AMF region includes the topology information of one or more TAs of the AMF service, wherein the topology information of the TA includes the TA's identifier and at least one of the following: the frequency band supported by the TA, the network slice supported by the TA, the frequency band supported by the network slice supported by the TA, the geographical location of the TA, and the TA's neighboring TAs.

[0471] S640, the first core network element sends the network topology information of the location of the first core network element to the third core network element, or in other words, the third core network element receives the network topology information of the location of the first core network element from the first core network element.

[0472] Specifically, NSSF collects network topology information for each AMF region.

[0473] S640, the third core network element generates the entire network topology information.

[0474] Specifically, NSSF generates the entire network topology information based on the network topology information of each AMF region.

[0475] For example, the overall network topology information includes the topology information of one or more TAs, wherein the topology information of the TA includes the TA's identifier and at least one of the following: the frequency band supported by the TA, the network slice supported by the TA, the frequency band supported by the network slice supported by the TA, the geographical location of the TA, and the TA's neighboring TAs.

[0476] In the above method embodiments, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of this application embodiment. Furthermore, it is not necessary to perform all the operations in the above method embodiments.

[0477] It should be understood that in the above method embodiments, the terminal device and / or network device may perform some or all of the steps in the embodiments. These steps or operations are merely examples, and the embodiments of this application may also include variations of performing other operations or various operations.

[0478] It is understood that, in the above method embodiments, the method implemented by NWDAF can also be implemented by components that can be used with NWDAF (such as chips or circuits), and the method implemented by access and mobility management network elements can also be implemented by components that can be used with access and mobility management network elements.

[0479] It should also be understood that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions between different embodiments may be consistent and may be referenced by each other, and the technical features in different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0480] The above combination Figure 4 and Figure 6 The communication methods described in the embodiments of this application are detailed, primarily focusing on the interaction between various network elements. It is understood that each network element, in order to achieve the aforementioned functions, includes corresponding hardware structures and / or software modules for executing those functions.

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

[0482] The following, combined with Figures 7 to 9 This application provides a detailed description of the communication apparatus provided in its embodiments. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be found in the above method embodiments. For brevity, some content is omitted hereafter.

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

[0484] Figure 7 This is a schematic block diagram of the device 700 provided in an embodiment of this application. The device 700 includes a transceiver unit 710 and a processing unit 720. The transceiver unit 710 can implement corresponding communication functions, and the processing unit 720 is used for data processing. The transceiver unit 710 can also be referred to as a communication interface or a communication unit. When the transceiver unit 710 implements the function of acquiring information, it can also be referred to as an acquisition unit.

[0485] Optionally, the device 700 may further include a storage unit for storing instructions and / or data, and the processing unit 720 may read the instructions and / or data from the storage unit to enable the device to implement the aforementioned method embodiments.

[0486] The device 700 can be used to perform the actions performed by the network devices (such as the core network elements and access network devices mentioned above) in the above method embodiments. In this case, the device 700 can be a network device or a component that can be configured in the network device. The transceiver unit 710 is used to perform the transceiver-related operations on the network device side in the above method embodiments, and the processing unit 720 is used to perform the processing-related operations on the network device side in the above method embodiments.

[0487] As a design feature, the device 700 is used to perform the actions performed by the data analysis network element in the above method embodiments.

[0488] One possible implementation is that the transceiver unit 710 is used to acquire multiple tracking area (TA) information from the first core network element;

[0489] Processing unit 720 is configured to acquire at least one of the following information:

[0490] Information about the serving cell of the terminal device, information about neighboring cells of the serving cell, mobile information of the terminal device, and geographical location information of the terminal device.

[0491] Optionally, the transceiver unit 710 is further configured to acquire the MDT results of the terminal device, wherein the MDT results of the terminal device include at least one of the following information:

[0492] The terminal device's serving cell information, neighboring cell information, mobile information, and geographic location information;

[0493] The processing unit 720 generates network topology information based on the multiple TA information, including:

[0494] The processing unit 720 generates the network topology information based on the multiple TA information and the MDT results of the terminal device.

[0495] Optionally, the transceiver unit 710 is further configured to acquire information related to the access network equipment from the first core network element, including the TA and frequency band of the first cell and the TA and frequency band of the second cell.

[0496] The first cell is the cell managed by the access network device, and the second cell is the cell managed by the access network device adjacent to the access network device.

[0497] The processing unit 720 generates network topology information based on the multiple TA information, including:

[0498] The processing unit 720 generates the network topology information based on the multiple TA information and the information related to the access network device.

[0499] Optionally, the transceiver unit 710 is further configured to acquire access network device-related information from the access network device, the access network device-related information including at least one of the following:

[0500] The geographical location of the access network device, the TA and frequency band of the first cell, the TA and frequency band of the second cell, and the network topology information of the location of the access network device.

[0501] The first cell is the cell managed by the access network device, the second cell is the cell managed by the access network device adjacent to the access network device, and the network topology information of the location of the access network device includes the relationship between multiple cells;

[0502] The processing unit 720 generates network topology information based on the multiple TA information, including:

[0503] The processing unit 720 generates the network topology information based on the multiple TA information and the information related to the access network device.

[0504] Optionally, the processing unit 720 is further configured to perform terminal device mobility analysis or terminal device communication analysis to obtain analysis data;

[0505] The processing unit 720 verifies the validity of the network topology information based on the analysis data.

[0506] Optionally, the transceiver unit 710 is also used to send the network topology information to the second core network element, and the network topology information is used by the second core network element to optimize the network.

[0507] The device 700 can implement the steps or processes corresponding to those executed by the data analysis network element in the method embodiment according to the present application. The device 700 may include units for executing the methods executed by the data analysis network element in the method embodiment. Furthermore, each unit in the device 700 and the other operations and / or functions described above are respectively for implementing the corresponding processes of the method embodiment in the data analysis network element of the method embodiment.

[0508] Among them, when the device 700 is used to perform Figure 4When the method is in use, the transceiver unit 710 can be used to execute the transceiver steps in the method, such as steps S420, S431, S432, S433, S440, S441, S450, S451, S452 and S460; the processing unit 720 can be used to execute the processing steps in the method, such as step S430.

[0509] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0510] As an alternative design, the device 700 is used to perform the actions performed by the second core network element in the above method embodiment.

[0511] One possible implementation is that the transceiver unit 710 is used to acquire network topology information from the data analysis network element or generate the network topology information, which includes the association relationship between the multiple TAs;

[0512] The processing unit 720 is used to optimize the network based on the network topology information.

[0513] Optionally, the processing unit 720 optimizes the network based on the network topology information, including:

[0514] The processing unit 720 optimizes the registration area of ​​the terminal device and / or optimizes the frequency band selection priority of the terminal device based on the network topology information.

[0515] Optionally, if the network topology information also includes information related to network slices, the processing unit 720 optimizes the network based on the network topology information, including at least one of the following:

[0516] The processing unit 720 optimizes at least one of the following based on the network topology information: the registration area of ​​the terminal device, the list of network slices that the terminal device is allowed to access, the list of network slices that the terminal device is targeting to access, or the frequency band selection priority of the terminal device.

[0517] The device 700 can implement the steps or processes corresponding to the second core network element executed in the method embodiment according to the present application. The device 700 may include units for executing the method executed by the second core network element in the method embodiment. Furthermore, each unit in the device 700 and the other operations and / or functions described above are respectively for implementing the corresponding processes of the method embodiment in the second core network element of the method embodiment.

[0518] Among them, when the device 700 is used to perform Figure 4When the method is in use, the transceiver unit 710 can be used to execute the transceiver steps in the method, such as steps S440, S441, S451, S452 and S460; the processing unit 720 can be used to execute the processing steps in the method, such as step S470.

[0519] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0520] As another design, the device 700 is used to perform the actions performed by the first core network element in the above method embodiment.

[0521] One possible implementation is that the transceiver unit 710 is used to acquire multiple tracking area (TA) information, which is used to generate network topology information, including the association relationship between the multiple TAs.

[0522] The transceiver unit 710 is used to send the multiple tracking area TA information to the data analysis network element.

[0523] Optionally, the transceiver unit 710 is used to acquire network topology information from the data analysis network element.

[0524] Optionally, the processing unit 720 is used to optimize the network according to the network topology information, including: the first core network element optimizing the registration area of ​​the terminal device and / or optimizing the frequency band selection priority of the terminal device according to the network topology information.

[0525] Optionally, the network topology information also includes network slice-related information. The processing unit 720 optimizes the network based on the network topology information, including at least one of the following: the processing unit 720 optimizes the registration area of ​​the terminal device, optimizes the list of network slices that the terminal device is allowed to access, optimizes the list of network slices that the terminal device is targeting to access, or optimizes the frequency band selection priority of the terminal device based on the network topology information.

[0526] The device 700 can implement the steps or processes corresponding to the first core network element executed in the method embodiment according to the present application. The device 700 may include units for executing the method executed by the first core network element in the method embodiment. Furthermore, each unit in the device 700 and the other operations and / or functions described above are respectively for implementing the corresponding processes of the method embodiment in the first core network element of the method embodiment.

[0527] Among them, when the device 700 is used to perform Figure 4 When using the method, the transceiver unit 710 can be used to execute the transceiver steps in the method, such as steps S410 and S420.

[0528] When the device 700 is used to perform Figure 6 When the method is in use, the transceiver unit 710 can be used to execute the transceiver steps in the method, such as steps S620 and S640; the processing unit 720 can be used to execute the processing steps in the method, such as step S630.

[0529] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0530] As another design, the device 700 is used to perform the actions performed by the access network device in the above method embodiments.

[0531] One possible implementation is that the processing unit 720 is configured to generate network topology information of the location of the access network device based on the TA and frequency band of the first cell, the TA and frequency band of the second cell, the neighbor cell relationships between the first cells, and the neighbor cell relationships between the first cell and the second cell.

[0532] Transceiver unit 710 is used to send information related to the access network device to core network elements. The information related to the access network device includes at least one of the following:

[0533] The geographical location of the access network device, the TA and frequency band of the first cell, the TA and frequency band of the second cell, and the network topology information of the location of the access network device.

[0534] The first cell is the cell managed by the access network device, the second cell is the cell managed by the access network device adjacent to the access network device, and the network topology information of the location of the access network device includes the relationship between multiple cells.

[0535] The apparatus 700 can implement steps or processes corresponding to those executed by the access network device in the method embodiments according to the present application. The apparatus 700 may include units for executing the methods performed by the access network device in the method embodiments. Furthermore, each unit in the apparatus 700 and the other operations and / or functions described above respectively implement the corresponding processes of the method embodiments in the access network device.

[0536] Among them, when the device 700 is used to perform Figure 4 When the method is in use, the transceiver unit 710 can be used to execute the transceiver steps in the method, such as step S410.

[0537] When the device 700 is used to perform Figure 6 When the method is in use, the transceiver unit 710 can be used to execute the transceiver steps in the method, such as step S620; the processing unit 720 can be used to execute the processing steps in the method, such as step S610.

[0538] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0539] As another design, the device 700 is used to perform the actions performed by the third core network element in the above method embodiment.

[0540] One possible implementation is that the transceiver unit 710 is used to obtain network topology information of the location of the first core network element from the first core network element, and the processing unit 720 is used to generate full network topology information based on the network topology information of the location of the first core network element.

[0541] The apparatus 700 can implement the steps or processes corresponding to those executed by the third core network element in the method embodiment according to the present application. The apparatus 700 may include units for executing the methods performed by the third core network element in the method embodiment. Furthermore, each unit in the apparatus 700 and the other operations and / or functions described above respectively implement the corresponding processes of the method embodiment in the third core network element of the method embodiment.

[0542] Among them, when the device 700 is used to perform Figure 6 When the method is in use, the transceiver unit 710 can be used to execute the transceiver steps in the method, such as step S640; the processing unit 720 can be used to execute the processing steps in the method, such as step S650.

[0543] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0544] The processing unit 720 in the above embodiments can be implemented by at least one processor or processor-related circuitry. The transceiver unit 710 can be implemented by a transceiver or transceiver-related circuitry. The storage unit can be implemented by at least one memory.

[0545] like Figure 8 As shown, this application embodiment also provides an apparatus 800. The apparatus 800 includes a processor 810 and may further include one or more memories 820. The processor 810 is coupled to the memory 820, which stores computer programs or instructions and / or data. The processor 810 executes the computer programs or instructions and / or data stored in the memory 820, causing the methods in the above method embodiments to be executed. Optionally, the apparatus 800 includes one or more processors 810.

[0546] Alternatively, the memory 820 may be integrated with the processor 810 or set separately.

[0547] Optionally, such as Figure 8 As shown, the device 800 may further include a transceiver 830 for receiving and / or transmitting signals. For example, a processor 810 is used to control the transceiver 830 to receive and / or transmit signals.

[0548] As one approach, the device 800 is used to implement the operations performed by network devices (such as the aforementioned core network elements, access network devices, etc.) in the above method embodiments.

[0549] This application also provides an apparatus 900, which may be a network device (such as the access network device described above) or a chip disposed within the network device. The apparatus 900 can be used to perform the operations performed by the network device (such as the access network device described above) in the above method embodiments.

[0550] Figure 9 A simplified structural diagram is shown. This device can be a network device (such as the access network device described above), and device 900 includes part 910 and part 920. Part 910 is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals to baseband signals; part 920 is mainly used for baseband processing and controlling the network device. Part 910 is commonly referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver. Part 920 is typically the control center of the network device, often referred to as a processing unit, used to control the network device to perform the processing operations described in the above method embodiments.

[0551] The transceiver unit of section 910, also known as a transceiver or transceiver unit, includes an antenna and radio frequency (RF) circuitry, where the RF circuitry is primarily used for RF processing. Optionally, the devices in section 910 that implement the receiving function can be considered as receiving units, and the devices that implement the transmitting function can be considered as transmitting units; that is, section 910 includes both receiving and transmitting units. The receiving unit can also be called a receiver, receiver circuit, or receiving unit, while the transmitting unit can be called a transmitter, transmitter, or transmitting circuit.

[0552] The 920 section may include one or more single boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control the base station. If multiple single boards exist, they can be interconnected to enhance processing capabilities. As an optional implementation, multiple single boards may share one or more processors, multiple single boards may share one or more memories, or multiple single boards may simultaneously share one or more processors.

[0553] It should be understood that Figure 9This is merely an example and not a limitation; the network devices described above, including transceiver units and processing units, may not rely on... Figure 9 The structure shown.

[0554] When the device 900 is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. Alternatively, the device 900 can be a chip system or a processing system, enabling devices equipped with the device 900 to implement the methods and functions of the embodiments of this application. For example, the processing unit 920 can be a processing circuit within the chip system or processing system, controlling devices equipped with the chip system or processing system. It can also be coupled to a storage unit to call instructions stored in the storage unit, enabling the device to implement the methods and functions of the embodiments of this application. The transceiver unit 910 can be an input / output circuit within the chip system or processing system, outputting information processed by the chip system or inputting data or signaling information to be processed into the chip system for processing.

[0555] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by network devices (such as the aforementioned core network elements, access network devices, etc.) in the above-described method embodiments.

[0556] For example, when the computer program is executed by a computer, it enables the computer to implement the method executed by the network device in the above method embodiments.

[0557] This application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to implement the method described above, which is executed by network devices (such as the aforementioned core network elements, access network devices, etc.).

[0558] This application also provides a communication system, which includes network devices (such as the core network elements and access network devices mentioned above) in the above embodiments, such as NWDAF and AMF.

[0559] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0560] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0561] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM can include a variety of forms, such as: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0562] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0563] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

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

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

[0566] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to implement the solution provided in this application, depending on actual needs.

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

[0568] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs). For example, the aforementioned available media may include, but are not limited to, various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A communication method, characterized in that, include: The data analysis network element obtains multiple tracking area (TA) information from the first core network element; The data analysis network element generates network topology information based on the multiple TA information, and the network topology information includes the relationships between the multiple TAs. The association relationships among the plurality of TAs include at least one of the following: The relationships between the frequency bands supported by the multiple TAs, the relationships between the network slices supported by the multiple TAs, the relationships between the geographical locations of the multiple TAs, and the adjacency relationships between the multiple TAs.

2. The method according to claim 1, characterized in that, The method further includes: The data analysis network element acquires at least one of the following information: The terminal device's serving cell information, the serving cell's neighboring cell information, the terminal device's mobility information, and the terminal device's geographical location information.

3. The method according to claim 2, characterized in that, The method further includes: The data analysis network element obtains the minimum drive test (MDT) results of the terminal device, and the MDT results of the terminal device include at least one of the following: The terminal device's serving cell information, the serving cell's neighbor cell information, the terminal device's movement information, and the terminal device's geographical location information; The data analysis network element generates network topology information based on the multiple TA information, including: The data analysis network element generates the network topology information based on the multiple TA information and the MDT results of the terminal device.

4. The method according to claim 2 or 3, characterized in that, The information of the serving cell of the terminal device includes at least one of the following: the identifier of the access network device providing services to the terminal device, the identifier of the serving cell of the terminal device, the identifier of the TA to which the serving cell belongs, and the frequency band of the serving cell; The neighbor cell information of the serving cell includes at least one of the following: the identifiers of the neighboring cells of the serving cell, the identifiers of the TAs to which the neighboring cells belong, and the frequency bands of the neighboring cells; The mobility information of the terminal device includes: the adjacency relationship between the source cell before the handover and the destination cell after the handover and / or the type of handover.

5. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The data analysis network element acquires access network device-related information from the first core network element. This access network device-related information includes the local transfer address (TA) and frequency band of the first cell, and the TA and frequency band of the second cell. Wherein, the first cell is a cell managed by the access network device, and the second cell is a cell managed by an access network device adjacent to the access network device; The data analysis network element generates network topology information based on the multiple TA information, including: The data analysis network element generates the network topology information based on the multiple TA information and information related to the access network device.

6. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The data analysis network element acquires access network device-related information from the access network equipment, and the access network device-related information includes at least one of the following: The geographical location of the access network device, the local area coordinate (TA) and frequency band of the first cell, the TA and frequency band of the second cell, and the network topology information of the location of the access network device. Wherein, the first cell is a cell managed by the access network device, the second cell is a cell managed by an access network device adjacent to the access network device, and the network topology information of the location of the access network device includes the association relationship between multiple cells; The data analysis network element generates network topology information based on the multiple TA information, including: The data analysis network element generates the network topology information based on the multiple TA information and information related to the access network device.

7. The method according to any one of claims 1 to 3, characterized in that, The network topology information includes the TA identifier and at least one of the following: The frequency band supported by the TA, the geographical location of the TA, or the TA adjacent to the TA.

8. The method according to claim 7, characterized in that, The multiple TAs correspond to multiple cells, and the network topology information further includes the cell identifier corresponding to the cell and at least one of the following: The frequency band to which the cell belongs, the TA to which the cell belongs, the radio access network device to which the cell belongs, the adjacent cells of the cell, the first geographical location covered by the cell, the cells whose second geographical location is adjacent to the first geographical location, and the cells whose third geographical location overlaps with the first geographical location.

9. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The data analysis network element performs mobile analysis of the terminal device or communication analysis of the terminal device to obtain analysis data; The data analysis network element verifies the validity of the network topology information based on the analyzed data.

10. The method according to claim 9, characterized in that, If the network topology information is invalid, the method further includes: The data analysis network element updates the network topology information.

11. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The data analysis network element obtains network slice information supported by each of the multiple TAs from the first core network element; The data analysis network element generates network topology information based on the multiple TA information, including: The data analysis network element generates the network topology information based on the multiple TA information and the network slice information supported by each of the multiple TAs.

12. The method according to claim 11, characterized in that, The network topology information also includes at least one of the following: The network slices supported by the TA, the frequency bands supported by the network slices supported by the TA, and the network slices supported by the cell.

13. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The data analysis network element sends the network topology information to the second core network element, and the network topology information is used by the second core network element to optimize the network.

14. A method of communication, characterized in that, include: The second core network element obtains network topology information from the data analysis network element, and the network topology information includes the association relationship between multiple TAs; The second core network element optimizes the network based on the network topology information. The association relationships among the plurality of TAs include at least one of the following: The relationships between the frequency bands supported by the multiple TAs, the relationships between the network slices supported by the multiple TAs, the relationships between the geographical locations of the multiple TAs, and the adjacency relationships between the multiple TAs.

15. The method according to claim 14, characterized in that, The second core network element optimizes the network based on the network topology information, including: The second core network element optimizes the registration area of ​​the terminal device and / or optimizes the frequency band selection priority of the terminal device based on the network topology information.

16. The method according to claim 15, characterized in that, The second core network element optimizes the registration area of ​​the terminal device based on the network topology information, including: The second core network element, based on the geographical location of the TA, removes TAs from the registration area of ​​the terminal device whose geographical location range can be contained within a geographical area formed by other TAs in the registration area; and / or, The second core network element removes TAs that are not adjacent to any other TAs in the registration area of ​​the terminal device based on the TAs adjacent to the TA; The second core network element optimizes the frequency band selection priority of the terminal device based on the network topology information, including: The second core network element determines, based on the frequency bands supported by the TA, the frequency bands supported by as many TAs as possible in the registration area of ​​the terminal device and the corresponding frequency band selection priority.

17. The method according to claim 14, characterized in that, When the network topology information also includes network slice-related information, the second core network element optimizes the network based on the network topology information, including at least one of the following: The second core network element optimizes at least one of the following based on the network topology information: the registration area of ​​the terminal device, the list of network slices that the terminal device is allowed to access, the list of network slices that the terminal device is targeting to access, or the frequency band selection priority of the terminal device.

18. The method according to claim 17, characterized in that, The second core network element optimizes the registration area of ​​the terminal device based on the network topology information, including at least one of the following: The second core network element, based on the list of TAs supporting network slicing and the geographical location of the TAs, forms the registration area of ​​the terminal device by TAs with consecutive geographical locations that support the network slicing; The second core network element, based on the list of TAs supporting network slicing and the TAs adjacent to the TAs, forms the registration area of ​​the terminal device by combining the adjacent TAs supporting the network slicing; The second core network element determines the number of network slices supported by the TA in the network slice list requested by the terminal and the TA list supporting network slices, and removes TAs from the registration area of ​​the terminal device whose number of TAs is different from that of other TAs in the registration area.

19. The method according to claim 17 or 18, characterized in that, The second core network element optimizes the list of network slices that the terminal device is allowed to access based on the network topology information, including: The second core network element determines the list of network slices that the terminal is allowed to access based on the network slice list requested by the terminal, the TA list that supports network slices, and the TAs adjacent to the TA.

20. The method according to claim 17 or 18, characterized in that, The second core network element optimizes the list of network slices that the terminal device aims to access based on the network topology information, including: The second core network element determines the list of network slices that the terminal wants to access based on the list of network slices requested by the terminal, the list of TAs that support network slices, and the geographical location of the TAs.

21. The method according to claim 17 or 18, characterized in that, The second core network element optimizes the frequency band selection priority of the terminal device based on the network topology information, including: The second core network element determines the frequency band selection priority of the terminal based on the network slice list requested by the terminal, the list of TAs supporting network slices, the TAs adjacent to the TAs, and the frequency bands supported by the network slices supported by the TAs; and / or The second core network element determines the frequency band selection priority of the terminal based on the network slice list requested by the terminal, the list of TAs that support network slices, the geographical location of the TAs, and the frequency bands supported by the network slices supported by the TAs.

22. A communication apparatus, characterized in that, include: The acquisition unit is used to acquire multiple tracking area (TA) information from the first core network element; A processing unit is configured to generate network topology information based on the plurality of TA information, wherein the network topology information includes the association relationships between the plurality of TAs. The association relationships among the plurality of TAs include at least one of the following: The relationships between the frequency bands supported by the multiple TAs, the relationships between the network slices supported by the multiple TAs, the relationships between the geographical locations of the multiple TAs, and the adjacency relationships between the multiple TAs.

23. The apparatus according to claim 22, characterized in that, The device further includes: The sending unit is used to send the network topology information to the second core network element, and the network topology information is used by the second core network element to optimize the network.

24. A mobile communication device, characterized in that, include: The acquisition unit is used to acquire network topology information from data analysis network elements or generate the network topology information, wherein the network topology information includes the association relationship between multiple TAs; The processing unit is used to optimize the network based on the network topology information. The association relationships among the plurality of TAs include at least one of the following: The relationships between the frequency bands supported by the multiple TAs, the relationships between the network slices supported by the multiple TAs, the relationships between the geographical locations of the multiple TAs, and the adjacency relationships between the multiple TAs.

25. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by the device, causes the device to perform the method as described in any one of claims 1 to 13, or causes the device to perform the method as described in any one of claims 14 to 21.

26. A chip system, characterized in that, include: A processor is configured to retrieve and run a computer program from memory, causing a communication device equipped with the chip system to perform the method as described in any one of claims 1 to 13; or, causing a communication device equipped with the chip system to perform the method as described in any one of claims 14 to 21.

27. A communication device, characterized in that, include: Memory, used to store computer programs; A processor is configured to execute a computer program stored in the memory to cause the communication device to perform the method of any one of claims 1 to 13, or to cause the communication device to perform the method of any one of claims 14 to 21.

28. A communication system, characterized in that, The communication system includes: Core network elements are used to send multiple tracking area (TA) information to data analysis network elements; and The data analysis network element is used to perform the method as described in any one of claims 1 to 13.

Images