A communication method, apparatus, system, storage medium and computer program product

Abstract

A communication method, device, system, storage medium and computer program product are used to reduce signaling overhead. In the present application, a first network device acquires first tunnel information of the first network device. The first tunnel information is determined according to a correspondence relationship between a first region and the first tunnel information. The first region belongs to a signal coverage region of the first network device. The first network device receives a first message from a user plane entity according to the first tunnel information. The first message includes the first tunnel information. The first network device sends information in the first message to a first terminal device located in the first region. Since the tunnel information of the network device is associated with the region, when the network device providing service to the first terminal device changes, the tunnel information (such as the tunnel information of the network device) of the user plane of the terminal device can not be updated, thereby reducing the signaling overhead.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a communication method, apparatus, system, storage medium, and computer program product. Background Technology

[0002] Currently, the 5th generation (5G) New Radio (NR) technology is evolving from Release 18 to Release 19. Simultaneously, NR technology has moved from the standardization phase to the commercial deployment phase. The NR standard protocol was initially designed for wireless communication in terrestrial cellular network scenarios, providing users with ultra-low latency, ultra-reliability, ultra-high speed, and massive connectivity wireless communication services. Compared to terrestrial networks (TN), non-terrestrial networks (NTN) communication features large coverage areas and flexible networking, achieving seamless global network coverage. NTN communication utilizes equipment such as drones, high-altitude platforms, and satellites to build networks, providing data transmission, voice communication, and other services to user equipment (UE).

[0003] In TN or NTN networks, base stations can establish user plane tunnel connections with user plane entities. Information about terminal devices, such as messages sent to and / or messages sent by the terminal devices, is transmitted between the base station and the user plane entity through this tunnel. In some scenarios, the serving base station of the terminal device updates frequently. For example, if the base station is a satellite or deployed on a satellite, and the satellite's movement speed is as high as 7.5 kilometers per second (km / s), the satellite movement will cause the terminal device to frequently switch serving satellites. For example, a satellite may experience tens of thousands of switches approximately every 3 minutes, or a single satellite station may experience tens of thousands of switches per minute. This switching frequency may be 10 times that of a high-speed rail scenario and 1000 times that of a typical terrestrial scenario. The signaling overhead for satellite access networks is 10 to 1000 times that of terrestrial access networks. Frequent updates to the serving base station also require frequent updates to the information in the user plane tunnel connection, resulting in significant signaling overhead. Summary of the Invention

[0004] This application provides a communication method, apparatus, system, storage medium, and computer program product for associating tunnel information of a network device with an area, thereby reducing the update frequency of the tunnel information of the network device and thus reducing signaling overhead.

[0005] To facilitate a clearer understanding of the beneficial effects of the embodiments of this application, an example is provided below. This example illustrates one possible scenario to which this application can be applied, and the solutions provided by this application can also be applied to other scenarios.

[0006] For example, satellites #1 and #2 pass over the first area sequentially, providing communication services to terminal device #1 in the first area. Satellites #1 and #2 can be access network equipment (e.g., base stations) or have the functionality of access network equipment (e.g., base stations). The base station-side tunnel information in the user plane tunnel information associated with the first area is tunnel information #1. When satellite #1 passes over the first area, it can use tunnel information #1 as its own tunnel information to provide a user plane tunnel connection for terminal device #1. When satellite #2 passes over the first area, terminal device #1 switches from satellite #1 to satellite #2, and satellite #2 still uses tunnel information #1 as its own tunnel information to provide a user plane tunnel connection for terminal device #1. It can be seen that although the satellite providing services to terminal device #1 in the first area is updated from satellite #1 to satellite #2, the tunnel information used by both satellite #2 and satellite #1 is tunnel information #1 and has not been updated. Therefore, when the service satellites in a region change, there is no need to update the user plane tunnel information (e.g., tunnel information on the base station side) of the terminal devices in that region via signaling, thereby reducing signaling overhead.

[0007] In a first aspect, embodiments of this application provide a communication method, which can be executed by a first network device. The first network device can be a network device or a chip (or chip system, circuit, module, or unit) within the network device. The network device may include, for example, an access network device. The solution provided in this application can be applied to an NTN communication system. For example, the network device is an NTN device. Another example is that some functions of the network device are deployed on the NTN device, and some functions are deployed on ground equipment. Another example is that the network device is a ground-based device, and the terminal device is an NTN device. For example, the NTN device can include / be replaced by a satellite, drone, high-altitude platform, aircraft, or other non-ground-based device. For example, when the NTN device is a satellite, the satellite can operate in regenerative mode. Another example is that the NTN device can include integrated access and backhaul (IAB), network-controlled repeaters (NCR), or wireless access backhaul (WAB), etc.

[0008] A first network device acquires first tunnel information. The first tunnel information is determined based on the correspondence between a first area and the first tunnel information, where the first area belongs to the signal coverage area of ​​the first network device. Based on the first tunnel information, the first network device receives a first message from a user plane entity, the first message including the first tunnel information. The first network device then sends the information in the first message to a first terminal device located in the first area.

[0009] Because the tunnel information of the network device is associated with the region, when the region where the first terminal device is located remains unchanged, but the network device providing services to the first terminal device changes, the tunnel information of the user plane of the terminal device (e.g., the tunnel information of the network device) does not need to be updated, thereby reducing the update frequency of the tunnel information of the network device and thus reducing signaling overhead.

[0010] In one possible implementation, a region may include one terminal device or multiple terminal devices. For example, the first region may also include a second terminal device. The first network device receives a second message from a user plane entity, which includes the first tunnel information, based on the first tunnel information. The first network device then sends the information from the second message to the second terminal device. It can be seen that multiple terminal devices in a region can share the same tunnel information. In this implementation, the tunnel information of the network device is at the region level. This reduces the amount of tunnel information on the first network device side, as well as the number of correspondences between tunnel information and regions, thereby reducing the complexity of the solution and the storage space occupied by the correspondences between tunnel information and regions.

[0011] In one possible implementation, the first message further includes a first identifier of the first terminal device, which indicates the first terminal device. The first network device sends the information in the first message to the first terminal device located in the first area based on the first identifier. Thus, when the first tunnel information is at the area-level granularity, the first network device can identify which terminal device the received message belongs to based on the first identifier of the first terminal device. This scheme can prevent the first network device from sending information to the wrong terminal device.

[0012] In one possible implementation, the first network device may cease providing service to the first area, for example, it may be providing service to other areas. In this case, other network devices (such as the second network device) can provide service to the first area. In another possible implementation, the first network device sends a first identifier of the first terminal device to the second network device. The signal coverage area of ​​the second network device includes the first area, and the first identifier is used to indicate the first terminal device. For the first terminal device, the first network device can be the source network device, and the second network device can be the target network device. The first terminal device can switch from the first network device to the second network device. The second network device can be a network device that subsequently provides communication services to the first area. For example, the first network device informs the second network device of the first identifier, and the second network device continues to use the corresponding tunnel information of the network device for the first terminal device based on the first identifier. This scheme can implement network device tunnel information at the terminal level, providing finer-grained control.

[0013] In one possible implementation, the first tunnel information is further determined based on the first terminal device, and the tunnel information of the first network devices of at least two terminal devices in the first area is different. Thus, the first network device can identify whether a received packet is a packet it needs to receive, and also identify which terminal device the received packet belongs to, based on the first tunnel information. In this scheme, the first tunnel information can indicate multiple contents, thereby reducing the number of identifiers carried in the packet and thus reducing signaling resource overhead.

[0014] In one possible implementation, the first tunnel information is further determined based on the first terminal device and its first session. For example, the tunnel information of the first network device may differ for different sessions of the first terminal device in the first area (e.g., at least two sessions, any two sessions, or every two sessions). Thus, the first network device can identify whether a received packet is one it needs to receive, which terminal device the received packet belongs to, and which session of which terminal device the received packet belongs to, based on the first tunnel information. In this scheme, the first tunnel information can indicate multiple contents, thereby reducing the number of identifiers carried in the packet and thus reducing signaling resource overhead.

[0015] In one possible implementation, a first network device sends an identifier of a first session to a second network device, the signal coverage area of ​​the second network device including the first area. The second network device may be a network device that subsequently provides communication services to the first area. The first network device informs the second network device of the first identifier, and the second network device can continue to use the first tunnel information as the tunnel information of the network device corresponding to the first session of the first terminal device. This scheme eliminates the need to update the correspondence between sessions and the tunnel information of network devices, thereby reducing signaling overhead.

[0016] In one possible implementation, the first network device determines that its signal coverage area includes a first region. For example, the first network device determines the first tunnel information based on the correspondence between the first region and first tunnel information. In this scheme, the first network device can configure the correspondence between the first region and the first tunnel information, and then look up the correspondence itself to obtain the first tunnel information. This scheme can reduce the amount of signaling required by the first network device to obtain the first tunnel information, thereby saving resource overhead.

[0017] In one possible implementation, a first network device sends first tunnel information. For example, the first network device may send the first tunnel information to a mobility management entity, a session management entity, or a user plane entity, thereby establishing an uplink tunnel from the first network device of the terminal device to the user plane entity. Alternatively, the first network device may send the first tunnel information to a second network device, where the first tunnel information belongs to the second network device's tunnel information. The second network device may be a network device that subsequently provides communication services to the first area. After obtaining the first tunnel information, the second network device can use it as its own tunnel information. In this scheme, although the tunnel information of the network device providing services to the first area changes, the tunnel information of the network device corresponding to that area does not need to be updated, thus saving signaling overhead.

[0018] In one possible implementation, the first network device sends a third message to the user plane entity. The third message includes tunnel information of the user plane entity and first tunnel information. The first network device informs the user plane entity of its tunnel information via the third message to establish a downlink tunnel. In this scheme, the third message is transmitted through an already established uplink tunnel. This scheme can combine the downlink tunnel establishment process and the uplink message tunnel usage process (or uplink message transmission process) into a single process, thereby saving signaling overhead.

[0019] In one possible implementation, the first network device receives the first tunnel information. This reduces the complexity of the scheme for the first network device to obtain the first tunnel information.

[0020] In one possible implementation, the first network device sends location information of the first terminal device, which is used to determine the first tunnel information. For example, the first network device sends the location information of the first terminal device to a mobility management entity, a session management entity, or a user plane entity, so that these network elements can determine the first tunnel information based on the location information. This approach can reduce the complexity of other network elements determining the first tunnel information.

[0021] In one possible implementation, the first network device sends a first indication message, which indicates that the first network device has not acquired the tunnel information of the first network device. Thus, other network elements can determine whether the first network device has acquired the tunnel information based on whether they receive the first indication message. If the first network device has already acquired the tunnel information, it will not send the first indication message again, thereby saving signaling overhead.

[0022] In one possible implementation, the first network device sends a second indication message, which indicates that the first network device has acquired the tunnel information of the first network device. In this way, other network elements can determine whether the first network device has acquired the tunnel information based on whether they receive the second indication message. If the first network device has already acquired the tunnel information, it will not send the second indication message again, thereby saving signaling overhead.

[0023] In one possible implementation, if the first network device's signal coverage area does not include the first area, it stops using the first tunnel information as its tunnel information. In this way, the first tunnel information can be used by the next network device serving the first area. This approach associates tunnel information with the area, thereby reducing the frequency of tunnel information updates by the network devices and saving signaling overhead.

[0024] In one possible implementation, the first network device receives a fifth message from a user plane entity, the fifth message including the identifier of a third terminal device. If the third terminal device is not a terminal device for which the first network device provides communication services, the first network device sends the fifth message to the third network device. In scenarios where multiple network devices provide services for a region, since the tunnel information of multiple network devices is identical, one network device may receive messages from terminal devices managed by other network devices. The above scheme provides a possible solution to this situation, allowing a network device to forward messages that do not belong to it to other network devices, thereby reducing message loss.

[0025] In one possible implementation, the first network device receives tunnel information of a user plane entity corresponding to a first region. Based on the tunnel information of the user plane entity corresponding to the first region and a first identifier of the first terminal device, the first network device sends a fourth message to the user plane entity. The fourth message includes the tunnel information of the user plane entity and the first identifier of the first terminal device. In this way, the UPF can obtain the first identifier and then send a message based on the UPF's tunnel information and the first identifier, so that the first network device can identify which terminal device the information in the received message belongs to.

[0026] In one possible implementation, a first network device obtains a second identifier of a first terminal device, which is determined based on the correspondence between a first region and a second identifier, with the first terminal device located in the first region. The first network device transmits information about the first terminal device based on the second identifier. Since the second identifier of the first terminal device is associated with the first region, it does not need to be updated when the first terminal device is located in the first region. Even if the network device providing communication services to the first terminal device changes, the second identifier of the first terminal device does not need to be updated, thus avoiding the signaling overhead required to update the identifier of the control plane of the first terminal device, thereby saving signaling overhead.

[0027] In one possible implementation, the first network device determines that its signal coverage area includes a first region, and identifies at least one terminal device corresponding to the first region. The first network device then selects one of the terminal device identifiers as a second identifier. The first region may correspond to one or more terminal device identifiers. The first network device can select the identifier of the first terminal device on the network device side of the control plane connection from these identifiers. This approach can reduce the signaling overhead for obtaining the second identifier, thereby saving resource overhead.

[0028] In one possible implementation, the first network device sends information indicating a second identifier. For example, the first network device sends the information indicating the second identifier to a mobility management entity. In this way, the mobility management entity can use the second identifier to transmit control plane information of the first terminal device with the first network device.

[0029] In one possible implementation, the first network device receives information indicating the second identifier. This approach can reduce the complexity of the first network device acquiring the second identifier.

[0030] Secondly, embodiments of this application provide a communication method, which can be executed by a mobility management entity or a session management entity. The mobility management entity can be a device implementing mobility management entity functions or a chip (or chip system, circuit, module, or unit) within the device. The session management entity can be a device implementing session management entity functions or a chip (or chip system, circuit, module, or unit) within the device. For ease of description, the following description uses a first device as the execution subject; the first device in the following description can include / be replaced by: a mobility management entity or a session management entity.

[0031] The first device acquires first information. The first information indicates first tunnel information. The first tunnel information is the tunnel information of the first network device. The first tunnel information is determined based on the correspondence between a first area and the first tunnel information; the first area belongs to the signal coverage area of ​​the first network device. The first device transmits the first information.

[0032] The first information can be used to determine the first tunnel information. Since the tunnel information of the network device is associated with the region, when the region where the first terminal device is located does not change, but the network device providing services to the first terminal device changes, the tunnel information of the user plane of the terminal device (e.g., the tunnel information of the network device) does not need to be updated, thereby reducing the update frequency of the tunnel information of the network device and thus reducing signaling overhead.

[0033] In one possible implementation, the first information includes at least one of the following: location information of the first terminal device, information of a first region, or first tunnel information, wherein the location of the first terminal device belongs to the first region. This increases the flexibility of the solution. Furthermore, if the first information includes the location information of the first terminal device and / or the information of the first region, the first tunnel information can be determined based on this information. This solution allows other devices to determine the first tunnel information based on the first information.

[0034] In one possible implementation, the first device acquires second information, which is determined based on the first information. The second information includes at least one of the following: location information of the first terminal device, information of a first region, or first tunnel information. The location of the first terminal device belongs to the first region. The first device can determine the second information itself or receive second information from other devices. The first device can determine the first information based on the second information, thereby improving the accuracy of the first information. When the second information differs from the first information, the step of determining the first information based on the second information (e.g., determining the region of the first terminal device based on its location information) can be a step within the first tunnel information determination step, thereby reducing the complexity of the scheme executed by other devices to determine the first tunnel information.

[0035] In one possible implementation, the second information includes the location information of the first terminal device, and the first information includes first tunnel information. For example, the first device determines a first region based on the location information of the first terminal device, and determines the first tunnel information based on the correspondence between the first region and the first tunnel information. For example, the first device can determine the first tunnel information, thereby reducing the complexity of the scheme executed by other devices to determine the first tunnel information.

[0036] In one possible implementation, the second information includes the location information of the first terminal device, and the first information includes a first region. The first device determines the first region based on the location information of the first terminal device. The step of the first device determining the first region based on the location information of the first terminal device can be a step within the first tunnel information determination step, thereby reducing the complexity of the scheme executed by other devices to determine the first tunnel information.

[0037] In one possible implementation, the second information includes the location information of the first terminal device. The first device receives the location information of the first terminal device, or the first device receives positioning measurement results and determines the location information of the first terminal device based on the positioning measurement results. This can improve the flexibility of the solution. For example, if the first device determines that the obtained location information of the first terminal device is inaccurate, lacks sufficient precision, or cannot determine the first information where the first terminal device is located, the first device initiates a positioning process to re-acquire the location information of the first terminal device, so that the first device can determine the first information based on the location of the first terminal device.

[0038] In one possible implementation, the first device receives first indication information, which indicates that the first network device has not obtained tunnel information for the first area. Based on the first indication information, the first device sends the tunnel information for the first area to the first network device. Thus, the first device can determine whether the first network device has obtained tunnel information based on whether it receives the first indication information. If the first network device has already obtained tunnel information, it will not send the information again, thereby saving signaling overhead.

[0039] In one possible implementation, the first device receives second indication information, which indicates that the first network device has acquired tunnel information for the first area. Based on the second indication information, the first device determines that it is unnecessary to send the tunnel information for the first area to the first network device. Thus, the first device can determine whether the first network device has acquired tunnel information based on whether it has received the second indication information. If the first network device has already acquired tunnel information, it will not send the information again, thereby saving signaling overhead.

[0040] In one possible implementation, the first device sends the first information to the user plane entity even if the user plane entity has not obtained the first tunnel information. This can save signaling overhead.

[0041] In one possible implementation, the first device sends a first identifier of the first terminal device to the user plane entity. This first identifier indicates the first terminal device and is used by the user plane entity and the first network device to transmit information about the first terminal device. Thus, when the first tunnel information is at the region-level granularity, the first network device can identify which terminal device a received message belongs to based on the first identifier of the first terminal device. This approach avoids the first network device sending information to the wrong terminal device.

[0042] In one possible implementation, the first tunnel information is further determined based on the first terminal device, and the tunnel information of the first network device of at least two terminal devices in the first area is different.

[0043] In one possible implementation, the first tunnel information is further determined based on the first terminal device and its first session, wherein the tunnel information of the first network device corresponding to at least two sessions of the first terminal device in the first area is different. Related beneficial effects and descriptions can be found in the description of the possible implementations of the first aspect, and will not be repeated here.

[0044] In one possible implementation, the first device acquires a second identifier of the first terminal device. The second identifier of the first terminal device is determined based on a correspondence between a first region and a second identifier, with the first terminal device located in the first region. For example, the first device transmits information about the first terminal device based on the second identifier. Related beneficial effects and descriptions can be found in the description of possible implementations of the first aspect, and will not be repeated here.

[0045] In one possible implementation, the first device receives information for indicating the second identifier. Related beneficial effects and descriptions can be found in the description of possible implementations of the first aspect, and will not be repeated here.

[0046] In one possible implementation, the first device determines that the signal coverage area of ​​the first network device includes a first region, the first device determines the identifier of at least one terminal device corresponding to the first region, and the first device selects one identifier from the identifiers of the at least one terminal device as a second identifier. Related beneficial effects and descriptions can be found in the description of the possible implementations of the first aspect, and will not be repeated here.

[0047] In one possible implementation, the first device sends information indicating the second identifier. Related beneficial effects and descriptions can be found in the description of possible implementations of the first aspect, and will not be repeated here.

[0048] Thirdly, embodiments of this application provide a communication method that can be executed by a user plane entity. The user plane entity can be a device implementing the functions of a user plane entity or a chip (or chip system, or circuit, or unit, or module) within that device.

[0049] The user plane entity acquires first tunnel information. The first tunnel information is the tunnel information of the first network device. The first tunnel information is determined based on the correspondence between a first region and the first tunnel information; the first region belongs to the signal coverage area of ​​the first network device. The user plane entity sends a first message to the first network device, the first message including the first tunnel information.

[0050] Because the tunnel information of the network device is associated with the region, when the region where the first terminal device is located remains unchanged, but the network device providing services to the first terminal device changes, the tunnel information of the user plane of the terminal device (e.g., the tunnel information of the network device) does not need to be updated, thereby reducing the update frequency of the tunnel information of the network device and thus reducing signaling overhead.

[0051] In one possible implementation, the first message further includes a first identifier of the first terminal device, which is used to indicate the first terminal device. Related beneficial effects and descriptions can be found in the description of the possible implementations of the first aspect, and will not be repeated here.

[0052] In one possible implementation, the user plane entity receives information indicating a first identifier. Thus, when the first tunnel information is at the region-level granularity, the user plane entity can carry the first identifier in the message. The first network device can identify which terminal device the received message belongs to based on the first identifier of the first terminal device. This scheme can prevent the first network device from sending information to the wrong terminal device.

[0053] In one possible implementation, the user plane entity receives a fourth message from the first network device. This fourth message includes tunnel information of the user plane entity and a first identifier of the first terminal device. Thus, the UPF can obtain the first identifier and then send a message based on the UPF's tunnel information and the first identifier, enabling the first network device to identify which terminal device the information in the received message belongs to.

[0054] In one possible implementation, the first region further includes a second terminal device. The user plane entity sends a second message to the first network device, the second message including the first tunnel information. It can be seen that multiple terminal devices in a region can share the tunnel information of the same network device. In this implementation, the tunnel information of the network device is at the region level. This reduces the amount of tunnel information on the first network device side, and also reduces the number of correspondences between tunnel information and regions, thereby reducing the complexity of the solution and the storage space occupied by the correspondences between tunnel information and regions.

[0055] In one possible implementation, the user plane entity receives first tunnel information. Thus, the user plane entity can send information to the first network device based on the first tunnel information, and a downlink tunnel from the user plane entity to the first network device can be established.

