Communication method and apparatus

Abstract

The application discloses a communication method and device, and belongs to the technical field of communication. The communication method of the application comprises the following steps: in the case that a core network function serving a first terminal is a first core network function, the first core network function sends a first registration message to a second core network function, and the first registration message carries first indication information; the first indication information is used for indicating that the first terminal is a terminal accessing a network through a first relay device, or indicating that the second core network function performs a registration-related operation, wherein the first terminal is a terminal accessing a network through the first relay device.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a communication method and apparatus. Background Technology

[0002] Relay technology involves adding one or more relay devices between access network equipment and terminals. These relay devices are responsible for forwarding wireless signals one or more times, meaning the wireless signal must travel through multiple hops to reach the terminal. Taking a simple two-hop relay as an example, a single access network equipment-terminal link is split into two links: access network equipment-relay device and relay device-terminal. This allows a lower-quality link to be replaced with two higher-quality links, resulting in higher link capacity and better coverage.

[0003] In scenarios where a terminal can communicate with network-side devices via a relay device, the terminal may leave the relay device or switch to another relay device. During this process, the terminal's communication performance may be affected. Summary of the Invention

[0004] This application provides a communication method and apparatus that can solve the problem of terminal communication performance being affected.

[0005] Firstly, a communication method is provided, including:

[0006] When the core network function serving the first terminal is the first core network function, the first core network function sends a first registration message to the second core network function. The first registration message carries first indication information. The first indication information is used to indicate that the first terminal is a terminal that accesses the network through the first relay device, or to instruct the second core network function to perform deregistration-related operations, wherein the first terminal is a terminal that accesses the network through the first relay device.

[0007] Secondly, a communication method is provided, including:

[0008] The second core network function receives a first registration message sent by the first core network function, the first core network function being a core network function serving the first terminal; the first registration message carries first indication information.

[0009] The second core network function performs at least one of the following:

[0010] Stop deregistering the third core network function of the first terminal that was not registered using the first instruction information;

[0011] Cancel the third core network function of the first terminal registered using the first instruction information;

[0012] Cancel the third core network function of the first terminal that was not registered using the first instruction information;

[0013] The first core network function will not be cancelled.

[0014] Thirdly, a communication device is provided, comprising:

[0015] The sending module is used to send a first registration message to a second core network function when the core network function serving the first terminal is the first core network function. The first registration message carries first indication information, which is used to indicate that the first terminal is a terminal that accesses the network through a first relay device, or to indicate that the second core network function performs a deregistration-related operation. The first terminal is a terminal that accesses the network through a first relay device.

[0016] Fourthly, a communication device is provided, comprising:

[0017] The receiving module is used to receive a first registration message sent by a first core network function, wherein the first core network function is a core network function that serves a first terminal; the first registration message carries first indication information.

[0018] The second core network function performs at least one of the following:

[0019] Stop deregistering the third core network function of the first terminal that was not registered using the first instruction information;

[0020] Cancel the third core network function of the first terminal registered using the first instruction information;

[0021] Cancel the third core network function of the first terminal that was not registered using the first instruction information;

[0022] The first core network function will not be cancelled.

[0023] Fifthly, a first core network function is provided, the first core network function including a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0024] In a sixth aspect, a first core network function is provided, including a processor and a communication interface, wherein the communication interface is used to send a first registration message to a second core network function when the core network function serving the first terminal is the first core network function. The first registration message carries first indication information, which is used to indicate that the first terminal is a terminal that accesses the network through a first relay device, or to indicate that the second core network function performs a deregistration-related operation, wherein the first terminal is a terminal that accesses the network through a first relay device.

[0025] In a seventh aspect, a second core network function is provided, the second core network function including a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0026] Eighthly, a second core network function is provided, including a processor and a communication interface, wherein the communication interface is used to receive a first registration message sent by a first core network function, the first core network function being a core network function serving a first terminal; the first registration message carries first indication information; the second core network function performs at least one of the following: stopping the deregistration of a third core network function serving the first terminal that has not registered using the first indication information; deregistering a third core network function serving the first terminal that has registered using the first indication information; deregistering a third core network function serving the first terminal that has not registered using the first indication information; and not deregistering the first core network function.

[0027] A ninth aspect provides a communication system, comprising: a terminal, a relay device, and a network-side device. The network-side device includes a first core network function and a second core network function. The first core network function is used to execute the steps of the communication method as described in the first aspect, and the second core network function is used to execute the steps of the communication method as described in the second aspect. The terminal is used to execute the steps of the method executed by the terminal in various embodiments of this application, and the relay device is used to execute the steps of the method executed by the relay device in various embodiments of this application.

[0028] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0029] Eleventhly, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0030] In a twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and executed by at least one processor to implement the steps of the communication method as described in the first or second aspect.

[0031] In this embodiment, when the core network function serving the first terminal is the first core network function, the first core network function sends a first registration message to the second core network function. The first registration message carries first indication information, which is used to indicate that the first terminal is a terminal accessing the network through the first relay device, or to instruct the second core network function to perform deregistration-related operations. In the above scheme, when the terminal accesses the network through the first relay device, the first core network function can feed back terminal-related information or deregistration-related operations to the second core network function, so that the second core network function can make correct decisions and avoid affecting the terminal's communication. Attached Figure Description

[0032] Figure 1 This is a structural diagram of a wireless communication system to which the embodiments of this application can be applied;

[0033] Figure 2 This is one of the flowcharts illustrating the communication method provided in the embodiments of this application;

[0034] Figure 3 This is one of the interactive flow diagrams of the communication method provided in the embodiments of this application;

[0035] Figure 4 This is the second schematic diagram of the interaction flow of the communication method provided in the embodiments of this application;

[0036] Figure 5 This is a second schematic flowchart of the communication method provided in the embodiments of this application;

[0037] Figure 6 This is one of the structural schematic diagrams of the communication device provided in the embodiments of this application;

[0038] Figure 7 This is a second schematic diagram of the communication device provided in the embodiments of this application;

[0039] Figure 8 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application;

[0040] Figure 9 This is a schematic diagram of the network-side device provided in the embodiments of this application. Detailed Implementation

[0041] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0042] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0043] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0044] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment 12 may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment 12 may include base stations, WLAN access points, or WiFi nodes, etc. Base stations may be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B node, home evolved B node, Transmitting Receiving Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for description, and the specific type of base station is not limited.Core network equipment may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Function. Function (AF), etc. It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment.

[0045] First, the concepts involved in the embodiments of this application will be introduced:

[0046] Relay equipment includes, for example, vehicle-mounted relay equipment and mobile base station relays (MBSRs).

[0047] Each relay is serviced by a core network function (such as AMF, which can be represented as an AMF-relay device), which maintains the relay context within the AMF-relay device.

[0048] The Relay context includes information related to the relay device, such as information about the core network functions that serve the relay device, like the AMF ID.

[0049] In addition, each terminal is served by a core network function (such as AMF, i.e., AMF-terminal or AMF-UE), which maintains the terminal context. When the terminal is relayed by a relay device, the terminal context will include relay device-related information, such as the AMF ID (which is associated with Link information), which indicates the AMF serving the relay device.

