Disclosure of Invention
The embodiment of the application provides a communication method and a device thereof, which are used for realizing the establishment of communication connection between base stations.
In a first aspect, the present application provides a communication method, which may be performed by a first network device, or by another device comprising the functionality of the first network device, or by a system-on-chip (which may also be replaced by a chip) or other functional module, which is capable of implementing the functionality of the first network device, the system-on-chip or functional module being provided in the first network device, for example. The method is described by a first network device, and is implemented as an example, the first network device sends a first indication to a first terminal, wherein the first indication is used for indicating the identification of the first terminal, the identification of the first terminal is associated with the first network device, the first network device serves the first terminal, the first network device receives an establishment request from a second network device, the establishment request is used for requesting to establish a communication connection between the first network device and the second network device, the establishment request comprises the first indication, the second network device is combined with the first terminal, the first network device sends an establishment response to the second network device based on the first indication, and the establishment response is used for indicating that the communication connection between the first network device and the second network device is successfully established.
In this embodiment, a communication connection is allowed to be established between a network device co-located with the terminal (i.e. the first network device) and a network device serving the terminal (i.e. the second network device). And the communication connection between the first network device and the second network device can be established through the transmission of the first indication, namely the first network device transmits the first terminal, the first terminal transmits the second network device, and the second network device transmits the first indication to the first network device.
In one possible implementation, the first network device may determine that the first terminal and the second network device are co-located based on the first indication. For example, the first network device determines that the indication included in the establishment request is an indication that the first network device transmits to the terminal serving itself, determines that a communication connection between the first network device and the network device transmitting the establishment request (i.e., the second network device) can be established, and otherwise determines that a communication connection between the first network device and the network device transmitting the establishment request (i.e., the second network device) is not established.
In one possible implementation, a first network device may receive a second indication from a core network element, the second indication indicating that the first network device and the second network device serve the same public land mobile network PLMN, and the first network device sends the setup response to the second network device based on the first indication and the second indication.
In this implementation manner, the communication connection between network devices serving the same PLMN is defined, so that it can be ensured that parameters of the same PLMN are transmitted by both the first network device and the second network device in the process of establishing connection, and thus, after the first network device receives an establishment request from the second network device, the parameters carried in the establishment request can also be saved locally.
In one possible implementation, a first network device sends first configuration information to the first terminal, where the first configuration information is used for the first network device to establish a communication connection with the second network device, and then receives an establishment request from the second network device. The establishment request contains some parameters configured in the first configuration information, for example, the parameters include one or more of an identification (e.g., gNB ID) of the second network device, a tracking area identification (TRACKING AREA IDENTITY, TAI) list supported by the second network device, cell information supported by the second network device, AMF information to which the second network device may be connected, an identification (neighbor NG-RAN node list) of a neighboring cell device of the second network device, and the like. It is further noted that in the present technology, one device sends configuration information to another device in order that a communication connection may be established between the two devices, whereas in this embodiment configuration information for establishing a communication connection between two network devices is sent to a first terminal, which forwards the configuration information to a second network device.
In one possible implementation, the setup request further includes a third indication indicating that the second network device has mobility, and the first configuration information is determined based on the third indication. For example, when configuring a network device, configuration information sent to a conventional network device (herein conventional network device refers to a network device without mobility) may differ slightly in certain parameters from configuration information sent by a network device with mobility, e.g., the IP address of the first network device. The first network device may obtain that the second network device has mobility based on the third indication, for which case the first configuration information is determined, that is, the first configuration information sent to the second network device is associated with the third indication.
In one possible implementation, when the first network device no longer serves the first terminal, a fourth indication is sent to the second network device, the fourth indication being used to indicate that the communication connection between the first network device and the second network device is released.
In a second aspect, the present application provides a communication method, which may be performed by a second network device, or by another device comprising the functionality of the second network device, or by a system-on-chip (which may also be replaced by a chip) or other functional module, which is capable of implementing the functionality of the second network device, the system-on-chip or functional module being provided in the second network device, for example. The method is described by using a second network device as an example, the second network device obtains a first indication, the first indication is used for indicating the identification of the first terminal, the identification of the first terminal is associated with the first network device, the first network device serves the first terminal, the second network device sends an establishment request to the first network device, the establishment request is used for requesting to establish communication connection between the first network device and the second network device, the establishment request comprises the first indication, the second network device is combined with the first terminal, the second network device receives an establishment response from the first network device, and the establishment response is used for indicating that the communication connection between the first network device and the second network device is successfully established.
In one possible implementation, the second network device may further obtain first configuration information, where the first configuration information is from the first network device, and the first configuration information is used for the first network device to establish a communication connection with the second network device, and then send an establishment request to the first network device. The establishment request contains certain parameters configured in the first configuration information.
In one possible implementation, the setup request further includes a third indication indicating that the second network device has mobility, and the first configuration information is determined based on the third indication.
In one possible implementation, the second network device may also receive a fourth indication from the first network device, the fourth indication indicating to release the communication connection between the first network device and the second network device.
The effects of the second aspect may refer to the effects of the first aspect and will not be described in detail.
In a third aspect, the present application provides a communication method executable by a first network device, or by another device comprising the functionality of the first network device, or by a system-on-chip (which may also be replaced by a chip) or other functional module capable of implementing the functionality of the first network device, the system-on-chip or functional module being for example provided in the first network device. The method is described by taking an example of execution of first network equipment, wherein the first network equipment acquires information of an area where the network equipment allowing communication connection to be established with the first network equipment is located, the first network equipment receives an establishment request from second network equipment, the establishment request is used for requesting establishment of communication connection between the first network equipment and the second network equipment, the second network equipment has mobility, the first network equipment acquires position information of the second network equipment, and sends an establishment response to the second network equipment based on the position information of the second network equipment and the information of the area, and the establishment response is used for indicating that communication connection establishment between the first network equipment and the second network equipment is successful.
For example, before sending a setup response to the second network device, a first network device determines that the second network device is located in the area based on location information of the second network device and information of the area.
In this embodiment, one or more areas are configured for a first network device to limit the range of network devices having mobility that are capable of establishing a communication connection with the first network device, and when a second network device is in the configured area, a communication connection may be established between the first network device and the second network device.
In one possible implementation manner, the establishment request includes an identifier of the first terminal, the first terminal and the second network device are combined, and the first network device can acquire the location information of the second network device based on the identifier of the first terminal. For example, the first network device acquires location information of the first terminal from a core network registered with the first terminal.
In one possible implementation, the establishment request includes a first indication indicating that the second network device has mobility, and the first network device obtains location information of the second network device based on the first indication and an identification of the first terminal. It is also understood that the first network device triggers the acquisition of the location information of the second network device based on the first indication.
In one possible implementation, the establishment request includes location information of the second network device, and the first network device obtains the location information of the second network device in the establishment request.
In a fourth aspect, the present application provides a communication method, which may be performed by a second network device, or by another device comprising the functionality of the second network device, or by a system-on-chip (which may also be replaced by a chip) or other functional module, which is capable of implementing the functionality of the second network device, the system-on-chip or functional module being provided in the second network device, for example. The method is described by taking an example of execution of the second network device, wherein the second network device sends an establishment request to the first network device, the establishment request is used for requesting establishment of a communication connection between the first network device and the second network device, the second network device has mobility, the establishment request comprises identification of a first terminal or location information of the second network device, the identification of the first terminal can be used for determining the location information of the second network device, the location information of the second network device is used for determining whether the first network device and the second network device can establish the communication connection, the second network device receives an establishment response from the first network device, and the establishment response is used for indicating that the communication connection between the first network device and the second network device is successfully established.
In one possible implementation, the establishment request includes a first indication indicating that the second network device has mobility.
The effects of the fourth aspect may refer to the effects of the third aspect and will not be described in detail.
In a fifth aspect, the present application provides a communication method, which may be performed by a first network device, or by another device comprising the functionality of the first network device, or by a system-on-chip (which may also be replaced by a chip) or other functional module, which is capable of implementing the functionality of the first network device, the system-on-chip or functional module being provided in the first network device, for example. The method is described by taking an example of execution of a first network device, wherein the first network device receives an establishment request from a second network device, the establishment request is used for requesting establishment of a communication connection between the first network device and the second network device, the establishment request comprises identification of a first terminal or position information of the second network device, the second network device is combined with the first terminal, the second network device has mobility, the first network device sends the identification of the first terminal or the position information of the second network device to an operation management and maintenance function entity (OAM), the identification of the first terminal or the position information of the second network device is used for determining whether establishment of the communication connection between the first network device and the second network device is allowed, the first network device receives a first indication from the OAM, the first indication is used for indicating establishment of the communication connection between the first network device and the second network device is allowed, and the first network device sends an establishment response to the second network device, and the establishment response is used for successfully establishing the communication connection between the first network device and the second network device.
In this embodiment, it is determined by the location information of the second network device whether a communication connection can be established between the first network device and the second network device.
In one possible implementation, the first network device may also send a second indication to the OAM, the second indication indicating that a communication connection between the first network device and the second network device has been established.
In one possible implementation, the first network device may further receive a third indication from the OAM, the third indication indicating to release the communication connection between the first network device and the second network device, and the first network device sends a fourth indication to the second network device, the fourth indication indicating to release the communication connection between the first network device and the second network device.
In a sixth aspect, the present application provides a communication method that may be performed by OAM, or by other devices including OAM functions, or by a chip system (which may also be replaced by a chip) or other functional modules capable of implementing OAM functions, for example, provided in OAM. The method is described by taking OAM execution as an example, the OAM receives an identification of a first terminal of a first network device or position information of a second network device, wherein the second network device is combined with the first terminal and has mobility, and the OAM sends a first indication to the first network device based on the identification of the first terminal or the position information of the second network device, wherein the first indication is used for indicating that communication connection between the first network device and the second network device is allowed to be established.
For example, the OAM determines that the second network device is located in a set area associated with the first network device based on location information of the second network device before sending the first indication to the first network device.
In this embodiment, it is determined by the location information of the second network device whether a communication connection can be established between the first network device and the second network device.
In one possible implementation, the OAM may further obtain location information of the second network device based on the identification of the first terminal, determine that the communication connection between the first network device and the second network device is allowed to be established based on the location information of the second network device, or determine that the communication connection between the first network device and the second network device is allowed to be established based on the location information of the second network device before sending the first indication to the first network device.
In one possible implementation, the OAM may also receive a second indication from the first network device indicating that a communication connection between the first network device and the second network device has been established.
In one possible implementation, the OAM may also send a third indication to the first network device, the third indication indicating to release the communication connection between the first network device and the second network device. For example, the OAM determines that the second network device is moving beyond a set threshold, so the communication connection between the first network device and the second network device needs to be released.
In a seventh aspect, the present application provides a communication method, which may be performed by a first network device, or by another device comprising the functionality of the first network device, or by a system-on-chip (which may also be replaced by a chip) or other functional module, which is capable of implementing the functionality of the first network device, the system-on-chip or functional module being provided in the first network device, for example. The method is described by taking an example of execution of first network equipment, wherein the first network equipment receives first configuration information, the first configuration information comprises identification of at least one cell, the first network equipment receives an establishment request from second network equipment, the establishment request is used for requesting establishment of communication connection between the first network equipment and the second network equipment, the establishment request comprises identification of the first cell, the identification of the first cell belongs to the identification of the at least one cell, the second network equipment has mobility, and the first network equipment sends an establishment response to the second network equipment, wherein the establishment response is used for indicating that the communication connection between the first network equipment and the second network equipment is successfully established.
In this embodiment, the identity of the cell is configured for the first network device. And comparing the cell identifier carried in the establishment request with the cell identifier configured in the first network device to determine whether the network device (namely the second network device) sending the establishment request and the first network device can establish communication connection.
In one possible implementation, the first network device may further receive an identity of a second cell from the second network device after sending the setup response to the second network device, the identity of the second cell not belonging to the identity of the at least one cell, and send a first indication to the second network device, the first indication being used to indicate that the communication connection between the first network device and the second network device is released. In this implementation, the second network device updates the cell, but the updated cell is not within the cell configured by the first network device, so the communication connection between the first network device and the second network device needs to be released.
In one possible implementation, the first network device sends a second indication to the second network device, where the second indication is used to instruct the first network device to periodically report the identity of the cell.
In an eighth aspect, the present application provides a communication method, which may be performed by a second network device, or by another device comprising the functionality of the second network device, or by a system-on-chip (which may also be replaced by a chip) or other functional module, which is capable of implementing the functionality of the second network device, the system-on-chip or functional module being provided in the second network device, for example. The method is described by a second network device, and is implemented by the second network device, wherein the second network device acquires an identifier of a first cell, the second network device sends an establishment request to the first network device, the establishment request is used for requesting to establish communication connection between the first network device and the second network device, the establishment request comprises the identifier of the first cell, the second network device has mobility, and the first network device sends an establishment response to the second network device, wherein the establishment response is used for indicating that the communication connection between the first network device and the second network device is successfully established.
In this embodiment, the identity of the cell is configured for the first network device. And comparing the cell identifier carried in the establishment request with the cell identifier configured in the first network device to determine whether the network device (namely the second network device) sending the establishment request and the first network device can establish communication connection.
In one possible implementation, after the second network device establishes a communication connection with the first network device, the second network device moves and then receives the identifier of the second cell, and the second network device sends the identifier of the second cell to the first network device, where the second network device receives a first indication from the first network device, where the first indication is used to indicate that the communication connection between the first network device and the second network device is released. In this implementation, the second network device updates the cell, but the updated cell is not within the cell configured by the first network device, so the communication connection between the first network device and the second network device needs to be released.
In one possible implementation, the second network device receives a second indication from the first network device, the second indication indicating that the first network device periodically reports an identity of the cell.
In a ninth aspect, the present application provides a communication method, which is executable by a second network device, or by another device comprising the functionality of the second network device, or by a system-on-chip (which may also be replaced by a chip) or other functional module, which is capable of implementing the functionality of the second network device, the system-on-chip or functional module being provided in the second network device, for example. The method is described by taking an example of execution of second network equipment, wherein the second network equipment receives first configuration information, the first configuration information comprises information of at least one authorized network equipment, information of at least one area and a mapping relation of the information, the authorized network equipment at least comprises first network equipment, the second network equipment has mobility, the second network equipment determines that the second network equipment is in a first area based on the current position of the second network equipment, the first area belongs to the at least one area, the first area corresponds to first network equipment, the first network equipment belongs to the at least one authorized network equipment, the second network equipment sends a first establishment request to the first network equipment based on the information of the first network equipment, the first establishment request is used for requesting to establish communication connection between the first network equipment and the second network equipment, and the second network equipment receives a first establishment response from the first network equipment, and the first establishment response is used for indicating successful establishment of the communication connection between the first network equipment and the second network equipment.
In this embodiment, the second network device determines with which network devices a communication connection can be established based on the area in which the location of the second network device is located.
In one possible implementation manner, the first configuration information further includes an identifier of a cell corresponding to the authorized network device, and the first establishment request includes an identifier of a first cell, where the first cell corresponds to the first network device.
In one possible implementation, a second network device may also determine that the second network device is currently moving out of the first area and then send a first indication to the first network device, the first indication indicating that a communication connection between the first network device and the second network device is released.
In one possible implementation manner, after the second network device sends the first indication to the first network device, the second network device may also send a second establishment request to a third network device, where the second establishment request is used to request to establish a communication connection between the first network device and the third network device, and the third network device belongs to the authorized network device, and the second network device receives a second establishment response from the third network device, where the second establishment response is used to indicate that the communication connection between the first network device and the third network device is successfully established.
In a tenth aspect, a communication apparatus is provided, which may be the first network device described in the above aspects. The communication device has the function of the first network device. The communication means are for example functional modules in the first network device, such as baseband means or a system on chip or the like. Or the communication means may be a second network device as described in the above aspects. The communication device has the function of the second network device. The communication means are for example functional modules in the second network device, such as baseband means or a system-on-chip or the like. Or the communication device may be OAM as described in the sixth aspect above. The communication device has the function of OAM. The communication device is, for example, a functional module in OAM, such as a baseband device or a system on chip, etc.
In an alternative implementation, the communication device includes a baseband device and a radio frequency device. In another alternative implementation, the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module). The transceiver unit can realize a transmission function and a reception function, and may be referred to as a transmission unit (sometimes referred to as a transmission module) when the transceiver unit realizes the transmission function, and may be referred to as a reception unit (sometimes referred to as a reception module) when the transceiver unit realizes the reception function. The transmitting unit and the receiving unit may be the same functional module, which is called a transceiver unit, which can implement the transmitting function and the receiving function, or the transmitting unit and the receiving unit may be different functional modules, and the transceiver unit is a generic term for these functional modules.
In a possible implementation manner, the communication apparatus further includes a storage unit (sometimes referred to as a storage module), where the processing unit is configured to couple to the storage unit and execute a program or an instruction in the storage unit, and enable the communication apparatus to perform a function of the first network device described in the foregoing aspects, or perform a function of the second network device described in the foregoing aspects, or perform a function of the OAM described in the sixth aspect.
In an eleventh aspect, a communications apparatus is provided that includes an interface circuit and a processor, and optionally, a memory. Wherein the memory is configured to store a computer program, and the processor is coupled to the memory and the interface circuit, and when the processor reads the computer program or instructions, the processor causes the communication device to perform the method performed by the first network device in the above aspects, or perform the method performed by the second network device in the above aspects, or perform the method performed by the OAM in the above sixth aspect. The interface circuit is for receiving signals from or transmitting signals from other communication devices than the communication device to the processor, and the processor is for implementing the method performed by the first network device in each of the above aspects, or for implementing the method performed by the second network device in each of the above aspects, or for implementing the method performed by OAM in each of the above sixth aspects, by logic circuits or executing code instructions.
In one possible implementation, the communication device is a chip or a system-on-chip.
In a twelfth aspect, there is provided a communication apparatus comprising a processor, optionally further comprising a memory, the processor and the memory being coupled, the memory being configured to store a computer program or instructions, the processor being configured to execute a part or all of the computer program or instructions in the memory, and when executed, to implement the functions of the first network device in each of the aspects described above, or to implement the functions of the second network device in each of the aspects described above, or to implement the functions of OAM in each of the sixth aspects described above.
In a possible implementation manner, the apparatus may further include a transceiver, where the transceiver is configured to send the signal processed by the processor, or receive the signal input to the processor. The transceiver may perform the sending or receiving actions performed by the first network device in each aspect, or performed by the second network device in each aspect, or performed by the OAM in the sixth aspect.
In a possible implementation manner, the processing unit in the tenth aspect may be implemented by the processor, the storage unit in the tenth aspect may be implemented by the memory, and the transceiver unit in the tenth aspect may be implemented by the transceiver.
In one possible implementation, the communication device is a chip or a system-on-chip.
In a thirteenth aspect, there is provided a communication system comprising the first network device of the first aspect and the second network device of the second aspect, or the communication system comprising the first network device of the third aspect and the second network device of the fourth aspect, or the communication system comprising the first network device of the seventh aspect and the second network device of the eighth aspect. For example, the first network device and the second network device may be implemented by the communication apparatus described in the tenth aspect.
In a fourteenth aspect, there is provided a computer readable storage medium storing a computer program or instructions which, when executed, cause the method of the above aspects to be carried out.
In a fifteenth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the method of the above aspects to be carried out.
Detailed Description
The technical scheme of the application can be applied to a ground network (TERRESTRIAL NETWORK, TN) and a non-ground network (non terrestrial network, NTN), such as a satellite network. The technical solution of the present application may be applied to various wireless communication systems, may be applied to, but not limited to, a fourth generation mobile communication technology (the 4th generation,4G) system (also referred to as a long term evolution (long term evolution, LTE) system), a fifth generation mobile communication technology (the 5th generation,5G) system (also referred to as a New Radio (NR) system), or may also be applied to a next generation mobile communication system or other similar communication system (for example, the sixth generation mobile communication technology (the 6th generation,6G) system), etc., and is particularly not limited. In addition, the technical scheme of the application can be applied to device-to-device (D2D) scenes, such as NR-D2D scenes and the like, or can be applied to V2X scenes, such as NR-V2X scenes and the like. The technical scheme of the application can also be applied to the fields of intelligent driving, auxiliary driving, intelligent network connection, factory manufacturing scenes and the like.
For example, fig. 1a is a schematic diagram of a 5G communication system architecture to which the present application may be applied. Specifically, fig. 1a is a schematic diagram of a 5G network architecture based on a server architecture. For example, fig. 1b is a schematic diagram of another 5G communication system architecture to which the present application may be applied. Specifically, fig. 1b is a schematic diagram of a point-to-point based 5G architecture. The main difference between fig. 1a and fig. 1b is that the interfaces between the individual network elements in fig. 1a are servitized interfaces and the interfaces between the individual network elements in fig. 1b are point-to-point interfaces.
The 5G network architecture shown in fig. 1a and 1b may include a terminal device portion, an access network portion, and a core network portion. Optionally, a Data Network (DN) and an application function (application function, AF) network element part are also included. The terminal accesses a core network through an access network, and the core network communicates with DN or AF. The following provides a brief description of the functionality of some of the network elements.
The terminal device (TERMINAL DEVICE), which may be referred to as a User Equipment (UE), is a device with a wireless transceiving function, and may be deployed on land, including indoor or outdoor, handheld or vehicle-mounted, on water (such as a ship, etc.), or in air (such as an airplane, a balloon, a satellite, etc.). The terminal device may be a mobile phone, a tablet computer (pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (SELF DRIVING), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (SMART GRID), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (SMART CITY), a wireless terminal in smart home (smart home), or the like.
The (R) AN device in the present application is a device for providing a wireless communication function for a terminal device, and is also referred to as AN access network device. The RAN equipment in the present application includes, but is not limited to, next generation base stations (G nodeB, gNB), evolved node bs (eNB), radio network controllers (radio network controller, RNC), node Bs (NB), base station controllers (base station controller, BSC), base transceiver stations (base transceiver station, BTS), home base stations (e.g., home evolved nodeB, or home node B, HNB), baseband units (baseBand unit, BBU), transmission points (TRANSMITTING AND RECEIVING point, TRP), transmission points (TRANSMITTING POINT, TP), mobile switching centers, and the like in 5G. The names of base station-capable devices may vary in systems employing different radio access technologies, for example, in fifth generation (5th generation,5G) systems, referred to as RAN or gNB (5 GNodeB), in LTE systems, referred to as evolved NodeB (eNB or eNodeB), in third generation (3rd generation,3G) systems, referred to as NodeB (Node B), etc.
The data network DN can be used for deploying various services and can provide data and/or voice services for the terminal equipment. For example, the DN is a private network of an intelligent plant, the sensors installed in the plant of the intelligent plant may be terminal devices, the sensors and control servers are deployed in the DN, and the control servers may serve the sensors. The sensor may communicate with the control server, obtain instructions from the control server, transmit collected sensor data to the control server, etc., according to the instructions. For another example, DN is an internal office network of a company, where a mobile phone or a computer of an employee of the company may be a terminal device, and the mobile phone or the computer of the employee may access information, data resources, etc. on the internal office network of the company.
Application network elements, mainly supporting interactions with the third generation partnership project (3rd generation partnership project,3GPP) core network to provide services, such as influencing data routing decisions, policy control functions or providing some services of third parties to the network side. In a 5G communication system, the application network element may be an application function (application function, AF) network element. In future communication systems, the application network element may still be an AF network element, or may have other names, which is not limited by the present application.
The core network portion may include one or more of the following network elements:
The access management network element (may also be referred to as a mobility management network element) is a control plane network element provided by the operator network and is responsible for access control and mobility management of the terminal device accessing the operator network, for example, including mobility state management, allocation of a temporary identity of a user, authentication, user and other functions. In a 5G communication system, the access management network element may be an access and mobility management function (ACCESS AND mobility management function, AMF) network element. In future communication systems, the access management network element may still be an AMF network element, or may have other names, which is not limited by the present application.
Session management network element is mainly responsible for session management in mobile network, such as session establishment, modification and release. Specific functions include assigning an IP address to a user, selecting a user plane network element that provides a message forwarding function, and the like. In a 5G communication system, the session management network element may be a session management function (session management function, SMF) network element. In future communication systems, the session management network element may still be an SMF network element, or may have other names, which is not limited by the present application.
And the user plane network element is responsible for forwarding and receiving user data in the terminal equipment. The user plane network element can also receive the user data from the terminal equipment through the access network equipment and forward the user data to the data network. The transmission resources and scheduling functions in the user plane network element that serve the terminal device are managed and controlled by the SMF network element. In a 5G communication system, the user plane network element may be a user plane function (user plane function, UPF) network element. In future communication systems, the user plane network element may still be a UPF network element, or may have other names, which is not limited by the present application.
And the data management network element is used for generating authentication credentials, user identification processing (such as storing and managing the permanent identity of a user and the like), access control, subscription data management and the like. In a 5G communication system, the data management network element may be a unified data management (unified DATA MANAGEMENT, UDM) network element. In future communication systems, the unified data management may still be a UDM network element, or may have other names, which is not limited by the present application.
The data storage network element is responsible for storing structured data information, including subscription information, policy information, and network data or service data defined by a standard format. In a 5G communication system, the data storage network element may be a unified data store (unified data repository, UDR). In future communication systems, the network element with the network opening function may still be a UDR network element, or may have other names, which is not limited by the present application.
The policy control network element mainly supports providing a unified policy framework to control network behavior, provides policy rules for a control layer network function, and is responsible for acquiring user subscription information related to policy decision. In the 4G communication system, the policy control network element may be a Policy and Charging Rules Function (PCRF) network element. In a 5G communication system, the policy control element may be a policy control function (policy control function, PCF) element. In future communication systems, the policy control network element may still be a PCF network element, or may have other names, which is not limited by the present application.
The network storage network element can be used for providing a network element discovery function and providing network element information corresponding to the network element type based on the requests of other network elements. NRF also provides network element management services such as network element registration, update, deregistration, and network element state subscription and push. In a 5G communication system, the network storage element may be a network registration function (network repository function, NRF) element. In future communication systems, the network storage network element may still be an NRF network element, or may have other names, which is not limited by the present application.
A network opening function network element may be used to provide a method for securely opening services and capabilities provided by a 3GPP network function device to the outside, etc. In a 5G communication system, the network open function network element may be a network open function (network exposure function, NEF) network element. In future communication systems, the network element with the network open function may be a NEF network element, or may have other names, which is not limited by the present application.
The network slice selection function network element can be used for selecting a proper network slice for the service of the terminal. In a 5G communication system, the network slice selection network element may be a network slice selection function (network slice selection function, NSSF) network element. In future communication systems, the network element with the network opening function may be NSSF network elements, or may have other names, which is not limited by the present application.
The network data analysis function element may collect data from various Network Functions (NF), such as policy control element, session management element, user plane element, access management element, application function element (through network capability open function element), and analyze and predict. In a 5G communication system, the network data analysis network element may be a network data analysis function (network DATA ANALYTICS function, NWDAF). In future communication systems, the network data analysis function element may be NWDAF network elements, or may have other names, which is not limited by the present application.
It will be appreciated that the network elements or functions described above may be either network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). In one possible implementation manner, the network element or the function may be implemented by one device, or may be implemented by a plurality of devices together, or may be a functional module in one device, which is not specifically limited by the embodiment of the present application.
As shown in fig. 2, a schematic diagram of a communication architecture of a mobile base station (mobile gNB WITH WIRELESS ACCESS backhauling, MWAB) device with wireless access backhaul capability is presented, wherein a MWAB device can be deployed on a moving vehicle or other object, a MWAB device is composed of a gNB and a UE, and a gNB in a MWAB device can be referred to as MWAB-gNB, a UE in a MWAB device can be referred to as MWAB-UE, and MWAB-gNB and MWAB-UE have mobility in order to distinguish from a conventional base station (a base station fixed on the ground) and a conventional UE (a UE not collocated with the base station). Wherein MWAB-UE has the function of conventional UE and can be connected with a core network. The N2/N3 backhaul link between the conventional gNB and the core network can be realized through an optical fiber, the N2/N3 backhaul link between the MWAB-gNB with mobility and the core network can be borne on PDU session between MWAB-UE and the core network, and wireless backhaul is realized, so that MWAB-gNB can provide wireless access for other UEs nearby the vehicle.
MWAB-the UE may access the core network through a base station (e.g., a donor-gNB) on the off-board floor and establish a PDU session between MWAB-the UE and the UPF (e.g., UPF #1 in fig. 2). N2 messaging between MWAB-gNB and AMF (e.g., AMF#2 in FIG. 2) is accomplished through PDU sessions between MWAB-UE and UPF. For example, when MWAB-gNB needs to send an N2 message to amf#2, MWAB-gNB forwards the N2 message to MWAB-UE through an internal interface between MWAB-gNB and MWAB-UE, MWAB-UE transfers the N2 message as a payload (payload) of a data packet to an anchor UPF (e.g., upf#1 in fig. 2) of the PDU session through an already established PDU session, and the anchor UPF forwards the data packet to amf#2 to complete the forwarding of the N2 message. N3 messaging between MWAB-gNB and UPF (e.g., UPF #2 in FIG. 2) can also be achieved through PDU sessions between MWAB-UE and UPF. For example, when MWAB-gNB needs to send an N3 message to UPF#2, MWAB-gNB forwards the N3 message to MWAB-UE through an internal interface with MWAB-UE, MWAB-UE transfers the N3 message as a load of a data packet to an anchor UPF (which may be UPF#1 in FIG. 2 or other UPF, without limitation) of the PDU session through an already established PDU session, and the anchor UPF forwards the data packet to UPF#2, thereby completing the forwarding of the N3 message.
The application provides a plurality of communication modes, and realizes the communication connection of the network equipment with mobility and other network equipment (which can be the network equipment with mobility or the conventional network equipment without mobility).
In the following, some terms or concepts in the embodiments of the present application are explained for easy understanding by those skilled in the art.
The first network device is a network device where the first terminal is currently resident, i.e. a network device currently serving the first terminal. The first network device may be a conventional network device, and in the present application, the conventional network device refers to a network device that has no mobility and is not co-located with a terminal. For example, the first network device is a base station in fig. 2, e.g., a donor-gNB. Or the first network device may also be a network device with mobility, e.g., the second network device is a MWAB-gNB device, or MWAB device.
The second network device is integrated with the first terminal, and the first terminal is capable of moving, so the second network device has mobility. For example, the first terminal is MWAB-UE in fig. 2, and the second network device is MWAB-gNB in fig. 2.
In addition, the first terminal may establish a protocol data unit (protocol data unit, PDU) session (session) for accessing the first network device, and interactions between the first network device and the second network device may be carried on a user plane path of the PDU session. For example, the establishment request sent by the second network device to the first network device may be delivered to the first network device through the user plane path of the PDU session. For another example, the setup response, the configuration information, and various indication information sent by the first network device to the second network device may be transmitted to the second network device through the user plane path of the PDU session.
In addition, the first terminal and the second network device are combined together and can be regarded as an integral device, in all embodiments of the present application, the interaction between the first terminal and the first network device can be replaced by the interaction between the integral device and the first network device, the interaction between the second network device and the first network device can be replaced by the interaction between the integral device and the first network device, and the integral device can be MWAB devices.
The communication connection established between the first network device and the second network device is an Xn connection.
In order to better describe the embodiments of the present application, the method provided by the embodiments of the present application is described below with reference to the accompanying drawings. In the drawings corresponding to the embodiments of the present application, the steps indicated by the broken lines are optional steps unless specifically described below.
Fig. 3 is a schematic diagram of a communication flow provided in an embodiment of the present application, including the following steps:
Step 301, a first network device sends a first indication to a first terminal, and the first terminal receives the first indication correspondingly, wherein the first indication is used for indicating the identification of the first terminal, and the identification of the first terminal is associated with the first network device.
The identifier of the first terminal is a terminal identifier of an air interface side, and the identifier of the first terminal is a unique identifier of the first terminal in the first network device, for example, the first indication is RRC-Transaction Identifier. Optionally, during the interaction of the first network device with the second network device, the first terminal is always in the RRC connected state, so that the first network device maintains RRC-Transaction Identifier.
In one possible example, the first terminal may obtain the identity of the first terminal through an RRC establishment procedure of the first terminal with the first network device. For example, before step 301, the first terminal sends an RRC establishment request to the first network device to request establishment of an RRC connection between the first terminal and the first network device, the first network device sends an RRC establishment response to the first terminal, where the RRC establishment response is used to indicate that establishment of an RRC connection between the first terminal and the first network device is successful, and the RRC establishment response includes the first indication.
In a possible example, before step 301, the first terminal may further send indication information to the first network device, where the indication information is used to indicate that the first terminal is a terminal device co-located with the second network device, or that the first terminal is a terminal of MWAB devices. For example, the indication information is carried in an RRC setup request. Further, the first network device determines a first indication to send to the first terminal based on the indication information.
Step 302, the first terminal sends the first indication to the second network device, and correspondingly, the second network device receives the first indication from the first terminal.
The first terminal is co-located with the second network device and the transmitting and receiving of step 302 refers to transmitting and receiving through an internal interface between the first terminal and the second network device.
Step 303, the second network device sends an establishment request to the first network device, and correspondingly, the first network device receives an establishment request from the second network device, wherein the establishment request is used for requesting to establish communication connection between the first network device and the second network device, and the establishment request comprises the first indication.
In addition, the establishment request message may include, in addition to the first indication, one or more parameters including a type (MESSAGE TYPE) of the establishment request message, an identity (e.g., gNB ID) of the second network device, a tracking area identity (TRACKING AREA IDENTITY, TAI) list supported by the second network device, cell information supported by the second network device, information of AMFs to which the second network device may be connected, and an identity (neighbor NG-RAN node list) of a neighbor device of the second network device. For example, the type of the SETUP REQUEST message is XN SETUP REQUEST.
Step 304, the first network device sends an establishment response to the second network device, and the second network device receives the establishment response correspondingly, wherein the establishment response is used for indicating that the communication connection between the first network device and the second network device is successfully established.
The setup response may further include one or more parameters including a type of setup response message (MESSAGE TYPE), an identity of the first network device (e.g., gNB ID), a TAI list supported by the first network device, cell information supported by the first network device, AMF information to which the first network device may be connected, and an identity of a neighbor NG-RAN node list of the first network device. For example, the type of setup response message is XN SETUP RESPONSE.
The first network device may send a setup response to the second network device based on the first indication. For example, the first network device determines that the indication included in the establishment request is an indication that the first network device transmits to the terminal serving itself, determines that a communication connection between the first network device and the network device transmitting the establishment request (i.e., the second network device) can be established, and otherwise determines that a communication connection between the first network device and the network device transmitting the establishment request (i.e., the second network device) is not established.
In this embodiment, it may be defined that the terminal will send an RRC-transmission indication from the resident network device to the network device collocated with itself, and not to the network device not collocated with itself.
In this embodiment, a communication connection is allowed to be established between a network device co-located with the terminal (i.e. the first network device) and a network device serving the terminal (i.e. the second network device). And the communication connection between the first network device and the second network device can be established through the transmission of the first indication, namely the first network device transmits the first terminal, the first terminal transmits the second network device, and the second network device transmits the first indication to the first network device.
In one possible implementation, a communication connection may be established between network devices serving the same public land mobile network (public land mobile network, PLMN), so that it may be ensured that, during the connection establishment process, the first network device and the second network device both transmit parameters of the same PLMN, and thus, after the first network device receives an establishment request from the second network device, the parameters carried in the establishment request may also be saved to the local area. If a communication connection is established between network devices serving different PLMNs, network devices from different PLMNs may not understand the parameters communicated during the establishment of the connection, resulting in meaningless establishment procedures for the communication connection. For example, the setup request message carries a TAI list supported by the first network device, where the TAI is composed of a PLMN ID and a tracking area code (TRACKING AREA code, TAC), where the PLMN ID is a combination of a mobile country code (mobile country code, MCC) and a mobile network number (mobile network code, MNC), and is a unique code allocated to each operator. If the first network device serves PLMN #1 and the second network device serves PLMN #2, then when the setup request message carries the TAI list supported by the first network device (which TAI is assigned by PLMN # 1), the second network device does not belong to PLMN #1 and does not understand the TAI list supported by the first network device, so that it is not meaningful for the network devices between two different PLMNs to make a connection. Based on this, the core network element may send a second indication to the first network device before step 304 (sending a setup response to the second network device), and the first network device may receive a second indication from the core network element, the second indication being used to indicate that the first network device and the second network device serve the same PLMN, respectively, such that in step 304 the first network device may send a setup response to the second network device based on the first indication and the second indication. If the first network device receives an indication that the first network device and the second network device serve different PLMNs, a response indicating that the establishment was successful is not sent to the second network device.
Before step 303 (the first network device receives the establishment request from the second network device), the first network device may configure parameters required for the first network device to establish a communication connection with the second network device to the second network device through the first terminal. In one possible implementation manner, a first network device sends first configuration information to a first terminal, and the first terminal receives the first configuration information correspondingly, where the first configuration information is used for establishing communication connection between the first network device and the second network device. The first terminal sends the first configuration information to the second network device, which may then receive the first configuration information, and may then perform step 303 (sending an establishment request to the second network device) based on the first configuration information, the first configuration information comprising parameters required by the second network device to establish a communication connection with the first network device, including, but not limited to, one or more of an identification of the second network device (e.g., a gNB ID), an IP address of the second network device, a TAI list supported by the second network device, cell information supported by the second network device, an AMF to which the second network device may be connected, an identification of the first network device, an IP address of the first network device.
In configuring the network device, configuration information sent to a regular network device (here, the regular network device refers to a network device not together with the terminal) and configuration information sent to an irregular network device (here, the irregular network device refers to a network device together with the terminal) may be slightly different in some parameters, for example, an IP address (e.g., IP address # 1) of the first network device required for the regular network device to establish a communication connection with the first network device may be different from an IP address (e.g., IP address # 2) of the first network device required for the network device having mobility to establish a communication connection with the first network device. The first indication is included in the setup request of step 303, which is sent by the first network device to the first terminal, which is again acquired by the first network device at the second network device, on the basis of which the first network device knows that the second network device is co-located with the first terminal, for which case the first configuration information is determined, that is to say the first configuration information sent to the second network device is associated with the first indication.
In one possible example, the second network device may inform the first network device that the second network device has mobility. Illustratively, the setup request of step 303 includes a third indication indicating that the second network device has mobility. In configuring a network device, configuration information sent to a conventional network device (herein conventional network device refers to a network device without mobility) may be slightly different from configuration information sent by a network device with mobility in some parameters, for example, the IP address of the first network device is different. The first network device may obtain that the second network device has mobility based on the third indication, for which case the first configuration information is determined, that is, the first configuration information sent to the second network device is associated with the third indication.
Referring to fig. 3 and related content, as shown in fig. 4, a flowchart of a specific communication method is further described, which includes the following steps:
Step 400a, configuring PLMN information served by the second network device in the second network device.
For example, the PLMN served by the second network device may be a PLMN broadcast by the second network device. For example, the PLMN information includes a PLMN ID.
And step 400b, the second network equipment sends PLMN information served by the second network equipment to the first terminal through the internal interface.
Step 401, the first terminal sends an RRC setup request to the first network device (RRC setup request), and correspondingly, the first network device receives an RRC setup request, where the RRC setup request is used to request establishment of an RRC connection between the first terminal and the first network device.
Optionally, in the RRC setup request message, indication information indicating the type of the first terminal device may be further included. For example, the indication information indicates that the first terminal is co-located with the second network device or that the first terminal is a terminal of MWAB devices. Optionally, in the RRC setup request message, PLMN information served by the second network device, such as PLMN ID, may also be included.
Step 402, the first network device sends an RRC setup response (RRC setup response) to the first terminal, and correspondingly, the first terminal receives an RRC setup response, where the RRC setup response is used to indicate that the RRC connection between the first terminal and the first network device is established successfully, and the RRC setup response includes RRC-Transaction Identifier (i.e., the first indication described above).
The order of steps 400b, 401, 402 is not limited.
In step 403a, the first terminal sends a registration request to the first network device.
Optionally, the registration request includes the PLMN served by the second network device in step 400 b.
Step 403b, the first network device sends the registration request to an access management network element (for example, AMF), and the access management network element receives the registration request correspondingly. The registration request is a NAS message and the first network device transparently passes the registration request.
Step 404, the access management network element obtains subscription information of the first terminal from the data management network element (for example, UDM), and determines whether the first terminal is authorized successfully based on the subscription information.
The subscription information of the first terminal includes the type of the first terminal, such as a terminal of MWAB devices.
The subscription information of the first terminal also includes information for authorizing the area where the first terminal is located.
In this example, the first terminal authorization success is described as an example. The successful authorization here means that the first terminal is allowed to register in the current network or the first terminal device is allowed to act as a terminal (MWAB operation allowed) for the MWAB devices.
Step 405, the access management network element sends an N2 message to the first network device, and correspondingly, the first network device receives the N2 message, where the N2 message includes a registration accept response. Optionally, the N2 message further comprises an indication that the first terminal authorization is successful.
Optionally, the N2 message further includes an indication (i.e., the second indication described above) that the first network device and the second network device serve the same PLMN. If the registration request includes the PLMN served by the second network device, the access management network element may obtain the PLMN served by the second network device from the registration request, and the access management network element may also obtain the PLMN served by the first network device, where the access management network element determines whether the two PLMNs are the same by comparing the two PLMNs. If the two PLMNs are the same, the N2 message may further include an indication that the first network device and the second network device serve the same PLMN (i.e., the second indication described above), and if the two PLMNs are not the same, the N2 message may further include an indication that the first network device and the second network device serve different PLMNs. If the embodiment does not restrict that the PLMNs served by the two network devices are the same to establish the communication connection, in step 403 the PLMN served by the second network device may not be needed to be carried, or even if the PLMN served by the second network device is carried in step 403, the access management network element may do other things with the PLMN served by the second network device without comparing the PLMN served by the second network device with the PLMN served by the first network device.
Step 406, the first network device sends the registration accept response in step 404 to the first terminal, and correspondingly, the first terminal receives the registration accept response. The registration accept response is a NAS message that the first network device transparently passes.
Step 407, the first network device sends an RRC configuration signaling to the first terminal, where the RRC configuration signaling includes first configuration information, and the first configuration information includes parameters required for the second network device to establish a communication connection with the first network device.
Parameters required to establish a communication connection include, but are not limited to, one or more of an identification of the second network device (e.g., a gNB ID), an IP address of the second network device, a list of TAIs supported by the second network device, cell information supported by the second network device, information of AMFs to which the second network device may connect, an identification of the first network device, an IP address of the first network device. Further, the second network device carries these parameters in the setup request sent to the first network device.
If the embodiment defines that the PLMNs served by both network devices are identical, the first network device will only send the first configuration information to the first terminal after receiving an indication (i.e. the second indication introduced earlier) that the first network device and the second network device serve the same PLMN. If the embodiment does not restrict the PLMNs served by both network devices to be the same for establishing a communication connection, then the indication that the PLMNs served by both network devices are the same (i.e., the second indication) need not be carried in step 405, or even if the indication that the PLMNs served by both network devices are the same (i.e., the second indication) is carried in step 405, the first network device can use the indication to do other things without being used to determine whether to allow both network devices to establish a communication connection.
In a possible example, the first network device may send an indication of the success of the authorization of the first terminal in step 405 to the first terminal, which is sending an indication of the success of the authorization to the second network device over the internal interface. In another possible example, the first terminal may not be informed of the success of the authorization by default, and only the first terminal may not be informed of the success of the authorization by default, which may save signaling overhead, in which case the first network device may not need to send an indication of the success of the authorization by the first terminal in step 405 to the first terminal.
Optionally, the first network device issues the first configuration information to the first terminal after determining that the first terminal is authorized successfully.
The registration accept response of step 406, the first configuration information of step 407, and the indication that the authorization of the first terminal is successful may be carried and sent to the first terminal in a different message, or may be carried and sent to the first terminal in a different message.
Step 408, the first terminal sends the first indication (RRC-Transaction Identifier) in step 402 and the first configuration information in step 407 to the second network device through the internal interface.
It may be appreciated that the RRC-Transaction Identifier in step 402 and the first configuration information in step 407 may be sent to the second network device at the same time, or may be sent to the second network device in no sequence. The RRC-Transaction Identifier in step 402 is sent to the second network device after step 402 before step 409.
Step 409, the second network device sends an establishment request to the first network device, and the first network device receives the establishment request, where the establishment request is used to request establishment of a communication connection between the first network device and the second network device.
The second network device may acquire an IP address of the first network device based on the first configuration information, and further send an establishment request to the first network device.
The establishment request includes the RRC-Transaction Identifier and an identification of the second network device (for identifying the network device that sent the establishment request). Optionally, the establishment request further includes an indication that the second network device has mobility (i.e., the third indication introduced above, which may also be referred to as MWAB indication). The first terminal may establish a PDU session for accessing the first network device. The establishment request sent by the second network device to the first network device may be transferred to the first network device through the user plane path of the PDU session. Subsequently, interactions between the second network device and the first network device may all be transferred via the user plane path of the PDU session, e.g. the setup response of step 411, the fourth indication of step 413.
The setup request also includes one or more of a type (MESSAGE TYPE) of the setup request message, an identity (e.g., gNB ID) of the second network device, a list of tracking area identities (TRACKING AREA IDENTITY, TAI) supported by the second network device, cell information supported by the second network device, AMF information to which the second network device may connect, and an identity (neighbor NG-RAN node list) of a neighbor device of the second network device. For example, the type of the SETUP REQUEST message is XN SETUP REQUEST.
Step 410, the first network device determines, based on the first indication (RRC-Transaction Identifier), whether the second network device and the first terminal are co-located, and if so, allows a communication connection between the first network device and the second network device to be established, and if not, does not allow both to be established.
In step 411, the first network device determines that the first terminal and the second network device are combined, the first network device sends an establishment response to the second network device, and correspondingly, the second network device receives the establishment response, wherein the establishment response is used for indicating that the communication connection between the first network device and the second network device is successfully established.
The setup response may further include one or more parameters including a type of setup response message (MESSAGE TYPE), an identity of the first network device (e.g., gNB ID), a TAI list supported by the first network device, cell information supported by the first network device, AMF information to which the first network device may be connected, and an identity of a neighbor NG-RAN node list of the first network device. For example, the type of setup response message is XN SETUP RESPONSE.
Step 412, the first network device no longer serves the first terminal.
The first terminal is moved or otherwise caused to reside no longer on the first network device, the first network device no longer serves the first terminal, and the first network device no longer maintains a communication connection between the first network device and the second network device. For example, after the first network device establishes a communication connection with the second network device, the first network device may locally maintain an association between the RRC-Transaction Identifier and the second network device, and store the association locally, and when the first network device no longer serves the first terminal, the first network device may determine the second network device in the locally stored information based on the first indication.
Step 413, the first network device sends a fourth indication to the second network device, and the second network device receives the fourth indication, where the fourth indication is used to indicate to release (remote) the communication connection between the first network device and the second network device.
After releasing the communication connection, the first network device may release the resources occupied by the communication connection, and the second network device may also release the resources occupied by the communication connection.
The second network device has mobility, and the location of the second network device may change, and examples are described below in which the location information of the second network device determines with which network devices (which may or may not be a network device having mobility) the second network device is capable of establishing a communication connection.
As shown in fig. 5, a flow chart of a communication method is introduced, which includes the following steps:
step 501, a first network device obtains information of an area where a network device allowing a communication connection to be established with the first network device is located.
For example, a first network device obtains information from an operation administration and maintenance function entity (operation administration AND MAINTENANCE, OAM) or a core network element of an area where network devices allowing communication connections to be established with the first network device are located. The region may be a geographical region, which may be represented by a latitude and longitude. The area may be one or a plurality of areas. The information of the area may be determined based on a current location of the first network device.
Step 502, a second network device sends an establishment request to a first network device, and the first network device receives an establishment request from the second network device, where the establishment request is used to request establishment of a communication connection between the first network device and the second network device.
Step 503, the first network device acquires the location information of the second network device.
In a possible implementation, the establishment request includes an identifier of the first terminal (alternatively, an identifier of a network device where the first terminal and the second network device are combined, such as an identifier of MWAB devices), and the identifier of the first terminal may be a common public subscription identifier (generic public subscription identifier, GPSI). The first network device may acquire the location information of the second network device based on the identifier of the first terminal, and exemplary, the first network device may first acquire the location information of the first terminal based on the identifier of the first terminal, and determine the location information of the first terminal as the location information of the second network device. Optionally, the establishment request includes a second indication, where the second indication is used to indicate that the second network device has mobility, and the first network device may determine, based on the second indication, that the second network device will move, so that the first network device may be triggered to acquire location information of the first terminal/second network device based on the identifier of the first terminal.
In another possible implementation, the establishment request includes location information of the second network device, and the first network device may obtain the location information of the second network device in the establishment request.
Step 504, the first network device sends an establishment response to the second network device, and correspondingly, the second network device receives the establishment response, wherein the establishment response is used for indicating that the communication connection between the first network device and the second network device is successfully established.
The first network device may send an establishment response to the second network device based on the location information of the second network device and the information of the area acquired in step 501, where, by way of example, the first network device determines that the second network device is located in the area based on the location information of the second network device and the information of the area, and may establish a communication connection between the first network device and the second network device, and further send a response of successful establishment to the second network device, and if the second network device is not located in the area, the communication connection between the first network device and the second network device cannot be established.
In this embodiment, one or more areas are configured for a first network device in step 501 to limit the range of network devices having mobility that are capable of establishing a communication connection with the first network device, and when a second network device is in the configured area, a communication connection may be established between the first network device and the second network device.
On the basis of fig. 5, as shown in fig. 6, a flowchart of a specific communication method is introduced, which includes the following steps:
Step 600, each network device (including but not limited to the first network device) transmits broadcast information, which may be received by the first terminal, as well as by the regular terminal.
The broadcast information includes synchronization information, PLMN information (e.g., ID), cell ID, and the like. The conventional terminal may be a terminal residing in the first network device or a terminal residing in a neighboring network device of the first network device.
The second network device may obtain candidate cell IDs from the first terminal and the regular terminal to determine candidate network devices in step 601.
For example, the first terminal transmits the cell ID in the received broadcast information to the second network device, and the conventional terminal transmits the cell ID in the received broadcast information to the second network device, and the second network device regards the received cell IDs as candidate cell IDs, and determines candidate network devices based on the candidate cell IDs, wherein the candidate cell IDs comprise the identifiers of the candidate network devices.
If there are multiple candidate cell IDs, the candidate network devices contained in the multiple candidate cell IDs may be identical or different in identity. For example, candidate cell id#1 contains the identity of candidate network device#1, candidate cell id#2 contains the identity of candidate network device#1, and candidate cell id#3 contains the identity of candidate network device#2, which can be understood that candidate network device#1 broadcasts cell id#1 and cell id#2 simultaneously, and candidate network device#2 broadcasts only candidate cell#3.
In this example, the candidate network device includes, but is not limited to, the first network device.
Step 602, the second network device sends a request message to the OAM, and correspondingly, the OAM receives the request message, where the request message is used to request to obtain parameters required for establishing a communication connection between the candidate network device and the second network device.
The request message may include an identification of the candidate network device and an identification of the second network device to identify which network devices to establish a communication connection between.
Optionally, before step 602, it is determined that the first terminal authorization is successful, configuration information is requested. The content related to the successful authorization of the first terminal may be described with reference to fig. 4, which is not described herein.
Step 603, OAM determines parameters required for establishing communication connection between the second network device and each candidate network device based on the identification of the candidate network device.
The parameters include, but are not limited to, one or more of an identification of the second network device (e.g., a gNB ID), an IP address of the second network device, a TAI list supported by the second network device, cell information supported by the second network device, information of AMFs to which the second network device may connect, an identification of each candidate network device, an IP address of each candidate network device.
If there are multiple candidate network devices, when the second network device initiates an establishment request with each candidate network device, parameters carried by the second network device may be the same or different, and are not limited.
Optionally, an indication that the second network device has mobility (also referred to as MWAB indication) may also be included in the request message of step 602. The OAM may determine that the second network device has mobility based on the identity of the second network device and/or MWAB indication, and further determine parameters required for the second network device to establish a communication connection with each candidate network device. The parameters sent to the regular network device (here the regular network device refers to a network device without mobility) may be slightly different from the parameters sent to the network device with mobility, e.g. the IP address required for the regular network device to establish a communication connection with the candidate network device (e.g. IP address # 1) may be different from the IP address required for the network device with mobility to establish a communication connection with the candidate network device (e.g. IP address # 2), so it may be determined whether the second network device has mobility or not first and then the parameters sent to the second network device.
Step 604, OAM sends configuration information to the second network device, and the second network device receives the configuration information, wherein the configuration information comprises parameters required by the second network device to establish communication connection with the candidate network devices.
These configuration information may be embodied in the form of a list, for example, one possible list of configuration information is shown in table 1.
Table 1:
Step 605, the first network device obtains, from the OAM, information of an area where the network device that allows the communication connection with the first network device is located.
For example, the first network device transmits location information of the first network device to the OAM, and the OAM determines information of an area where the network device that allows communication connection with the first network device is located based on the location information of the first network device. The region may be a geographical region, which may be represented by a latitude and longitude. The number of the regions can be one or a plurality of the regions, and depends on the granularity of dividing the regions. The region herein may be referred to as a region of interest (area of interest).
The order of step 605 and steps 600-604 is not limited.
Step 606, the second network device sends an establishment request to the first network device, and the first network device receives the establishment request, where the establishment request is used to request establishment of a communication connection between the first network device and the second network device.
The establishment request includes an identifier of the second network device (for identifying the network device that sends the establishment request) and an identifier of the first terminal (the identifier of the first terminal may also be replaced by an identifier of a network device that is configured by the first terminal and the second network device, for example, an identifier of MWAB devices), for example, the identifier of the first terminal is GPSI. Optionally, the establishment request further includes an indication (also referred to as MWAB indication) that the second network device has mobility.
The second network device sends a setup request to the first network device based on the configuration information obtained in step 604, for example, determines the first network device based on an identification or an IP address of the first network device (candidate network device) in the configuration information, and sends the setup request to the first network device, where the setup request includes one or more parameters including a type (MESSAGE TYPE) of a setup request message, an identification (e.g., a gNB ID) of the second network device, a list of tracking area identifications (TRACKING AREA IDENTITY, TAI) supported by the second network device, cell information supported by the second network device, AMF information to which the second network device can connect, and an identification (neighbor NG-RAN node list) of a neighboring cell device of the second network device. For example, the type of the SETUP REQUEST message is XN SETUP REQUEST.
The first terminal may establish a PDU session for accessing the first network device, and the establishment request sent by the second network device to the first network device may be transferred to the first network device through a user plane path of the PDU session.
Step 607, the first network device acquires the location information of the first terminal from the core network registered with the first terminal.
In a possible implementation, the first network device may determine that the second network device will move based on the MWAB indication, so that the first network device is triggered to acquire location information of the first terminal based on an identification of the first terminal (GPSI), and determine the location information of the first terminal as location information of the second network device. The first network device triggers a periodic positioning procedure as LCS CLIENT to a core network currently registered by the first terminal, and obtains the location information of the first terminal. Network elements participating in the positioning procedure include, but are not limited to, an access management network element (e.g., AMF #1 in fig. 2) and a positioning management function network element LMF.
The order of steps 606, 605 and 607 is not limited.
Step 608, the first network device determines whether the first network device and the second network device can establish a communication connection based on the location information of the first terminal acquired in step 607 and the information of the area (area of interes) acquired in step 605. If the first terminal is located in the area (area of interest), the communication connection between the first network device and the second network device is allowed to be established, otherwise the communication connection between the first network device and the second network device is not allowed to be established.
Step 609, the first network device sends an establishment response to the second network device, and correspondingly, the second network device receives the establishment response, where the establishment response is used to indicate that the communication connection between the first network device and the second network device is successfully established.
The setup response may further include one or more parameters including a type of setup response message (MESSAGE TYPE), an identity of the first network device (e.g., gNB ID), a TAI list supported by the first network device, cell information supported by the first network device, AMF information to which the first network device may be connected, and an identity of a neighbor NG-RAN node list of the first network device. For example, the type of setup response message is XN SETUP RESPONSE.
The first network device may periodically obtain location information of the first terminal, step 610. The process may be described with reference to step 607.
In step 611, the first network device determines, based on the obtained location information of the first terminal and the information of the area (area of interes) obtained in step 605, that the first terminal is no longer located in the area (area of interest), and that the first network device does not need to maintain the communication connection between the first network device and the second network device.
Step 612, the first network device sends a release indication to the second network device, and the second network device receives a release indication, where the release indication is used to indicate to release the communication connection between the first network device and the second network device.
The first network device and the second network device release resources associated with the communication connection.
Fig. 5 and 6 described above describe the first network device determining whether the first terminal/second network device is located within the region of interest of the first network device, thereby deciding whether to establish a communication connection between the first network device and the second network device. Next, as shown in fig. 7, a flow chart of a communication method is introduced, and the operation administration and maintenance function entity OAM determines whether the first terminal/second network device is located in the region of interest of the first network device, thereby determining whether to establish a communication connection between the first network device and the second network device, and notifying the first network device.
Fig. 7 includes the following steps:
step 701, the second network device sends a first request to the OAM, where the first request is used to request to obtain configuration information for establishing a communication connection between the second network device and other network devices.
The first request includes an identifier of the second network device, optionally, the first request further includes an identifier of the first terminal (the identifier of the first terminal may also be replaced by an identifier of a network device where the first terminal and the second network device are combined, for example, an identifier of MWAB devices) and/or location information of the second network device, where the identifier of the first terminal may be a GPSI.
The step 701 is an optional step, and the configuration information may be actively issued to the second network device without a request from the second network device.
Optionally, before step 701, it is determined that the authorization of the first terminal is successful, the configuration information is requested. The content related to the successful authorization of the first terminal may be described with reference to fig. 4, which is not described herein.
Step 702, OAM determines information of an area, information of surrounding network devices in the area capable of establishing a communication connection with a second network device.
The number of regions may also be referred to as area of interest, where the number of regions may be one or more, depending on the granularity of the division of the regions, and if there are multiple regions, the multiple regions are very close together. The surrounding network devices may be one or more, and the surrounding network devices are merely distinguished by one name for convenience of description. Surrounding network devices are within the one or more areas and a second network device is also within one of the areas, it being understood that a communication connection may be established between the network devices within the one or more areas. For example, the OAM determines location information of the second network device, and determines surrounding network devices and the area based on the location information of the second network device. In a possible example, the OAM acquires location information of the first terminal based on the identification of the first terminal in step 701, and determines the location information of the first terminal as the location information of the second network device.
Step 703, the OAM sends configuration information to the second network device, and correspondingly, the second network device receives the configuration information, where the configuration information includes information of surrounding network devices, parameter information required by the second network device to establish communication connection with the surrounding network devices, and optionally, information of an area.
The parameters include, but are not limited to, one or more of an identification of the second network device (e.g., a gNB ID), an IP address of the second network device, a TAI list supported by the second network device, cell information supported by the second network device, information of AMFs to which the second network device may connect, an identification of each surrounding network device, an IP address of each surrounding network device. These configuration information may be embodied in the form of a list, similar to the list 1 described above. The surrounding network devices in the configuration information include, but are not limited to, the first network device. If there are multiple surrounding network devices, the parameters carried by the second network device may be the same or different when the second network device initiates an establishment request with each surrounding network device, which is not limited.
Step 704, the second network device sends an establishment request to the first network device, and the first network device receives an establishment request from the second network device, where the establishment request is used to request establishment of a communication connection between the first network device and the second network device.
The establishment request comprises a second network device identity (representing the network device sending the establishment request), the establishment request further comprising an identity of the first terminal and/or location information of the second network device. Optionally, the establishment request further includes an indication (which may also be referred to as MWAB indication) that the second network device has mobility.
The first network device belongs to the surrounding network devices in the configuration information of step 703. The second network device sends a setup request to the first network device based on configuration information of the first network device establishing a communication connection with the second network device, for example, based on an identification or an IP address of the first network device (candidate network device) in the configuration information, determines the first network device, sends the setup request to the first network device, and includes one or more parameters including a type (MESSAGE TYPE) of the setup request message, an identification (e.g., a gNB ID) of the second network device, a list of tracking area identifications (TRACKING AREA IDENTITY, TAI) supported by the second network device, cell information supported by the second network device, AMF information to which the second network device can be connected, and an identification (neighbor NG-RAN node list) of a neighbor device of the second network device. For example, the type of the SETUP REQUEST message is XN SETUP REQUEST.
The first terminal may establish a PDU session for accessing the first network device, and the establishment request sent by the second network device to the first network device may be transferred to the first network device through a user plane path of the PDU session.
Step 705, the first network device sends the identifier of the first terminal and/or the location information of the second network device to the OAM, and correspondingly, the OAM receives the identifier of the first terminal and/or the location information of the second network device.
The first network device sends a check request to the OAM, where the check request includes an identifier of the first terminal, and the check request is used to request to confirm whether a communication connection can be established between the network device and the first network device that are co-located with the identified terminal.
The first network device sends a check request to the OAM, where the check request includes location information of the second network device, and the check request is used to request to confirm whether a communication connection can be established between the network device located in the location information and the first network device.
Optionally, in step 706, the oam obtains location information of the first terminal from a core network registered with the first terminal based on the identity of the first terminal.
For example, the OAM triggers a periodic positioning procedure as LCS CLIENT to a core network currently registered by the first terminal, obtains location information of the first terminal, and determines the location information of the first terminal as location information of the second network device. Network elements participating in the positioning procedure include, but are not limited to, an access management network element (e.g., AMF #1 in fig. 2) and a positioning management function network element (location management function, LMF). If the OAM has received the location information of the second network device in step 705, step 706 may not be performed.
Step 707, the OAM determines whether the second network device is located in the area of step 702 based on the location information of the second network device obtained in step 705 or step 706. If so, the reply allows the establishment for step 705, and if not, the reply does not allow the establishment for step 705.
Step 708 comprises the step of the OAM sending a first indication to the first network device, and correspondingly, the first network device receiving the first indication from the OAM, wherein the first indication is used for indicating that the communication connection between the first network device and the second network device is allowed to be established.
Step 709, the first network device sends an establishment response to the second network device, and correspondingly, the second network device receives an establishment response from the first network device, wherein the establishment response is used for indicating that the communication connection between the first network device and the second network device is successfully established.
The setup response may further include one or more parameters including a type of setup response message (MESSAGE TYPE), an identity of the first network device (e.g., gNB ID), a TAI list supported by the first network device, cell information supported by the first network device, AMF information to which the first network device may be connected, and an identity of a neighbor NG-RAN node list of the first network device. For example, the type of setup response message is XN SETUP RESPONSE.
Optionally, step 710 includes the first network device sending a second indication to the OAM, and in response, the OAM receiving a second indication from the first network device, the second indication indicating that a communication connection between the first network device and the second network device has been established.
The first network device may also notify the OAM of the state of the established communication connection after the first network device establishes the communication connection with the second network device, or it may be provided that the first network device does not need to feed back the established communication connection to the OAM after the first indication based on the OAM establishes the communication connection.
Optionally, the first network device may further send an identifier of the first terminal to the OAM, where the identifier of the first terminal may be used by the OAM to obtain the location information of the second network device.
Optionally, the first network device may further send a second network device identifier to the OAM for identifying the second network device.
Step 711 oam may periodically obtain location information of the second network device and if the second network device is not in the area determined in step 702, the communication connection between the first network device and the second network device needs to be released.
After the first network device establishes a communication connection with the second network device, if the OAM determines that the second network device is no longer located in the area based on the location information of the second network device, the OAM may indicate to the first network device to release the connection. One possible implementation of the OAM periodically obtaining location information of the second network device is that when the first network device sends a second indication (for indicating that a communication connection between the first network device and the second network device is established) to the OAM, the first network device also sends an identifier of the first terminal to the OAM, the OAM receives the identifier of the first terminal, and the OAM periodically obtains the location information of the first terminal based on the identifier of the first terminal. The process of step 711 may refer to step 706 and step 707, and a detailed description will not be repeated.
Step 712, the OAM sends a third indication to the first network device, and the first network device receives the third indication, where the third indication is used to indicate to release (removal) the communication connection between the first network device and the second network device.
The third indication comprises a second network device identification for the first network device to learn with which network device to release the communication connection.
If the first network device sends the second network device identification to the OAM in step 710, the OAM may include the second network device identification directly in the third indication. If the first network device sends the identity of the first terminal to the OAM in step 710, the OAM may determine the second network device identity based on the identity of the first terminal and step 701.
Step 713, the first network device sends a fourth indication to the second network device, and the second network device receives the fourth indication, where the fourth indication is used to instruct to release the communication connection between the first network device and the second network device.
An example of establishing a communication connection between network devices based on the identity of the cell carried by the second network device in the establishment request is described next. As shown in fig. 8, a flow chart of a communication method is introduced, comprising the steps of:
Step 801, a second network device sends a first request to an OAM, where the first request is used to request to obtain configuration information for establishing a communication connection between the second network device and a surrounding network device.
The first request includes an identifier of the second network device, and optionally, the first request further includes an identifier of the first terminal (the identifier of the first terminal may also be replaced by an identifier of a network device where the first terminal and the second network device are combined, such as an identifier of MWAB devices), or location information of the second network device. The identity of the first terminal may be GPSI.
The step 801 is an optional step, and the configuration information may be actively issued to the second network device by the OAM without a request from the second network device.
Optionally, before step 801, it is determined that the first terminal authorization is successful, configuration information is requested. The content related to the successful authorization of the first terminal may be described with reference to fig. 4, which is not described herein.
Step 802, OAM determines information of an area, information of an authorized network device in the area capable of establishing a communication connection with a second network device.
The number of regions may also be referred to as area of interest, where the number of regions may be one or more, depending on the granularity of the division of the regions, and if there are multiple regions, the multiple regions are very close together. The authorized network device may be one or more, and the authorized network device is merely a distinction in name for convenience of description. Authorizing network devices within the one or more areas and a second network device also within one of the areas or in relatively close proximity to those areas is understood to mean that a communication connection may be established between network devices within the one or more areas. For example, the OAM determines location information of the second network device, determines the licensed network device and the area based on the location information of the second network device. In a possible example, the OAM acquires location information of the first terminal based on the identification of the first terminal in step 701, and determines the location information of the first terminal as the location information of the second network device.
Optionally, the OAM may further determine an identifier of a cell corresponding to each area (that is, the identifier of a cell corresponding to the authorized network device in the area is the same), where the identifier of the cell is used for being carried when the second network device sends the establishment request to the authorized network device in the area, and the identifiers of the cells in different areas may be the same or different. Or the OAM may also determine the identity of the cell corresponding to each authorized network device (that is, the identities of the cells corresponding to different authorized network devices are different, which is not to be excluded from the fact that the identities of the cells corresponding to two authorized network devices are the same), where the identity of the cell is used for the second network device to carry when sending the establishment request to the authorized network device.
In this example, the licensed network device includes at least a first network device and a third network device.
Step 803, the OAM sends first configuration information to the second network device, and accordingly, the second network device receives the first configuration information, wherein the first configuration information comprises information of authorized network devices, information of areas and mapping relation of the information of the authorized network devices and the information of the areas, that is, the first configuration information is used for indicating the authorized network devices in each area, and optionally, the first configuration information further comprises an identifier of a cell corresponding to each area or the authorized network devices.
It will be appreciated that the first configuration information also includes parameter information required for the second network device to establish a communication connection with the authorised network devices. The parameters include, but are not limited to, one or more of an identification of the second network device (e.g., a gNB ID), an IP address of the second network device, a TAI list supported by the second network device, cell information supported by the second network device, information of AMFs to which the second network device may connect, an identification of each authorized network device, an IP address of each authorized network device. These configuration information may be embodied in the form of a list, similar to the list 1 described above. The authorized network devices in the configuration information include, but are not limited to, a first network device and a third network device. If there are multiple authorized network devices, the parameters carried by the second network device may be the same or different, but not limited to, when the second network device initiates an establishment request with each authorized network device.
Optionally, step 804, the oam sends the identifier of each corresponding cell to the authorized network device (including the first network device and the third network device) in step 802, where the identifier of the cell refers to the identifier of the cell that can be carried in the establishment request sent by the authorized network device, so that the authorized network device verifies the establishment request. The OAM may not configure the identity of the cell to the licensed network device, so that the licensed network device cannot verify the setup request.
Optionally, the OAM may further configure the identifier of the second network device to the authorized network device, so that it is limited that only if the second network device can carry the identifiers of the cells in the establishment request, the authentication can be performed, and the other network devices cannot be performed.
The order of steps 804 and 803 is not limited.
Step 805 the second network device determines an authorized network device capable of sending the setup request based on the current location and the first configuration information of step 803. Optionally, the identity of the cell carried when the establishment request is sent to the licensed network device may also be determined.
For example, the second network device determines which area is currently in the first configuration information, and selects one of the authorized network devices from this area, to which to send the establishment request.
Step 806 is described with respect to sending a setup request to the first network device.
Step 806, the second network device sends a first establishment request to the first network device, and correspondingly, the first network device receives a first establishment request from the second network device, where the first establishment request is used to request to establish a communication connection between the first network device and the second network device. The second network device is currently located in a first area, the first area belongs to an area in the first configuration information, and the first network device is located in the first area.
Optionally, the first establishment request includes an identifier of a first cell, where the first cell is a cell corresponding to the first network device.
The first network device belongs to an authorized network device in the configuration information of step 803. The second network device sends a setup request to the first network device based on parameters required for the first network device to establish a communication connection with the second network device, for example, based on an identification or an IP address of the first network device (candidate network device) in the configuration information, determines the first network device, sends the setup request to the first network device, and includes one or more parameters including a type (MESSAGE TYPE) of a setup request message, an identification (e.g., a gNB ID) of the second network device, a tracking area identification (TRACKING AREA IDENTITY, TAI) list supported by the second network device, cell information supported by the second network device, AMF information to which the second network device can be connected, and an identification (neighbor NG-RAN node list) of a neighbor device of the second network device. For example, the type of the SETUP REQUEST message is XN SETUP REQUEST.
The first terminal may establish a PDU session for accessing the first network device, and the establishment request sent by the second network device to the first network device may be transferred to the first network device through a user plane path of the PDU session.
Optionally, step 807, the first network device determines whether the identity of the first cell included in the first setup request belongs to the identity of the OAM configured cell in step 804. If so, it may be determined that a communication connection between the first network device and the second network device is allowed to be established, and if not, a communication connection between the first network device and the second network device cannot be established.
If step 804 is not performed, the first network device need not perform step 807 either. The first network device may directly reply to the setup response after receiving the setup request.
Step 808, the first network device sends a first establishment response to the second network device, and correspondingly, the second network device receives the first establishment response from the first network device, where the first establishment response is used to indicate that the communication connection between the first network device and the second network device is successfully established.
The first setup response may further include one or more parameters including a type of setup response message (MESSAGE TYPE), an identity of the first network device (e.g., a gNB ID), a TAI list supported by the first network device, cell information supported by the first network device, AMF information to which the first network device may connect, and an identity of a neighbor NG-RAN node list of the first network device. For example, the type of setup response message is XN SETUP RESPONSE.
Step 809, the second network device determines that the second network device is currently moving out of the first area, at which time the established communication connection of the second network device with the first network device may be released.
Step 810, a second network device sends a first indication to the first network device, the first indication indicating to release a communication connection between the first network device and the second network device.
Step 811 the second network device determines an authorised network device capable of sending the setup request based on the current location and the first configuration information of step 803. Optionally, the identity of the cell carried when the establishment request is sent to the licensed network device may also be determined.
For example, the second network device determines which area is currently in the first configuration information, and selects one of the authorized network devices from this area, to which to send the establishment request.
Step 812 is presented as an example of sending a setup request to a third network device.
Step 812, the second network device sends a second establishment request to the third network device, where the second establishment request is used to request establishment of a communication connection between the third network device and the second network device. The second network device is currently located in a second area, the second area belongs to at least one area in the first configuration information, and the third network device is located in the second area.
Optionally, the second establishment request includes an identifier of a second cell, where the second cell is a cell corresponding to the third network device.
The first terminal may establish a PDU session for accessing the third network device, and the establishment request sent by the second network device to the third network device may be transferred to the third network device through a user plane path of the PDU session.
Optionally, step 813, the third network device determines whether the identity of the second cell included in the second setup request belongs to the identity of the OAM configured cell in step 804. If so, it may be determined that a communication connection between the third network device and the second network device is allowed to be established, and if not, a communication connection between the third network device and the second network device cannot be established.
If step 804 is not performed, the first network device need not perform step 813 either. The third network device may directly reply to the setup response after receiving the setup request.
Step 814, the third network device sends a second setup response to the second network device, and correspondingly, the second network device receives the second setup response from the third network device, where the second setup response is used to indicate that the communication connection between the second network device and the third network device is successfully established.
The second setup response may further include one or more parameters including a type of setup response message (MESSAGE TYPE), an identity of a third network device (e.g., a gNB ID), a TAI list supported by the third network device, cell information supported by the third network device, AMF information to which the third network device may be connected, and an identity of a neighbor NG-RAN node list of the third network device. For example, the type of setup response message is XN SETUP RESPONSE.
Next, a description will be given of determining whether or not a communication connection can be established with a network device that receives an establishment request based on the identity of a cell carried by the second network device in the establishment request, and the difference from fig. 8 includes that, in fig. 8, the second network device detects its own location, determines the identity of the cell carried in the establishment request, and in fig. 9, OAM detects the location of the first terminal/the location of the second network device, and when the location changes, OAM informs the second network device of the identity of the cell carried in the establishment request. In addition, the second network device may periodically send the identity of the cell to the first network device, and the first network device determines whether to release the communication connection with the second network device according to the identity of the cell. As shown in fig. 9, a flow chart of a communication method is introduced, comprising the steps of:
step 901, a second network device sends a first request to an OAM, where the first request is used to request to obtain configuration information for establishing a communication connection between the second network device and a surrounding network device.
The first request includes an identifier of the second network device, and optionally, the first request further includes an identifier of the first terminal (the identifier of the first terminal may also be replaced by an identifier of a network device where the first terminal and the second network device are combined, such as an identifier of MWAB devices), or location information of the second network device. The identity of the first terminal may be GPSI.
The step 901 is an optional step, and the configuration information may be actively issued to the second network device by the OAM without a request from the second network device.
Optionally, before step 901, it is determined that the first terminal authorization is successful, the configuration information is requested. The content related to the successful authorization of the first terminal may be described with reference to fig. 4, which is not described herein.
Step 902, the OAM determines, based on the location information of the second network device, an authorized network device capable of establishing a communication connection with the second network device currently, and an identifier of a cell carried by the second network device in the establishment request.
The authorized network device may be one or more, and the authorized network device is merely a distinction in name for convenience of description. In this example, the authorized network devices include at least a first network device and a third network device.
Step 903, the OAM sends first configuration information to the second network device, and correspondingly, the second network device receives the first configuration information, wherein the first configuration information comprises information of the authorized network device and an identifier of a cell carried when sending an establishment request to the authorized network device.
It will be appreciated that the first configuration information also includes parameter information required for the second network device to establish a communication connection with the authorised network devices. The parameters include, but are not limited to, one or more of an identification of the second network device (e.g., a gNB ID), an IP address of the second network device, a TAI list supported by the second network device, cell information supported by the second network device, information of AMFs to which the second network device may connect, an identification of each authorized network device, an IP address of each authorized network device. These configuration information may be embodied in the form of a list, similar to the list 1 described above. The authorized network device in the configuration information includes, but is not limited to, the first network device. If there are multiple authorized network devices, the parameters carried by the second network device may be the same or different, but not limited to, when the second network device initiates an establishment request with each authorized network device.
Step 904 oam configures the licensed network device with the identity of the cell in step 902.
Optionally, the OAM may further configure the identifier of the second network device to the authorized network device, so that it is limited that only if the second network device can carry the identifiers of the cells in the establishment request, the authentication can be performed, and the other network devices cannot be performed.
Step 905, a second network device sends an establishment request to the first network device, and correspondingly, the first network device receives an establishment request from the second network device, where the establishment request is used to request to establish a communication connection between the first network device and the second network device. The setup request comprises the identity of the first cell in step 903.
Optionally, the establishment request further includes an indication (also referred to as MWAB indication) that the second network device has mobility.
The first network device belongs to an authorized network device in the configuration information of step 903. The second network device sends a setup request to the first network device based on parameters required for the first network device to establish a communication connection with the second network device, for example, based on an identification or an IP address of the first network device (candidate network device) in the configuration information, determines the first network device, sends the setup request to the first network device, and includes one or more parameters including a type (MESSAGE TYPE) of a setup request message, an identification (e.g., a gNB ID) of the second network device, a tracking area identification (TRACKING AREA IDENTITY, TAI) list supported by the second network device, cell information supported by the second network device, AMF information to which the second network device can be connected, and an identification (neighbor NG-RAN node list) of a neighbor device of the second network device. For example, the type of the SETUP REQUEST message is XN SETUP REQUEST.
The first terminal may establish a PDU session for accessing the first network device. The establishment request sent by the second network device to the first network device may be transferred to the first network device through the user plane path of the PDU session.
Step 906, the first network device verifies the identity of the first cell.
For example, in step 904, the first network device obtains the identifier of the cell that may be carried in the establishment request, and the first network device determines whether the identifier of the cell obtained in step 904 is the same as the identifier of the cell carried in the first establishment request in step 903, if so, a communication connection between the first network device and the second network device may be further established, and if not, a communication connection between the first network device and the second network device may not be established.
Step 907, the first network device sends a setup response to the second network device, and correspondingly, the second network device receives the setup response from the first network device, where the setup response is used to indicate that the communication connection between the first network device and the second network device is successfully established.
The setup response may further include one or more parameters including a type of setup response message (MESSAGE TYPE), an identity of the first network device (e.g., gNB ID), a TAI list supported by the first network device, cell information supported by the first network device, AMF information to which the first network device may be connected, and an identity of a neighbor NG-RAN node list of the first network device. For example, the type of setup response message is XN SETUP RESPONSE.
Optionally, step 908 indicates to the first network device to periodically report to the second network device the identity of the cell from the OAM.
This step 908 is an optional step, where after the second network device establishes a communication connection with the first network device based on the establishment request carrying the cell identifier, the second network device may send, by default, the identifier of the cell from the OAM to the first network device.
Step 909, the second network device moves.
In step 910, the oam sends indication information to the second network device, where the indication information is used to indicate an identity of the second cell, where the second cell is changed compared to the first cell in step 903.
The OAM may learn, based on the identity of the first terminal, that the first terminal is moving, and that the second network device is also moving. The movement of the second network device may or may not require updating the identity of the cell carried in the establishment request. For example, in the OAM, different cell identities may be set for different areas, and the identity of the cell sent to the second network device is determined based on the area where the location of the second network device is located.
Step 911. The second network device sends the identity of the second cell to the first network device, and in response, the second network device receives the identity of the second cell from the first network device.
If the OAM does not perform step 910, the identity of the cell that the second network device sent to the first network device is still the identity of the first cell in the setup request in step 905.
Step 912, the first network device verifies the identity of the second cell.
For example, in step 904, the first network device acquires the identifier of the cell that may be carried in the establishment request, and the first network device determines whether the identifier of the cell acquired in step 904 is the same as the identifier of the second cell in step 911, and if so, may continue to maintain the communication connection between the first network device and the second network device, and if not, needs to release the communication connection between the first network device and the second network device.
Step 913, the first network device sends a release indication to the second network device, and the second network device receives the release indication from the first network device, where the release indication is used to indicate to release the communication connection between the first network device and the second network device.
In fig. 9, steps 908, 910 and 911 described above may be replaced by the following processes:
The OAM sends the identification of the second network device and the identification of the second cell to the first network device. That is, when the OAM determines that the second network device moves and needs to update the cell identifier, the OAM may directly send the updated cell identifier to the first network device. This example requires the OAM to maintain an identification of which network devices correspond to which cells, and which communication connections are established between which network devices.
It will be appreciated that, in order to implement the functions in the above embodiments, the terminal device and the network device include corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application scenario and design constraints imposed on the solution.
Fig. 10 and 11 are schematic structural diagrams of a possible communication device according to an embodiment of the present application. These communication devices may be used to implement the functions of the terminal device and the network device in the above method embodiments, so that the beneficial effects of the above method embodiments may also be implemented.
As shown in fig. 10, the communication apparatus 1000 includes a processing unit 1010 and a transceiver unit 1020.
For example, the communication apparatus 1000 is configured to implement the functions of the first network device, the second network device, and the first terminal in the method embodiments shown in fig. 3, fig. 4, fig. 5, fig. 6, fig. 7, fig. 8, and fig. 9. The transceiver unit 1020 may perform the receiving actions and the sending actions performed by the first network device, the second network device, and the first terminal in the foregoing method embodiment. The processing unit 1010 may perform actions other than the sending action and the receiving action in the actions performed by the first network device, the second network device, and the first terminal in the above method embodiment.
Illustratively, when the communication apparatus 1000 is configured to implement the function of the first network device in the method embodiment shown in fig. 4, the transceiver unit 520 is configured to send the first indication, send the first configuration information, receive the establishment request, send the establishment response, and send the fourth indication. The processing unit 1010 is configured to determine, based on the first indication, that the first terminal and the second network device are co-located, and determine that the communication connection between the first network device and the second network device is no longer maintained.
Illustratively, when the communication apparatus 1000 is configured to implement the function of the second network device in the method embodiment shown in fig. 4, the transceiver unit 520 is configured to receive the first indication and the first configuration information, send the establishment request, and receive the establishment response. The processing unit 510 is configured to determine that the first indication is carried in the establishment request.
The above-mentioned more detailed description of the processing unit 1010 and the transceiver unit 1020 can be directly obtained by referring to the related description in the method embodiments shown in fig. 3 to 9, which is not repeated herein. The processing unit 1010 may be implemented by a processor, and the transceiver unit 1020 may be implemented by a transceiver.
As shown in fig. 11, the communication device 1100 includes a processor 1110 and an interface circuit 1120. The processor 1110 and the interface circuit 1120 are coupled to each other. It is understood that the interface circuit 1120 may be a transceiver or an input-output interface. Optionally, the communication device 1100 may further include a memory 1130 for storing instructions to be executed by the processor 1110 or for storing input data required by the processor 1110 to execute instructions or for storing data generated after the processor 1110 executes instructions. Sometimes, the interface circuit 1120 may also be understood as being part of the processor 1110, in which case the communication device 1100 includes the processor 1110.
When the communication device 1100 is configured to implement the method shown in fig. 3-9, the processor 1110 is configured to implement the function of the processing unit 1010, and the interface circuit 1120 is configured to implement the function of the transceiver unit 1020.
When the communication device is a chip applied to the terminal equipment, the terminal equipment chip realizes the functions of the terminal equipment in the embodiment of the method. The terminal device chip receives information from the network device, which is understood to be received by other modules (e.g. radio frequency modules or antennas) in the terminal device before being sent to the terminal device chip by these modules. The terminal device chip sends information to the network device, which is understood to be sent to other modules (such as a radio frequency module or an antenna) in the terminal device, and then sent to the network device by the modules.
When the communication device is a chip applied to the network equipment, the network equipment chip realizes the functions of the network equipment in the embodiment of the method. The network device chip receives information from the terminal device, which is understood to be received by other modules (such as radio frequency modules or antennas) in the network device before being sent to the network device chip by these modules. The network device chip sends information to the terminal device, which is understood to be sent down to other modules (such as radio frequency modules or antennas) in the network device, and then sent to the terminal device by these modules. The network device module may be a baseband chip of the network device, or may be a DU or other module, where the DU may be a DU under an open radio access network O-RAN architecture.
In the application, the entity A sends information to the entity B, and the information can be directly sent to the B by the entity A or indirectly sent to the B by the entity A through other entities. Similarly, the entity B may receive the information from the entity a, which may be that the entity B directly receives the information sent by the entity a, or that the entity B indirectly receives the information sent by the entity a through other entities. The entities a and B may be network devices or terminal devices, or may be modules inside the network devices or modules inside the terminal devices. The sending and receiving of the information can be information interaction between the network device and the terminal device, the sending and receiving of the information can also be information interaction between two network devices, such as CU and DU, and the sending and receiving of the information can also be information interaction between different modules in a device, such as information interaction between a terminal device chip and other modules of the terminal device, or information interaction between a network device chip and other modules of the network device.
It is to be appreciated that the processor in embodiments of the application may be a central processing unit (central processing unit, CPU), but may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL processors, DSPs), application Specific Integrated Circuits (ASICs), field programmable gate arrays (field programmable GATE ARRAY, FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general purpose processor may be a microprocessor, but in the alternative, it may be any conventional processor.
The embodiment of the application also provides a computer readable storage medium, which stores a computer program, and the computer program can enable the computer to execute the communication method when being executed by the computer. Alternatively, the computer program includes instructions for implementing the communication described above.
The embodiment of the application also provides a computer program product comprising computer program code which, when run on a computer, enables the computer to perform the communication method provided above.
The embodiment of the application also provides a communication system which comprises the first network device and the second network device for executing the communication method.
The method steps in the embodiments of the present application may be implemented by hardware, or may be implemented by executing software instructions by a processor. The software instructions may be comprised of corresponding software modules that may 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 disk, removable disk, compact disk-read-only memory (compact disc read-only memory) (also known as compact disk-read-only memory), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a base station or terminal. The processor and the storage medium may reside as discrete components in a base station or terminal.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network device, a first control plane network element, a user device, or other programmable apparatus. The computer program or instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer program or instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center by wired or wireless means. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that integrates one or more available media. The usable medium may be a magnetic medium such as a floppy disk, a hard disk, a magnetic tape, an optical medium such as a digital video disk, or a semiconductor medium such as a solid state disk. The computer readable storage medium may be volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage medium.
In various embodiments of the application, where no special description or logic conflict exists, terms and/or descriptions between the various embodiments are consistent and may reference each other, and features of the various embodiments may be combined to form new embodiments based on their inherent logic.
In the embodiments of the present application, the number of nouns, unless otherwise indicated, means "a singular noun or a plural noun", i.e. "one or more". "at least one" means one or more, and "a plurality" means two or more. "and/or" describes an association of associated objects, meaning that there may be three relationships, e.g., A and/or B, and that there may be A alone, both A and B, and B alone, where A or B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. For example, A/B, represents A or B. The expression "at least one item(s)" or "one or more of the items" and the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one of a, b, or c, or one or more of a, b, or c, represents a, b, c, a and b, a and c, b and c, or a and b and c. Wherein each item of a, b and c can be single or multiple.
The ordinal terms such as "first," "second," and the like in the embodiments of the present application are used for distinguishing a plurality of objects, and are not used for limiting the size, content, sequence, timing, priority, importance, and the like of the plurality of objects. Also, such names do not indicate the difference in content, transmitting/receiving ends, transmission order, size, application scenario, priority, importance, or the like included in the two pieces of information. In addition, the numbers of the steps in the embodiments described in the present application are only for distinguishing different steps, and are not used for limiting the sequence of the steps.