[0056] In one possible implementation, the user plane entity receives a third message from the first network device, the third message including tunnel information of the user plane entity and first tunnel information. Related beneficial effects and descriptions can be found in the description of the possible implementations of the first aspect, and will not be repeated here.

[0057] In one possible implementation, the user plane entity receives information indicating the location of a first terminal device. This information includes the location of the first terminal device and / or information about a first region. The user plane entity determines the first tunnel information based on the information indicating the location of the first terminal device and the correspondence between the first region and the first tunnel information. In this approach, the user plane entity can determine the first tunnel information itself, thereby reducing the complexity of obtaining the first tunnel information for other devices.

[0058] In one possible implementation, the user plane entity sends the first tunnel information. This approach can reduce the complexity of other devices acquiring the first tunnel information.

[0059] In one possible implementation, the first tunnel information is further determined based on the first terminal device, and the tunnel information of the first network devices of at least two terminal devices in the first area is different. Related beneficial effects and descriptions can be found in the description of the possible implementations of the first aspect, and will not be repeated here.

[0060] In one possible implementation, the first tunnel information is further determined based on the first terminal device and its first session, wherein the tunnel information of the first network device corresponding to at least two sessions of the first terminal device in the first area is different. Related beneficial effects and descriptions can be found in the description of the possible implementations of the first aspect, and will not be repeated here.

[0061] Fourthly, a communication device is provided, which may be the aforementioned first network device, mobility management entity, session management entity, or user plane entity. The communication device may include a communication unit and a processing unit to perform any one of the first to third aspects, or any possible implementation of the first to third aspects. The communication unit is used to perform functions related to sending and receiving. The communication unit may be referred to as a transceiver unit. Optionally, the communication unit includes a receiving unit and a sending unit. In one design, the communication device is a communication chip, the processing unit may be one or more processors or processor cores, and the communication unit may be the input / output circuit, input / output interface, or antenna port of the communication chip.

[0062] In another design, the communication unit can be a transmitter and a receiver, or the communication unit can be a transmitter and a receiver.

[0063] Optionally, the communication device may also include modules that can be used to perform any one of the first to third aspects described above, or to perform any possible implementation of the first to third aspects.

[0064] Fifthly, a communication device is provided, which may be the aforementioned first network device, mobility management entity, session management entity, or user plane entity. The communication device may include at least one processor and a memory to execute any one of the first to third aspects, or to execute any possible implementation of the first to third aspects. Optionally, it may also include a transceiver, the memory for storing computer programs or instructions, and the at least one processor for retrieving and executing the computer program or instructions from the memory. When the at least one processor executes the computer program or instructions in the memory, the communication device executes any one of the first to third aspects, or to execute any possible implementation of the first to third aspects.

[0065] Optionally, there may be one or more processors and one or more memories.

[0066] Optionally, the memory can be integrated with at least one processor, or the memory can be set separately from at least one processor.

[0067] Optionally, the transceiver may include a transmitter and a receiver.

[0068] In a sixth aspect, a communication device is provided, which may be the aforementioned first network device, mobility management entity, session management entity, or user plane entity. The communication device may include at least one processor to execute any one of the first to third aspects, or to execute any possible implementation of the first to third aspects. For example, at least one processor executes any one of the first to third aspects, or to execute any possible implementation of the first to third aspects, via logic circuitry or by executing computer programs or instructions in memory. At least one processor is coupled to a memory. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and at least one processor is coupled to the communication interface.

[0069] In one implementation, when the communication device is a first network device, a mobility management entity, a session management entity, or a user plane entity, the communication interface can be a transceiver or an input / output interface. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0070] In another implementation, when the communication device is a chip or chip system, the communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. At least one processor can also be embodied as a processing circuit or logic circuit.

[0071] In a seventh aspect, a system is provided, which includes at least one of a mobility management entity, a session management entity, or a user plane entity.

[0072] In one possible implementation, the system may further include a first network device and / or a second network device.

[0073] In one possible implementation, the system may also include a terminal device.

[0074] Eighthly, a chip system is provided, the chip system including at least one processor and an interface circuit, the interface circuit and the at least one processor being interconnected by a line, the at least one processor executing a computer program (also referred to as code or instructions) to cause any one of the first to third aspects and any possible implementation of the first to third aspects to be executed.

[0075] Ninthly, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when executed, causes a computer to perform any one of the first to third aspects described above, or to perform any possible implementation of the first to third aspects.

[0076] In a tenth aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform any one of the first to third aspects described above, or to perform any possible implementation of the first to third aspects.

[0077] Eleventhly, a processing apparatus is provided, comprising: an interface circuit and a processing circuit. The interface circuit may include an input circuit and an output circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, thereby enabling any one of the first to third aspects described above, or any possible implementation of the first to third aspects, to be implemented.

[0078] In specific implementation, the aforementioned processing device can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, gate circuit, flip-flop, and various logic circuits, etc. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as the input circuit and output circuit at different times. This application does not limit the specific implementation method of the processor and various circuits.

[0079] In one implementation, the communication device is a first network device, a mobility management entity, a session management entity, or a user plane entity. The interface circuit can be a radio frequency processing chip in the first network device, the mobility management entity, the session management entity, or the user plane entity, and the processing circuit can be a baseband processing chip in the first network device, the mobility management entity, the session management entity, or the user plane entity.

[0080] In another implementation, the communication device can be a component of a first network device, mobility management entity, session management entity, or user plane entity, such as an integrated circuit product like a system-on-a-chip or communication chip. The interface circuit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processing circuit can be the logic circuit on the chip. Attached Figure Description

[0081] Figure 1A This application provides a schematic diagram of a possible communication system architecture.

[0082] Figure 1B This is a schematic diagram of another possible communication system architecture provided in the embodiments of this application;

[0083] Figure 1CThis is a schematic diagram of another possible communication system architecture provided in the embodiments of this application;

[0084] Figure 1D This is a schematic diagram of another possible communication system architecture provided in the embodiments of this application;

[0085] Figure 1E This is a schematic diagram of another possible communication system architecture provided in the embodiments of this application;

[0086] Figure 2 A schematic diagram illustrating a possible communication scenario provided in an embodiment of this application;

[0087] Figure 3 A possible flowchart illustrating a communication method provided in an embodiment of this application;

[0088] Figure 4 A schematic diagram illustrating another possible correspondence between area and tunnel information provided in an embodiment of this application;

[0089] Figure 5 A schematic diagram illustrating yet another possible communication scenario provided in an embodiment of this application;

[0090] Figure 6 A possible flowchart illustrating a communication method provided in an embodiment of this application;

[0091] Figure 7 A possible flowchart illustrating another communication method provided in an embodiment of this application;

[0092] Figure 8 A possible flowchart illustrating a communication method provided in an embodiment of this application;

[0093] Figure 9 A possible flowchart illustrating a communication method provided in an embodiment of this application;

[0094] Figure 10 A possible flowchart illustrating a communication method provided in an embodiment of this application;

[0095] Figure 11 This is a possible structural schematic diagram of a communication device provided in an embodiment of this application;

[0096] Figure 12 This is a possible structural schematic diagram of another communication device provided in the embodiments of this application. Detailed Implementation

[0097] For ease of understanding, the terms used in the embodiments of this application are explained below.

[0098] (1) User plane connection.

[0099] A connection can be established between a network device and a user plane entity; this connection may be called a user plane connection, a tunnel connection, or a user plane tunnel connection. A network device may be, for example, an access network device (e.g., a base station).

[0100] In this user plane connection, the network device enables (or allocates, or uses) its tunnel information, and the user plane entity enables (or allocates, or uses) its tunnel information. The tunnel information of the network device and the user plane entity are used to assist or enable the transmission of data (also known as packets) through this user plane connection. In this application embodiment, "enable" can be replaced with "allocate" or "use," etc.

[0101] For example, the network device stores the tunnel information of user plane entities. This enables uplink data to be sent from the network device to the user plane entity. For instance, the network device can carry the tunnel information of the user plane entity in the uplink data. If the tunnel information of the user plane entity received in the uplink data is its own tunnel information, the user plane entity can determine that this information is the data it needs to receive. If the tunnel information of the user plane entity received in the uplink data is not its own tunnel information, it can determine that this information is not the data it needs to receive and can discard it or send it to another device, etc.

[0102] For example, a user plane entity can store tunnel information of a network device, enabling downlink data to be sent from the user plane entity to the network device. For instance, the user plane entity can carry the network device's tunnel information in the downlink data. If the tunnel information of the network device in the received downlink data is its own tunnel information, the network device can determine that this information is the data it needs to receive. If the tunnel information of the network device in the received downlink data is not its own tunnel information, it can determine that this information is not the data it needs to receive and can discard it or send it to another device, etc.

[0103] The network device knows both the tunnel information of the user plane entity and the tunnel information of the network device. Similarly, the user plane entity knows both the tunnel information of the network device and the tunnel information of the user plane entity. Knowing the tunnel information of the peer node is for data transmission, that is, sending data to the peer node. Knowing the node's own tunnel information is for verifying whether the received data was intended for itself.

[0104] In this application's embodiments, tunnel information (e.g., tunnel information of user plane entities and / or tunnel information of network devices) can be replaced with information or identifiers. For example, tunnel information of a network device can be used to identify the network device. A network device can include / be replaced by a network device or an access network device. For another example, tunnel information of a network device can include / be replaced by: the identifier of the network device, the tunnel information of the network device, or the tunnel information of the access network device. For another example, tunnel information of a network device can include / be replaced by: at least one of the following: base station tunnel information, RAN tunnel information, NG-RAN tunnel information, AN tunnel information, gNB tunnel information, or gNodeB tunnel information. For another example, tunnel information in this application's embodiments can be referred to as tunnel information. For example, RAN tunnel information can include / be replaced by: RAN tunnel information, or can also be written as RAN tunnel info. Specifically, tunnel information can include at least one of the following: Internet Protocol (IP) and tunnel endpoint identifier (TEID).

[0105] For example, tunnel information of a user face entity can be used to identify that user face entity, and the tunnel information of the user face entity can be replaced with the identifier of the user face entity. For example, the tunnel information of a user face entity can include / be replaced with: UPF tunnel information, or it can be written as UPF tunnel info.

[0106] (2) Control plane connection.

[0107] During the terminal device's network access process, network devices (such as access network equipment) can establish a control plane connection with the mobility management entity to manage and control the terminal device.

[0108] A connection can be established between the network device and the mobility management entity; this connection may be referred to as a control plane connection. The network device may be, for example, an NTN device or a chip (or chip system, circuit, unit, or module) within an NTN device. The NTN device may include, for example, access network equipment (e.g., a base station).

[0109] In this control plane connection, the network device enables (or assigns, or uses) a second identifier for the first terminal device. This second identifier uniquely identifies the first terminal device among all terminal devices for which the network device provides communication services. The second identifier can also be the second identifier of the first terminal device on the network device side. For example, the second identifier of the first terminal device can include / be replaced by: a radio access network (RAN) UE NGAP identifier (ID). Here, NGAP is the abbreviation for Next Generation Application Protocol (NGAP). NGAP can be the protocol interface between the RAN and the mobility management entity.

[0110] In this control plane connection, the mobility management entity enables, assigns, or uses a third identifier for the first terminal device. This third identifier uniquely identifies the first terminal device among all terminal devices for which the mobility management entity provides communication services. The third identifier can also be a third identifier of the first terminal device on the mobility management entity side. For example, the third identifier of the first terminal device can include / be replaced with: AMF UENGAP ID.

[0111] When network devices interact with mobility management entities (except for the initial interaction), they may simultaneously carry a second identifier (e.g., RAN UE NGAP ID) and a third identifier (e.g., AMF UENGAP ID) of the first terminal device in the message. The second identifier and the third identifier of the first terminal device may be the same or different. The second identifier and / or the third identifier of the first terminal device may be permanent identifiers of the first terminal device, such as a subscription permanent identifier (SUPI), or temporary identifiers, such as a globally unique temporary identity (GUTI).

[0112] The network device and the mobility management entity can transmit mobility management information or session management information of the first terminal device, which may not need to be sent to the first terminal device. For example, the network device can use this information to perform some mobility management on the first terminal device. For instance, this information might instruct the first terminal device to access only one of RAN#1, RAN#2, and RAN#3; if the first terminal device wants to access RAN#4, the network device can control the first terminal device to be unable to access RAN#4. As another example, the network device can use this information to perform some session management on the first terminal device, such as quality of service (QoS) management, or configuring the air interface bearer between the RAN and the UE. For yet another example, session management also includes tunnel information of user plane entities, which the network device uses to establish a tunnel with the user plane entity.

[0113] (3) Beam.

[0114] In the NR protocol, beaming can be represented as a spatial domain filter, spatial filter, spatial domain parameter, spatial parameter, spatial domain setting, spatial setting, quasi-colocation (QCL) information, QCL assumption, QCL indication, etc. Beaming can be indicated by transmission configuration indication state (TCI-state) parameters or by spatial relation parameters. Therefore, in this application, beaming can be replaced by spatial domain filter, spatial filter, spatial parameter, spatial parameter, spatial setting, spatial setting, QCL information, QCL assumption, QCL indication, TCI-state (DL TCI-state, UL TCI-state), spatial relation, etc. These terms are also equivalent to each other. Beaming can also be replaced with other beaming terms, which are not limited in this application.

[0115] A beam can include a beam for transmitting signals and / or a beam for receiving signals. A transmitting beam can refer to the distribution of signal strength in different directions in space after a signal is transmitted through an antenna, while a receiving beam can refer to the distribution of signal strength in different directions in space of a wireless signal received from an antenna.

[0116] Beams are generally associated with resources. For example, during beam measurement, network devices transmit different beams through different resources, and the terminal devices provide feedback on the measured resource quality, allowing the network devices to determine the quality of the corresponding beam. During data transmission, beam information is also indicated through its corresponding resources. For instance, network devices use the Transmission Configuration Index (TCI) field in downlink control information (DCI) to indicate the Physical Downlink Shared Channel (PDSCH) beam information of the terminal devices.

[0117] Optionally, multiple beams with the same or similar communication characteristics can be considered as a single beam. A beam may include one or more antenna ports for transmitting data channels, control channels, and detection signals, etc. One or more antenna ports forming a beam can also be considered as a set of antenna ports.

[0118] For example, a satellite device in a certain time unit (such as the first satellite device) can concentrate energy in a certain direction, which can transmit the signal further, but the signal cannot be received in other directions. The next time unit transmits in another direction, and finally, by continuously changing the direction of the beam, coverage of multiple areas can be achieved.

[0119] (4) Region.

[0120] Region: Unless otherwise specified, "region" in the following embodiments of this application refers to a geographical region. That is, a region is fixed relative to the Earth, or it can be understood as a geographical region that is fixed relative to the Earth. For example, a region may have at least one of the following attributes: shape, outline, size, radius, area, geographical location, etc.

[0121] The term "region" can also have an altitude attribute, meaning a region can be understood as a geographical area at a given altitude or altitude range. By default, a region can refer to a geographical area on the ground with an altitude of 0 kilometers (km) or an altitude around 0 km (e.g., within the range of [-2, 2] km), or a geographical area with a certain average altitude. Additionally, it can refer to geographical areas at other specific altitudes or altitude ranges, such as a geographical area with an altitude of 10 km, or a geographical area with an altitude around 10 km (e.g., within the range of [7, 13] km).

[0122] In one possible implementation, the aforementioned region fixed relative to the Earth can also be referred to as a "wave position," "geographical region," etc. Of course, other names are also possible, and this application does not specifically limit the name of the region fixed relative to the Earth.

[0123] Different regions may have the same or different shapes, outlines, sizes, radii, and areas. Different regions may be geographically different. Different regions may or may not overlap.

[0124] In one possible implementation, "region fixed relative to the Earth" can be understood as follows: the region's outline, size, or geographical location remains unchanged; for example, the region's outline, size, or geographical location does not change over time. Alternatively, "region fixed relative to the Earth" can be understood as follows: the region's outline and the points within it can be described using a fixed Earth coordinate system, or the coordinates of each point on the region's outline in the fixed Earth coordinate system remain constant.

[0125] In one possible implementation, the shape of the region can be a regular hexagon, or other shapes such as a regular pentagon, a circle, an ellipse, etc. Alternatively, the shape of the region can also be irregular, without limitation.

[0126] For example, the shape of a region can be defined by a protocol or by a network device. Regions defined by different network devices can have the same or different shapes. The same network device can also define multiple region shapes. Similarly, the size, radius, and area of ​​a region can also be defined by a protocol or by a network device. Regions defined by different network devices can have the same or different sizes, radii, or areas. The same network device can also define multiple region sizes, multiple region radii, or multiple region areas.

[0127] In one possible implementation, the Earth's surface can be divided into multiple regions, and these regions can be indexed (e.g., numbered). Terminal devices and network devices can agree on the numbering method for these regions (e.g., starting from 1 or 0) and the correspondence between regions and indexes. Alternatively, the protocol can define the numbering method for these regions and the correspondence between regions and indexes. Based on the region indexes, information such as the region's geographical location can be determined.

[0128] Optionally, the multiple regions can completely cover the Earth's surface, such that any location on the Earth's surface belongs to a certain region; or, the multiple regions can also cover part of the geographical location on Earth, for example, the multiple regions may not cover the Earth's South Pole and / or North Pole, that is, the South Pole and / or North Pole may not exist in the region.

[0129] Optionally, the method of dividing the network into multiple zones can be defined by a protocol or by the network device. Different network devices can define the same or different division methods. The same network device can also define multiple division methods.

[0130] As a first possible method of partitioning, the Earth's surface can be divided using a latitude and longitude grid with a granularity, for example, a latitude and longitude grid with a granularity of 1 degree. If only this discretization method is used, the globe can be divided into 360×360=129600 regions. Terminal devices and network devices can define the indexes of these 129600 regions as 0,1,…,129599, or they can also define them as 1,2,…,129600.

[0131] Optionally, when introducing the altitude attribute of a geographic region, multiple grids can be defined to divide the Earth's surface. For example, a grid at an altitude of 0 km or within the range of [-2, 2] km can be divided into 1-degree latitude and longitude grids, generating 129,600 regions. At an altitude of 10 km or within the range of [7, 13] km, further division using 1-degree latitude and longitude grids generates another 129,600 regions. When indexing these regions, the index range needs to be expanded. For example, the total index could be 0, 1, ..., 129,599, 129,600, 129,601, ..., 259,199, where the first 129,600 indices represent the region index at an altitude of 0 km or within the range of [-2, 2] km, and the last 129,600 indices represent the region index at an altitude of 10 km or within the range of [7, 13] km.

[0132] For example, the granularity of the latitude and longitude grid can be determined based on the type of network device. For instance, a relatively small granularity can be used for discretization when the network device is a LEO satellite, and a relatively large granularity can be used when the network device is a geosynchronous earth orbit (GEO) satellite.

[0133] As a second possible method of division, the Earth's surface can be divided using latitude and longitude grids of various granularities. For example, a portion of the Earth's surface or a portion of its administrative region can be divided using a latitude and longitude grid with a granularity of 1 degree, while another portion of the surface or administrative region can be divided using a latitude and longitude grid with a granularity of 2 degrees.

[0134] Alternatively, by introducing the altitude attribute of a geographic region, the Earth's surface can be divided using a latitude and longitude grid with a granularity of 1 degree at an altitude of 0 km, and the Earth's surface can be divided using a latitude and longitude grid with a granularity of 2 degrees at an altitude of 10 km.

[0135] As a third possible method of division, the Earth's surface can be divided by administrative regions. For example, a township-level administrative region could be considered as a region.

[0136] As a fourth possible division method, for GEO satellites, the projection of one of the GEO satellite's beams onto the ground can be considered as a region. Since GEO satellites are stationary relative to the Earth, the projection of the GEO satellite's beams onto the ground can be considered fixed relative to the Earth.

[0137] In practical applications, the Earth's surface can be divided using a combination of different methods. For example, a portion of the Earth's surface or a part of its administrative region can be divided using a latitude and longitude grid with a granularity of 1, while another portion of the surface or administrative region can be divided according to its administrative region.

[0138] In one possible implementation, when the Earth's surface is divided into multiple regions, different levels of region division can be applied to the same surface area. For example, for a given surface area, a first level of region division can be performed using a 10-degree granularity latitude and longitude grid, a second level using a 6-degree granularity grid, and a third level using a 1-degree granularity grid. In this case, within the surface area, the number of regions at the first level is greater than the number at the second level, and the number of regions at the second level is greater than the number at the third level. Furthermore, in this scenario, each level of region can be individually numbered.

[0139] The technical solutions of this application can be applied to satellite communication systems, high altitude platform station (HAPS) communications, and non-terrestrial network (NTN) systems such as unmanned aerial vehicles (UAVs). Examples include integrated communication and navigation (ICAN) systems, global navigation satellite systems (GNSS), and ultra-dense low-Earth orbit (LEO) satellite communication systems. Satellite communication systems can be integrated with traditional mobile communication systems. For example, mobile communication systems can be fourth-generation (4G) communication systems (e.g., Long Term Evolution (LTE) systems), worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) communication systems (e.g., new radio (NR) systems), and future mobile communication systems.

[0140] This embodiment of the application uses a 5G network architecture as an example for illustration. However, there are various possible architectures for 5G networks. Figure 1A This is a schematic diagram of a possible 5G network architecture provided in an embodiment of this application. The following is in conjunction with... Figure 1A The communication system architecture applicable to the embodiments of this application is described, such as... Figure 1A As shown, this network architecture typically includes the following devices, network elements, and networks:

[0141] 1. Terminal equipment.

[0142] Figure 1A The example provided uses user equipment (UE) as the terminal device. In specific implementations, the terminal device in this application embodiment can be a device used to implement wireless communication functions. Specifically, the terminal device can be a user equipment (UE), access terminal, terminal unit, terminal station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, terminal agent, or terminal device in a 5G network or a future evolved public land mobile network (PLMN). Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices or wearable devices, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc. Terminals can be mobile or fixed.