[0050] Typically, only one AMF retains the terminal context. When a terminal moves with a relay device and does not perform mobility registration, the terminal's context will migrate from the old Access and Mobility Management Function (AMF) to the new AMF. Once the terminal stops moving with the relay device, it will use its original terminal identifier ID (assigned by the old AMF and carrying information from the old AMF) to send registration requests or other messages. This will cause the access network device or the new AMF to obtain the terminal context from the old AMF. However, the terminal context in the old AMF may have already been migrated, thus affecting the terminal's communication.

[0051] The communication method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0052] Figure 2 This is one of the flowcharts illustrating the communication method provided in the embodiments of this application. For example... Figure 2 As shown, the method provided in this embodiment includes:

[0053] Step 101: When the core network function serving the first terminal is the first core network function, the first core network function sends a first registration message to the second core network function, and the first registration message carries first instruction information.

[0054] The first instruction information is used to indicate that the first terminal is a terminal that accesses the network through the first relay device, or to instruct the second core network function to perform a deregistration-related operation, wherein the first terminal is a terminal that accesses the network through the first relay device.

[0055] Specifically, the first core network function can be AMF, and the second core network function can be UDM. Of course, in other embodiments of this application, the first core network function can also be SMF, and the second core network function can also be a server, etc.

[0056] It should be noted that the first terminal is a terminal that accesses the network through the first relay device. Here, the network may include a base station and a core network, and the core network may include the functions of the first core network. Furthermore, the core network may also include the functions of a second core network.

[0057] In scenarios where the first core network function provides services to the first terminal, for example, when the first terminal updates its location while moving with the first relay device, and the original core network function is changed to the first core network function to provide services; or, when the first terminal does not follow the first relay device and requests registration from the access network device, and the access network device requests the first core network function; or, when the first terminal accesses the network through the first relay device, the first core network function sends a first registration message carrying first indication information to the second core network function. The first indication information is used to indicate that the first terminal is a terminal that accesses the network through the first relay device.

[0058] For example, when the first indication information is used to indicate that the first terminal is a terminal that accesses the network through the first relay device, the first core network function can notify the second core network function that the first terminal accesses the network through the first relay device, that is, the first terminal can send messages through the first relay device, that is, the first terminal follows the first relay device.

[0059] Alternatively, the first instruction information is used to instruct the second core network function to perform deregistration-related operations; wherein, the first terminal is a terminal that accesses the network through the first relay device.

[0060] For example, deregistration-related operations may include deregistering core network functions (such as AMF) or stopping the deregistration of core network functions (such as AMF).

[0061] Cancellation of core network functions may include canceling the core network functions of the first terminal that were registered using the first instruction information, or canceling the core network functions of the first terminal that were not registered using the first instruction information.

[0062] Stopping the deregistration of core network functions may include stopping the deregistration of core network functions of the first terminal that have not been registered using the first instruction information, or stopping the deregistration of the current first core network function.

[0063] Cancelling a core network function means that the core network function does not need to retain the context of the first terminal it serves, reducing resource waste and improving resource utilization. Stopping the cancellation of a core network function means that the core network function serving the first terminal is not cancelled. This allows the first terminal to easily obtain the terminal's context from the previously uncancelled core network function when accessing the network or in other scenarios without going through the first relay device, thus not affecting the communication of the first terminal.

[0064] In this embodiment, when the core network function serving the first terminal is the first core network function, the first core network function sends a first registration message to the second core network function. The first registration message carries first indication information, which is used to indicate that the first terminal is a terminal accessing the network through the first relay device, or to instruct the second core network function to perform deregistration-related operations. In the above scheme, when the terminal accesses the network through the first relay device, the first core network function can feed back terminal-related information or deregistration-related operations to the second core network function, so that the second core network function can make correct decisions and avoid affecting the terminal's communication.

[0065] Optionally, when the first terminal is a terminal that sends messages to the core network function through the first relay device, i.e., the first terminal follows the first relay device, the deregistration operation may include at least one of the following:

[0066] Cancel the third core network function of the service first terminal registered using the first instruction information;

[0067] Cancel the third core network function of the first terminal that was not registered using the first instruction information;

[0068] Stop deregistering the first core network function.

[0069] For example, since there is a limit to the number of core network functions (such as AMF) that retain the terminal context, for example, at most only two core network functions can retain the context of the first terminal. For example, if the first registration message is a second registration message carrying the first indication information sent to the second core network function (assuming that there is a service that has not been registered using the first indication information and the third core network function of the first terminal has not been deregistered), then it is necessary to deregister the service that was previously registered using the first indication information and the third core network function of the first terminal.

[0070] For example, when the first terminal can obtain information about the core network function serving the first terminal from the network-side device, even if there was a core network function that previously served the first terminal and was not registered using the first instruction information, it is not necessary for the third core network function that previously served the first terminal to retain the context of the first terminal. Even if the first terminal does not follow the first relay device or needs to send messages to the first core network function, the first terminal can still send information carrying the core network function that previously served the first terminal to the first core network function. The core network function that previously served the first terminal retains the context of the first terminal, thereby enabling the first core network function to obtain the context of the first terminal.

[0071] For example, when the first terminal accesses the network for the first time through the first relay device, it does not need to cancel the first core network function. That is, the first core network function retains the context of the first terminal, so that subsequent network-side devices can easily obtain the context of the first terminal.

[0072] In the above embodiments, when the first terminal is a terminal that sends messages to the core network function through the first relay device, that is, the first terminal follows the first relay device, the first core network function can instruct the second core network function to perform at least one of the following deregistration-related operations: deregister the third core network function that serves the first terminal registered using the first instruction information; deregister the third core network function that serves the first terminal that has not registered using the first instruction information, that is, the third core network function does not need to retain the context of the first terminal, thereby reducing resource waste; stop deregistering the first core network function, which allows network-side devices to easily obtain the context of the first terminal from the first core network function, thereby avoiding affecting the communication of the first terminal.

[0073] Optionally, when the first terminal moves with the first relay device, or when the first core network function receives third indication information for the first relay device from the access network device, the deregistration operation may include at least one of the following:

[0074] Stop deregistering the third core network function of the service first terminal that was not registered using the first instruction information;

[0075] Cancel the third core network function of the service first terminal registered using the first instruction information;

[0076] The third indication information is used to indicate access point updates, core network function relocation, or location updates.

[0077] For example, in the case where the first terminal moves to follow the first relay device, or the core network function serving the first relay device is relocated, or the access point of the first relay device is updated, or the location of the first relay device is updated:

[0078] Assuming the third core network function is the core network function that previously served the first terminal, and this third core network function did not use the first instruction information when registering with the second core network function, in order to facilitate the subsequent acquisition of the context of the first terminal, such as when the first terminal does not follow the first relay device and the first core network function needs to be changed, the context of the first terminal stored in the third core network function needs to be retained, that is, the third core network function is not deregistered, which means the deregistration of the third core network function is stopped.

[0079] For example, since there is a limit to the number of core network functions (such as AMF) that retain the terminal context, for example, at most only two core network functions can retain the context of the first terminal. For example, if the first registration message is a second registration message sent to the second core network function carrying the first indication information (assuming that there is a service registered without using the first indication information and the third core network function of the first terminal has not been deregistered), then it is necessary to deregister the service previously registered with the first indication information and the third core network function of the first terminal.