[0143] The aforementioned terminal devices can establish connections with the operator's network through interfaces provided by the operator's network (such as N1), and use data and / or voice services provided by the operator's network. The terminal devices can also access the DN (Network Provider) through the operator's network, and use operator services deployed on the DN, and / or services provided by third parties. These third parties can be service providers outside of the operator's network and terminal devices, and can provide other data and / or voice services to the terminal devices. The specific form of these third parties can be determined based on the actual application scenario and is not limited here.

[0144] 2. Access Network Equipment: Used to provide network access functionality for authorized terminal equipment in a specific area, and capable of using transmission tunnels of different quality according to the terminal equipment's level, service requirements, etc. For example, access network equipment may include / become: access network (AN) equipment, and / or radio access network (RAN) equipment. In the embodiments of this application, (R)AN can represent RAN, and / or AN. Any combination of access network equipment, access network elements, or access network entities can be substituted for each other; for example, (R)AN equipment can also be replaced by (R)AN network elements, or (R)AN entities.

[0145] (R)AN is a subnetwork of a carrier network, serving as the implementation system between service nodes and terminal devices within the carrier network. For a terminal device to access the carrier network, it first passes through the (R)AN, and then connects to the service nodes of the carrier network via the (R)AN. The (R)AN device in this application is a device that provides wireless communication functionality for terminal devices.

[0146] The network devices involved in the embodiments of this application include, for example, (R)AN. (R)AN can be a base station, an evolved NodeB (eNodeB or eNB), a transmission reception point (TRP), a transmission point (TP), a base station in a 5th generation (5G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system; it can also be a module or unit that performs some of the functions of a base station, for example, it can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). The CU (Radio Control Unit) performs the functions of the Radio Resource Control Protocol (RRC) and Packet Data Convergence Protocol (PDCP) of the base station, and can also perform the functions of the Service Data Adaptation Protocol (SDAP). The DU (Radio Link Control Unit) performs the functions of the Radio Link Control (RRC) and Medium Access Control (MAC) layers of the base station, and can also perform some or all of the physical layer functions. For specific descriptions of the above-mentioned protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). The CU and DU can be set up separately or included in the same network element, such as in the baseband unit (BBU). The RU (Radio Receiver Unit) can be included in radio frequency equipment or radio frequency units, such as in the remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH). In different systems, the CU, DU, or RU may also have different names, but those skilled in the art will understand their meaning. For example, in an open radio access network (ORAN) system, a CU can also be called an open CU (open-CU, O-CU), a DU can also be called an open DU (open-DU, O-DU), and a RU can also be called an open RU (open-RU, O-RU).In this application, any of the following units—CU (or CU control plane (CU-CP), CU user plane (CU-UP), DU, and RU)—can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU-CP can also be called open-CU-CP (O-CU-CP), and CU-UP can also be called open-CU-UP (O-CU-UP).

[0147] In this application, the base station sends downlink signals or downlink information to the terminal device, with the downlink information carried on the downlink channel; the terminal device sends uplink signals or uplink information to the base station, with the uplink information carried on the uplink channel. In order to communicate with the base station, the terminal device needs to establish a radio connection with a cell controlled by the base station. The cell with which the terminal device has established a radio connection is called the serving cell of the terminal device. When the terminal device communicates with this serving cell, it is also subject to interference from signals from neighboring cells.

[0148] 3. User plane network elements: used for packet routing and forwarding, as well as quality of service (QoS) processing of user plane data.

[0149] like Figure 1A As shown, in a 5G communication system, the user plane network element can be a user plane function (UPF) network element (or UPF entity), such as at least one of an intermediate user plane function (I-UPF) network element or a PDU session anchor user plane function (PSA-UPF) network element. In future communication systems, the user plane network element can still be a UPF network element, or it can have other names; this application does not limit this. The user plane network element can also be replaced by a user plane entity.

[0150] 4. Data network (DN) element: A network used to provide data transmission.

[0151] like Figure 1A As shown, in a 5G communication system, the data network can be DN1 and DN2. In future communication systems, the data network can still be DN, or it can have other names; this application does not limit this. The data network element can also be replaced by a data network entity.

[0152] 5. Mobility Management Entity: Primarily used for mobility management and access management, it can implement functions other than session management within the Mobility Management Entity (MME) system, such as lawful monitoring and access authorization / authentication. The Mobility Management Entity can also be replaced by the Mobility Management Entity.

[0153] like Figure 1A As shown, in a 5G communication system, the access and mobility management can be an access and mobility management function (AMF) network element. In future communication systems, access and mobility management can still be an AMF network element (or AMF entity), or it can have other names; this application does not limit this.

[0154] 6. Session Management Network Element: Primarily used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection of endpoints for manageable user plane functions, policy control, and billing function interfaces, and downlink data notification. The session management network element can also be replaced by a session management entity.

[0155] like Figure 1A As shown, in a 5G communication system, the session management network element can be a session management function (SMF) network element (or SMF entity), such as at least one of an intermediate session management function (I-SMF) network element or an anchor session management function (A-SMF) network element. In future communication systems, the session management network element can still be an SMF network element, or it can have other names; this application does not limit this.

[0156] 7. Policy control network element: A unified policy framework used to guide network behavior, providing policy rule information to control plane functional network elements (such as AMF, SMF, etc.).

[0157] like Figure 1A As shown, in a 5G communication system, this policy control network element can be a policy control function (PCF) network element. In future communication systems, the policy control network element can still be a PCF network element, or it can have other names; this application does not limit this.

[0158] The communication system architecture applicable in the embodiments of this application may also include other network elements, such as network analysis function network elements and service communication function network elements.

[0159] Among them, the network analytics function network element is used to provide network slice instance-level data analysis capabilities. For example, it can acquire data, then use the data for training and analysis, and perform corresponding inferences based on the analysis results. In 5G communication systems, this network analytics function network element can be a network analytics function (NWDAF) network element.

[0160] Figure 1A In this context, Npcf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the definitions in the 3GPP standard protocols, and are not limited here.

[0161] It is understood that the aforementioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). These network elements or functions can be divided into one or more services; furthermore, services existing independently of network functions may also exist. In this application, instances of the aforementioned functions, instances of services included in the aforementioned functions, or instances of services existing independently of network functions can all be referred to as service instances.

[0162] It should be noted that the embodiments of this application are not limited to the system architecture described above, and can also be applied to other future communication systems, such as the 6th generation (6G) communication system architecture. Furthermore, the names of the various network elements used in the embodiments of this application may remain functionally the same in future communication systems, but their names may change.

[0163] For example, Figure 1B An exemplary diagram of a service-based 5G network architecture provided in an embodiment of this application is shown.

[0164] Figure 1B For an introduction to the functions of network elements, please refer to [reference needed]. Figure 1A The functions of the corresponding network elements will not be described in detail here. Figure 1B and Figure 1A The main difference is: Figure 1B The interfaces between the various network elements are point-to-point interfaces, rather than service-oriented interfaces.

[0165] exist Figure 1B In the architecture shown, the interface names and functions between the various network elements are as follows:

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

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

[0168] N3: Interface between RAN and UPF.

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

[0170] N6: Interface between UPF and DN.

[0171] N7: The interface between PCF and SMF, used to issue protocol data unit (PDU) session granularity and business data stream granularity control strategies.

[0172] N9: The interface between UPFs, used to transmit uplink and downlink data between them. The interface protocol is GTP-U (GPRS tunneling protocol for the user plane), which uses a tunneling protocol to transmit data, shielding it from the influence of upper-layer protocols, while providing a session-level bidirectional high-speed transmission channel. GPRS is the general packet radio service.

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

[0174] N14: An interface between AMFs, used for passing the context of terminal devices between AMFs.

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

[0176] Figure 1C and Figure 1D The diagram illustrates network architectures for several communication systems applicable to embodiments of this application. These communication systems may include satellites, network devices, and terminal devices. They may also include gateways and core network devices. Figure 1C and Figure 1D An exemplary network architecture combining NTN and terrestrial networks is illustrated below. This will be described in conjunction with the accompanying drawings.

[0177] The satellite can be a highly elliptical orbit (HEO) satellite, a geosynchronous orbit (GSO) satellite, a geostationary earth orbit (GEO) satellite, a medium earth orbit (MEO) satellite, or a low-earth orbit (LEO) satellite. This application does not limit the satellite's operating mode; for example, the satellite can operate in transparent mode or regenerative mode. Figure 1C This illustration uses the satellite's transparent transmission mode as an example. Figure 1D This illustration uses the satellite's operating mode as the regeneration mode as an example.

[0178] When a satellite operates in transparent mode, it provides transparent relay forwarding functionality. A gateway possesses the functions of a network device (such as a base station) or some of the functions of a network device (such as a base station); in this case, the gateway can be considered a network device (such as a base station). Alternatively, the network device (such as a base station) can be deployed separately from the gateway. In this case, the feeder link latency includes both the latency from the satellite to the gateway and the latency from the gateway to the gNB. The transparent mode discussed later assumes that the gateway and gNB are located together or close to each other. For cases where the gateway and gNB are far apart, the feeder link latency is simply the sum of the latency from the satellite to the gateway and the latency from the gateway to the gNB.

[0179] When a satellite is operating in regenerative mode, it has data processing capabilities and functions as a network device (such as a base station) or partially functions as a network device (such as a base station). In this case, the satellite can be regarded as a network device (such as a base station).

[0180] Satellites can communicate wirelessly with terminal devices via broadcast communication signals and navigation signals. Optionally, each satellite can provide communication, navigation, and positioning services to terminal devices through multiple beams. For example, each satellite uses multiple beams to cover the service area, and the relationship between different beams can be one or more of time-division, frequency-division, and space-division.

[0181] A gateway (also known as a ground station, earth station, or gateway) is a network device used to connect satellites and ground-based network equipment (such as ground base stations). One or more satellites can connect to one or more ground-based network devices (such as ground base stations) through one or more gateways; this is not a limitation. The link between the satellite and the terminal device is called a service link, and the link between the satellite and the gateway is called a feeder link. Network equipment can be deployed separately from the gateway; therefore, the latency of the feeder link can include both the latency from the satellite to the gateway and the latency from the gateway to the network equipment.

[0182] The network devices in this application embodiment may include network devices deployed on satellites (such as satellite base stations), network devices deployed on gateways, or network devices deployed on the ground (such as ground base stations). Network devices include, for example, (R)AN. For a description of network devices and terminal devices, please refer to the foregoing. Figure 1A The relevant descriptions will not be repeated here.

[0183] The core network involved in this application embodiment may include network devices that process and forward user signaling and data. Examples include core network devices such as mobility management entities, session management entities, and user plane gateways. Related details are as described above and will not be repeated here.

[0184] The embodiments of this application can also be applied to other communication system architectures, such as air-to-ground (ATG) communication systems. For example, please refer to... Figure 1E This is a schematic diagram of a network architecture for another communication system applicable to embodiments of this application. The communication system includes at least one network device and at least one high-altitude terminal device. Data forwarding between the network device and the high-altitude terminal device can also be achieved through relay devices. High-altitude terminal devices include, for example, high-altitude aircraft and onboard terminal devices.

[0185] Figure 2 An exemplary schematic diagram illustrates a possible scenario to which embodiments of this application are applicable.

[0186] Figure 2 (a) shows a schematic diagram of the scene at time t1. Figure 2(b) shows a schematic diagram of the scene at time t2. Time t2 is a time after time t1. For example, at time t1, the signal coverage area of ​​the first network device (e.g., RAN#1) includes / is the first region (e.g., region #1), and the signal coverage area of ​​the second network device (e.g., RAN#2) includes / is the region #2. For example, at time t2, the signal coverage area of ​​the first network device (e.g., RAN#1) includes / is the region #3, and the signal coverage area of ​​the second network device (e.g., RAN#2) includes / is the first region (e.g., region #1).

[0187] Network devices can establish user plane connections with user plane entities (such as UPF entities), and can also establish control plane connections with mobility management entities (such as AMF entities). For example Figure 2 In (a), the first network device establishes a control plane connection with the mobility management entity and a user plane connection with the user plane entity. The first region (e.g., region #1) may include at least one terminal device, such as UE #1 and UE #2. There is a correspondence (or association) between the first region and the tunnel information #1 of the network device.

[0188] At time t1, the first network device enables tunnel information #1 as its own tunnel information. This tunnel information can be used to transmit information about terminal devices in the first region (e.g., region #1) via a user plane connection between the first network device and a user plane entity. For example, the user plane entity sends message #1 to the first network device, and message #1 carries the tunnel information #1 of the first network device. After recognizing the tunnel information, the first network device determines that message #1 is a message from a terminal device in the first region, and then sends the information in message #1 to the terminal device in the first region.

[0189] As time progresses, the first network device and the second network device move. At time t2, the first network device no longer provides communication services to the terminal devices in the first area (e.g., area #1), and instead, the second network device provides communication services to the terminal devices in the first area (e.g., area #1). The second network device enables tunnel information #1 as its own tunnel information, which can be used to transmit information about the terminal devices in the first area (e.g., area #1) via a user plane connection between the second network device and the user plane entity. For example, the user plane entity sends message #2 to the second network device, and message #2 carries the tunnel information #1 of the first network device. After recognizing the tunnel information, the second network device determines that message #2 is a message from a terminal device in the first area, and then sends the information in message #2 to the terminal devices in the first area.

[0190] As can be seen from the above, although the network device providing services to the terminal device (e.g., UE#1) in the first area is updated from the first network device to the second network device, since the terminal device (e.g., UE#1) has not moved out of the first area, the tunnel information used by the first network device and the second network device to provide services to the terminal device (e.g., UE#1) in the first area remains the same and has not been updated. Therefore, there is no need to update the user plane information (e.g., user plane information on the base station side) of the terminal device (e.g., UE#1) via signaling, thereby reducing signaling overhead. For example, in a satellite-to-ground network, this scheme can reduce signaling interaction between the base station located on the satellite (e.g., gNB on board) and the core network device located on the ground (e.g., mobility management entity, session management entity, or user plane entity located on the ground), thereby saving resource overhead in the satellite-to-ground network.

[0191] In another possible implementation, for the connection of the control plane of the terminal device (e.g., UE#1) in the first region, the first region may have a correspondence (or association) with the second identifier #1 of UE#1 on the network device side.

[0192] At time t1, the first network device determines that the second identifier of UE#1 on the network device side is the second identifier #1. This second identifier #1 can be used to transmit information about UE#1 in the first area (e.g., area #1) via a control plane connection between the first network device and the mobility management entity. For example, the mobility management entity sends message #1 to the first network device, and message #1 carries the second identifier #1 of UE#1. After recognizing the second identifier #1, the first network device determines that message #1 is a message from UE#1 in the first area, and can then perform some management on UE#1 based on this message.

[0193] As time progresses, the first network device and the second network device move. At time t2, the first network device no longer provides communication services to terminal devices in the first area (e.g., area #1), and instead, the second network device provides communication services to terminal devices in the first area (e.g., area #1). The second network device determines that the second identifier of UE#1 on the network device side is still the second identifier #1. This second identifier #1 can be used to transmit information about UE#1 in the first area (e.g., area #1) via a control plane connection between the second network device and the mobility management entity. For example, the mobility management entity sends message #2 to the second network device, and message #2 carries the second identifier #1 of UE#1. After recognizing the second identifier #1, the second network device determines that message #2 is a message from UE#1 in the first area, and can then perform some management on UE#1 based on this message.

[0194] As can be seen from the above, although the network device providing services to the terminal device (e.g., UE#1) in the first area is updated from the first network device to the second network device, since the terminal device (e.g., UE#1) has not moved out of the first area, the second identifier of the terminal device on the control plane used by the first network device and the second network device to provide services to the terminal device (e.g., UE#1) in the first area is the same and has not been updated. Therefore, there is no need to update the control plane information (e.g., control plane information on the base station side) of the terminal device (e.g., UE#1) through signaling, thereby reducing signaling overhead. For example, in a satellite-to-ground network, this scheme can reduce signaling interaction between the base station located on the satellite (e.g., gNB on board) and the mobility management entity located on the ground (e.g., AMF on ground), thereby saving resource overhead in the satellite-to-ground network.

[0195] based on Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E and Figure 2 At least one of the contents shown in the above and the other contents mentioned above, Figure 3 An exemplary flowchart of a possible communication method provided in an embodiment of this application is shown. For ease of understanding, Figure 3 The interaction between the terminal device, the first network device, the mobility management entity, the session management entity, the user plane entity, and the second network device will be used as an example for introduction.

[0196] Terminal devices can be Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E and Figure 2 At least one of the terminal devices or chips (or chip systems, or circuits, or units, or modules) involved in the terminal device.

[0197] The first network device can be a network device or a chip (or chip system, circuit, module, or unit) within a network device. The second network device can be a network device or a chip (or chip system, circuit, module, or unit) within a network device. The network device may include, for example, […]. Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E and Figure 2The access network equipment involved in at least one of the above. For example, the first network device is a physical device, and the scheme executed on the first network device side can be implemented by a chip (or chip system, or circuit, or module, or unit) inside the first network device. For example, the second network device is a physical device, and the scheme executed on the second network device side can be implemented by a chip (or chip system, or circuit, or module, or unit) inside the second network device.

[0198] The solution provided in this application can be applied to NTN communication systems. For example, the network device is an NTN device. Another example is that some functions of the network device are deployed on the NTN device, and some functions are deployed on ground equipment. For example, the NTN device can include / be replaced by a device at a certain altitude relative to the ground-deployed device. Another example is that the NTN device can include / be replaced by a non-ground-based device. Yet another example is that the NTN device can include / be replaced by a satellite, drone, high-altitude platform, aircraft, etc. For example, when the NTN device is a satellite, the satellite can operate in regenerative mode. Yet another example is that the NTN device can include IAB, or NCR, or WAB, etc. In yet another possible implementation, the network device is a ground-deployed device, and the terminal device is an airborne NTN device.

[0199] For example, a mobility management entity can be Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E and Figure 2 The device or chip (or chip system, circuit, unit, or module) within the device that implements the functions of the mobility management entity, including at least one of the above. For example, the mobility management entity is a physical device, and the scheme executed on the mobility management entity side can be implemented by a chip (or chip system, circuit, module, or unit) within the mobility management entity.

[0200] For example, the session management entity can be Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E and Figure 2The device or chip (or chip system, circuit, unit, or module) within the device that implements the functions of the session management entity, involving at least one of the above. For example, the session management entity is a physical device, and the scheme executed on the session management entity side can be implemented by a chip (or chip system, circuit, module, or unit) within the session management entity. For ease of description, some parts of this application may also refer to the mobility management entity and / or session management entity as a first device. In this application, for ease of description, some parts refer to the mobility management entity and / or session management entity as a first device.

[0201] For example, a user-facing entity can be Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E and Figure 2 The device or chip (or chip system, circuit, unit, or module) within the device that implements the functionality of the user plane entity, including at least one of the above. For example, the user plane entity is a physical device, and the scheme executed on the user plane entity side can be implemented by a chip (or chip system, circuit, module, or unit) within the user plane entity.

[0202] Mobility management entities, session management entities, and user plane entities can belong to core network devices. The functions of any one of the mobility management entities, session management entities, or user plane entities can be: deployed on terrestrial equipment; deployed on NTN equipment; or have some functions deployed on NTN equipment and some functions deployed on terrestrial equipment.

[0203] The following is combined with Figure 3 To introduce, for example Figure 3 The method shown includes steps 301, 302, 303 and 304.

[0204] Step 301: The first network device acquires the first tunnel information.

[0205] The first tunnel information is determined based on the correspondence between the first area and the first tunnel information.

[0206] In this application embodiment, at least one region can be defined, and a first region belongs to the at least one region. For example, the first region is one of the at least one regions. For example, the first region may include / be at least one of the following: a geographical region, an administrative region, a location (e.g., at least one designated location), a beam (or a beam) coverage area, a signal (or a beam) coverage area, a cell (or a cell), or a tracking area (TA). As another example, the first region includes at least one terminal device located in the first region, and the first terminal device may belong to the at least one terminal device. For example, the first region may include / be replaced by: the location of the first terminal device, or replaced by the area where the location of the first terminal device is located (or the corresponding area). For example, the first region belongs to the signal coverage area of ​​a first network device. The signal coverage area of ​​the first network device may also include / be replaced by: the cell or TA of the first network device, the beam coverage area of ​​the first network device, etc.

[0207] The first network device may include one or more tunnel information, where the first tunnel information is one of the tunnel information of the first network device. The first tunnel information may also be referred to as the tunnel information of the first network device, or simply the tunnel information of the network device. The first tunnel information may also include / be replaced by RAN tunnel information. In the embodiments of this application, the first tunnel information may be replaced with other names; please refer to the foregoing description of tunnel information, which will not be repeated here. The tunnel information of the first network device can be used to transmit terminal device information between the first network device and a user plane entity. For example, the first tunnel information of the first network device can be used to transmit information of at least one terminal device in a first region between the first network device and a user plane entity. For example, the first tunnel information may include at least one of the following: the first network device's Internet Protocol (IP) address (e.g., RAN IP), or a Tunnel Endpoint Identification (TEID).

[0208] For example, the tunnel information of the first network device can have a correspondence with a region. For instance, a region can correspond to one tunnel information of the first network device. Or, for example, one tunnel information of the first network device can correspond to a region. For example, a first region corresponds to the first tunnel information of the first network device. A region can include one terminal device or multiple terminal devices. For instance, the first terminal device is a terminal device included in the first region, or the first terminal device is located in the first region. The first network device can use the first tunnel information to transmit information corresponding to the terminal devices in the first region (e.g., uplink and / or downlink information). Or, for instance, the first region includes a first terminal device and a second terminal device. The tunnel information of the first network device corresponding to both the first and second terminal devices is the same first tunnel information, meaning that the tunnel information of the first network device corresponding to multiple terminal devices in the first region is the same. The first network device can use the first tunnel information to transmit information corresponding to both the first and second terminal devices (e.g., uplink and / or downlink information).

[0209] Figure 4 An exemplary schematic diagram illustrates a possible correspondence between area and network device tunnel information. For example... Figure 4 As shown, region #A corresponds to tunnel information #A, which includes RAN IP #A and TEID #A. Network device #A, providing communication services to terminal devices in region #A, uses RAN IP #A and TEID #A as its tunnel information. Similarly, region #B corresponds to tunnel information #B, and network device #B, providing communication services to terminal devices in region #B, uses RAN IP #B and TEID #B as its tunnel information. Region #C corresponds to tunnel information #C, and network device #C, providing communication services to terminal devices in region #C, uses RAN IP #C and TEID #C as its tunnel information. Region #D corresponds to tunnel information #D, and network device #D, providing communication services to terminal devices in region #D, uses RAN IP #D and TEID #D as its tunnel information. The first network device can be any one of network device #A, network device #B, network device #C, or network device #D.

[0210] The signal coverage area of ​​the first network device may include one area or multiple areas. The first area is one of the signal coverage areas of the first network device. For example, the first network device enables one beam, and the coverage area of ​​that beam is the first area. In the embodiments of this application, the coverage area of ​​one beam can be understood as the coverage area of ​​the signal transmitted through that beam. For another example, the first network device enables multiple beams, such as two beams, beam #1 and beam #2. Beam #1 covers area #1, and beam #2 covers area #2. Area #1 may correspond to tunnel information #1 of the first network device, and area #2 may correspond to tunnel information #2 of the first network device. The first area can be either area #1 or area #2. Taking area #1 as the first area as an example, the first tunnel information can be tunnel information #1. Area #1 and area #2 may partially overlap or not overlap at all. If area #1 and area #2 are two different areas, then the tunnel information #1 and tunnel information #2 of the first network device will also be different. The first network device can use tunnel information #1 to transmit information corresponding to the terminal device in area #1 (e.g., uplink and / or downlink information), and the first network device can use tunnel information #2 to transmit information corresponding to the terminal device in area #2 (e.g., uplink and / or downlink information).

[0211] In step 301, the first network device can obtain the first tunnel information in several ways. Several possible implementation methods are exemplarily described below through implementation methods A1 and A2. In implementation method A1, the first network device can find the first tunnel information based on the correspondence between the first region and the first tunnel information. In implementation method A2, the first network device can receive first tunnel information from other devices.

[0212] In implementation method A1, the first network device finds the first tunnel information based on the correspondence between the first region and the first tunnel information.

[0213] For example, the first network device can obtain the correspondence between the first area and the first tunnel information before determining the first tunnel information. For example, the correspondence between the first area and the first tunnel information can be configured (e.g., pre-configured) on the first network device side. In this embodiment, the configuration can also include / be replaced by: allocation, assign, or configure. Alternatively, other network devices, mobility management entities, session management entities, user plane entities, or other devices besides the first network device can send information indicating the correspondence between the first area and the first tunnel information to the first network device.

[0214] For example, the first network device receives information indicating the location of the first terminal device. The information indicating the location of the first terminal device includes information about the location of the first terminal device and / or information about a first region. The first network device determines the first tunnel information based on the information indicating the location of the first terminal device and the correspondence between the first region and the first tunnel information. Alternatively, the first network device determines the first tunnel information based on the correspondence between the location of the first terminal device and the first tunnel information.

[0215] For example, if the information used to indicate the location of the first terminal device includes the location information of the first terminal device, the first network device can determine the region to which the first terminal device belongs, such as the first region, based on the location of the first terminal device. As another example, if the information used to indicate the location of the first terminal device includes information about the first region, the first network device can determine that the first terminal device belongs to the first region based on this information. Further, the first network device, based on the correspondence between the first region and the first tunnel information, finds the tunnel information corresponding to the first region as the first tunnel information. Then, the first network device uses the first tunnel information as the tunnel information used by the first network device when transmitting information about the terminal device in the first region between the first network device and the user plane entity. For example, if the signal of the first network device's beam #1 needs to cover region #1, and the first network device stores the correspondence between region #1 and tunnel information #1, then the first network device determines to enable tunnel information #1, and the first network device uses tunnel information #1 to transmit information about the terminal device in the first region between the first network device and the user plane entity.

[0216] In this embodiment, the first region can also be replaced by a location, etc. Therefore, the correspondence between the first region and the first tunnel information can also be replaced by the correspondence between the first location and the first tunnel information. The first location can include / be the current location of the first terminal device, or a location where the distance between the first terminal device and its current location is less than a distance threshold. In this embodiment, the device used to determine the first tunnel information (e.g., a first network device, a mobility management entity, a session management entity, or a user plane entity, etc.) can determine the first tunnel information based on the correspondence between the first region and the first tunnel information, or based on the correspondence between the location of the first terminal device (e.g., the first location) and the first tunnel information. That is, the step of determining the first region based on the first terminal device can be executed or not. If not executed, the location (or current location) of the first terminal device can be directly regarded as the first region.

[0217] In one possible implementation, the first network device may also send first tunnel information to other devices. Several possible examples are described below using Examples A1.1, A1.2, A1.3, and A1.4. In Example A1.1, the first network device may send the first tunnel information to a second network device. In Example A1.2, the first network device may send the first tunnel information to a mobility management entity. In Example A1.3, the first network device may send the first tunnel information to a session management entity. In Example A1.4, the first network device may send the first tunnel information to a user plane entity. In any of these examples, the first tunnel information sent by the first network device may be carried in an N2 message, an N3 message transmission process, or an NG establishment request message, etc., thus achieving greater compatibility with existing technologies.

[0218] Example A1.1: The first network device can send first tunnel information to the second network device.

[0219] The first tunnel information can be transmitted through the Xn interface between network devices, or it can be forwarded through other devices. For example, the first network device and the second network device can transmit the first tunnel information through the Xn interface, or the first tunnel information can be forwarded through core network devices (such as mobility management entities, session management entities, or user plane entities).

[0220] For example, the first network device (e.g., satellite #1) will (or has) left the airspace above the first area and will (or has) been unable to provide communication services to the first area. The second network device (e.g., satellite #2) will (or has) moved to the airspace above the first area and will (or has) been providing communication services to terminal devices in the first area.

[0221] In this embodiment of the application, the provision of communication services by the first network device (or the second network device) for the first area may include / be replaced by: the beam coverage area (or signal coverage area, or cell) of the first network device (or the second network device) including / being the first area. The inability of the first network device (or the second network device) to provide communication services for the first area may include / be replaced by: the beam coverage area (or signal coverage area, or cell) of the first network device (or the second network device) not including / being the first area.

[0222] In this example, the first network device can be the source network device of the first terminal device, and the second network device can be the target network device of the first terminal device. A terminal device in a first region (e.g., the first terminal device) switches from the first network device to the second network device, and the signal coverage area of ​​the second network device includes / is the first region. In this scenario, the first network device sends first tunnel information corresponding to the first region to the second network device, enabling the second network device to continue using the first tunnel information as its own tunnel information. For example, the second network device uses this first tunnel information to transmit information about the terminal device in the first region (e.g., the first terminal device) between itself and a user plane entity.

[0223] For another example, region #1 corresponds to 100 NTN tunnel information entries. The first network device allocates 100 tunnel information entries to 100 UEs in region #1, with one UE corresponding to one tunnel information entry, and one tunnel information entry corresponding to one UE. These tunnel information entries can be at the region-level granularity. The first network device can send the correspondence between the 100 terminal devices and the 100 tunnel information entries to the second network device, so as to inform the second network device which UE each tunnel information entry has been assigned to. In another possible implementation, the second network device can, similar to the first network device, enable the first tunnel information itself, or have the first tunnel information sent to it by other devices such as the AMF. The workflow is similar to that of the first network device and can be used interchangeably, so it will not be described in detail here.

[0224] It can be seen that although the network device providing services to the terminal devices in the first area is updated to the second network device, the tunnel information of the second network device remains the same as the first tunnel information corresponding to the first area used by the first network device, and has not been updated. Therefore, the second network device does not need to announce its tunnel information to the user plane entity via signaling. The user plane entity has already obtained the first tunnel information of the first area, and continues to use the previously obtained first tunnel information to transmit information about the terminal devices in the first area with the second network device. This scheme can save signaling overhead.

[0225] Example A1.2: The first network device may send first tunneling information to the mobility management entity.

[0226] The first network device can send first tunnel information to the mobility management entity via a link (e.g., a control plane link) between itself and the mobility management entity. After obtaining the first tunnel information, the mobility management entity can send it to a user plane entity so that the user plane entity can obtain the first tunnel information from the first network device. The user plane entity then sends information about the terminal device in the first area to the first network device based on the first tunnel information.

[0227] Sending the first tunnel information from the mobility management entity to the user plane entity may include, for example, the mobility management entity sending the first tunnel information to the session management entity, and the session management entity sending the first tunnel information to the user plane entity. Alternatively, the mobility management entity may send the first tunnel information to the user plane entity through other links between the mobility management entity and the user plane entity.

[0228] Example A1.3: The first network device may send first tunnel information to the session management entity.

[0229] The first network device can send first tunnel information to the session management entity via the link between the first network device and the session management entity. For example, the first network device sends the first tunnel information to the mobility management entity, and the mobility management entity sends the first tunnel information to the session management entity. Alternatively, the first network device can send the first tunnel information to the session management entity via other links between the first network device and the session management entity.

[0230] After obtaining the first tunnel information, the session management entity can send the first tunnel information to the user plane entity so that the user plane entity can obtain the first tunnel information of the first network device, and then send the terminal device information of the first area to the first network device based on the first tunnel information of the first network device.

[0231] Sending first tunnel information from the session management entity to the user plane entity may include, for example, sending the first tunnel information from the session management entity to the user plane entity through the link between the session management entity and the user plane entity.

[0232] Example A1.4: The first network device can send first tunnel information to the user plane entity.

[0233] For example, the first network device sends the first tunnel information to the mobility management entity, the mobility management entity sends the first tunnel information to the session management entity, and the session management entity sends the first tunnel information to the user plane entity.

[0234] For example, the first network device sends first tunnel information to the user plane entity through other links between the first network device and the user plane entity. For instance, the first network device receives information from a terminal device (e.g., the first terminal device or other terminal devices) in a first region. The first network device can re-encapsulate this information (e.g., according to the transmission protocol between the first network device and the user plane entity), such as by adding a header, to obtain a third message. The message in this embodiment can also include / be replaced with a message or information. The third message may include, for example, a header and a payload, the payload of which may include information from the terminal device (this information may include, for example, service data, control signaling, etc.). The third message includes tunnel information of the user plane entity and first tunnel information. For example, the header of the third message may carry the tunnel information of the user plane entity. The first network device sends the third message to the user plane entity. After obtaining the first tunnel information from the first network device, the user plane entity can establish a downlink tunnel from the user plane entity to the first network device.

[0235] In this scheme, the third message can be a message transmitted through an established uplink tunnel (e.g., the tunnel from the first network device to the user plane entity, also known as a user plane connection). This scheme establishes the downlink tunnel during the use of the uplink tunnel, merging the downlink tunnel establishment process and the uplink tunnel usage process (or uplink message transmission process) into a single process, thereby saving signaling overhead. Optionally, in this scheme, the user plane entity can send the first tunnel information carried in the third message to the session management entity. The first tunnel information carried in the third message can also be replaced with: first area and first tunnel information, or later, the correspondence between the first area and the first tunnel information.

[0236] In another possible implementation, the mobility management entity acquires the first information and then sends the first information. For example, the session management entity acquires the first information and then sends the first information.

[0237] In this embodiment of the application, the first information includes at least one of the following: location information of the first terminal device, information of the first area, or first tunnel information. For example, the first information is used to indicate first tunnel information. The first information used to indicate first tunnel information may include / be replaced by: the first information may be used to determine first tunnel information.

[0238] In another possible implementation, the mobility management entity or session management entity may also acquire second information and determine the first information based on the second information. The first information is determined based on the second information. For example, the second information includes at least one of the following: information about the location of the first terminal device, information about a first area, or information about a first tunnel.

[0239] In implementation A1, the second information may be the first tunnel information, and the first information may include the first tunnel information. The mobility management entity receives the first tunnel information from the first network device and sends the first tunnel information to the session management entity.

[0240] For example, the first information is the location information of the first terminal device. The mobility management entity determines a first region based on the location information of the first terminal device, that is, the first terminal device is located in the first region. The mobility management entity sends the first region to the session management entity, and the session management entity determines the corresponding second information, that is, the first tunnel information, based on the first region. In this method, the mobility management entity is configured with regions corresponding to the tunnel information, such as configuring a first region, a second region, etc. The mobility management entity determines the corresponding region based on the location; the session management entity configures the correspondence between regions and tunnel information, including the correspondence between the first region and the first tunnel information.

[0241] For example, the second information can be the first tunnel information, and the first information can include the first tunnel information. The session management entity receives the first tunnel information from the mobility management entity and sends the first tunnel information to the user plane entity.

[0242] In implementation method A2, the first network device receives first tunnel information from other devices.

[0243] The first tunnel information received by the first network device can be carried in an N2 message, a message transmitted on N3, or a next generation (NG) establishment request message, etc. This makes it more compatible with existing technologies. Several possible examples are described below using Examples A2.1, A2.2, A2.3, and A2.4. In these examples, the first network device can receive first tunnel information from other network devices, mobility management entities, session management entities, or user plane entities, respectively.

[0244] Example A2.1: A first network device receives first tunnel information from another network device (e.g., a fourth network device).

[0245] For example, the first tunnel information is carried in the N2 message. The first tunnel information can be transmitted via the Xn interface between network devices, or it can be forwarded by other devices. For example, the first network device and the fourth network device can transmit the first tunnel information via the Xn interface, or the first tunnel information can be forwarded by core network devices (such as mobility management entities, session management entities, or user plane entities). The scheme for the fourth network device to obtain the first tunnel information is the same as the scheme for the first network device to obtain the first tunnel information, and will not be described again.

[0246] For example, a fourth network device (e.g., satellite #3) will (or has) leave the airspace above the first area and will (or has) be unable to provide communication services to the first area. A first network device (e.g., satellite #1) will (or has) move to the airspace above the first area and will (or has) provide communication services to the terminal devices in the first area. In this example, the fourth network device can be the source network device of the first terminal device, and the first network device can be the target network device of the first terminal device. The terminal devices in the first area (e.g., the first terminal device) switch from the fourth network device to the first network device. In this scenario, the fourth network device sends the first tunnel information corresponding to the first area to the first network device, which allows the first network device to continue using the first tunnel information as its tunnel information. The content of this example can also be found in the description of the aforementioned example A1.1, and the scheme by which the fourth network device obtains the first tunnel information can also be found in the method by which the first network device obtains the first tunnel information in the embodiments of this application, and will not be described again.

[0247] It can be seen that although the network device providing services to the terminal devices in the first area has been updated from the fourth network device to the first network device, the tunnel information of the first network device remains the same as the first tunnel information corresponding to the first area used by the fourth network device, and has not been updated. Therefore, the first network device does not need to announce its tunnel information to the user plane entity via signaling. The user plane entity has already obtained the first tunnel information of the first area, and continues to use the previously obtained first tunnel information to transmit information about the terminal devices in the first area with the first network device. It can be seen that this scheme can save signaling overhead.

[0248] Example A2.2: The first network device may receive first tunneling information from the mobility management entity.

[0249] For example, a mobility management entity can send first tunnel information to a first network device through a link between the first network device and the mobility management entity.

[0250] For example, the mobility management entity obtains the location information of the first terminal device. In this embodiment, the location information of the first terminal device is used to determine the first tunnel information. The mobility management entity determines the first tunnel information based on the received location information of the first terminal device. For example, the mobility management entity determines that the signal coverage area of ​​the first network device includes / is a first region. The mobility management entity determines (or finds) the first tunnel information based on the correspondence between the first region and the first tunnel information. The mobility management entity sends the first tunnel information to the first network device. Alternatively, the mobility management entity determines the first tunnel information based on the correspondence between the location of the first terminal device and the first tunnel information.

[0251] In this embodiment of the application, the location information of the first terminal device may include, for example, at least one of: cell identifier, beam identifier, geographic location, base station identifier, or TA.

[0252] There are multiple ways for the mobility management entity to obtain the location information of the first terminal device.

[0253] For example, the first network device obtains location information of the first terminal device. The first network device then sends the location information of the first terminal device to the mobility management entity.

[0254] For example, the mobility management entity receives location measurement results and determines the location information of the first terminal device based on the location measurement results. Alternatively, the mobility management entity initiates a location process and receives location measurement results from the terminal device, a base station, or other devices.

[0255] In this embodiment, the location information of the first terminal device reported by the first network device may be insufficient to determine the first tunnel information due to certain reasons (such as insufficient accuracy). In this case, devices that need to use the location information of the first terminal device can obtain the location information of the first terminal device through other means. That is to say, it is not mandatory for the first network device to report the location information of the first terminal device.

[0256] In one possible implementation, the mobility management entity acquires first information and then sends the first information. Alternatively, the mobility management entity may acquire second information and determine the first information based on the second information.

[0257] In another possible implementation, the session management entity acquires the first information and then sends the first information. Alternatively, the session management entity may acquire second information and determine the first information based on the second information.

[0258] The contents of the first and second information can be found in the foregoing description and will not be repeated here.

[0259] In Example A2.2, for example, the second information may be the location information of the first terminal device, and the first information may include first tunnel information. The mobility management entity receives the location information of the first terminal device from the first network device or other devices, and sends the first tunnel information to the session management entity.

[0260] Example A2.3: The first network device may receive first tunnel information from the session management entity.

[0261] For example, the session management entity can send first tunnel information to the first network device through the link between the session management entity and the first network device. For example, the session management entity sends the first tunnel information to the mobility management entity, and the mobility management entity sends the first tunnel information to the first network device.

[0262] For example, the session management entity can send the first tunnel information and the tunnel information of the user plane entity in a single message, thereby saving signaling overhead.

[0263] For example, the mobility management entity obtains the location information of a first terminal device. The mobility management entity determines that the signal coverage area of ​​the first network device includes / is a first area. The mobility management entity sends the information of the first area to the session management entity. The session management entity determines (or finds) the first tunnel information based on the correspondence between the first area and the first tunnel information. The session management entity sends the first tunnel information to the first network device. Alternatively, the session management entity determines the first tunnel information based on the correspondence between the location of the first terminal device and the first tunnel information.

[0264] For another example, the session management entity obtains the location information of the first terminal device. Based on the received location information, the session management entity determines the first tunnel information. For instance, the session management entity determines that the signal coverage area of ​​the first network device includes / is a first region. Based on the correspondence between the first region and the first tunnel information, the session management entity determines (or finds) the first tunnel information. The session management entity then sends the first tunnel information to the first network device.

[0265] There are several ways for the session management entity to obtain the location information of the first terminal device.

[0266] For example, the first network device obtains the location information of the first terminal device. The first network device sends the location information of the first terminal device to the session management entity.

[0267] For example, the mobility management entity obtains the location information of the first terminal device, and then sends the location information of the first terminal device to the session management entity. The method by which the mobility management entity obtains the location information of the first terminal device is as described above and will not be repeated here.

[0268] For example, the session management entity obtains the location information of the first terminal device. The session management entity receives the location measurement results and determines the location of the first terminal device based on these results. Alternatively, the mobility management entity initiates a location process, receives location measurement results from the terminal device, a base station, or other devices, and sends these results to the session management entity. Or, the session management entity initiates a location process and receives location measurement results from the terminal device or a base station.

[0269] In one possible implementation, the mobility management entity acquires first information and sends the first information. In another possible implementation, the mobility management entity may also acquire second information and determine the first information based on the second information.

[0270] In one possible implementation, the session management entity acquires first information and sends the first information. In another possible implementation, the session management entity may also acquire second information and determine the first information based on the second information.

[0271] The contents of the first and second information can be found in the foregoing description and will not be repeated here.

[0272] In Example A2.3, for example, the second information may be the location information of the first terminal device, and the first information may include information about a first region. The mobility management entity receives the location information of the first terminal device from the first network device or other devices, and sends the information about the first region to the session management entity.

[0273] For example, the second information can be information about the first area, and the first information can include first tunnel information. The session management entity receives the information about the first area from the mobility management entity and sends the first tunnel information to the user plane entity.

[0274] Example A2.4: The first network device can receive first tunnel information from a user plane entity.

[0275] For example, the user plane entity sends the first tunnel information to the session management entity, the session management entity sends the first tunnel information to the mobility management entity, and the mobility management entity sends the first tunnel information to the first network device.

[0276] For example, a user plane entity can send the first tunnel information and the user plane entity's tunnel information together in a single message, thereby saving signaling overhead.

[0277] For example, a session management entity or other device (such as a mobility management entity) obtains the first tunnel information and sends it to a user plane entity. The user plane entity receives the first tunnel information and then sends it to a first network device. The method by which the session management entity or other device (such as a mobility management entity) obtains the first tunnel information is described above and will not be repeated here.

[0278] For another example, the user plane entity obtains the location information of the first terminal device. The user plane entity determines that the signal coverage area of ​​the first network device includes / is a first region. The user plane entity determines (or finds) the first tunnel information based on the correspondence between the first region and the first tunnel information. The user plane entity sends the first tunnel information to the first network device. Alternatively, the user plane entity determines the first tunnel information based on the correspondence between the location of the first terminal device and the first tunnel information.

[0279] There are multiple ways for a user entity to obtain the location information of the first terminal device.

[0280] For example, the first network device obtains the location information of the first terminal device. The first network device sends the location information of the first terminal device to the user plane entity.

[0281] For example, the mobility management entity or session management entity obtains the location information of the first terminal device, and then sends the location information of the first terminal device to the user plane entity. The method by which the mobility management entity or session management entity obtains the location information of the first terminal device is described above and will not be repeated here.

[0282] For example, the user plane entity obtains the location information of the first terminal device. The user plane entity receives the location measurement results and determines the location information of the first terminal device based on the location measurement results. Alternatively, the mobility management entity initiates a location procedure and receives location measurement results from the terminal device, a base station, or other devices, and sends the location measurement results to the session management entity, which then sends the location measurement results to the user plane entity. Or, the user plane entity initiates a location procedure and receives location measurement results from the terminal device or a base station.

[0283] In one possible implementation, the mobility management entity acquires first information and then sends the first information. Alternatively, the mobility management entity may acquire second information and determine the first information based on the second information.

[0284] In another possible implementation, the session management entity acquires the first information and then sends the first information. Alternatively, the session management entity may acquire second information and determine the first information based on the second information.

[0285] The contents of the first and second information can be found in the foregoing description and will not be repeated here.

[0286] In implementation A2, the first network device may also inform other devices (mobility management entity, session management entity, user plane entity, or other network devices) whether it has obtained tunnel information through some means. In this way, when other devices (mobility management entity, session management entity, user plane entity, or other network devices) know that the first network device has obtained the first tunnel information, they can stop sending the first tunnel information to the first network device, thereby saving signaling overhead.

[0287] For example, before acquiring the first tunnel information, the first network device sends a first indication message to other devices (mobility management entity, session management entity, user plane entity, or other network devices). Correspondingly, the other devices (mobility management entity, session management entity, user plane entity, or other network devices) receive the first indication message. The first indication message indicates that the first network device has not acquired the tunnel information of the first network device. If the other devices (mobility management entity, session management entity, user plane entity, or other network devices) receive the first indication message within a specified time period or on a specified signaling, they then send the first tunnel information to the first network device. Alternatively, if the other devices (mobility management entity, session management entity, user plane entity, or other network devices) do not receive the first indication message within a specified time period or on a specified signaling, they may not send the first tunnel information to the first network device, thereby saving signaling overhead.

[0288] For example, after obtaining the first tunnel information, the first network device sends a second instruction to other devices (mobility management entity, session management entity, user plane entity, or other network devices). Correspondingly, the other devices (mobility management entity, session management entity, user plane entity, or other network devices) receive the second instruction and determine, based on the second instruction, that they do not need to send the first tunnel information to the first network device, thereby saving signaling overhead. For example, if other devices (mobility management entity, session management entity, user plane entity, or other network devices) do not receive the second instruction within a specified time period or on specified signaling, they can determine that the first network device has not received the first tunnel information and can then send the first tunnel information to the first network device.

[0289] For example, other devices (mobility management entity, session management entity, user plane entity, or other network devices) can determine whether the first tunnel information has been sent to the first network device based on the saved context information, and then determine whether the first network device has obtained the first tunnel information based on the information (for example, if the session management entity has sent the first tunnel information to the first network device, it is determined that the first network device has obtained the first tunnel information; otherwise, it is determined that the first network device has not obtained the first tunnel information), and then determine whether it is necessary to send the first tunnel information to the first network device based on this.

[0290] Step 302: The user face entity obtains the first tunnel information.

[0291] There is no absolute order between step 302 and the aforementioned step 301. Step 301 can be executed first, followed by step 302, or vice versa. In step 302, the user face entity can obtain the first tunnel information in several ways.

[0292] Several possible implementations are exemplified below using implementations B1 and B2. In implementation B1, the user plane entity can receive first tunnel information from other devices. In implementation B2, the user plane entity can locate the first tunnel information based on the correspondence between the first region and the first tunnel information.

[0293] In implementation B1, the user plane entity receives first tunneling information from other devices.

[0294] The first tunnel information received by the first network device can be carried in an N2 message, or a message transmitted on N3, or an NG establishment request message, etc.

[0295] The following examples, B1.1, B1.2, and B1.3, illustrate several possible scenarios in which the user plane entity may receive first tunneling information from a first network device, a session management entity, or a mobility management entity, respectively.

[0296] Example B1.1: The user plane entity receives first tunnel information from the first network device.

[0297] For example, the first network device sends the first tunnel information to the mobility management entity, the mobility management entity sends the first tunnel information to the session management entity, and the session management entity sends the first tunnel information to the user plane entity.

[0298] For example, the first network device sends first tunnel information to the user plane entity through other links between the first network device and the user plane entity. For instance, the first network device receives information from a terminal device in the first area (e.g., the first terminal device or other terminal devices). The first network device can re-encapsulate this information, for example, by adding a header, to obtain a third message. The third message includes the tunnel information of the user plane entity and the first tunnel information. The first network device sends the third message to the user plane entity. After the user plane entity obtains the first tunnel information from the first network device, it can establish a downlink tunnel from the user plane entity to the first network device. In this scheme, the third message can be a message transmitted through an already established uplink tunnel (e.g., the tunnel from the first network device to the user plane entity). In this scheme, the downlink tunnel is established during the use of the uplink tunnel, merging the downlink tunnel establishment process and the uplink tunnel usage process (or the uplink message transmission process) into one process, thereby saving signaling overhead. This example can be found in the relevant content of the first network device sending first tunnel information to the user plane entity in Example A1.4 above, and will not be repeated here.

[0299] In Example B1.2, the user plane entity can receive first tunneling information from the session management entity.

[0300] For example, the session management entity can send the first tunnel information to the user plane entity through the link between the user plane entity and the session management entity.

[0301] For example, the mobility management entity obtains the location information of the first terminal device. The mobility management entity determines that the signal coverage area of ​​the first network device includes / is a first area. The mobility management entity sends the information of the first area to the session management entity. The session management entity determines (or finds) the first tunnel information based on the correspondence between the first area and the first tunnel information. The session management entity sends the first tunnel information to the user plane entity.

[0302] For another example, the session management entity obtains the location information of the first terminal device. Based on the received location information, the session management entity determines the first tunnel information. For instance, the session management entity determines that the signal coverage area of ​​the first network device includes / is a first region. Based on the correspondence between the first region and the first tunnel information, the session management entity determines (or finds) the first tunnel information. The session management entity then sends the first tunnel information to the user plane entity.

[0303] There are several ways for the session management entity to obtain the location information of the first terminal device, which can be found in the above description and will not be repeated here.

[0304] In Example B1.3, the user plane entity can receive first tunneling information from the mobility management entity.

[0305] For example, the mobility management entity can send the first tunnel information to the user plane entity via the link between the user plane entity and the mobility management entity. For instance, the mobility management entity sends the first tunnel information to the session management entity, which then sends it to the user plane entity. Alternatively, the mobility management entity can send the first tunnel information to the user plane entity via a direct link between the mobility management entity and the user plane entity.

[0306] For example, the mobility management entity obtains the location information of the first terminal device. In this embodiment, the location information of the first terminal device is used to determine the first tunnel information. The mobility management entity determines the first tunnel information based on the received location information of the first terminal device. For example, the mobility management entity determines that the signal coverage area of ​​the first network device includes / is a first region. The mobility management entity determines (or finds) the first tunnel information based on the correspondence between the first region and the first tunnel information. The mobility management entity sends the first tunnel information to the user plane entity.

[0307] There are several ways for the mobility management entity to obtain the location information of the first terminal device, as described above, and will not be repeated here.

[0308] In implementation method B2, the user face entity finds the first tunnel information based on the correspondence between the first region and the first tunnel information.

[0309] For example, a user plane entity can obtain the correspondence between a first area and the first tunnel information before determining the first tunnel information. For example, the correspondence between the first area and the first tunnel information can be configured (e.g., pre-configured) on the user plane entity's side, or it can be sent to the user plane entity by other devices. For example, a first network device, mobility management entity, session management entity, or user plane entity or other devices send information to the user plane entity indicating the correspondence between the first area and the first tunnel information.

[0310] For example, the user plane entity receives information indicating the location of the first terminal device. This information includes the location of the first terminal device and / or information about a first region. The user plane entity determines the first tunnel information based on the information indicating the location of the first terminal device and the correspondence between the first region and the first tunnel information.

[0311] For example, if the information used to indicate the location of the first terminal device includes the location information of the first terminal device, the user plane entity can determine the region to which the first terminal device belongs, such as the first region, based on the location of the first terminal device. As another example, if the information used to indicate the location of the first terminal device includes information about the first region, the user plane entity can determine that the first terminal device belongs to the first region based on this information. Further, the user plane entity, based on the correspondence between the first region and the first tunnel information, finds the tunnel information corresponding to the first region as the first tunnel information. Then, the user plane entity uses the first tunnel information as the tunnel information used by the first network device when transmitting information about the terminal device in the first region between the first network device and the user plane entity. For example, the user plane entity stores a correspondence between region #1 and tunnel information #1. The user plane entity determines that tunnel information #1 is the tunnel information of the first network device, and the user plane entity determines that tunnel information #1 is the tunnel information of the first network device when transmitting information about the terminal device in the first region between the user plane entity and the first network device.

[0312] In one possible implementation, the user plane entity can also send the first tunnel information to other devices. For example, the user plane entity sends the first tunnel information to a session management entity, the session management entity sends the first tunnel information to a mobility management entity, and the mobility management entity sends the first tunnel information to a first network device. Alternatively, the user plane entity can carry the first tunnel information and its own tunnel information in a single message, thereby saving signaling overhead. The first tunnel information sent by the first network device can be carried in an N2 message, a message transmitted on N3, or an NG establishment request message, etc.

[0313] Step 303: The user plane entity sends a first message to the first network device.

[0314] Correspondingly, the first network device receives the first message from the user plane entity.

[0315] The first message includes first tunnel information. For example, the first network device can receive the first message based on the first tunnel information. For example, the first network device can identify whether the message is a message it needs to receive based on the tunnel information in the received message. For example, if the first network device determines that the tunnel information of the network device in the first message is the tunnel information of the first network device (e.g., the first tunnel information), then it determines that the message is a message it needs to receive. Or, if the first network device determines that the tunnel information of the network device in the first message is not the tunnel information of the first network device (e.g., the first tunnel information), then it determines that the message is not a message it needs to receive, and can discard the message or not perform any further processing on the message.

[0316] Step 304: The first network device sends the information in the first message to the first terminal device located in the first area.

[0317] In this application embodiment, the packet may also include / be replaced with a message or information, etc. The first packet may, for example, include a packet header and a payload. The payload may include information about the first terminal device (or information to be sent to the terminal device), such as service data, control signaling, etc., of the first terminal device. In this application embodiment, the information in the first packet sent by the first network device includes / is / means that: the first network device can process the received first packet, for example, re-encapsulate the information in the payload of the first packet according to the air interface protocol between the first network device and the first terminal device, and then send the re-encapsulated information to the first terminal device through the air interface.

[0318] In this embodiment of the application, the information of the terminal device (e.g., the information of the first terminal device) transmitted between the first network device and the user plane entity may include the service data, control signaling, and other content of the terminal device (e.g., the first terminal device).

[0319] In another possible implementation, the first network device may further receive tunnel information from a user plane entity corresponding to a first area of ​​a session management entity, user plane entity, or mobility management entity. The first network device sends a fourth message to the user plane entity based on the tunnel information of the user plane entity corresponding to the first area and a first identifier of the first terminal device. The fourth message includes the tunnel information of the user plane entity and the first identifier of the first terminal device. Thus, the UPF can obtain the first identifier and then send a message based on the UPF's tunnel information and the first identifier, so that the first network device can identify which terminal device the information in the received message belongs to. For example, the tunnel information enabled by the user plane entity can also be area-associated. For example, the first area may be associated with tunnel information #1 of the user plane entity, and the second area may be associated with tunnel information #2 of the user plane entity; the tunnel information #1 and the tunnel information #2 of the user plane entity are different.

[0320] In one possible implementation, the tunnel information of the first network device is region-dependent. The first network device may move, and its signal coverage area may change. For example, due to the movement of the first network device, its beam (or signal) coverage area may no longer be the first region, but another region (e.g., the second region). When the first network device moves from the first region to another region, it can activate the tunnel information corresponding to that region. This scheme is similar to the scheme where the first network device activates the first tunnel information of the first region, and will not be described again. For example, if the signal coverage area of ​​the first network device does not include the first region, the first network device stops using the first tunnel information as its tunnel information. Other network devices providing services to the first region (e.g., the second network device) can use the first tunnel information as their tunnel information. In this embodiment, "stop using" can also be replaced with / include: not using, not enabling, invalid, etc.

[0321] For example, a first network device (e.g., satellite #1) will (or has) left the airspace above the first region and will (or has) become unable to provide communication services to the first region. A second network device (e.g., satellite #2) will (or has) moved to the airspace above the first region and will (or has) provide communication services to terminal devices in the first region. Terminal devices in the first region (e.g., the first terminal device) switch from the first network device (source network device) to the second network device (target network device). The second network device uses the first tunneling information to transmit information about the terminal devices in the first region (e.g., the first terminal device) between the second network device and the user plane entity.

[0322] It can be seen that although the network device providing services to the terminal devices in the first area is updated to the second network device, the tunnel information of the second network device remains the same as the first tunnel information corresponding to the first area used by the first network device, and has not been updated. Therefore, the second network device does not need to announce its tunnel information to the user plane entity via signaling. The user plane entity has already obtained the first tunnel information of the first area, and continues to use the previously obtained first tunnel information to transmit information about the terminal devices in the first area with the second network device. This scheme can save signaling overhead.

[0323] In another possible implementation, the first terminal device may also move. If the first terminal device does not move out of the first area, the network device tunnel information in the user plane tunnel information of the first terminal device does not need to be updated. See the foregoing for the solution, which will not be repeated here. When the first terminal device moves out of the first area, the user plane tunnel of the first terminal device can be rebuilt. The method for establishing the user plane tunnel of the first terminal device can refer to the method for establishing the user plane tunnel of the first terminal device within the first area, which will not be repeated here. Regarding the second network device, when the second network device provides communication services to the first area, if the terminal devices within the first area change, for example, if the first terminal device is no longer in the first area, the second network device no longer needs to provide communication services to the first terminal device and can dismantle the user plane tunnel of the first terminal device. For example, if a new terminal device is added to the first area, the second network device can establish a user tunnel for the newly added terminal device. The establishment scheme can refer to the method for establishing the user plane tunnel of the first terminal device. The network device tunnel information in the user plane tunnel of this terminal device is still associated with the first area and can still be the first tunnel information. The solution is similar and will not be repeated here.

[0324] In another possible implementation, if the first terminal device moves out of the first area, the first network device (referred to as the source network device) determines that it will no longer serve the first terminal device. If the first network device initiates a handover process to the second network device (referred to as the target network device), the second network device establishes a user plane tunnel between the second network device and the user plane entity for the first terminal device. The scheme is the same as the above (replacing the first network device with the second network device), and will not be described again.

[0325] In another possible implementation, if the first terminal device moves out of the first area, the second network device (target network device) provides services to the UE. In this case, the first terminal device initiates a non-access stratum (NAS) procedure, such as a mobility registration update procedure. In this procedure, the establishment or update of control plane and user plane connections can be achieved through the aforementioned scheme. Detailed scheme descriptions are provided above and will not be repeated here.

[0326] In another possible implementation, the first terminal device can also identify its own location. For example, the first terminal device can obtain the correspondence between area and location information. In another possible implementation, the first terminal device can also obtain the correspondence between area and tunnel information. The correspondence between area and location information, and / or the correspondence between area and tunnel information, can be pre-configured on the first terminal device side, or sent to the first terminal device by other devices. For example, the first terminal device obtains the correspondence between area and location information, and / or the correspondence between area and tunnel information, by receiving at least one of the following messages: a broadcast message from a network device (which may be the first network device or other network devices); or signaling from the AMF / SMF. The correspondence between area and location information can include a correspondence between at least one area (including the first area) and at least one piece of location information, and the correspondence between area and tunnel information can include a correspondence between at least one area (including the first area) and at least one piece of tunnel information.

[0327] In this embodiment, the first tunnel information is associated with a region, and the granularity of the first tunnel information can be flexibly set.

[0328] For example, the first tunnel information can be at the region level (or region-specific), such as at least two terminal devices in a first region having the same tunnel information for the first network device (see Implementation C1). Since the first tunnel information is at the region level, one region can correspond to the tunnel information of one network device, thereby reducing the amount of tunnel information for network devices associated with a region and thus saving overhead.

[0329] For example, the first tunnel information can be UE-level (or UE-granular). For instance, the tunnel information of the first network device corresponding to at least two terminal devices in the first area is different (see Implementation C2). Since the first tunnel information is UE-level, one area can correspond to the tunnel information of one or more network devices. The first network device can identify which terminal device the packet corresponds to based on the tunnel information (without relying on other information), thereby saving resource overhead and avoiding packet transmission errors.

[0330] For example, the first tunnel information can be session-level (or session-granular). For instance, the tunnel information of the first network device corresponding to at least two sessions of the first terminal device in the first area (e.g., two different sessions, any two sessions, or every two sessions) is different (see embodiment C2). Since the first tunnel information is session-level, the first network device can identify which terminal device and which session a message belongs to based on the tunnel information (without needing other information). This allows it to provide finer-grained communication service quality to the terminal device, save resource overhead, and avoid message transmission errors.

[0331] In implementation C1, the first tunnel information can be at the regional granularity (or regional level), for example, the tunnel information of the first network devices corresponding to at least two terminal devices in the first region is the same.

[0332] For example, the tunnel information of the first network device corresponding to at least two regions (or any two regions) is different. For example, the signal coverage area of ​​the first network device includes a first region and a second region. The first network device enables first tunnel information and second tunnel information; the first tunnel information is associated with the first region, and the second tunnel information is associated with the second region. When the first network device transmits information about a terminal device in the first region to a user plane entity, the first network device uses the first tunnel information as its tunnel information. When the first network device transmits information about a terminal device in the second region to a user plane entity, the first network device uses the second tunnel information as its tunnel information. The first tunnel information and the second tunnel information are different.

[0333] For example, the first region may include one or more terminal devices. For instance, the first region may include a first terminal device and a second terminal device. The tunnel information of the first network device corresponding to the second terminal device is also the first tunnel information. That is, the tunnel information of the first network device corresponding to multiple terminal devices (or all terminal devices) in the same region is the same tunnel information. The user plane connection in this embodiment C1 can be called a node-level user plane connection. For example, a user plane entity can send a second message to the first network device. For example, the user plane entity sends a second message to the first network device through the user plane connection between the user plane entity and the first network device. Correspondingly, the first network device receives the second message from the user plane entity. The second message includes the first tunnel information. The second message is used to enable the first network device to send the information in the second message to the second terminal device. The receiving end of the second message is the second terminal device. The first network device can send the information in the second message to the second terminal device according to the first tunnel information. For example, if the first terminal device and the second terminal device are served by the same user plane entity, then for the user plane connection between the first network device and the user plane entity, the tunnel information of the first network device corresponding to the first terminal device and the second terminal device is the first tunnel information, and the tunnel information of the user plane entity corresponding to the first terminal device and the second terminal device is also the tunnel information of the same user plane entity.

[0334] In implementation C1, the first network device can use other information to help determine which terminal device the received message should be sent to. For example, the first network device can identify which terminal device the message needs to be sent to based on the message header, such as the first tunnel information (see implementation C1.1). Alternatively, the first network device can identify which terminal device the message needs to be sent to based on other information in the first message (such as the identifier of the terminal device) (see implementation C1.2).

[0335] In implementation C1.1, the first network device can identify which terminal device the message needs to be sent to based on the information in the message header.

[0336] For example, the message header may include information such as channel information or address information. This information can help the first network device identify which terminal device the message needs to be sent to.

[0337] In implementation C1.2, the first network device can identify which terminal device the message needs to be sent to based on other information in the first message (such as the identifier of the terminal device).

[0338] In one possible implementation, the user plane entity can obtain the first identifier of the first terminal device and then add the first identifier to the first message.

[0339] The first identifier of the first terminal device is one of the identifiers of the first terminal device. The first terminal device may have one identifier or multiple identifiers; for distinction, the identifier of the first terminal device will be referred to as the first identifier here. The first identifier is used to transmit information about the first terminal device between the user plane entity and the first network device. The first identifier of the first terminal device can be a permanent or temporary identifier, such as the IP address or ID of the first terminal device, or information that identifies the first terminal device (e.g., UE information). The UE ID can be a temporary or permanent identifier, as described above, and will not be repeated here.

[0340] There are several ways for a user plane entity to obtain the first identifier of the first terminal device. For example, a session management entity (or mobility management entity, or the first network device, etc.) sends the first identifier of the first terminal device to the user plane entity. Another example is that the user plane entity receives a fourth message from the first network device, the fourth message including the user plane entity's tunnel information and the first identifier of the first terminal device. When the user plane entity responds with information (or a message) corresponding to the fourth message, it can include the first tunnel information and the identifier of the first terminal device in that information (or message). Yet another example is that the user plane entity can configure the first identifier for the first terminal device.

[0341] For example, the first network device can obtain the first identifier of the first terminal device, and then, after receiving a message, can identify which terminal device the message needs to be sent to based on the identifier of the terminal device in the message. There are several ways for the first network device to obtain the first identifier of the first terminal device. For example, the session management entity (or mobility management entity, or user plane entity, etc.) sends the first identifier of the first terminal device to the first network device. Another example is that the first network device can configure the first identifier for the first terminal device.

[0342] For example, the first message includes first tunnel information and a first identifier of the first terminal device. The first identifier of the first terminal device is used to indicate or identify the first terminal device. For example, the first identifier of the first terminal device can be UEIP or UE ID, etc. The first network device identifies that the first message is a message that needs to be sent to a terminal device in the first area based on the first tunnel information in the first message. The first network device identifies that the first message is a message that needs to be sent to the first terminal device based on the first identifier of the first terminal device. The first network device can send the information in the first message to the first terminal device located in the first area based on the first tunnel information and the first identifier of the first terminal device.

[0343] For example, a first network device receives a second message from a user plane entity. The second message includes first tunnel information and an identifier for a second terminal device. The identifier for the second terminal device is used to indicate or identify the second terminal device. For example, the second identifier for the second terminal device could be a UE ID, etc. The first network device identifies, based on the first tunnel information in the second message, that the second message is a message that needs to be sent to a terminal device in a first area. The first network device also identifies, based on the identifier for the second terminal device, that the second message needs to be sent to the second terminal device. The first network device can then send the information in the second message to the second terminal device located in the first area, based on the first tunnel information and the identifier for the second terminal device.

[0344] In another possible implementation, the first network device (e.g., satellite #1) will (or has) left the airspace above the first area and will (or has) been unable to provide communication services to the first area. The second network device (e.g., satellite #2) will (or has) moved to the airspace above the first area and will (or has) been providing communication services to terminal devices in the first area. The second network device can obtain the first identifier of the first terminal device. Thus, the second network device can continue to use the first identifier. For example, a user plane entity sends a message to the second network device, the message including first tunnel information and the identifier of the first terminal device. The second network device identifies, based on the first tunnel information, that the message is a message that needs to be sent to a terminal device in the first area. The second network device identifies, based on the first identifier of the first terminal device, that the message is a message that needs to be sent to the first terminal device, and then sends the information in the first message to the first terminal device located in the first area.

[0345] In implementation C1, although the network device providing services to the terminal device in the first area is updated to the second network device, the tunnel information of the second network device is still the tunnel information corresponding to the first area used by the first network device and is not updated, thereby saving signaling overhead.

[0346] There are several ways for the second network device to obtain the first identifier of the first terminal device. For example, the first network device can send the first identifier of the first terminal device to the second network device. Another example is that the session management entity (or mobility management entity, or user plane entity, etc.) sends the first identifier of the first terminal device to the second network device.

[0347] In another possible implementation, the second network device automatically configures an identifier for the first terminal device. This identifier can serve as the updated first identifier of the first terminal device, and correspondingly, the first identifier of the first terminal device obtained by the first network device can be referred to as the original first identifier. The updated first identifier may be the same as or different from the original first identifier. When configuring the updated first identifier for the first terminal device, the second network device may disregard the original first identifier. After configuring the updated first identifier, the second network device can send the updated first identifier to the user plane entity so that the user plane entity can obtain the updated first identifier. The scheme for the user plane entity to obtain the updated first identifier is similar to the scheme for the user plane entity to obtain the original first identifier, and will not be described again. The scheme for the second network device to obtain the updated first identifier can also refer to the scheme for the first network device to obtain the original first identifier.

[0348] In one possible implementation, the user plane entity may further obtain the identifier of the first session of the first terminal device and then add the identifier of the first session to the first message. The identifier of the first session can be used to distinguish which session the message corresponds to. For example, the first message includes first tunnel information and the identifier of the first session. The identifier of the first session of the first terminal device is used to indicate or identify the first session of the first terminal device, for example, the first session identifier is a session ID or UE IP. Different sessions may correspond to different UE IPs. The first network device identifies the first message as a message that needs to be sent to the terminal device in the first area based on the first tunnel information in the first message. The first network device identifies the first message as a message of the first session of the first terminal device based on the identifier of the first session, and then sends the information in the first message (e.g., may include the identifier of the first session) to the first terminal device located in the first area. The first terminal device can also identify the received information as information of the first session based on the identifier of the first session in the received information.

[0349] In another possible implementation, the first message in this example may or may not include the identifier of the first terminal device. The first network device can identify the receiver of the first message as the first terminal device based on the identifier of the first session, the bearer of the first message (e.g., implementation C1.1), or the first identifier of the first terminal device in the first message. The aforementioned first identifier of the first terminal device can be at the UE granularity; for example, multiple sessions of the first terminal device may correspond to the same first identifier of the first terminal device. If the first identifier of the first terminal device is at the session level (e.g., the first terminal device may include multiple first identifiers, and the multiple first identifiers corresponding to multiple sessions may be different), then the first identifier can also be regarded as a possible example of a session identifier.

[0350] The schemes for the user plane entity, the first network device, and the second network device to obtain the identifier of the first session of the first terminal device can all refer to the aforementioned schemes for the user plane entity, the first network device, and the second network device to obtain the first identifier of the first terminal device, and will not be repeated here.

[0351] In implementation C2, the first tunnel information can be UE-level (or UE-grade), for example, the tunnel information of the first network device corresponding to at least two terminal devices in the first area is different.

[0352] For example, the first tunnel information is also determined based on the first terminal device. For example, the tunnel information of the first network devices of at least two terminal devices in the first area is different.

[0353] For example, area #1 (the first area) corresponds to 100 NTN tunnel information entries. The first network device allocates these 100 NTN tunnel information entries to 100 terminal devices in area #1. For instance, the tunnel information for the network device corresponding to UE #1 in area #1 is tunnel information #1, and the tunnel information for the network device corresponding to UE #2 in area #1 is tunnel information #2. The user plane entity sends message #1 to the first network device, and message #1 includes tunnel information #1. The first network device identifies that message #1 needs to be sent to UE #1 in the first area based on tunnel information #1, and then sends the information in message #1 to UE #1. Similarly, the user plane entity sends message #2 to the first network device, and message #2 includes tunnel information #2. The first network device identifies that message #2 needs to be sent to UE #2 in the first area based on tunnel information #2, and then sends the information in message #2 to UE #2.

[0354] In another possible implementation, the first network device (e.g., satellite #1) will (or has) left the airspace above the first area and will (or has) become unable to provide communication services to the first area. The second network device (e.g., satellite #2) will (or has) moved to the airspace above the first area and will (or has) provide communication services to the terminal devices in the first area. The second network device can obtain the correspondence between the tunnel information of the terminal devices and network devices in the first area, so that the second network device knows which network device's tunnel information has been assigned to which terminal device. For example, the correspondence between the tunnel information of the terminal devices and network devices in the first area includes the correspondence between the first terminal device and the first tunnel information. Thus, the second network device can continue to use the tunnel information of the network devices corresponding to each terminal device in the first area. For example, a user plane entity sends a message to the second network device, the message including the first tunnel information. The first tunnel information is the tunnel information corresponding to the first terminal device in the first area. The second network device identifies, based on the first tunnel information, that the message needs to be sent to the first terminal device in the first area, and then sends the information in the first message to the first terminal device located in the first area. In implementation C2, although the network device providing services to the terminal device in the first area is updated to the second network device, the tunnel information of the second network device is still the tunnel information corresponding to the first area used by the first network device and is not updated, thereby saving signaling overhead.

[0355] There are several ways for the second network device to obtain the correspondence between the tunnel information of the terminal devices and the network devices in the first area. For example, the first network device can send information to the second network device to indicate the correspondence between the tunnel information of the terminal devices and the network devices in the first area. Another example is that a session management entity (or mobility management entity, or user plane entity, etc.) sends information to the second network device to indicate the correspondence between the tunnel information of the terminal devices and the network devices in the first area.

[0356] In another possible implementation, the second network device can configure its tunnel information for the terminal devices in the first area independently. Similar solutions exist, as described in the scheme where the first network device configures its tunnel information for the terminal devices in the first area, and will not be repeated here. The user plane entity can obtain information that the second network device can configure its tunnel information for the terminal devices in the first area independently. Similar solutions exist, as described in the scheme where the user plane entity obtains information that the first network device configures its tunnel information for the terminal devices in the first area, and will not be repeated here.

[0357] In one possible implementation, the user plane entity may further obtain the identifier of the first session of the first terminal device and then add the identifier of the first session to the first message. The identifier of the first session can be used to distinguish which session the message corresponds to. For example, the first message includes first tunnel information and the identifier of the first session. The identifier of the first session of the first terminal device is used to indicate or identify the first session of the first terminal device, for example, the first session identifier is a session ID or UE IP. The first network device determines the first session of the first terminal device corresponding to the first message based on the first tunnel information in the first message. Specifically, the first network device identifies the first message as a message that needs to be sent to a terminal device in the first area based on the first tunnel information in the first message. The first network device identifies the first message as a message of the first session of the first terminal device based on the identifier of the first session, and then sends the information in the first message (e.g., may include the identifier of the first session) to the first terminal device located in the first area. The first terminal device can also identify the received information as information of the first session based on the identifier of the first session in the received information.

[0358] In this example, since the first tunnel information is at the UE level, the first message may not include the first identifier of the first terminal device (or it may carry the first identifier of the first terminal device). The first network device can identify the receiver of the first message as the first terminal device based on the first tunnel information.

[0359] The schemes for the user plane entity, the first network device, and the second network device to obtain the identifier of the first session of the first terminal device can all refer to the aforementioned schemes for the user plane entity, the first network device, and the second network device to obtain the first identifier of the first terminal device, and will not be repeated here.

[0360] In implementation C3, the first tunnel information can be at the session granularity (or session level). For example, the tunnel information of the first network device corresponding to at least two sessions of the first terminal device in the first area (e.g., two different sessions, or any two sessions, or every two sessions) is different.

[0361] For example, the first tunnel information is also determined based on the first terminal device and the first session of the first terminal device. The tunnel information of the first network device corresponding to at least two sessions of the first terminal device in the first area (e.g., two different sessions, or any two sessions, or every two sessions) is different.

[0362] For example, the first terminal device in area #1 (first area) corresponds to 10 NTN tunnel information sets, and the first network device allocates these 10 NTN tunnel information sets for 10 sessions of the first terminal device. For instance, the tunnel information of the network device corresponding to session #1 of UE #1 in area #1 is tunnel information #1, and the tunnel information of the network device corresponding to session #2 of UE #1 in area #1 is tunnel information #2. The user plane entity sends message #1 to the first network device, and message #1 includes tunnel information #1. The first network device determines that message #1 corresponds to session #1 of UE #1 based on tunnel information #1 in message #1. Specifically, the first network device identifies that message #1 needs to be sent to UE #1 in the first area based on tunnel information #1, and identifies that the message corresponds to session #1. Similarly, the user plane entity sends message #2 to the first network device, and message #2 includes tunnel information #2. The first network device identifies that the message #2 is to be sent to UE #2 in the first area based on the tunnel information #2, and identifies that the message is the message corresponding to session #2.

[0363] In another possible implementation, the first network device (e.g., satellite #1) will (or has) left the airspace above the first area and will (or has) become unable to provide communication services to the first area. The second network device (e.g., satellite #2) will (or has) moved to the airspace above the first area and will (or has) provide communication services to the terminal devices in the first area. The second network device can obtain the correspondence between the sessions of the terminal devices in the first area and the tunnel information of the network devices, so that the second network device knows which network device's tunnel information was assigned to which terminal device's session. For example, the correspondence between the sessions of the terminal devices in the first area and the tunnel information of the network devices includes the correspondence between the first session of the first terminal device and the first tunnel information. Thus, the second network device can continue to use the tunnel information of the network devices corresponding to the sessions of each terminal device in the first area. For example, a user plane entity sends a message to the second network device, and this message includes the first tunnel information. The first tunnel information is the tunnel information corresponding to the first session of the first terminal device in the first area. The second network device identifies the message as corresponding to the first session of the first terminal device in the first area based on the first tunnel information. In implementation C3, although the network device providing services to the terminal device in the first area is updated to the second network device, the tunnel information of the second network device is still the tunnel information corresponding to the first area used by the first network device and is not updated, thereby saving signaling overhead.

[0364] There are several ways for the second network device to obtain the correspondence between the sessions of the terminal devices in the first area and the tunnel information of the network devices. For example, the first network device can send an identifier of the first session to the second network device. Alternatively, the first network device can send information to the second network device indicating the correspondence between the sessions of the terminal devices in the first area and the tunnel information of the network devices. Another example is that a session management entity (or mobility management entity, or user plane entity, etc.) sends information to the second network device indicating the correspondence between the sessions of the terminal devices in the first area and the tunnel information of the network devices.

[0365] In another possible implementation, the second network device can autonomously configure the network device's tunnel information for the sessions of terminal devices in the first area. Similar solutions exist, as described in the scheme where the first network device configures the network device's tunnel information for the sessions of terminal devices in the first area, and will not be repeated here. The user plane entity can obtain information that the second network device can autonomously configure the network device's tunnel information for the sessions of terminal devices in the first area. Similar solutions exist, as described in the scheme where the user plane entity obtains information that the first network device configures the network device's tunnel information for the sessions of terminal devices in the first area, and will not be repeated here.

[0366] In this example, since the first tunnel information is at the session level, the first message may not include the first identifier of the first terminal device, or it may not carry the identifier of the first session (or it may carry the first identifier of the first terminal device and / or the identifier of the first session). The first network device can identify the receiver of the first message as the first terminal device based on the first tunnel information, and identify the session corresponding to the message based on the first tunnel information.

[0367] In another possible implementation, a region may have multiple network devices providing communication services (e.g., two satellites simultaneously providing services to terminal devices in the same region), and these multiple network devices may be configured with the same network device tunneling information. Information corresponding to a terminal device in the first region sent by the user plane entity may be randomly sent to any one of these multiple network devices. If the network device receiving the information determines that the recipient of the information is not a terminal device it serves, it can send the message to other network devices, causing those other network devices to forward the message to the recipient of the message.

[0368] Figure 5 An exemplary scenario is illustrated, to which embodiments of this application are applicable. For example... Figure 5As shown, the first network device and the third network device simultaneously provide services to a first region (e.g., region #1). The first network device can establish a user plane connection with a user plane entity and a control plane connection with a mobility management entity. The third network device can establish a user plane connection with a user plane entity and a control plane connection with a mobility management entity.

[0369] For example, a first network device and a third network device simultaneously provide services to a first area. For instance, the first network device provides communication services to 50 terminal devices in the first area, and the third network device provides communication services to another 50 terminal devices. The third terminal device is a terminal device for which the third network device provides communication services, but the first network device does not provide communication services to the third terminal device. The user plane entity sends a fifth message, which includes first tunnel information. The tunnel information of both the first and second network devices includes the first tunnel information. For example, if the first network device receives the fifth message, it identifies the receiver of the fifth message as the third terminal device (e.g., the fifth message includes the identifier of the third terminal device), or in other words, it identifies the fifth message as belonging to the third terminal device, but the first network device does not possess the context of the third terminal device, such as not possessing the corresponding air interface bearer. If the third terminal device is not a terminal device for which the first network device provides communication services, the first network device sends the fifth message to the third network device (e.g., the first network device broadcasts to surrounding satellites, or sends via multicast, or sends via unicast). Correspondingly, after receiving the fifth message, the third network device identifies the recipient of the fifth message as the third terminal device and can send the information in the fifth message to the third terminal device. The scheme for the third network device to send information to the third terminal device is the same as the scheme for the first network device to send information to the first terminal device, and will not be repeated here. The third terminal device not belonging to the terminal devices for which the first network device provides communication services can include / be replaced by: the first network device not including the context information of the third terminal device.

[0370] Similarly, the mobility management entity can also send messages, such as messages from a third terminal device. Upon receiving the message, the first network device can determine, based on the terminal device identifier in the message, that the terminal device corresponding to the message is not a terminal device for which it provides communication services. The first network device can then send the message (e.g., via broadcast, multicast, or unicast) to other devices (e.g., the third network device). Related details can be found in the aforementioned user plane scheme, which is similar and will not be repeated here.

[0371] based on Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E , Figure 2 , Figure 3 , Figure 4 and Figure 5 At least one of the contents shown in the above and the other contents mentioned above, Figure 6 An exemplary flowchart of a possible communication method provided in an embodiment of this application is shown. For ease of understanding, Figure 6 This section uses the interaction between the first network device and the mobility management entity as an example for explanation. For related information on the terminal device and the mobility management entity, please refer to [link to relevant documentation]. Figure 3 The description in the text will not be repeated here.

[0372] Step 601: The first network device obtains the second identifier of the first terminal device.

[0373] A connection can be established between the first network device and the mobility management entity, which may be referred to as a control plane connection. In this control plane connection, the first network device enables a second identifier for the first terminal device. This second identifier uniquely identifies the first terminal device among all terminal devices for which the first network device provides communication services. The second identifier of the first terminal device can also be a second identifier of the first terminal device on the first network device side.

[0374] The second identifier of the first terminal device can be temporary or permanent. For example, the second identifier of the first terminal device may include / be replaced by: RAN UE NGAP ID. The second identifier of the first terminal device may be the same as or different from the aforementioned first identifier of the first terminal device.

[0375] The second identifier of the first terminal device is determined based on the correspondence between the first region and the second identifier. The first terminal device is located in the first region. One region can correspond to one second identifier of the first terminal device. For example, the second identifier of the first terminal device in region #1 is second identifier #1, and the second identifier of the first terminal device in region #2 is second identifier #2. Regions #1 and #2 are different, and the second identifiers #1 and #2 of the first terminal device are also different.

[0376] There are several methods for the first network device to obtain the second identifier of the first terminal device.

[0377] For example, the first network device may also receive information from other devices that indicates a second identifier of the first terminal device. For instance, the first network device may receive information from a mobility management entity or other network devices that indicates a second identifier of the first terminal device. The methods by which other network devices obtain the second identifier of the first terminal device are described in the section on how the first network device obtains it, and will not be repeated here. The methods by which the mobility management entity obtains the second identifier of the first terminal device are described in subsequent step 602, and will not be described here.

[0378] For example, the first network device can configure a second identifier for the first terminal device. For instance, the first network device determines that its signal coverage area includes a first region. The first network device determines the identifier of at least one terminal device corresponding to the first region, and selects one of the identifiers from the at least one terminal device as the second identifier of the first terminal device. Alternatively, the first region may also include a second terminal device, and the first network device selects one of the identifiers from the at least one terminal device as the identifier of the second terminal device. This identifier of the second terminal device is used to uniquely identify the second terminal device among all terminal devices for which the first network device provides communication services. The second identifier of the first terminal device is different from the identifier of the second terminal device. This identifier of the second terminal device can be the identifier of the second terminal device on the first network device side of the control plane connection of the second terminal device; for example, the identifier of the second terminal device can be the RAN UE NGAP ID.

[0379] In another possible implementation, the first network device may send information indicating the second identifier. For example, the first network device sends the second identifier of the first terminal device to the mobility management entity so that the mobility management entity can obtain the second identifier of the first terminal device, and subsequent messages from the mobility management entity to the first network device regarding the first terminal device may carry the second identifier of the first terminal device.

[0380] For example, if the first network device no longer provides communication services to the first area, and the second network device provides communication services to the first area, the first terminal device can switch from the first network device to the second network device. The first network device can send the second identifier of the first terminal device to the second network device so that the second network device knows which identifier of the first area has been assigned to the first terminal device as its second identifier. This allows the second network device to continue using the second identifier of the first terminal device to transmit control plane information of the first terminal device to the mobility management entity.

[0381] In one possible implementation, the identifier on the network device side of the control plane connection of the first terminal device (e.g., the second identifier of the first terminal device) can be bound to a region. When the network device providing services for a region changes, but the first terminal device remains in the first region, the identifier on the network device side of the control plane connection of the first terminal device (e.g., the second identifier of the first terminal device) does not need to be changed. The first network device can send the context of the first terminal device to the second network device. The context of the first terminal device may, for example, include the second identifier of the first terminal device (e.g., RAN UE NGAP ID).

[0382] In another possible implementation, the network device can be configured with a set of identifiers on the network device side in the control plane connection of the terminal device. For example, the first network device configures the RAN UE NGAP ID as ID#1 and ID#2, and the second network device configures the RAN UE NGAP ID as ID#3 and ID#4. For example, when the first terminal device accesses the first network device, the first network device assigns a second identifier (e.g., RAN UE NGAP ID) of ID#1 to the first terminal device. When the first network device no longer provides communication services for the first area, and the second network device provides communication services for the first area, and the first terminal device switches from the first network device to the second network device, the first network device can transmit ID#1 to the second network device. For example, ID#1 is carried in the context of the first terminal device. Thus, the second network device can continue to use ID#1 as the identifier of the first terminal device. In this case, for example, the RAN UE NGAP ID managed by the first network device is ID#2, and the second network device configures the RAN UE NGAP ID range as ID#1, ID#3, and ID#4. In practical applications, a network device may be configured with more or fewer RAN UE NGAP IDs; here is one example.

[0383] Step 602: The mobility management entity obtains the second identifier of the first terminal device.

[0384] There are several methods for the mobility management entity to obtain the second identifier of the first terminal device.

[0385] For example, the mobility management entity may also receive information from other devices that indicates a second identifier of the first terminal device. For instance, the mobility management entity may receive information from the first network device or other network devices that indicates a second identifier of the first terminal device. The methods by which other network devices obtain the second identifier of the first terminal device are detailed in the documentation for the methods by which the first network device obtains the identifier, and will not be repeated here.

[0386] For example, the mobility management entity can configure a second identifier for the first terminal device. For instance, the mobility management entity determines that the signal coverage area of ​​the first network device includes a first area. The mobility management entity determines the identifiers of at least one terminal device corresponding to the first area, and selects one of the identifiers from the at least one terminal device as the second identifier for the first terminal device. Alternatively, the first area may also include a second terminal device, and the mobility management entity selects one of the identifiers from the at least one terminal device as the identifier for the second terminal device. This identifier for the second terminal device is used to uniquely identify the second terminal device among all terminal devices providing communication services to the first network device.

[0387] Step 603: The first network device transmits signaling of the first terminal device to the mobility management entity based on the second identifier.

[0388] In this embodiment, the signaling can also be replaced by messages or information. In this embodiment, the signaling of the first terminal device can also include / be replaced by: signaling that needs to be sent to the first terminal device, and / or, signaling sent by the first terminal device.

[0389] As can be seen from the above, although the network device providing services to the first terminal device in the first area is updated from the first network device to the second network device, since the first terminal device has not moved out of the first area, the second identifier of the terminal device in the control plane (e.g., RAN UE NGAP ID) used by the first network device and the second network device to provide services to the first terminal device in the first area is the same and has not been updated. Therefore, there is no need to update the control plane information (e.g., control plane information on the base station side) of the first terminal device through signaling, thereby reducing signaling overhead. For example, in a satellite-to-ground network device, this scheme can reduce the signaling interaction between the base station located on the satellite (e.g., gNB on board) and the mobility management entity located on the ground (e.g., AMF on ground), thereby saving resource overhead in the satellite-to-ground network.

[0390] based on Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E , Figure 2 , Figure 3 , Figure 4 , Figure 5 and Figure 6 At least one of the contents shown in the above and the other contents mentioned above, Figure 7 An exemplary flowchart of a possible communication method is shown. Figure 7This paper uses the interaction between a terminal device, a first network device, a mobility management entity, a session management entity, a user plane entity, and a second network device as an example for explanation. For a detailed description of the terminal device, the first network device, the mobility management entity, the session management entity, the user plane entity, and the second network device, please refer to the foregoing. Figure 3 The description will not be repeated here.

[0391] Figure 7 The embodiments shown can be those described above. Figure 3 An extended embodiment of the provided implementation method. Figure 7 In the illustrated embodiment, the first network device, the second network device, the mobility management entity, and the session management entity can all be configured with a correspondence between the first area and the first tunnel information. This saves signaling overhead for transmitting the first tunnel information, thereby conserving resources.

[0392] The following is combined with Figure 7 The method is described below, and includes steps 701, 702, 703, 704, 705, 706, 707, 708, 709, 710, 711, 712, 713, 714, and 715.

[0393] Step 701: The first terminal device sends a session establishment request to the first network device.

[0394] Correspondingly, the first network device receives the session establishment request.

[0395] A session establishment request is used to initiate a session establishment process. A session establishment request may include / contain AN information (message). For example, a session establishment request may carry NAS information (message) and AN parameters.

[0396] Step 702: The first network device determines the first tunnel information.

[0397] In step 702, the first network device can determine that the first tunnel information of the first area is used as its own tunnel information. For example, the first network device is configured with a correspondence between the first area and the first tunnel information, and the first network device determines the tunnel information to be used based on the signal coverage area. The scheme of step 702 is similar to that of step 301 described above.

[0398] Step 702 can be performed after step 701, or step 702 can be performed before step 701.

[0399] Step 703: The first network device sends an N2 message to the mobility management entity.

[0400] Correspondingly, the mobility management entity receives the N2 message.

[0401] For example, the N2 message sent by the first network device may carry a NAS message and / or the location information of the first terminal device.

[0402] Step 704: The mobility management entity sends an N11 request message to the session management entity.

[0403] Correspondingly, the session management entity receives the N11 request message.

[0404] N11 request messages may include, for example, a request to create a context for a PDU session, or an Nsmf_PDUSession_CreateSMContext Request.

[0405] For example, the N11 request message may include the location information of the first terminal device. Alternatively, the N11 request message may include information about a first region. In another possible implementation, if the location information of the first terminal device included in the N11 request message does not meet the requirements, such as having low accuracy, the mobility management entity may initiate a location process to obtain more accurate location information of the first terminal device. That is, the mobility management entity can obtain the location information of the first terminal device in various ways (see the foregoing), and the location information obtained through some methods may not be used.

[0406] Figure 7 In the illustrated embodiment, the content carried in the N2 and N11 messages is one possible example. In practical applications, these two messages can also carry other information. For example, the N2 message received by the mobility management entity can be an example of the second information in this application embodiment, and the N11 request message sent by the mobility management entity can be an example of the first information. The content carried in the N2 message can refer to the example of the content carried in the aforementioned second information, and the content carried in the N11 message can refer to the example of the content carried in the aforementioned first information, which will not be repeated here.

[0407] Step 705: The session management entity determines whether a tunnel connection already exists between the first network device and the user plane entity;

[0408] If it does not exist, proceed to step 706;

[0409] If it exists, step 706 can be skipped, and step 707 can be executed directly without executing step 706. In this case, the N4 session request message in step 707 can carry the first identifier of the first terminal device but not the first tunnel information. The N4 session response message in step 708 can not carry the tunnel information of the user plane entity. In another possible implementation, if it exists, steps 706 to 711 can be omitted, thereby saving signaling overhead. Figure 7 The example given is the session management entity determining in step 705 that a tunnel connection between the first network device and the user plane entity does not exist. Figure 7 The subsequent steps are also described using the example of the session management entity determining that the tunnel connection between the first network device and the user plane entity does not exist.

[0410] Step 705 can also be replaced by: the session management entity determining whether the first network device has obtained the tunnel information of the user plane entity, and whether the user plane entity has obtained the tunnel information of the first network device.

[0411] For example, the session management entity can determine whether the first network device has already acquired the first tunnel information based on the first indication information and / or the second indication information, and then determine whether it needs to send the first tunnel information to the first network device. Alternatively, the session management entity can determine whether the first tunnel information has already been sent to the first network device based on saved context information, and then determine whether the first network device has acquired the first tunnel information based on that information (e.g., if the session management entity has sent the first tunnel information to the first network device, it is determined that the first network device has acquired the first tunnel information; otherwise, it is determined that the first network device has not acquired the first tunnel information), and then determine whether it needs to send the first tunnel information to the first network device. For another example, if the first network device has not acquired the first tunnel information, the session management entity can send the first tunnel information to the first network device; otherwise, it can choose not to send the first tunnel information. Related solutions are described above and will not be repeated here.

[0412] Step 706: The session management entity determines the first tunnel information of the first network device.

[0413] There are several ways for the session management entity to determine the first tunnel information. For example, the session management entity can determine the area to which the first terminal device belongs, i.e., the first area, based on the location information of the first terminal device. The session management entity then determines the first tunnel information based on the correspondence between the first area and the first tunnel information. Alternatively, the session management entity can receive information about the first area and determine the first tunnel information based on the correspondence between the first area and the first tunnel information. Alternatively, the session management entity can receive first tunnel information from other devices (such as the first network device, the mobility management entity, or the user plane entity). Alternatively, the session management entity can determine the first tunnel information based on the correspondence between the location of the first terminal device and the first tunnel information. The scheme for the session management entity to obtain the first tunnel information of the first network device can be found in the foregoing description and will not be repeated here.

[0414] In another possible implementation, in step 706, the session management entity may also determine a first identifier of the first terminal device.

[0415] Step 707: The session management entity sends an N4 session request message to the user plane entity.

[0416] Correspondingly, the user plane entity receives the N4 message.

[0417] For example, an N4 session request message may carry first tunnel information of the first network device and a first identifier of the first terminal device.

[0418] Furthermore, the session management entity also instructs the user plane entity to add the first identifier of the first terminal device to the header of the downlink message of the first terminal device.

[0419] The user plane entity receives the first tunnel information from the first network device, thus completing the establishment of the downlink tunnel between the first network device and the user plane entity.

[0420] Step 708: The user plane entity sends an N4 session response message to the session management entity.

[0421] Correspondingly, the session management entity receives the N4 session response message.

[0422] For example, an N4 session response message can carry tunneling information for a user plane entity.

[0423] Step 709: The session management entity returns an N11 response message to the mobility management entity.

[0424] Correspondingly, the mobility management entity receives the N11 response message.

[0425] For example, the N11 response message carries tunnel information and NAS information for the user plane entity. The NAS information can be a session establishment acceptance message.

[0426] Step 710: The mobility management entity returns an N2 response message to the first network device.

[0427] Correspondingly, the first network device receives the N2 response message.

[0428] For example, an N2 response message carries tunnel information and NAS information for the user plane entity. The NAS information can be a session establishment acceptance message.

[0429] The first network device receives the tunnel information from the user plane entity, thus completing the establishment of the uplink tunnel between the first network device and the user plane entity.

[0430] Step 711: The first network device sends a radio resource control (RRC) message to the first terminal device.

[0431] Correspondingly, the first terminal device receives the RRC message.

[0432] RRC messages may include, for example, non-access stratum (NAS) information, which may include PDU session establishment accept information.

[0433] Step 712: The first terminal device, the first network device, and the user plane entity can transmit uplink and / or downlink information based on the first tunnel information and the tunnel information of the user plane entity.

[0434] Step 713: If the signal coverage area of ​​the first network device does not include the first area, then the use of the first tunnel information is stopped.

[0435] If the first terminal device remains stationary or moves within the first area, the user plane tunnel information corresponding to the first terminal device does not change. That is, the tunnel information used by the first network device corresponding to the first terminal device and the tunnel information of the user plane entity can remain unchanged.

[0436] If the first network device moves, its signal coverage area will no longer include the first area, and the first network device will stop using the first tunnel information.

[0437] For example, if the first area continues to receive communication services from the second network device, and the signal coverage area of ​​the second network device can include the first area, then the second network device can execute step 714.

[0438] Step 714: The second network device determines the first tunnel information.

[0439] The method by which the second network device determines the first tunnel information can refer to the method by which the first network device determines the first tunnel information. For example, the second network device can determine that the first tunnel information of the first region is used as its own tunnel information. For example, the second network device is configured with a correspondence between the first region and the first tunnel information. If the second network device determines that the signal coverage area of ​​the adopted beam includes the first region, then it determines that the first tunnel information is used as its own tunnel information. The scheme for step 712 can refer to the aforementioned method by which the first network device and / or the second network device determines the first tunnel information, and is similar, so it will not be described again.

[0440] The user plane tunnel information (first tunnel information and / or tunnel information of the user plane entity) corresponding to the first terminal device maintained on the session management entity and / or user plane entity does not change with the network device providing services to the first area. Therefore, the user plane tunnel information does not need to be updated, thereby saving signaling overhead.

[0441] Step 715: The first terminal device, the second network device, and the user plane entity can transmit uplink and / or downlink information based on the first tunnel information and the tunnel information of the user plane entity.

[0442] There are several ways for the second network device to obtain tunnel information of user plane entities. For example, the first network device can send the tunnel information of user plane entities to the second network device. For instance, the tunnel information of user plane entities can be carried in a handover request. Alternatively, a session management entity, user plane entity, or mobility management entity can send the tunnel information of user plane entities to the second network device. See the scheme for the first network device obtaining the tunnel information of user plane entities for further details.

[0443] In another possible implementation, if the first terminal device moves out of the current first area, it can initiate a NAS procedure, such as a mobility registration update procedure. In this procedure, the mobility management entity, session management entity, and user plane entity cooperate to determine the tunnel information of the network device corresponding to the area where the first terminal device is located after moving. This scheme is similar to the process by which the first terminal device determines the tunnel information of the network device as the first tunnel information, and will not be described in detail here.

[0444] As can be seen from the above scheme, since the user plane tunnel information of the terminal device (e.g., the tunnel information of the network device) is associated with the location of the terminal device, the user plane tunnel information of the terminal device (e.g., the tunnel information of the network device) does not need to be updated when the terminal device does not move or does not move out of the current area. When the network device is updated, the user plane tunnel information of the terminal device (e.g., the tunnel information of the network device) also does not need to be updated, thereby saving signaling overhead.

[0445] based on Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E , Figure 2 , Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7 At least one of the contents shown in the above and the other contents mentioned above, Figure 8 An exemplary flowchart of a possible communication method is shown. Figure 8 This paper uses the interaction between a terminal device, a first network device, a mobility management entity, a session management entity, a user plane entity, and a second network device as an example for explanation. For a detailed description of the terminal device, the first network device, the mobility management entity, the session management entity, the user plane entity, and the second network device, please refer to the foregoing. Figure 3 The description will not be repeated here.

[0446] Figure 8 The embodiments shown can be those described above. Figure 3 An extended embodiment of the provided implementation method. Figure 8 In the illustrated embodiment, the first network device does not configure a correspondence between the first region and the first tunnel information. Therefore, the first network device needs to receive information from other network elements indicating the first tunnel information. Figure 8 Provide one possible implementation method.

[0447] The following is combined with Figure 8 The method is described below, and includes steps 801, 802, 803, 804, 805, 806, 807, 808, 809, 810, 811, 812, 813, and 814.

[0448] Step 801: The first terminal device sends a session establishment request to the first network device.

[0449] Correspondingly, the first network device receives the session establishment request.

[0450] The content of step 801 is the same as that of step 701, and will not be repeated here.

[0451] Step 802: The first network device sends an N2 message to the mobility management entity.

[0452] Correspondingly, the mobility management entity receives the N2 message.

[0453] For example, the N2 message sent by the first network device may carry a NAS message and / or the location information of the first terminal device.

[0454] In one possible implementation, the first network device may send a first indication message and / or a second indication message to indicate whether the first network device has obtained the tunnel information it needs. The content of the first indication message and / or the second indication message is as described above and will not be repeated here.

[0455] For example, the content of step 802 is described in step 703, and will not be repeated here. Since the first network device has not yet obtained the first tunnel information, the N2 message will not carry the first tunnel information.

[0456] Step 803: The mobility management entity sends an N11 request message to the session management entity.

[0457] Correspondingly, the session management entity receives the N11 request message.

[0458] For example, the content of step 803 is described in step 704 and will not be repeated here.

[0459] Step 804: The session management entity determines whether a tunnel connection already exists between the first network device and the user plane entity;

[0460] If it does not exist, proceed to step 805;

[0461] If it exists, step 805 can be skipped, and step 806 can be executed directly without executing step 805. In step 806, the N4 session request message can only carry the first identifier of the first terminal device. In step 807, the N4 session response message can not carry the tunnel information of the user plane entity. In another possible implementation, if it exists, steps 805 to 810 can be omitted, thereby saving signaling overhead. Figure 8 The example given is step 804, in which the session management entity determines that a tunnel connection between the first network device and the user plane entity does not exist. Figure 8 The subsequent steps are also described using the example of the session management entity determining that the tunnel connection between the first network device and the user plane entity does not exist.

[0462] Step 805 can also be replaced by: the session management entity determining whether the first network device has obtained the tunnel information of the user plane entity, and whether the user plane entity has obtained the tunnel information of the first network device. For example, the session management entity makes the determination based on the first indication information and / or the second indication information. The relevant scheme is described above and will not be repeated here.

[0463] For example, the content of step 804 is described in step 705 and will not be repeated here.

[0464] Step 805: The session management entity determines the first tunnel information of the first network device.

[0465] For example, the content of step 805 is described in step 706 and will not be repeated here.

[0466] Step 806: The session management entity sends an N4 session request message to the user plane entity.

[0467] Correspondingly, the user plane entity receives the N4 message.

[0468] For example, the content of step 806 is described in step 707 and will not be repeated here.

[0469] Step 807: The user plane entity sends an N4 session response message to the session management entity.

[0470] Correspondingly, the session management entity receives the N4 session response message.

[0471] For example, the content of step 807 is described in the same way as step 708, and will not be repeated here. In this embodiment, the N4 session response message may or may not carry the first tunnel information.

[0472] Step 808: The session management entity returns an N11 response message to the mobility management entity.

[0473] Correspondingly, the mobility management entity receives the N11 response message.

[0474] The N11 response message can carry the first tunnel information and the tunnel information of the user plane entity.

[0475] In one possible implementation, the session management entity can determine whether it is necessary to send the first tunnel information to the first network device. If so, the first tunnel information is carried in the N11 response message; if not, the first tunnel information is not carried in the N11 response message.

[0476] It is understandable that the first tunnel information can be replaced with the correspondence between the first tunnel information and the first area.

[0477] For example, the session management entity can determine whether the first network device has already acquired the first tunnel information based on the first indication information and / or the second indication information, and then determine whether it needs to send the first tunnel information or the correspondence between the first tunnel information and the first area to the first network device. Alternatively, the session management entity can determine whether the first tunnel information or the correspondence between the first tunnel information and the first area has already been sent to the first network device based on saved context information, and then determine whether the first network device has already acquired the first tunnel information or the correspondence between the first tunnel information and the first area (for example, if the session management entity has sent the first tunnel information to the first network device, it is determined that the first network device has acquired the first tunnel information or the correspondence between the first tunnel information and the first area; otherwise, it is determined that the first network device has not acquired the first tunnel information or the correspondence between the first tunnel information and the first area), and then determine whether it needs to send the first tunnel information or the correspondence between the first tunnel information and the first area to the first network device. For example, if the first network device does not obtain the first tunnel information or the correspondence between the first tunnel information and the first area, the session management entity may send the first tunnel information or the correspondence between the first tunnel information and the first area to the first network device; otherwise, it may not send the first tunnel information or the correspondence between the first tunnel information and the first area.

[0478] For example, the content of step 808 is described in step 709 and will not be repeated here.

[0479] Step 809: The mobility management entity returns an N2 response message to the first network device.

[0480] Correspondingly, the first network device receives the N2 response message.

[0481] For example, the content of step 809 is described in the same way as step 710, and will not be repeated here. For example, the information involved in steps 808 and 809 both carry the first tunnel information.

[0482] For example, the first network device obtains the tunnel information of the user plane entity, as well as the first tunnel information, or the correspondence between the first tunnel information and the first region, and the uplink and downlink user plane tunnels are established.

[0483] Step 810: The first network device sends an RRC message to the first terminal device.

[0484] Correspondingly, the first terminal device receives the RRC message.

[0485] For example, the content of step 810 is described in step 711 and will not be repeated here.

[0486] Step 811: The first terminal device, the first network device, and the user plane entity may transmit uplink and / or downlink information based on the first tunnel information and the tunnel information of the user plane entity.

[0487] For example, the content of step 811 is described in step 712 and will not be repeated here.

[0488] Step 812: If the signal coverage area of ​​the first network device does not include the first area, then the use of the first tunnel information is stopped.

[0489] For example, the content of step 812 is described in step 713, and will not be repeated here.

[0490] If the first terminal device remains stationary or moves within the first area, the user plane tunnel information corresponding to the first terminal device does not change. That is, the tunnel information used by the first network device corresponding to the first terminal device and the tunnel information of the user plane entity can remain unchanged.

[0491] If the first network device moves, its signal coverage area will no longer include the first area, and the first network device will stop using the first tunnel information.

[0492] For example, if the first area continues to receive communication services from the second network device, and the signal coverage area of ​​the second network device can include the first area, then the second network device can execute step 813.

[0493] Step 813: The second network device determines the first tunnel information.

[0494] For example, the second network device can receive first tunnel information from the first network device.

[0495] Alternatively, the second network device learns the first tunnel information from a session management entity, mobility management entity, or user plane entity.

[0496] For example, step 813 includes the following steps:

[0497] Step 8131: The second network device sends a path switching request to the mobility management entity.

[0498] Correspondingly, the mobility management entity receives route switching requests.

[0499] Path switching requests can include, for example, / as a path switch request.

[0500] Since the second network device has not yet obtained the first tunnel information, the path switching request will not carry the first tunnel information. The path switching request may, for example, carry the location information of the first terminal device (or it may not).

[0501] Step 8132: The mobility management entity sends an N11 request message to the session management entity.

[0502] Correspondingly, the session management entity receives the N11 request message.

[0503] For example, the content of step 8132 is described in the same way as step 704, and will not be repeated here. The N11 request message may include, for example, the location information of the first terminal device, or the information of the first area, or the information of the first tunnel.

[0504] Step 8133: The session management entity sends an N4 session request message to the user plane entity.

[0505] Correspondingly, the user plane entity receives the N4 message. For example, the N4 message includes the first tunnel information corresponding to the second network device.

[0506] For example, the content of step 8133 is described in step 707 and will not be repeated here.

[0507] Step 8134: The user plane entity sends an N4 session response message to the session management entity.

[0508] Correspondingly, the session management entity receives the N4 session response message.

[0509] For example, the content of step 8134 is described in the same way as step 708, and will not be repeated here. In this embodiment, the N4 session response message may also carry the first tunnel information.

[0510] Step 8135: The session management entity returns an N11 response message to the mobility management entity.

[0511] Correspondingly, the mobility management entity receives the N11 response message.

[0512] The N11 response message may carry the first tunnel information. The N11 response message may or may not carry the tunnel information of the user plane entity.

[0513] For example, the content of step 808 is described in step 709 and will not be repeated here.

[0514] Step 8136: The mobility management entity returns a path switching request response to the first network device.

[0515] Correspondingly, the first network device receives a path switching request response. For example, the path switching request response carries first tunnel information.

[0516] For example, the content of step 8136 is described in step 710 and will not be repeated here.

[0517] For example, the second network device obtains the tunnel information of the user plane entity, as well as the first tunnel information, or the correspondence between the first tunnel information and the first region, and the uplink and downlink user plane tunnels are established.

[0518] The method by which the second network device determines the first tunnel information can also refer to the method by which the first network device determines the first tunnel information, and will not be repeated here.

[0519] Step 814: The first terminal device, the second network device, and the user plane entity can transmit uplink and / or downlink information based on the first tunnel information and the tunnel information of the user plane entity.

[0520] There are several ways for the second network device to obtain tunnel information of user plane entities. For example, the first network device can send the tunnel information of user plane entities to the second network device. For instance, the tunnel information of user plane entities can be carried in a handover request. Alternatively, a session management entity, user plane entity, or mobility management entity can send the tunnel information of user plane entities to the second network device. See the scheme for the first network device obtaining the tunnel information of user plane entities for further details.

[0521] In another possible implementation, if the first terminal device moves out of the current first area, it can initiate a NAS procedure, such as a mobility registration update procedure. In this procedure, the mobility management entity, session management entity, and user plane entity cooperate to determine the tunnel information of the network device corresponding to the area where the first terminal device is located after moving. This scheme is similar to the process by which the first terminal device determines the tunnel information of the network device as the first tunnel information, and will not be described in detail here.

[0522] In another possible implementation, as the network device moves, all NN devices covering the first area (e.g., satellites 1-10) acquire the first tunnel information corresponding to the first area. Subsequent network devices do not need to learn the first tunnel information again. For example, the first network device obtains the first tunnel information corresponding to the first area from the session management entity. As the first network device moves out of the first area, and then returns to the first area, the first network device can directly activate the first tunnel information of the first area without having to obtain this information from the session management entity or other devices, thereby saving signaling overhead.

[0523] As can be seen from the above scheme, since the user plane tunnel information of the terminal device (e.g., the tunnel information of the network device) is associated with the location of the terminal device, the user plane tunnel information of the terminal device (e.g., the tunnel information of the network device) does not need to be updated when the terminal device does not move or does not move out of the current area. When the network device is updated, the user plane tunnel information of the terminal device (e.g., the tunnel information of the network device) also does not need to be updated, thereby saving signaling overhead.

[0524] based on Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E , Figure 2 , Figure 3 , Figure 4 , Figure 5 , Figure 6 , Figure 7 and Figure 8 At least one of the contents shown in the above and the other contents mentioned above, Figure 9 An exemplary flowchart of a possible communication method is shown. Figure 9 The interaction between the first network device and the mobility management entity will be used as an example for explanation. For a detailed description of the first network device and the mobility management entity, please refer to the preceding text. Figure 3 The description will not be repeated here.

[0525] Figure 9 The embodiments shown can be those described above. Figure 3 An extended embodiment of the provided implementation method. Figure 9 The embodiments shown can be those described above. Figure 3 An extended embodiment of the provided implementation method. Figure 9 In the illustrated embodiment, the first network device does not configure a correspondence between the first region and the first tunnel information. Therefore, the first network device needs to receive information from other network elements indicating the first tunnel information. Figure 9 Provide one possible implementation method.

[0526] The following is combined with Figure 9 The method is described below, and includes steps 901 and 902.

[0527] Step 901: The first network device sends an NG establishment request message to the mobility management entity.

[0528] Correspondingly, the mobility management entity receives the NG setup request message.

[0529] For example, an NG setup request message carries the mapping between a first area and a first tunnel. NG setup request messages can also carry the mapping between other areas and tunnel information of the network device.

[0530] Step 902: The mobility management entity stores the correspondence between the first region and the first tunnel information.

[0531] The mobility management entity stores the correspondence between the first region and the first tunnel information. Subsequently, the mobility management entity can send the first tunnel information to the session management entity, and the session management entity can send the first tunnel information to the user plane entity. This example can be found in the preceding description. Figure 3 and / or Figure 7 The described solution will not be elaborated further.

[0532] based on Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E , Figure 2 , Figure 3 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 and Figure 9 At least one of the contents shown in the above and the other contents mentioned above, Figure 10 An exemplary flowchart of a possible communication method is shown. Figure 10 The interaction between the first network device and the second network device will be used as an example for explanation. For a description of the first network device and the second network device, please refer to the foregoing. Figure 3 The description will not be repeated here.

[0533] Figure 10 The embodiments shown can be those described above. Figure 3 An extended embodiment of the provided implementation method. Figure 10 The embodiments shown can be those described above. Figure 3 An extended embodiment of the provided implementation method. Figure 10 In the illustrated embodiment, the first network device is configured only in a subset of network devices (e.g., configured in the first network device itself), and not on the mobility management entity side, nor on the session management entity or user plane entity side. Thus, the first network device can send first tunneling information to the second network device and at least one of the mobility management entity, session management entity, or user plane entity. Figure 10 Provide one possible implementation method.

[0534] The following is combined with Figure 10The method is described in detail, including steps 1001 and 1002.

[0535] Step 1001: The first network device sends an Xn establishment request message to the second network device.

[0536] Correspondingly, the second network device receives the Xn setup request message.

[0537] For example, the Xn setup request message carries the mapping between the first area and the first tunnel information. The Xn setup request message can also carry the mapping between other areas and the tunnel information of the network device.

[0538] Step 1002: The second network device stores the correspondence between the first area and the first tunnel information.

[0539] The second network device stores the correspondence between the first area and the first tunnel information. The second network device can directly activate the first tunnel information when the signal coverage includes the first area. For relevant solutions, please refer to the foregoing. Figure 3 and / or Figure 7 The described solution will not be elaborated further.

[0540] On the other hand, the first network device can send first tunnel information to the mobility management entity, or send the correspondence between the first area and the first tunnel information. The mobility management entity can store the correspondence between the first area and the first tunnel information, and subsequently, the mobility management entity can send the first tunnel information to the session management entity, which in turn sends the first tunnel information to the user plane entity. This example can be found in the foregoing. Figure 3 , Figure 7 or Figure 9 The schemes described in at least one of the above are not elaborated further.

[0541] Based on the same concept Figure 11 and Figure 12 This is a schematic diagram illustrating the structure of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of the first network device, mobility management entity, session management entity, user plane entity, or second network device in the above method embodiments, and therefore can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be one of the aforementioned... Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10The communication device involved may be a first network device, a mobility management entity, a session management entity, a user plane entity, or a second network device. This communication device can be a communication equipment or a chip (or chip system, circuit, unit, or module) within a communication equipment. For a description of the first network device, mobility management entity, session management entity, user plane entity, or second network device, please refer to the foregoing. Figure 3 The description in, for example, can be found in the preceding text. Figure 1A , Figure 1B , Figure 1C , Figure 1D , Figure 1E or Figure 2 The equipment or chips (or chip systems, circuits, units, or modules) involved will not be described in detail.

[0542] like Figure 11 As shown, the communication device 1300 includes a processing unit 1310 and a transceiver unit 1320. The communication device 1300 is used to implement the above-mentioned... Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 The method embodiment shown illustrates the functions of the first network device, mobility management entity, session management entity, user plane entity, or second network device. The transceiver unit 1320 can also be referred to as a communication unit. The transceiver unit 1320 may include a sending unit and a receiving unit.

[0543] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the processing unit 1310 is used to obtain the first tunnel information of the first network device, receive the first message from the user plane entity through the transceiver unit 1320 based on the first tunnel information, and send the information in the first message to the first terminal device located in the first area through the transceiver unit 1320.

[0544] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10In the method embodiment shown, when the first network device functions, in one possible implementation, the processing unit 1310 is used to receive a second message from a user plane entity through the transceiver unit 1320 based on the first tunnel information, and send the information in the second message to the second terminal device through the transceiver unit 1320.

[0545] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the processing unit 1310 is used to send information in the first message to the first terminal device located in the first area through the transceiver unit 1320 according to the first identifier.

[0546] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions as described, in one possible implementation, the transceiver unit 1320 is used to send the first identifier of the first terminal device to the second network device.

[0547] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the processing unit 1310 is used to determine that the signal coverage area of ​​the first network device includes a first region, and to determine the first tunnel information based on the correspondence between the first region and the first tunnel information.

[0548] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the transceiver unit 1320 is used to send first tunnel information.

[0549] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10In the method embodiment shown, when the first network device functions as described, in one possible implementation, the transceiver unit 1320 is used to send first tunnel information to the second network device.

[0550] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the transceiver unit 1320 is used to send a third message to a user plane entity.

[0551] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the transceiver unit 1320 is used to receive first tunnel information.

[0552] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the transceiver unit 1320 is used to send information about the location of the first terminal device.

[0553] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the processing unit 1310 is used to obtain the location information of the first terminal device.

[0554] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the transceiver unit 1320 is used to send first instruction information.

[0555] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the transceiver unit 1320 is used to send second instruction information.

[0556] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In one possible implementation of the method embodiment shown, when the first network device functions as described above, the processing unit 1310 is used to stop using the first tunnel information as the tunnel information of the first network device if the signal coverage area of ​​the first network device does not include the first area.

[0557] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions as described, in one possible implementation, the transceiver unit 1320 is used to send the identifier of the first session to the second network device.

[0558] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the transceiver unit 1320 is used to receive tunnel information of the user plane entity corresponding to the first region; and send a fourth message to the user plane entity based on the tunnel information of the user plane entity corresponding to the first region and the first identifier of the first terminal device.

[0559] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the transceiver unit 1320 is used to receive a fifth message from a user plane entity and send the fifth message to the third network device when the third terminal device is not a terminal device for which the first network device provides communication services.

[0560] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the processing unit 1310 is used to obtain the second identifier of the first terminal device and transmit the information of the first terminal device through the transceiver unit 1320 according to the second identifier.

[0561] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the processing unit 1310 is used to determine that the signal coverage area of ​​the first network device includes a first region; determine the identifier of at least one terminal device corresponding to the first region; and select an identifier from the identifiers of the at least one terminal device as a second identifier.

[0562] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the transceiver unit 1320 is used to send information for indicating a second identifier.

[0563] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the first network device functions, in one possible implementation, the transceiver unit 1320 is used to receive information for indicating a second identifier.

[0564] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 When the mobility management entity and / or session management entity are functioning in the method embodiment shown, in one possible implementation, the processing unit 1310 is used to obtain first information and send the first information through the transceiver unit 1320.

[0565] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiments shown, when the mobility management entity and / or session management entity are functioning, in one possible implementation, the processing unit 1310 is used to obtain second information.

[0566] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 When the mobility management entity and / or session management entity are functioning in the method embodiment shown, in one possible implementation, the processing unit 1310 is used to determine the first area based on the location information of the first terminal device, and to determine the first tunnel information based on the correspondence between the first area and the first tunnel information.

[0567] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 When the mobility management entity and / or session management entity are functioning in the method embodiment shown, in one possible implementation, the processing unit 1310 is used to determine a first area based on the location information of the first terminal device.

[0568] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 When the mobility management entity and / or session management entity are functioning in the method embodiment shown, in one possible implementation, the transceiver unit 1320 is used to receive location information of the first terminal device, or to receive positioning measurement results and determine the location information of the first terminal device based on the positioning measurement results.

[0569] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 When the mobility management entity and / or session management entity are functioning in the method embodiment shown, in one possible implementation, the transceiver unit 1320 is used to receive first indication information and send tunnel information of the first area to the first network device according to the first indication information.

[0570] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the mobility management entity and / or session management entity are functioning, in one possible implementation, the processing unit 1310 is used to receive second indication information through the transceiver unit 1320, and determine, based on the second indication information, that it is not necessary to send tunnel information of the first area to the first network device.

[0571] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the mobility management entity and / or session management entity are functioning, in one possible implementation, the processing unit 1310 is used to send the first information to the user plane entity through the transceiver unit 1320 when the user plane entity has not obtained the first tunnel information.

[0572] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 When the mobility management entity and / or session management entity are functioning in the method embodiment shown, in one possible implementation, the transceiver unit 1320 is used to send the first identification information of the first terminal device to the user plane entity.

[0573] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 When the mobility management entity and / or session management entity are functioning in the method embodiment shown, in one possible implementation, the processing unit 1310 is used to obtain a second identifier of the first terminal device and transmit information of the first terminal device through the transceiver unit 1320 according to the second identifier.

[0574] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiments shown, when the mobility management entity and / or session management entity are functioning, in one possible implementation, the transceiver unit 1320 is used to receive information indicating a second identifier.

[0575] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 When the mobility management entity and / or session management entity are functioning in the method embodiment shown, in one possible implementation, the processing unit 1310 is used to determine that the signal coverage area of ​​the first network device includes a first area, determine the identifier of at least one terminal device corresponding to the first area, and select an identifier from the identifiers of at least one terminal device as a second identifier.

[0576] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the mobility management entity and / or session management entity are functioning, in one possible implementation, the transceiver unit 1320 is used to send information indicating a second identifier.

[0577] In the steps performed by the core network described above, some steps may be performed by the mobility management entity and some steps may be performed by the session management entity. The steps performed by the mobility management entity and the steps performed by the session management entity may overlap or not overlap; or all of these steps may be performed by the session management entity; or all of these steps may be performed by the mobility management entity; or all of these steps may be performed by the mobility management entity and the session management entity.

[0578] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the user plane entity performs its function, in one possible implementation, the processing unit 1310 is used to obtain the first tunnel information and send the first message to the first network device through the transceiver unit 1320. The first message includes the first tunnel information.

[0579] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 When the user plane entity is used to perform its function in the method embodiment shown, in one possible implementation, the transceiver unit 1320 is used to receive information for indicating the first identifier.

[0580] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the user plane entity is functioning, in one possible implementation, the transceiver unit 1320 is used to receive a fourth message from the first network device.

[0581] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the user plane entity is functioning, in one possible implementation, the transceiver unit 1320 is used to send a second message to the first network device.

[0582] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the user plane entity is functioning, in one possible implementation, the transceiver unit 1320 is used to receive first tunnel information.

[0583] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the user plane entity is functioning, in one possible implementation, the transceiver unit 1320 is used to receive a third message from the first network device.

[0584] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the user plane entity is functioning, in one possible implementation, the processing unit 1310 is used to receive information indicating the location of the first terminal device through the transceiver unit 1320, and determine the first tunnel information based on the information indicating the location of the first terminal device and the correspondence between the first region and the first tunnel information.

[0585] When the communication device 1300 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method embodiment shown, when the user plane entity is functioning, in one possible implementation, the transceiver unit 1320 is used to send first tunnel information.

[0586] For a more detailed description of the processing unit 1310 and the transceiver unit 1320, please refer to [the relevant documentation]. Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 The relevant descriptions in the method embodiments shown.

[0587] like Figure 12 As shown, the communication device 1400 includes a processor 1410 and an interface circuit 1420. The processor 1410 and the interface circuit 1420 are coupled to each other. It is understood that the interface circuit 1420 can be a transceiver or an input / output interface. The transceiver includes a transmitter and a receiver; the transmitter can be used to send information, and the receiver can be used to receive information. Other functions can be implemented by the processor. The input / output interface is used to input and / or output information; output can be understood as sending, and input can be understood as receiving. Other functions can be implemented by the processor. Optionally, the communication device 1400 may also include a memory 1430 for storing instructions executed by the processor 1410, or storing input data required by the processor 1410 to execute instructions, or storing data generated after the processor 1410 executes instructions.

[0588] When the communication device 1400 is used to implement Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 In the method shown, the processor 1410 is used to implement the functions of the processing unit 1310, and the interface circuit 1420 is used to implement the functions of the transceiver unit 1320.

[0589] When the aforementioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal device in the above method embodiments. The terminal chip receives information from the base station, which can be understood as the information being first received by other modules in the terminal (such as an RF module or antenna), and then sent to the terminal chip by these modules. The terminal chip sends information to the base station, which can be understood as the information being first sent to other modules in the terminal (such as an RF module or antenna), and then sent to the base station by these modules.

[0590] When the aforementioned communication device is a chip applied to a base station, the base station chip implements the functions of the network device in the above method embodiments. The base station chip receives information from the terminal, which can be understood as the information being first received by other modules in the base station (such as an RF module or antenna), and then sent to the base station chip by these modules. The base station chip sends information to the terminal, which can be understood as the information being sent down to other modules in the base station (such as an RF module or antenna), and then sent to the terminal by these modules.

[0591] Based on the same concept, embodiments of this application provide a system that includes at least one of a mobility management entity, a session management entity, or a user plane entity.

[0592] In one possible implementation, the system further includes a first network device and / or a second network device.

[0593] In another possible implementation, the system also includes a terminal device.

[0594] Based on the same concept, embodiments of this application provide a chip system including at least one processor and an interface circuit. The interface circuit and the at least one processor are interconnected via a circuit. The processor executes a computer program (also referred to as code or instructions) to enable... Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 Any of the possible implementation methods in the document is executed.

[0595] Based on the same concept, embodiments of this application provide a computer program product, which includes: a computer program (also referred to as code or instructions), which, when run, causes the computer to execute... Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 Any of the possible implementations in [the document / concept].

[0596] Based on the same concept, embodiments of this application provide a computer-readable storage medium storing a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform... Figure 3 , Figure 6 , Figure 7 , Figure 8 , Figure 9 or Figure 10 Any of the possible implementations in [the document / concept].

[0597] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be access network device nodes or terminals, or modules within those nodes or terminals. Information transmission and reception can be between an access network device node and a terminal, such as between a base station and a terminal; between two access network device nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

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

[0599] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, compact disc read-only memory (CD-ROM), or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. The processor and storage medium can also exist as discrete components in a base station or terminal.

[0600] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer programs or instructions. When a computer program or instruction is loaded and executed on a computer, all or part of the processes or functions of the embodiments of this application are performed. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, a computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0601] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0602] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, or C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0603] It is understood that the various numbers involved in the embodiments of this application (such as the numerical numbers "first" and "second", and the letter numbers "A1, B1", "B1, B1", "C1, C2", etc.) are only for the convenience of description and are not intended to limit the scope of the embodiments of this application. The order of the above-mentioned process numbers does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, The method is applicable to a first network device or a chip in the first network device, and the method includes: Obtain first tunnel information, which is the tunnel information of the first network device. The first tunnel information is determined based on the correspondence between the first region and the first tunnel information, where the first region belongs to the signal coverage area of ​​the first network device. Based on the first tunnel information, a first message is received from the user plane entity, the first message including the first tunnel information; The information in the first message is sent to the first terminal device located in the first area.

2. The method as described in claim 1, characterized in that, The first area also includes a second terminal device; The method further includes: Based on the first tunnel information, a second message is received from the user plane entity, the second message including the first tunnel information; The information in the second message is sent to the second terminal device.

3. The method as described in claim 1 or 2, characterized in that, The first message also includes a first identifier of the first terminal device, which is used to indicate the first terminal device; Sending the information in the first message to the first terminal device located in the first area includes: Based on the first identifier, the information in the first message is sent to the first terminal device located in the first area.

4. The method according to any one of claims 1-3, characterized in that, The acquisition of the first tunnel information includes: The signal coverage area of ​​the first network device is determined to include the first region; The first tunnel information is determined based on the correspondence between the first region and the first tunnel information.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Send the first tunnel information.

6. The method according to any one of claims 1-3, characterized in that, The acquisition of the first tunnel information includes: Receive the first tunnel information.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: The location information of the first terminal device is sent, and the location information of the first terminal device is used to determine the first tunnel information.

8. The method according to any one of claims 1-7, characterized in that, Before obtaining the first tunnel information, the process also includes: Send a first indication message, which indicates that the first network device has not obtained the tunnel information of the first network device.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: If the signal coverage area of ​​the first network device does not include the first area, the first tunnel information shall be discontinued as the tunnel information of the first network device.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: Obtain the second identifier of the first terminal device, wherein the second identifier of the first terminal device is determined based on the correspondence between the first region and the second identifier; Information from the first terminal device is transmitted according to the second identifier.

11. A communication method, characterized in that, The method is applicable to mobility management entities, session management entities, chips within mobility management entities, or chips within session management entities, and the method includes: First information is obtained, which is used to indicate first tunnel information. The first tunnel information is the tunnel information of the first network device. The first tunnel information is determined according to the correspondence between the first area and the first tunnel information. The first area belongs to the signal coverage area of ​​the first network device. Send the first message.

12. The method as described in claim 11, characterized in that, The first information includes at least one of the following: the location information of the first terminal device, the information of the first area, or the information of the first tunnel, wherein the location of the first terminal device belongs to the first area.

13. The method as described in claim 11 or 12, characterized in that, Before obtaining the first information, the process also includes: The second information is obtained, and the first information is determined based on the second information. The second information includes at least one of the following: the location information of the first terminal device, the information of the first area, or the information of the first tunnel. The location of the first terminal device belongs to the first area.

14. The method according to any one of claims 11-13, characterized in that, Sending the first information includes: If the user plane entity has not obtained the first tunnel information, send the first information to the user plane entity.

15. The method according to any one of claims 11-14, characterized in that, The method further includes: Send a first identifier of the first terminal device to the user plane entity. The location of the first terminal device belongs to the first area. The first identifier is used to indicate the first terminal device. The first identifier is used to transmit information of the first terminal device between the user plane entity and the first network device.

16. The method according to any one of claims 11-15, characterized in that, The method further includes: Receive a first indication message, the first indication message being used to indicate that the first network device has not obtained tunnel information for the first area; Based on the first instruction information, the tunnel information of the first area is sent to the first network device.

17. The method according to any one of claims 11-16, characterized in that, The method further includes: Obtain the second identifier of the first terminal device, which is determined based on the correspondence between the first region and the second identifier, wherein the first terminal device is located in the first region; Information from the first terminal device is transmitted according to the second identifier.

18. A communication method, characterized in that, The method is applicable to user plane entities or chips within user plane entities, and the method includes: Obtain first tunnel information, which is the tunnel information of the first network device. The first tunnel information is determined based on the correspondence between the first region and the first tunnel information, where the first region belongs to the signal coverage area of ​​the first network device. Send a first message to the first network device, the first message including the first tunnel information.

19. The method as described in claim 18, characterized in that, The first message also includes a first identifier of the first terminal device, which is used to indicate the first terminal device.

20. The method as described in claim 19, characterized in that, The method further includes: Receive information indicating the first identifier.

21. The method according to any one of claims 18-20, characterized in that, The first area also includes a second terminal device; The method further includes: A second message is sent to the first network device, the second message including the first tunnel information.

22. The method according to any one of claims 18-21, characterized in that, The acquisition of the first tunnel information includes: Receive the first tunnel information.

23. A communication device, characterized in that, It includes modules for performing the method as described in any one of claims 1 to 10, or modules for performing the method as described in any one of claims 11 to 17, or modules for performing the method as described in any one of claims 18 to 22.

24. A communication device, characterized in that, It includes at least one processor, which implements the method of any one of claims 1 to 10, or the method of any one of claims 11 to 17, or the method of any one of claims 18 to 22, by means of logic circuits or by executing computer programs or instructions.

25. A communication system, characterized in that, It includes at least one of the following: a module for performing the method as described in any one of claims 11 to 17, or a module for performing the method as described in any one of claims 18 to 22.

26. The system as described in claim 25, characterized in that, The system further includes a module for performing the method as described in any one of claims 1 to 10.

27. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 10, or the method as described in any one of claims 11 to 17, or the method as described in any one of claims 18 to 22.

28. A computer program product, characterized in that, The computer program product stores a computer program, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the method as described in any one of claims 1 to 10, or the method as described in any one of claims 11 to 17, or the method as described in any one of claims 18 to 22.

Images