[0080] In the above embodiments, when the first terminal moves with the first relay device, or when the first core network function receives third indication information for the first relay device sent by the access network device, the first core network function may instruct the second core network function to perform at least one of the following deregistration-related operations: deregister the third core network function that serves the first terminal using the first indication information, i.e., the third core network function does not need to retain the context of the first terminal, thereby reducing resource waste; stop deregistering the third core network function that serves the first terminal without using the first indication information, so that the first core network function can easily obtain the context of the first terminal from the third core network function, thereby avoiding affecting the communication of the first terminal.

[0081] Optionally, in scenarios where the terminal does not follow the first relay device, or where the first core network function receives a message that the terminal did not send through the first relay device (i.e., left the first relay device and sent the message to the first core network function through the access network device), the method may further include:

[0082] The first core network function receives the first message sent by the second terminal and stops sending the first registration message to the second core network function;

[0083] The second terminal is a terminal that does not send messages to the core network function through the first relay device.

[0084] Specifically, the first core network function receives the first message sent by the second terminal and stops sending the first registration message to the second core network function, that is, it does not need to send the first instruction information to the second core network device. At this time, the second terminal leaves the first relay device or does not connect to the first relay device, but directly connects to the access network device or directly sends a message to the first core network function through the access network device.

[0085] In this scenario, the previously registered AMF needs to be deregistered, and only one AMF needs to exist to retain the context of the second terminal.

[0086] Alternatively, a registration message without carrying the first instruction information can also be sent to the second core network function.

[0087] Optionally, in the scenario where the first core network function receives a message sent by the first terminal, step 101 may further include:

[0088] The first core network function receives a second message sent by the first terminal, and the second message carries information about the third core network function that serves the first terminal.

[0089] The first core network function requests the context of the first terminal from the third core network function.

[0090] Specifically, the scenario is, for example, that the first terminal does not follow the first relay device, or sends a message to the network-side device, and the first core network function receives the second message sent by the terminal, the second message carrying information about the third core network function of the serving terminal;

[0091] The first core network function requests the context of the first terminal from the third core network function based on the information from the third core network function. For example, the first core network function sends a request message to the third core network function to request the context of the first terminal, and the third core network function sends a response message to the first core network function, carrying the context of the first terminal.

[0092] The first core network function can send a first registration message to the second core network function based on the context of the first terminal.

[0093] In this scenario, the message sent by the first terminal can be sent through the first relay device or directly through the access network device; this application embodiment does not limit this.

[0094] Optionally, the first core network function and the third core network function are networks of the same standard, such as both being 5G networks, or they could be networks from versions before or after 5G.

[0095] Optionally, the method further includes:

[0096] The first core network function receives the fourth message sent by the third terminal;

[0097] The first core network function removes information related to the first relay device from the context of the third terminal;

[0098] The third terminal is a terminal that does not send messages to the core network function through the first relay device.

[0099] Specifically, if the third terminal does not follow the first relay device, for example, if the registration request sent by the third terminal to the core network function does not carry information related to the first relay device, then the first communication function can delete the information related to the first relay device from the context of the third terminal.

[0100] Optionally, the fourth message carries information about the fifth core network function serving the third terminal; the method further includes:

[0101] The first core network function obtains the context of the third terminal from the fifth core network function.

[0102] In the above embodiments, when the terminal does not follow the first relay device, the first core network function can delete information related to the first relay device from the terminal's context, thereby enabling the network-side device to make relevant decisions based on accurate information and avoid affecting the terminal's communication.

[0103] Optionally, in the scenario where the first terminal follows the first relay device, or the first core network function receives third indication information for the first relay device sent by the access network device, the third indication information carries information about the third core network function serving the first terminal; the method further includes:

[0104] The first core network function sends a sixth message to the third core network function. The sixth message is used to request the context of the terminal, including the context of the first terminal.

[0105] Specifically, the access network device sends a third indication message to the first core network function. The third indication message is used to indicate at least one of the following: relocation of the core network function serving the first relay device, or update of the access point of the first relay device, or update of the location of the first relay device. The third indication message carries information about the third core network function serving the first terminal.

[0106] The first core network function requests the context of the terminal from the third core network function, including the context of the first terminal.

[0107] Optionally, the method further includes:

[0108] The first core network function receives information from the second core network function sent by the fourth core network function;

[0109] The first core network function sends a third message to the fourth core network function. The third message is used to request information related to the first relay device. The information related to the first relay device includes information about the core network function that serves the first relay device.

[0110] The first core network function sends an unsubscribe message to the core network function serving the first relay device. The unsubscribe message is used to unsubscribe from events related to the core network function serving the first relay device.

[0111] Specifically, for example, in a scenario where the first terminal leaves the first relay device, when the first core network function registers with the second core network function, the second core network function can return information from the fourth core network function, which may be the AMF that previously served the first terminal. This fourth core network function retains the context of the first terminal.

[0112] The first core network function requests information related to the first relay device from the fourth core network function, such as information about the core network function serving the first relay device. The first core network function can send an unsubscribe message based on the information of the core network function to unsubscribe from events related to the core network function, such as AMF change events.

[0113] Optionally, the method further includes:

[0114] When the context of the first terminal includes information related to the first relay device, the first core network function sends an unsubscribe message to the core network function serving the first relay device based on the context of the first terminal. The unsubscribe message is used to unsubscribe from events related to the core network function serving the first relay device.

[0115] Specifically, for example, in the scenario where the first terminal leaves the first relay device, the first core network function can obtain the context of the first terminal from the core network function that retains the context of the first terminal. If the context of the first terminal includes information related to the first relay device, that is, if it includes information of the core network function that serves the first relay device, the first core network function can unsubscribe from the core network function that serves the first relay device by sending an unsubscription message to unsubscribe from events related to the core network function, such as the AMF change event.

[0116] Optionally, the method further includes:

[0117] The first core network function receives the deregistration message sent by the second core network function; the deregistration message carries information related to the fourth terminal;

[0118] The first core network function sends an unsubscribe message to the core network function serving the first relay device based on the context of the fourth terminal.

[0119] The context of the fourth terminal includes information related to the first relay device, and the unsubscribe message is used to unsubscribe from events related to the core network functions of the first relay device.

[0120] Specifically, when it is necessary to deregister the first core network function, the second core network function sends a deregistration message to the first core network function. After receiving the deregistration message, the first core network function, based on the context of the fourth terminal (the context of the fourth terminal can be obtained from the information related to the fourth terminal, which includes information related to the first relay device, such as at least the information of the core network function serving the first relay device), sends an unsubscribe message to the core network function serving the first relay device to unsubscribe from events related to that core network function, such as AMF change events.

[0121] In the above embodiments, when the terminal does not follow the first relay device, it can send an unsubscribe message to the core network function serving the first relay device. The unsubscribe message is used to unsubscribe from events related to the core network function serving the first relay device, thereby reducing signaling transmission and reducing resource waste.

[0122] Optionally, the method further includes:

[0123] The first core network device receives the fifth message from the fifth terminal;

[0124] The first core network function sends a second registration message to the second core network function, or sends a third registration message.

[0125] The second registration message carries second indication information, which indicates at least one of the following:

[0126] Cancel the sixth core network function of the service fifth terminal that was not registered using the first instruction information;

[0127] Cancel the sixth core network function of the service fifth terminal registered using the first instruction information;

[0128] The third registration message does not carry the first and second instruction information, and the third registration message is used to indicate at least one of the following:

[0129] Cancel the sixth core network function of the service fifth terminal that was not registered using the first instruction information;

[0130] Cancel the sixth core network function of the service fifth terminal registered using the first instruction information;

[0131] Cancel the sixth core network function of the service fifth terminal registered using the second instruction information;

[0132] The fifth terminal is a terminal that does not send messages to the core network function through the first relay device.

[0133] Specifically, when the first core network function receives the fifth message from the fifth terminal, the fifth terminal does not send the message through the first relay device. For example, if the fifth terminal leaves the first relay device, the first core network function sends a second registration message or a third registration message to the second core network function.

[0134] The second registration message carries second instruction information, which can serve as an instruction to leave the first relay device. In this case, the sixth core network function (e.g., AMF) that was previously registered using the first instruction information and / or the sixth core network function that was not registered using the first instruction information can be deregistered without retaining the context of the fifth terminal. The first core network function serving the fifth terminal can retain the context of the fifth terminal.

[0135] If the third registration message does not carry the first and second instruction information, and the fifth terminal does not follow the first relay device (i.e., it does not access the network through the first relay device), then the second core network function can perform at least one of the following based on the instruction of the third registration message: cancel the sixth core network function of the service fifth terminal that was not registered using the first instruction information; cancel the sixth core network function of the service fifth terminal that was registered using the first instruction information; cancel the sixth core network function of the service fifth terminal that was registered using the second instruction information. That is, the sixth core network function that was previously registered using the first instruction information and / or not using the first instruction information and / or using the second instruction information can be canceled without retaining the context of the fifth terminal. The first core network function serving the fifth terminal only needs to retain the context of the fifth terminal.

[0136] Optionally, the first core network function and the sixth core network function belong to the same network standard, such as both belonging to 5G networks.

[0137] Optionally, the step "the first core network function sends a second registration message to the second core network function, or sends a third registration message" includes:

[0138] When the context of the fifth terminal includes information related to the first relay device, the first core network function sends a second registration message to the second core network function based on the context of the fifth terminal.

[0139] If the context of the fifth terminal does not include information related to the first relay device, the first core network function sends a third registration message to the second core network function based on the context of the fifth terminal.

[0140] Optionally, the fifth message carries information about the sixth core network function serving the fifth terminal; the method further includes:

[0141] The first core network function requests the context of the fifth terminal from the sixth core network function.

[0142] Specifically, if the context of the fifth terminal includes information related to the first relay device, that is, if the fifth terminal previously moved with the first relay device (correspondingly, the core network function serving the fifth terminal is the sixth core network function), and has now left the first relay device, then the first core network function sends a second registration message to the second core network function based on the context of the fifth terminal. The second registration message carries second indication information, that is, indicating the cancellation of the sixth core network function serving the fifth terminal that has not been registered and / or has been registered using the first indication information.

[0143] If the context of the fifth terminal does not include information related to the first relay device, i.e., the fifth terminal did not previously move with the first relay device, the first core network function sends a third registration message to the second core network function based on the context of the fifth terminal. This message indicates the cancellation of the sixth core network function of the service fifth terminal that has not used and / or has registered using the first instruction information, and / or the cancellation of the sixth core network function of the service fifth terminal that has registered using the second instruction information.

[0144] In the above embodiments, when the first core network device receives a fifth message from the terminal, the first core network function can instruct the second core network function to deregister the sixth core network function of the service fifth terminal that is not using and / or registered using the first instruction information; or perform at least one of the following: deregister the sixth core network function of the service fifth terminal that is not using and / or registered using the first instruction information; deregister the sixth core network function of the service fifth terminal that is registered using the second instruction information; that is, the sixth core network function does not need to retain the context of the terminal, thereby reducing resource waste.

[0145] Optionally, in the scenario where the access network device sends a message to the first core network function, the method further includes:

[0146] The first core network function sends a third registration message to the second core network function;

[0147] The third registration message does not carry the first and second indication information, and is used to indicate at least one of the following:

[0148] Stop canceling the third core network functions registered using the first instruction information;

[0149] Cancel the third core network function that was not registered using the first instruction information.

[0150] Optionally, before the first core network function sends the third registration message to the second core network function, it also includes:

[0151] The first core network function receives third instruction information sent by the access network device for the first relay device.

[0152] Specifically, in the scenario where the first core network function receives messages from the access network device, i.e., the first terminal directly accesses the network through the access network device without going through the first relay device, the message from the access network device is, for example, third indication information for the first relay device. This third indication information is used to indicate access point update, core network function relocation, or location update. In this case, the first core network function sends a third registration message to the second core network function, without carrying the first and second indication information. This message is used to indicate the cessation of deregistration of the third core network function registered using the first indication information, and / or the deregistration of the third core network function not registered using the first indication information. That is, the third core network function does not need to retain the context of the first terminal, thereby reducing resource waste.

[0153] In the above embodiments, when the access network device sends a message to the first core network function, the first core network function can instruct the second core network function to stop deregistering the third core network function registered using the first instruction information; this allows the network-side device to easily obtain the context of the first terminal from the first core network function, thereby avoiding affecting the communication of the first terminal; and / or, it can be used to instruct the deregistration of the third core network function that was not registered using the first instruction information, that is, the third core network function does not need to retain the context of the first terminal, thereby reducing resource waste.

[0154] For example, such as Figure 3 As shown, Figure 3 In this context, AMF-UE represents the AMF of the serving terminal, and AMF-Relay represents the AMF of the serving relay device. This embodiment provides a solution for scenarios where the terminal follows a relay device, including:

[0155] Step 0: AMF-UE registers with UDM;

[0156] Step 1a: The relay device sends a registration message to the access network device (such as Next Generation Radio Access Network (NG-RAN)), which includes, for example, the relay device ID;

[0157] Step 2a: The AMF-relay sends a context migration request for the terminal, including the relay device ID, to the old AMF-relay;

[0158] Step 2b: The old AMF-relay sends a response to the AMF-relay, including the context of the relay device, including link information associated with multiple terminals;

[0159] The link information includes at least one of the following: identification information (such as Link ID), terminal-related information, relay equipment-related information, core network function-related information, and association indication.

[0160] Terminal-related information includes various possible information related to the terminal, such as the terminal's identifier and information about the core network functions serving the terminal.

[0161] Information related to relay equipment includes various possible information related to relay equipment, such as the identifier of the relay equipment and information on the core network functions that serve the relay equipment.

[0162] Step 3a: The AMF-relay sends an N2 message, i.e., a registration and acceptance message, to the access network device, which includes information on multiple links;

[0163] Step 3b: The access network device sends a registration acceptance message to the relay device;

[0164] Step 1b: Relay equipment switching;

[0165] Step 4: Modify AMF-UE based on link information;

[0166] Step 5: The access network device sends an AMF relocation request, including link information, to the new AMF-UE1;

[0167] Step 6a: Perform batch migration of terminal context from new AMF-UE1 to AMF-UE;

[0168] Step 6b: The AMF-UE sends a response to the new AMF-UE1, including the terminal context;

[0169] Step 7: The new AMF-UE1 sends an AMF relocation response to the access network equipment, including new link information;

[0170] Step 8: After obtaining the terminal context, the new AMF-UE1 sends a registration message to the UDM, including the first indication information;

[0171] Step 9: UDM stops deregistering AMF-UE;

[0172] Step 10: When the terminal does not move with the relay device (e.g., leaves the relay device), the terminal sends a registration request to the access network device, carrying the terminal ID (e.g., the 5G-Globally Unique Temporary UE Identity (GUTI) obtained during registration in Step 0). This terminal ID is assigned and sent to the terminal by the AMF-UE, therefore the AMF information contained in the terminal ID is the AMF-UE information. The access network device then sends the registration request to AMF-UE2 (which provides services to the terminal).

[0173] In steps 11a and 11b, AMF-UE2 requests terminal context from AMF-UE based on the AMF information in the terminal ID. The obtained terminal context contains information related to the relay device, such as information on the core network functions serving the relay device. For example, information on the core network functions serving the relay device can be obtained through link information.

[0174] Step 12: If there is no relay device information in the registration request or the N2 message carrying the registration request, then AMF-UE2 deletes the information related to the relay device from the terminal context.

[0175] Step 13a: AMF-UE2 registers with UDM (without carrying the first and second indication information).

[0176] Optionally, in step 13b, UDM can return information about AMF-UE1, such as the ID of AMF-UE1.

[0177] Step 14b: UDM can instruct AMF-UE to deregister (AMF-UE will delete the terminal context upon receiving the deregistration instruction). Step 14a: UDM can instruct new AMF-UE1 to deregister (new AMF-UE1 will delete the terminal context).

[0178] Step 15: The new AMF-UE2, based on the relay device-related information in the terminal context, instructs the new AMF-Relay to unsubscribe from events related to that relay device (e.g., unsubscribe from AMF change events).

[0179] Specifically, when the information returned by UDM in step 13 includes information about AMF-UE1, AMF-UE2 obtains the information about the new AMF-relay from AMF-UE1 and cancels its subscription to the new AMF-relay.

[0180] In practical applications, steps 1-8 may occur multiple times. Step 9 only applies to the initial AMF-UE. That is, the UDM only stops deregistering AMFs that were not previously registered using the first indication information. In other words, if a registration message using the first indication information is received, and there was no AMF previously registered using the first indication information, the previous AMF will not be deregistered. If there was an AMF previously registered using the first indication information, the AMF that sent the first registration information will still be deregistered after step 8. This ensures that at most two AMFs retain the terminal's context until a registration message without the first indication information is received again (step 13a). After executing step 14, the operation of deregistering the previously registered AMF is resumed, meaning that only one AMF retains the terminal's context.

[0181] For example, such as Figure 4As shown, this embodiment provides another solution in a scenario where the terminal follows a relay device, including:

[0182] Step 1: The terminal follows relay device 1;

[0183] Step 2: The terminal initiates a service request or registration request through relay device 1; relay device 1 sends an N1 message to the access network device;

[0184] Step 3: The access network device forwards the N1 message to the AMF-UE, for example, via the N2 message, and includes the ID of relay device 1, such as 5G-GUTI, and / or may also include a list of Tracking Area Identities (TAIs) configured for relay device 1.

[0185] During the registration process, access network devices can select a new AMF-UE.

[0186] Step 4: If a new AMF-UE is selected, a terminal context needs to be requested from the old AMF-UE;

[0187] Step 5: The new AMF-UE sends an N2 message using the acquired link information. The N2 message may include the N1 message. In the case of the registration procedure, if the TAI list configured for the relay device has not been changed, the AMF-UE can use the TAI list to send a registration acceptance to the terminal to save mobility registration for terminals following the relay device. The access network device associates the link information with the relay device and stores the link information in the terminal context.

[0188] Step 6: The AMF-UE registers with the UDM, including the first instruction information.

[0189] Step 7: The access network device associates the link information with the relay device ID and the terminal ID, and sends an RRC message to the terminal, which may include an N1 message.

[0190] Step 8: If the terminal continues to follow the relay device, the terminal can suspend mobile registration (for example, the TAI / Tracking Area Code (TAC) broadcast by the relay device will not change, and the access network device will send the TAI to the AMF-UE).

[0191] Step 9: The terminal follows another relay device or access network device.

[0192] Step 10: If mobile registration was previously suspended, the terminal will resume mobile registration (e.g., the TAI / TAC broadcast by the relay device was not configured for the terminal following the relay device, but when the terminal follows another relay device, the TAI / TAC MBSR of that other relay device will be configured for the terminal). If the terminal follows another relay device, steps 2-9 will be performed using different link information (such as LinkID), different relay device IDs, and possibly different AMF-relays. If the terminal directly accesses the access network device, the registration procedure will be performed.

[0193] Optionally, after steps 1-7 are completed, the following occurs: Figure 3 During the process, Figure 3 Step 8 may not include the first instruction information. Figure 3 In step 9, the UDM stops deregistering AMFs registered using the first indication information. In step 13a, if the new AMF-UE2 carries the first indication information based on the relay device-related information (such as Link ID) contained in the terminal context, and if there is relay device-related information in step 10 (carried in a Non-Access Stratum (NAS) message or in an N2 message carrying NAS), then the first indication information is carried. If there is no relay device-related information in step 10, then the second indication information is carried. If the UDM determines that there is another AMF registered using the first indication information, then steps 14a and 14b are executed, i.e., deregistering the AMFs previously registered using the first indication information and deregistering the AMFs not previously registered using the first indication information. If the UDM determines that there is an AMF registered using the second indication information, then after executing steps 14a and 14b, the second indication information of the AMF is deleted, i.e., the operation of deregistering the previously registered AMF is restored, meaning that only one AMF retains the terminal context.

[0194] Figure 5 This is a second schematic flowchart of the communication method provided in the embodiments of this application. Figure 5 As shown, the method provided in this embodiment includes:

[0195] Step 201: The second core network function receives the first registration message sent by the first core network function, whereby the first core network function is the core network function serving the first terminal; the first registration message carries first indication information.

[0196] Step 202: The second core network function performs at least one of the following: stops deregistering the third core network function of the service first terminal that has not registered using the first instruction information; deregisters the third core network function of the service first terminal that has registered using the first instruction information; deregisters the third core network function of the service first terminal that has not registered using the first instruction information; does not deregister the first core network function.

[0197] It should be noted that in step 202, the second core network function may be to perform at least one of the functions described in step 202 according to the first instruction information.

[0198] Optionally, the method further includes:

[0199] The second core network function sends information about the fourth core network function to the first core network function.

[0200] Optionally, after the second core network function receives the first registration message sent by the first core network function, the method further includes:

[0201] The second core network function receives the first registration message and sends a deregistration message to the first core network function.

[0202] Optionally, the method further includes:

[0203] The second core network function receives a second registration message or a third registration message;

[0204] The second registration message carries second indication information, and the second core network function performs at least one of the following:

[0205] Cancel the sixth core network function that was not registered using the first instruction information;

[0206] Cancel the sixth core network function registered using the first instruction information;

[0207] If the third registration message does not carry the first and second indication information, the second core network function performs at least one of the following:

[0208] Cancel the sixth core network function that was not registered using the first instruction information;

[0209] Cancel the sixth core network function registered using the first instruction information;

[0210] Cancel the sixth core network function registered using the second instruction information.

[0211] Optionally, the method further includes:

[0212] The second core network function receives the third registration message;

[0213] Wherein, the third registration message does not carry the first indication information and the second indication information, and the second core network function performs at least one of the following:

[0214] Stop canceling the third core network functions registered using the first instruction information;

[0215] Cancel the third core network function that was not registered using the first instruction information.

[0216] Optionally, the first core network function and the third core network function belong to the same network standard, and / or the first core network function and the sixth core network function belong to the same network standard.

[0217] The method in this embodiment is similar to the method embodiment for the first core network functional side in terms of its specific implementation process and technical effects. For details, please refer to the detailed description in the method embodiment for the first core network functional side, which will not be repeated here.

[0218] The communication method provided in this application can be executed by a communication device. This application uses the example of a communication device executing the communication method to illustrate the communication device provided in this application.

[0219] Figure 6 This is one of the structural schematic diagrams of the communication device provided in this application. For example... Figure 6 As shown, the communication device provided in this embodiment includes:

[0220] The sending module 210 is used to send a first registration message to a second core network function when the core network function serving the first terminal is the first core network function. The first registration message carries first indication information. The first indication information is used to indicate that the first terminal is a terminal that accesses the network through the first relay device, or to indicate that the second core network function performs a deregistration-related operation. The first terminal is a terminal that accesses the network through the first relay device.

[0221] Optionally, when the first terminal is a terminal that sends messages to the core network function through the first relay device, the deregistration-related operation includes at least one of the following:

[0222] Cancel the third core network function of the first terminal registered using the first instruction information;

[0223] Cancel the third core network function of the first terminal that was not registered using the first instruction information;

[0224] Stop deregistering the first core network function.

[0225] Optionally, when the first terminal is a terminal that moves with the first relay device, or when the first core network function receives third indication information for the first relay device sent by the access network device, the deregistration-related operation includes at least one of the following:

[0226] Stop deregistering the third core network function of the first terminal that was not registered using the first instruction information;

[0227] Cancel the third core network function of the first terminal registered using the first instruction information;

[0228] The third indication information is used to indicate access point updates, core network function relocation, or location updates.

[0229] Optionally, the device further includes:

[0230] The receiving module is used to receive the first message sent by the second terminal, and the processing module is used to stop sending the first registration message to the second core network function.

[0231] The second terminal is a terminal that does not send messages to the core network function through the first relay device.

[0232] Optionally, before the first core network function sends the first registration message to the second core network function, the receiving module is further configured to:

[0233] Receive a second message sent by the first terminal, the second message carrying information about the third core network function serving the first terminal;

[0234] The first core network function requests the context of the first terminal from the third core network function.

[0235] Optionally, the receiving module is also used for:

[0236] Receive the fourth message sent by the third terminal;

[0237] The processing module is also configured to remove information related to the first relay device from the context of the third terminal;

[0238] The third terminal is a terminal that does not send messages to the core network function through the first relay device.

[0239] Optionally, the fourth message carries information about the fifth core network function serving the third terminal; the receiving module is further configured to:

[0240] The context of the third terminal is obtained from the fifth core network function.

[0241] Optionally, the third indication information carries information about the third core network function of the serving terminal; the sending module 210 is further configured to:

[0242] A sixth message is sent to the third core network function, the sixth message being used to request the context of the terminal, including the context of the first terminal.

[0243] Optionally, the receiving module is also used for:

[0244] Receive information from the fourth core network function sent by the second core network function;

[0245] The sending module 210 is further configured to:

[0246] Send a third message to the fourth core network function. The third message is used to request information related to the first relay device. The information related to the first relay device includes information about the core network function that serves the first relay device.

[0247] Send an unsubscribe message to the core network function serving the first relay device. The unsubscribe message is used to unsubscribe from events related to the core network function serving the first relay device.

[0248] Optionally, the sending module 210 is further configured to:

[0249] If the context of the first terminal includes information related to the first relay device, an unsubscribe message is sent to the core network function serving the first relay device based on the context of the first terminal. The unsubscribe message is used to unsubscribe from events related to the core network function serving the first relay device.

[0250] Optionally, the receiving module is also used for:

[0251] Receive a deregistration message sent by the second core network function, the deregistration message carrying information related to the fourth terminal;

[0252] The sending module 210 is further configured to:

[0253] Based on the context of the fourth terminal, an unsubscribe message is sent to the core network function serving the first relay device;

[0254] The context of the fourth terminal includes information related to the first relay device, and the unsubscribe message is used to unsubscribe from events related to the core network functions of the first relay device.

[0255] Optionally, the receiving module is also used for:

[0256] Receive the fifth message from the fifth terminal;

[0257] The sending module 210 is further configured to:

[0258] Send a second registration message or a third registration message to the second core network function;

[0259] The second registration message carries second indication information, which indicates at least one of the following:

[0260] Cancel the sixth core network function of the fifth terminal that was not registered using the first instruction information;

[0261] Cancel the sixth core network function of the fifth terminal registered using the first instruction information;

[0262] The third registration message does not carry the first and second indication information, and the third registration message is used to indicate at least one of the following:

[0263] Cancel the sixth core network function of the fifth terminal that was not registered using the first instruction information;

[0264] Cancel the sixth core network function of the fifth terminal registered using the first instruction information;

[0265] Cancel the sixth core network function of the fifth terminal registered using the second instruction information;

[0266] The fifth terminal is a terminal that does not send messages to the core network function through the first relay device.

[0267] Optionally, the sending module 210 is specifically used for:

[0268] When the context of the fifth terminal includes information related to the first relay device, the first core network function sends the second registration message to the second core network function based on the context of the fifth terminal.

[0269] If the context of the fifth terminal does not include information related to the first relay device, the first core network function sends the third registration message to the second core network function based on the context of the fifth terminal.

[0270] Optionally, the fifth message carries information about the sixth core network function serving the fifth terminal; the sending module 210 is further configured to:

[0271] The sixth core network function requests the context of the fifth terminal.

[0272] Optionally, the sending module 210 is further configured to:

[0273] Send a third registration message to the second core network function;

[0274] The third registration message does not carry the first indication information and the second indication information, and the third registration message is used to indicate at least one of the following:

[0275] Stop canceling the third core network functions registered using the first instruction information;

[0276] Cancel the third core network function that was not registered using the first instruction information.

[0277] Optionally, the receiving module is also used for:

[0278] Receive the third indication information sent by the access network device for the first relay device.

[0279] Optionally, the first core network function and the third core network function belong to the same network standard, and / or the first core network function and the sixth core network function belong to the same network standard.

[0280] The apparatus of this embodiment can be used to execute the method of any of the embodiments of the first core network functional side method described above. Its specific implementation process and technical effects are similar to those of the first core network functional side method embodiment. For details, please refer to the detailed description in the first core network functional side method embodiment, which will not be repeated here.

[0281] Figure 7 This is the second schematic diagram of the communication device provided in this application. Figure 7 As shown, the communication device provided in this embodiment includes:

[0282] The receiving module 310 is used to receive a first registration message sent by a first core network function, wherein the first core network function is a core network function that serves the first terminal; the first registration message carries first indication information.

[0283] The second core network function performs at least one of the following:

[0284] Stop deregistering the third core network function of the first terminal that was not registered using the first instruction information;

[0285] Cancel the third core network function of the first terminal registered using the first instruction information;

[0286] Cancel the third core network function of the first terminal that was not registered using the first instruction information;

[0287] The first core network function will not be cancelled.

[0288] Optionally, the device further includes:

[0289] The sending module is used to send information about the fourth core network function to the first core network function.

[0290] Optionally, after the second core network function receives the first registration message sent by the first core network function, the receiving module 310 is further configured to:

[0291] The receiving and sending module is also used to send a deregistration message to the first core network function.

[0292] Optionally, the receiving module 310 is further configured to:

[0293] Receive a second or third registration message;

[0294] The second registration message carries second indication information, and the second core network function performs at least one of the following:

[0295] Cancel the sixth core network function that was not registered using the first instruction information;

[0296] Cancel the sixth core network function registered using the first instruction information;

[0297] If the third registration message does not carry the first and second indication information, the second core network function performs at least one of the following:

[0298] Cancel the sixth core network function that was not registered using the first instruction information;

[0299] Cancel the sixth core network function registered using the first instruction information;

[0300] Cancel the sixth core network function registered using the second instruction information.

[0301] Optionally, the receiving module 310 is further configured to:

[0302] Receive third-party registration messages;

[0303] Wherein, the third registration message does not carry the first indication information and the second indication information, and the second core network function performs at least one of the following:

[0304] Stop canceling the third core network functions registered using the first instruction information;

[0305] Cancel the third core network function that was not registered using the first instruction information.

[0306] Optionally, the first core network function and the third core network function belong to the same network standard, and / or the first core network function and the sixth core network function belong to the same network standard.

[0307] The apparatus of this embodiment can be used to execute the method of any of the embodiments of the aforementioned second core network functional side method embodiments. Its specific implementation process and technical effects are similar to those of the second core network functional side method embodiments. For details, please refer to the detailed description in the second core network functional side method embodiments, which will not be repeated here.

[0308] The communication device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the type.

[0309] The communication device provided in this application embodiment can achieve... Figures 2 to 5 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0310] Optionally, such as Figure 8 As shown in the illustration, this application also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores programs or instructions that can run on the processor 801. For example, when the communication device 800 functions as a first core network, the program or instructions executed by the processor 801 implement the various steps of the above-described communication method embodiments and achieve the same technical effect. When the communication device 800 functions as a second core network, the program or instructions executed by the processor 801 implement the various steps of the above-described communication method embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0311] This application embodiment also provides a first core network function, including a processor and a communication interface. The communication interface is used to send a first registration message to a second core network function when the core network function serving the first terminal is the first core network function. The first registration message carries first indication information, which is used to indicate that the first terminal is a terminal accessing the network through a first relay device, or to instruct the second core network function to perform a deregistration-related operation, wherein the first terminal is a terminal accessing the network through the first relay device. This first core network function embodiment corresponds to the above-described first core network function method embodiment. All implementation processes and methods of the above method embodiments can be applied to this first core network function embodiment and can achieve the same technical effects.

[0312] This application embodiment also provides a second core network function, including a processor and a communication interface, wherein the communication interface is used to receive a first registration message sent by a first core network function, the first core network function being a core network function serving a first terminal; the first registration message carries first indication information; the second core network function performs at least one of the following: stopping the cancellation of a third core network function serving the first terminal that has not registered using the first indication information; canceling a third core network function serving the first terminal that has registered using the first indication information; canceling a third core network function serving the first terminal that has not registered using the first indication information; and not canceling the first core network function. This second core network function embodiment corresponds to the above-described second core network function method embodiment, and all implementation processes and methods of the above method embodiments can be applied to this second core network function embodiment and can achieve the same technical effect.

[0313] Specifically, embodiments of this application also provide a network-side device. For example... Figure 9 As shown, the network-side device 900 includes a processor 901, a network interface 902, and a memory 903. The network interface 902 is, for example, a common public radio interface (CPRI).

[0314] Specifically, the network-side device 900 of this embodiment further includes: instructions or programs stored in a memory 903 and executable on a processor 901, wherein the processor 901 calls the instructions or programs in the memory 903 to execute. Figure 6 or Figure 7 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0315] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described communication method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0316] The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0317] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described communication method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0318] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0319] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described communication method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0320] This application also provides a communication system, including a first core network function and a second core network function. The first core network function can be used to execute the steps of the communication method described above, and the second core network function can be used to execute the steps of the communication method described above. Further, the communication system may also include a terminal and a relay device. The terminal can execute the steps executed by the terminal in the above method embodiments, and the relay device can execute the steps executed by the relay device in the above method embodiments.

[0321] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0322] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0323] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A communication method characterized by comprising: include: When the core network function serving the first terminal is the first core network function, the first core network function sends a first registration message to the second core network function. The first registration message carries first indication information. The first indication information is used to indicate that the first terminal is a terminal that accesses the network through the first relay device, or to instruct the second core network function to perform deregistration-related operations. Wherein, the first terminal is a terminal that accesses the network through the first relay device; When the first terminal is a terminal that sends messages to the core network function through the first relay device, the deregistration-related operations include at least one of the following: Cancel the third core network function of the first terminal registered using the first instruction information; Cancel the third core network function of the first terminal that was not registered using the first instruction information; Stop deregistering the first core network function; When the first terminal is a terminal that moves with the first relay device, or when the first core network function receives third indication information for the first relay device sent by the access network device, the deregistration-related operation includes at least one of the following: Stop deregistering the third core network function of the first terminal that was not registered using the first instruction information; Cancel the third core network function of the first terminal registered using the first instruction information; The third indication information is used to indicate access point updates, core network function relocation, or location updates.

2. The method of claim 1, wherein, The method further includes: The first core network function receives the first message sent by the second terminal and stops sending the first registration message to the second core network function. The second terminal is a terminal that does not send messages to the core network function through the first relay device.

3. The method of claim 1, wherein, Before the first core network function sends the first registration message to the second core network function, the method further includes: The first core network function receives a second message sent by the first terminal, and the second message carries information about the third core network function that serves the first terminal; The first core network function requests the context of the first terminal from the third core network function.

4. The method of claim 1, wherein, The method further includes: The first core network function receives a fourth message sent by the third terminal; The first core network function removes information related to the first relay device from the context of the third terminal; The third terminal is a terminal that does not send messages to the core network function through the first relay device.

5. The method of claim 4, wherein, The fourth message carries information about the fifth core network function serving the third terminal; the method further includes: The first core network function obtains the context of the third terminal from the fifth core network function.

6. The method of claim 1, wherein, The third indication information carries information about the third core network function of the serving terminal; the method further includes: The first core network function sends a sixth message to the third core network function, the sixth message being used to request the context of the terminal, including the context of the first terminal.

7. The method of claim 1, wherein, The method further includes: The first core network function receives information from the fourth core network function sent by the second core network function; The first core network function sends a third message to the fourth core network function. The third message is used to request information related to the first relay device. The information related to the first relay device includes information about the core network function that serves the first relay device. The first core network function sends an unsubscribe message to the core network function serving the first relay device. The unsubscribe message is used to unsubscribe from events related to the core network function serving the first relay device.

8. The method of claim 3, wherein, The method further includes: When the context of the first terminal includes information related to the first relay device, the first core network function sends an unsubscribe message to the core network function serving the first relay device based on the context of the first terminal. The unsubscribe message is used to unsubscribe from events related to the core network function serving the first relay device.

9. The method of claim 1, wherein, The method further includes: The first core network function receives a deregistration message sent by the second core network function, and the deregistration message carries information related to the fourth terminal; Based on the context of the fourth terminal, the first core network function sends an unsubscribe message to the core network function serving the first relay device; The context of the fourth terminal includes information related to the first relay device, and the unsubscribe message is used to unsubscribe from events related to the core network functions of the first relay device.

10. The method according to claim 1, characterized in that, The method further includes: The first core network function receives the fifth message from the fifth terminal; The first core network function sends a second registration message to the second core network function, or sends a third registration message; The second registration message carries second indication information, which indicates at least one of the following: Cancel the sixth core network function of the fifth terminal that was not registered using the first instruction information; Cancel the sixth core network function of the fifth terminal registered using the first instruction information; The third registration message does not carry the first and second indication information, and the third registration message is used to indicate at least one of the following: Cancel the sixth core network function of the fifth terminal that was not registered using the first instruction information; Cancel the sixth core network function of the fifth terminal registered using the first instruction information; Cancel the sixth core network function of the fifth terminal registered using the second instruction information; The fifth terminal is a terminal that does not send messages to the core network function through the first relay device.

11. The method according to claim 10, characterized in that, The first core network function sends a second registration message to the second core network function, or sends a third registration message, including: When the context of the fifth terminal includes information related to the first relay device, the first core network function sends the second registration message to the second core network function based on the context of the fifth terminal. If the context of the fifth terminal does not include information related to the first relay device, the first core network function sends the third registration message to the second core network function based on the context of the fifth terminal.

12. The method according to claim 9 or 10, characterized in that, The fifth message carries information about the sixth core network function serving the fifth terminal; the method further includes: The first core network function requests the context of the fifth terminal from the sixth core network function.

13. The method according to claim 1, characterized in that, The method further includes: The first core network function sends a third registration message to the second core network function; The third registration message does not carry the first indication information and the second indication information, and the third registration message is used to indicate at least one of the following: Stop canceling the third core network functions registered using the first instruction information; Cancel the third core network function that was not registered using the first instruction information.

14. The method according to claim 13, characterized in that, The method further includes: The first core network function receives the third indication information sent by the access network device for the first relay device.

15. The method according to claim 10, characterized in that, The first core network function and the third core network function belong to the same network standard, and / or the first core network function and the sixth core network function belong to the same network standard.

16. A communication method, characterized in that, include: The second core network function receives the first registration message sent by the first core network function, where the first core network function is the core network function that serves the first terminal. The first registration message carries first instruction information; If the first terminal is a terminal that sends messages to the core network function through the first relay device, the second core network function performs at least one of the following: Cancel the third core network function of the first terminal registered using the first instruction information; Cancel the third core network function of the first terminal that was not registered using the first instruction information; Do not cancel the first core network function; If the first terminal is a terminal that moves with the first relay device, or if the first core network function receives third indication information for the first relay device from the access network device, the second core network function performs at least one of the following: Stop deregistering the third core network function of the first terminal that was not registered using the first instruction information; Cancel the third core network function of the first terminal registered using the first instruction information; The third indication information is used to indicate access point updates, core network function relocation, or location updates.

17. The method according to claim 16, characterized in that, The method further includes: The second core network function sends information about the fourth core network function to the first core network function.

18. The method according to claim 16 or 17, characterized in that, After the second core network function receives the first registration message sent by the first core network function, the method further includes: The second core network function receives the first registration message and sends a deregistration message to the first core network function.

19. The method according to claim 16 or 17, characterized in that, The method further includes: The second core network function receives a second registration message or a third registration message; The second registration message carries second indication information, and the second core network function performs at least one of the following: Cancel the sixth core network function that was not registered using the first instruction information; Cancel the sixth core network function registered using the first instruction information; If the third registration message does not carry the first and second indication information, the second core network function performs at least one of the following: Cancel the sixth core network function that was not registered using the first instruction information; Cancel the sixth core network function registered using the first instruction information; Cancel the sixth core network function registered using the second instruction information.

20. The method according to claim 16 or 17, characterized in that, The method further includes: The second core network function receives the third registration message; Wherein, the third registration message does not carry the first indication information and the second indication information, and the second core network function performs at least one of the following: Stop canceling the third core network functions registered using the first instruction information; Cancel the third core network function that was not registered using the first instruction information.

21. The method according to claim 19, characterized in that, The first core network function and the third core network function belong to the same network standard, and / or the first core network function and the sixth core network function belong to the same network standard.

22. A communication device, characterized in that, include: The sending module is used to send a first registration message to a second core network function when the core network function serving the first terminal is the first core network function. The first registration message carries first indication information. The first indication information is used to indicate that the first terminal is a terminal that accesses the network through the first relay device, or to indicate that the second core network function performs a deregistration-related operation. The first terminal is a terminal that accesses the network through the first relay device. When the first terminal is a terminal that sends messages to the core network function through the first relay device, the deregistration-related operations include at least one of the following: Cancel the third core network function of the first terminal registered using the first instruction information; Cancel the third core network function of the first terminal that was not registered using the first instruction information; Stop deregistering the first core network function; When the first terminal is a terminal that moves with the first relay device, or when the first core network function receives third indication information for the first relay device sent by the access network device, the deregistration-related operation includes at least one of the following: Stop deregistering the third core network function of the first terminal that was not registered using the first instruction information; Cancel the third core network function of the first terminal registered using the first instruction information; The third indication information is used to indicate access point updates, core network function relocation, or location updates.

23. A communication device, characterized in that, include: The receiving module is used to receive the first registration message sent by the first core network function, wherein the first core network function is the core network function that serves the first terminal; The first registration message carries first instruction information; If the first terminal is a terminal that sends messages to the core network function through the first relay device, the second core network function performs at least one of the following: Cancel the third core network function of the first terminal registered using the first instruction information; Cancel the third core network function of the first terminal that was not registered using the first instruction information; Do not cancel the first core network function; If the first terminal is a terminal that moves with the first relay device, or if the first core network function receives third indication information for the first relay device from the access network device, the second core network function performs at least one of the following: Stop deregistering the third core network function of the first terminal that was not registered using the first instruction information; Cancel the third core network function of the first terminal registered using the first instruction information; The third indication information is used to indicate access point updates, core network function relocation, or location updates.

24. A first core network function, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the communication method as described in any one of claims 1 to 15.

25. A second core network function, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the communication method as described in any one of claims 16 to 22.

26. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the communication method as described in any one of claims 1 to 15, or implement the steps of the communication method as described in any one of claims 16 to 22.

Images