Patent Application
20230232366
A business-to-business (business-to-business, B2B) service is a service in which data information is exchanged and transmitted, and a trading activity is carried out between enterprises over a private network or the internet. Because the B2B service is very sensitive to an end-to-end latency and reliability, and few spectrum resources are available to the enterprise, the spectrum resources available to the enterprise are quite precious. B2B services are mainly classified into three types: remote control (remote Control, RC), control to control (control to control, C2C), and motion control (motion control, MC). An MC service uses an end-to-end latency that is less than or equal to 1 ms and reliability is 99.9999%. That the reliability is 99.9999% is understood as that total fault time allowed for communication service interruption in one year is about 30 seconds. However, reliability of an existing terminal device is only 99.9% or 99.99%. Therefore, to ensure the reliability of the MC service, the reliability of the terminal device is to be improved.
In the conventional technology, to improve the reliability of the terminal device and minimize impact on service continuity of the terminal device, a concept of performing data transmission by two terminal devices is proposed. To be specific, one primary terminal device and one secondary terminal device perform data transmission together, to avoid a case in which data transmission cannot be performed in response to the primary terminal device being faulty.
In response to the existing two terminal devices performing data transmission, the primary terminal device and the secondary terminal device is to be connected to different RANs and UPF network elements, to establish different PDU sessions from the terminal devices to the RANs to the UPF network elements. Consequently, double spectrum resources are occupied, causing high spectrum resource consumption.
Embodiments described herein provide a method for performing data transmission by two terminal devices and an apparatus, to resolve an existing problem that many spectrum resources are consumed in response to two terminal devices performing data transmission.
According to a first aspect, at least one embodiment provides a method for performing data transmission by two terminal devices. The method includes the following steps. A first core network device determines that a first terminal and a second terminal are in a mutual backup relationship. The first core network device sends pairing indication information to a base station, where the pairing indication information indicates that the first terminal and the second terminal are in the mutual backup relationship, so that in response to determining, based on the pairing indication information, that the first terminal is a primary terminal and the second terminal is a secondary terminal, the base station sends one copy of downlink data to the first terminal and the second terminal, or sends downlink data to the first terminal and sends the downlink data to the second terminal in response to the first terminal being faulty.
According to the foregoing design, after the first core network device determines that the first terminal and the second terminal are in the mutual backup relationship, the first core network device sends, to the base station, the pairing indication information indicating that the first terminal and the second terminal are in the mutual backup relationship, so that in response to determining, based on the pairing indication information, that the first terminal is the primary terminal and the second terminal is the secondary terminal, the base station sends one copy of downlink data to the first terminal and the second terminal, or sends downlink data to the first terminal and send the downlink data to the second terminal in response to the first terminal being faulty. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly performs data transmission with the base station, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
In at least one embodiment, the first core network device determines that the first terminal and the second terminal are in the mutual backup relationship includes: The first core network device receives registration request messages sent by the first terminal and the second terminal, where the registration request messages are used to request to connect the terminal to a core network; and after receiving the registration request information sent by the first terminal or the second terminal, the first core network device obtains identification information of the second terminal or the first terminal from a second core network device, and determines, based on the identification information of the second terminal or the first terminal, that the first terminal and the second terminal are in the mutual backup relationship; after receiving the registration request information sent by the first terminal or the second terminal, the first core network device obtains identification information of the second terminal or the first terminal from the registration request information sent by the first terminal or the second terminal, and determines, based on the identification information of the second terminal or the second terminal, that the first terminal and the second terminal are in the mutual backup relationship; or after receiving the registration request information sent by the first terminal or the second terminal, the first core network device obtains, from an application function AF network element, identification information of terminals in the mutual backup relationship, and determines, based on the identification information of the terminals in the mutual backup relationship, that the first terminal and the second terminal are in the mutual backup relationship.
According to the foregoing design, after receiving the registration request information of the first terminal or the second terminal, the first core network device determines that the first terminal and the second terminal are in the mutual backup relationship, so that the first core network device authenticates the backup relationship between the first terminal and the second terminal. Further, the base station authenticates the backup relationship between the first terminal and the second terminal, so that in response to determining that the first terminal is a primary terminal and the second terminal is a secondary terminal, the base station sends one copy of downlink data to the first terminal and the second terminal, or send downlink data to the first terminal and send the downlink data to the second terminal in response to the first terminal being faulty. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the base station, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
In the foregoing design, the method further includes: After receiving the registration request information sent by the first terminal or the second terminal, the first core network device receives session establishment request information sent by the first terminal or the second terminal, and sends the session establishment request information to a third core network device, where the session establishment request information is used to request the base station to establish, with a fourth core network device, a protocol data unit PDU session shared by the first terminal and the second terminal.
According to the foregoing design, after receiving the registration request information of the first terminal or the second terminal, the first core network device receives the session establishment request information of the first terminal or the second terminal, and send the session establishment request information to the third core network device, so that the base station and the fourth core network device establish the PDU session shared by the first terminal and the second terminal. Therefore, in response to any terminal accessing a network, in response to the SMF network element determining that the terminal that is in the mutual backup relationship with the terminal has triggered establishment of the PDU session, a PDU session is able to not be re-established, and the PDU session established by the terminal that is in the mutual backup relationship with the terminal is shared. In this way, in response to the primary terminal being faulty, the secondary terminal directly uses the PDU session shared by the primary terminal and the secondary terminal during data transmission, and a new PDU session is not re-established. This minimizes impact of a fault of the terminal device on service continuity of the terminal device, and improves reliability of the terminal device.
In at least one embodiment, the method further includes: After the first core network device determines that the first terminal and the second terminal are in the mutual backup relationship, the first core network device sends association indication information to a peer application layer of the terminal, where the association indication information indicates the peer application layer to send downlink data to the first terminal and the second terminal in response to the peer application layer receiving uplink data sent by the first terminal or the second terminal, and the association indication information carries internet protocol IP addresses of the first terminal and the second terminal or IP addresses of the first terminal and the second terminal and an IP address of the peer application layer.
According to the foregoing design, after determining that the first terminal and the second terminal are in the mutual backup relationship, the first core network device sends, to the peer application layer of the terminal, the association indication information indicating the peer application layer to send the downlink data to the first terminal and the second terminal in response to the peer application layer receiving the uplink data sent by the first terminal or the second terminal, so that in response to receiving the uplink data sent by any terminal, the peer application layer sends the downlink data to the terminal and the terminal that is in the mutual backup relationship with the terminal. Therefore, in response to the terminal sending the uplink data only after receiving the downlink data or the peer application layer sending the downlink data only after receiving the uplink data, the secondary terminal also normally performs data transmission. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, and improves reliability of the terminal device.
According to a second aspect, at least one embodiment further provides a method for performing data transmission by two terminal devices. The method includes: A base station receives pairing indication information sent by a first core network device, where the pairing indication information indicates that a first terminal and a second terminal are in a mutual backup relationship; and in response to determining, based on the pairing indication information, that the first terminal is a primary terminal and the second terminal is a secondary terminal, the base station sends one copy of downlink data to the first terminal and the second terminal, or sends downlink data to the first terminal and sends the downlink data to the second terminal in response to the first terminal being faulty.
According to the foregoing design, the base station receives the pairing indication information sent by the first core network device; and in response to determining, based on the pairing indication information, that the first terminal is the primary terminal and the second terminal is the secondary terminal, the base station sends one copy of downlink data to the first terminal and the second terminal, or sends downlink data to the first terminal and send the downlink data to the second terminal in response to the first terminal being faulty. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the base station, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
In at least one embodiment, the method further includes: The base station receives session establishment indication information sent by a third core network device, where the session establishment indication information indicates the base station to establish, with a fourth core network device, a protocol data unit PDU session shared by the first terminal and the second terminal; and the base station establishes, with the fourth core network device, based on the session establishment indication information, the PDU session shared by the first terminal and the second terminal.
According to the foregoing design, the base station receives the session establishment indication information that is sent by the third core network device and that indicates the base station to establish, with the fourth core network device, the protocol data unit PDU session shared by the first terminal and the second terminal, and establishes, with the fourth core network device, based on the session establishment indication information, the PDU session shared by the first terminal and the second terminal. Therefore, in response to any terminal accessing a network, in response to the SMF network element determining that the terminal that is in the mutual backup relationship with the terminal has triggered establishment of the PDU session, a PDU session is not re-established, and the PDU session established by the terminal that is in the mutual backup relationship with the terminal is shared, so that in response to the primary terminal being faulty, the secondary terminal directly uses the PDU session shared by the primary terminal and the secondary terminal during data transmission, and a new PDU session is not re-established. This minimizes impact of a fault of the terminal device on service continuity of the terminal device, and improves reliability of the terminal device.
In at least one embodiment, the base station sends one copy of downlink data to the first terminal and the second terminal includes: The base station sends first configuration information to the first terminal, and sends a part or all of the first configuration information to the second terminal, where the first configuration information carries a group radio network temporary identifier RNTI or a security key shared by the first terminal and the second terminal.
In at least one embodiment, the security key is any one or more of the following: a key generated by the base station based on an identifier of the first terminal and an identifier of the second terminal; a key generated by the base station based on a random number; or a key generated by the base station for the first terminal and the second terminal; or the security key is a key that is received by the base station and that is generated by the core network device based on an identifier of the first terminal and an identifier of the second terminal.
According to the foregoing design, the base station sends the first configuration information to the first terminal, and send the part or all of the first configuration information to the second terminal, so that the first terminal and the second terminal normally perform data transmission. In addition, the base station sends one copy of downlink data to the first terminal and the second terminal based on the group RNTI shared by the first terminal and the second terminal. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the gNB. In addition, only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
In at least one embodiment, the method further includes: The base station sends first state indication information to the second terminal, where the first state indication information indicates the terminal to enter a non-working state, and the non-working state is a state in which the terminal does not send uplink data but receives downlink data, a state in which the terminal does not perform data transmission, or a state in which the terminal does not perform service data transmission but performs signaling transmission.
According to the foregoing design, the base station sends, to the second terminal, the first state indication information indicating the terminal to enter the non-working state, so that the first terminal normally performs data transmission, and the second terminal does not perform data transmission, or the second terminal does not send uplink data but receives, together with the first terminal, one copy of downlink data sent by the base station, or the second terminal does not perform service data transmission but performs signaling transmission. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the base station, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
In at least one embodiment, the method further includes: The base station determines whether the first terminal is faulty, and in response to yes, the base station sends the first state indication information to the first terminal, and sends second state indication information to the second terminal, where the second state indication information indicates the terminal to enter a working state, and the working state is a state in which the terminal sends uplink data and receives downlink data.
In at least one embodiment, the base station determines whether the first terminal is faulty includes: The base station obtains fault detection information of the first terminal, where the fault detection information carries at least one of an uplink reference signal, feedback NACK information, uplink data, and fault indication information of the first terminal, and the fault indication information indicates whether the first terminal is faulty. In response to the fault detection information not being obtained within a preset time period, the base station determines that the first terminal is faulty. In response to the fault detection information being obtained within a preset time period, the base station determines, based on the fault detection information, whether the first terminal is faulty.
According to the foregoing design, in response to determining that the first terminal is faulty, the base station sends, to the first terminal, the first state indication information indicating the terminal to enter the non-working state, and sends, to the second terminal, the second state indication information indicating the terminal to enter the working state, so that the second terminal serving as the secondary terminal replaces the first terminal serving as the primary terminal to perform data transmission with the gNB. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, and improves reliability of the terminal device.
According to a third aspect, at least one embodiment further provides a first core network device. The first core network device has a function of implementing the method in any one of the first aspect. The function is implemented by hardware, or is implemented by hardware executing corresponding software. The hardware or the software includes one or more modules corresponding to the foregoing function. For example, the hardware or the software includes a processing unit and a sending unit.
In at least one embodiment, the processing unit is configured to determine that a first terminal and a second terminal are in a mutual backup relationship.
In at least one embodiment, the sending unit is configured to send pairing indication information to a base station, where the pairing indication information indicates that the first terminal and the second terminal are in the mutual backup relationship, so that in response to determining, based on the pairing indication information, that the first terminal is a primary terminal and the second terminal is a secondary terminal, the base station sends one copy of downlink data to the first terminal and the second terminal, or sends downlink data to the first terminal and sends the downlink data to the second terminal in response to the first terminal being faulty.
In at least one embodiment, the processing unit is specifically configured to: receive registration request messages sent by the first terminal and the second terminal, where the registration request messages are used to request to connect the terminal to a core network; and after receiving the registration request information sent by the first terminal or the second terminal, obtain identification information of the second terminal or the first terminal from a second core network device, and determine, based on the identification information of the second terminal or the first terminal, that the first terminal and the second terminal are in the mutual backup relationship; after receiving the registration request information sent by the first terminal or the second terminal, obtain identification information of the second terminal or the first terminal from the registration request information sent by the first terminal or the second terminal, and determine, based on the identification information of the second terminal or the second terminal, that the first terminal and the second terminal are in the mutual backup relationship; or after receiving the registration request information sent by the first terminal or the second terminal, obtain, from an application function AF network element, identification information of terminals in the mutual backup relationship, and determine, based on the identification information of the terminals in the mutual backup relationship, that the first terminal and the second terminal are in the mutual backup relationship.
In at least one embodiment, the processing unit is further configured to receive session establishment request information sent by the first terminal or the second terminal, and send the session establishment request information to a third core network device, where the session establishment request information is used to request the base station to establish, with a fourth core network device, a protocol data unit PDU session shared by the first terminal and the second terminal.
In at least one embodiment, the sending unit is further configured to send association indication information to a peer application layer of the terminal, where the association indication information indicates the peer application layer to send downlink data to the first terminal and the second terminal in response to the peer application layer receiving uplink data sent by the first terminal or the second terminal, and the association indication information carries internet protocol IP addresses of the first terminal and the second terminal or IP addresses of the first terminal and the second terminal and an IP address of the peer application layer.
In at least one embodiment, the first core network device is a chip or an integrated circuit.
In at least one embodiment, the first core network device includes at least one processor and a memory. The memory stores one or more computer programs. In response to the one or more computer programs stored in the memory being executed by the at least one processor, the first core network device is enabled to perform the method in any one of the first aspect.
According to a fourth aspect, at least one embodiment further provides a computer-readable storage medium. The computer-readable storage medium includes a computer program. In response to the computer program being run on a computer, the computer is enabled to perform the method in any one of the first aspect.
According to a fifth aspect, at least one embodiment further provides a program product. In response to the program product being run on a computer, the computer is enabled to perform the method in any one of the first aspect.
According to a sixth aspect, at least one embodiment further provides a chip. The chip is coupled to a memory in a first core network device, and is configured to invoke a computer program stored in the memory and perform the method in any one of the first aspect.
For beneficial effects of the third aspect to the sixth aspect, refer to the foregoing descriptions of the beneficial effects of the method in any one of the first aspect.
According to a seventh aspect, at least one embodiment further provides a base station. The base station has a function of implementing the method in any one of the second aspect. The function is implemented by hardware, or is implemented by hardware executing corresponding software. The hardware or the software includes one or more modules corresponding to the foregoing function. For example, the hardware or the software includes a receiving unit, a sending unit, and a processing unit.
In at least one embodiment, the receiving unit is configured to receive pairing indication information sent by a first core network device, where the pairing indication information indicates that a first terminal and a second terminal are in a mutual backup relationship.
In at least one embodiment, the sending unit is configured to, in response to determining, based on the pairing indication information, that the first terminal is a primary terminal and the second terminal is a secondary terminal, send one copy of downlink data to the first terminal and the second terminal, or send downlink data to the first terminal and send the downlink data to the second terminal in response to the first terminal being faulty.
In at least one embodiment, the receiving unit is further configured to: receive session establishment indication information sent by a third core network device, where the session establishment indication information indicates the base station to establish, with a fourth core network device, a protocol data unit PDU session shared by the first terminal and the second terminal; and establish, with the fourth core network device, based on the session establishment indication information, the PDU session shared by the first terminal and the second terminal.
In at least one embodiment, in response to sending the copy of downlink data to the first terminal and the second terminal, the sending unit is specifically configured to: send first configuration information to the first terminal, and send a part or all of the first configuration information to the second terminal, where the first configuration information carries a group radio network temporary identifier RNTI or a security key shared by the first terminal and the second terminal.
In at least one embodiment, the security key is any one or more of the following: a key generated by the base station based on an identifier of the first terminal and an identifier of the second terminal; a key generated by the base station based on a random number; a key generated by the base station for the first terminal and the second terminal; or a key that is received by the base station and that is generated by the core network device based on an identifier of the first terminal and an identifier of the second terminal.
In at least one embodiment, the sending unit is further configured to send first state indication information to the second terminal, where the first state indication information indicates the terminal to enter a non-working state, and the non-working state is a state in which the terminal does not send uplink data but receives downlink data, a state in which the terminal does not perform data transmission, or a state in which the terminal does not perform service data transmission but performs signaling transmission.
In at least one embodiment, the processing unit is configured to determine whether the first terminal is faulty, and in response to yes, the processing unit sends the first state indication information to the first terminal, and sends second state indication information to the second terminal, where the second state indication information indicates the terminal to enter a working state, and the working state is a state in which the terminal sends uplink data and receives downlink data.
In at least one embodiment, in response to determining whether the first terminal is faulty, the processing unit is specifically configured to: obtain fault detection information of the first terminal, where the fault detection information carries at least one of an uplink reference signal, feedback NACK information, uplink data, and fault indication information of the first terminal, and the fault indication information indicates whether the first terminal is faulty. In response to the fault detection information not being obtained within a preset time period, the processing unit determines that the first terminal is faulty. In response to the fault detection information being obtained within a preset time period, the processing unit determines, based on the fault detection information, whether the first terminal is faulty.
In at least one embodiment, the base station is a chip or an integrated circuit.
In at least one embodiment, the base station includes at least one processor and a memory. The memory stores one or more computer programs. In response to the one or more computer programs stored in the memory being executed by the at least one processor, the base station is enabled to perform the method in any one of the second aspect.
According to an eighth aspect, at least one embodiment further provides a computer-readable storage medium. The computer-readable storage medium includes a computer program. In response to the computer program being run on a computer, the computer is enabled to perform the method in any one of the second aspect.
According to a ninth aspect, at least one embodiment further provides a program product. In response to the program product being run on a computer, the computer is enabled to perform the method in any one of the second aspect.
According to a tenth aspect, at least one embodiment further provides a chip. The chip is coupled to a memory in a terminal, and is configured to invoke a computer program stored in the memory and perform the method in any one of the second aspect.
For beneficial effects of the seventh aspect to the tenth aspect, refer to the foregoing descriptions of beneficial effects of the method in any one of the second aspect.
According to an eleventh aspect, at least one embodiment further provides a system for performing data transmission by two terminal devices, where the system for performing data transmission by two terminal devices includes a first core network device unit and a base station. The first core network device is configured to perform the steps performed by the first core network device in the first aspect or the solutions provided in at least one embodiment. The base station is configured to perform the steps performed by the base station in the second aspect.
In at least one embodiment, the system for performing data transmission by two terminal devices further includes another device that interacts with the first core network device or the base station in the solutions provided in at least one embodiment, for example, a first core network device, a second core network device, a third core network device, a fourth core network device, an application function AF network element, a first terminal, or a second terminal. This is not specifically limited in embodiments described herein.
To make objectives, technical solution, and advantages of embodiments described herein clearer, the following further describes embodiments in detail with reference to the accompanying drawings.
The system 200 for performing data transmission by two terminal devices provided in embodiments described herein is applicable to both a low-frequency scenario and a high-frequency scenario. Application scenarios of the system 200 for performing data transmission by two terminal devices provided in embodiments described herein include but are not limited to a global system of mobile communications (global system of mobile communications, GSM), a code division multiple access (code division multiple access, CDMA) system, a wideband code division multiple access (wideband code division multiple access, WCDMA) system, a general packet radio service (general packet radio service, GPRS) system, a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD) system, a universal mobile telecommunications system (universal mobile telecommunications system, UMTS), a worldwide interoperability for microwave access (worldwide interoperability for microwave access, WiMAX) communication system, a future 5th generation (5th generation, 5G) system, a new radio (new radio, NR) communication system, or the like.
In at least one embodiment, the first core network device 201 and the access network device 202 directly communicate with each other, or communicate with each other through forwarding by another device. This is not specifically limited in at least one embodiment.
In at least one embodiment, the first core network device 201 includes but is not limited to a mobility management network element. In response to the first core network device 201 being a mobility management network element, in addition to the foregoing functions, the first core network device 201 is further configured for mobility management in a mobile network, for example, user location update, user network registration, or user handover. In a 5th generation (5th generation, 5G) communication system, a network element or an entity corresponding to a mobility management network element is an access and mobility management function (access and mobility management function, AMF) network element in a 5G network architecture. Namf is a service-based interface provided by the AMF network element. The AMF network element communicates with another network function through Namf. In a future communication system such as the 6th generation (the 6th generation, 6G) communication system, the mobility management network element is still the AMF network element, or the mobility management network element has another name. This is not limited in embodiments described herein.
In at least one embodiment, the access network device 202 includes but is not limited to: a next generation NodeB (gNodeB, gNB) in 5G, an evolved NodeB (evolved NodeB, eNB), a radio network controller (radio network controller, RNC), a NodeB (NodeB, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (for example, a home evolved NodeB, or a home NodeB, HNB), a baseband unit (baseband unit, BBU), a transmission point (transmitting and receiving point, TRP), a transmission point (transmitting point, TP), a mobile switching center, or the like. This is not limited in at least one embodiment. Alternatively, the access network device 202 is a communication chip having a communication module. In an execution process of the method for performing data transmission by two terminal devices provided in at least one embodiment, the access network device 202 is used as a radio access network (radio access network, RAN) base station to provide a wireless network connection for a first terminal and a second terminal. For example, the access network device 202 is used as an access network base station in a 4G access network such as an evolved universal mobile telecommunications system (universal mobile telecommunications system, UMTS) terrestrial radio access network (evolved UMTS terrestrial radio access network, E-UTRAN), the access network device 202 is used as an access network base station in a 5G access network such as a 5G RAN, or the access network device 202 is used as an access network base station in a future wireless communication system.
In at least one embodiment, the first terminal 301 and the second terminal 302 is devices having wireless transceiver functions, and is deployed on land, including indoors, outdoors, handheld, or vehicle-mounted devices; is deployed on the water (for example, on a ship); or is deployed in the air (for example, on an airplane, a balloon, or a satellite). The first terminal 301 and the second terminal 302 communicate with one or more network devices in one or more communication systems, and accept a network service provided by the access network device 202. For example, the first terminal 301 and the second terminal 302 in at least one embodiment are a mobile phone (which is also referred to as a “cellular” phone), a computer having a mobile terminal, or the like. Alternatively, the first terminal 301 and the second terminal 302 are user equipment (user equipment, UE), a terminal (terminal), a mobile station (mobile station, MS), a mobile phone (mobile phone), a tablet computer (pad), a computer having a wireless transceiver function, a virtual reality (virtual reality, VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in telemedicine (remote medical), a wireless terminal in a smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), or the like. Alternatively, the first terminal 301 and the second terminal 302 is communication chips having communication modules.
In at least one embodiment, the second core network device 303 includes but is not limited to a data management network element, and is configured to process a user identifier, access authentication, registration, mobility management, or the like. In the 5G communication system, a network element or an entity corresponding to the data management network element is a unified data management (unified data management, UDM) network element in a 5G network architecture, where Nudm is a service-based interface provided by the UDM network element, and the UDM network element communicates with another network function through Nudm. In a future communication system such as the 6G communication system, the data management network element is still the UDM network element, or the data management network element has another name. This is not limited in this embodiments described herein.
In at least one embodiment, the third core network device 304 includes but is not limited to a session management network element, and is configured to manage a protocol data unit (protocol data unit, PDU) session of the terminal device. The PDU session is a channel used to transmit a PDU. The terminal device transmits the PDU to a data network (data network, DN) by using the PDU session. The PDU session is established, maintained, deleted, and the like by the session management network element. The session management network element includes session-related functions such as session management (such as session establishment, modification, and release, including maintenance of a tunnel between a user plane network element and an access network), selection and control of a user plane network element, service and session continuity (Service and Session Continuity, SSC) mode selection, and roaming. In the 5G communication system, a network element or an entity corresponding to the session management network element is a session management function (session management function, SMF) network element in a 5G wireless communication system. In the future communication system such as the 6th generation (the 6th generation, 6G) communication system, the session management network element is still the SMF network element, or the session management network element uses another name. This is not limited in embodiments described herein.
In at least one embodiment, the fourth core network device 305 includes but is not limited to a user plane network element, and is configured to perform packet routing and forwarding, quality of service (quality of service, QoS) processing of user plane data, and the like. In the 5G communication system, a network element or an entity corresponding to the user plane network element is a user plane function (user plane function, UPF) network element in the 5G wireless communication system. In the future communication system such as the 6th generation (the 6th generation, 6G) communication system, the user plane network element is still the UPF network element, or the user plane network element has another name This is not limited in this embodiments described herein.
In at least one embodiment, the fifth core network device 306 includes but is not limited to a network exposure function network element. A service mainly provided enables a 3rd generation partnership project (3rd generation partnership project, 3GPP) network to securely provide a network service capability for a third-party service provider application function network element 307. In the 5G communication system, the network exposure function network element is a network exposure function (network exposure function, NEF) network element. Nnef is a service-based interface provided by the NEF network element, and the NEF network element communicates with another network function through Nnef. In the future communication system such as the 6G communication system, the network exposure function network element is still the NEF network element, or uses another name. This is not limited in embodiments described herein.
In at least one embodiment, the application function network element 307 is mainly configured to provide application layer information for a 3GPP network. In the 5G communication system, the application function network element is an application function (application function, AF) network element. Naf is a service-based interface provided by the AF network element, and the AF network element communicates with another network function through Naf. In the future communication system such as the 6G communication system, the application function network element is still be the AF network element, or uses another name. This is not limited in embodiments described herein. For example, the AF network element includes a service capability server (service capability server, SCS) or an application server (application server, AS).
In addition, a 5G communication system is used as an example.
An N1 interface in
In addition, control plane network elements such as the AMF network element, the SMF network element, the UDM network element, the NEF network element, or the AF network element shown in
The foregoing network elements or functions is network elements in a hardware device, is software functions running on dedicated hardware, or is virtualized functions instantiated on a platform (for example, a cloud platform). One or more services is obtained through division into the network elements or the functions. Further, services that exist independently of network functions occurs. In at least one embodiment, instances of the functions, instances of services included in the functions, or instances of the services that exist independently of network functions is referred to as service instances.
Before embodiments are described, some terms are first described, to help a person skilled in the art have a better understanding.
Carrying means that information is used to carry information or data, or means that the information includes the information.
In at least one embodiment, a mutual backup relationship means that in response to a terminal being faulty, a terminal replaces the terminal to perform data transmission.
In addition, terms “system” and “network” in embodiments described herein are used interchangeably. “At least one” means one or more, and “a plurality of” means two or more. A term “and/or” describes an association relationship between associated objects and indicates that three relationships exist. For example, A and/or B indicate the following cases: Only A exists, both A and B exist, and only B exists, where A and B is singular or plural. The character “/” generally represents an “or” relationship between associated objects. The singular expression forms “one”, “a”, “the”, “the foregoing”, “this”, and “the one” are also intended to include an expression form such as “one or more”, unless the opposite is explicitly indicated in the context thereof. In addition, unless otherwise stated, ordinal numbers such as “first” and “second” in at least one embodiment are for distinguishing between a plurality of objects, but are not intended to limit an order, a time sequence, priorities, or importance of the plurality of objects. For example, a first terminal and a second terminal are merely used to distinguish between different terminals, but do not indicate that priorities, importance degrees, or the like of the two terminals are different.
Reference to “an embodiment”, “some embodiments”, or the like described in embodiments herein means that one or more embodiments include a specific feature, structure, or characteristic described with reference to embodiments. Therefore, statements such as “in an embodiment”, “in some embodiments”, “in some other embodiments”, and “in other embodiments” that appear at different places in this specification do not necessarily mean referring to a same embodiment. Instead, the statements mean “one or more but not all of embodiments”, unless otherwise specifically emphasized in another manner. The terms “include”, “have”, and their variants all mean “include but are not limited to”, unless otherwise specifically emphasized in another manner.
The following specifically describes, with reference to
The method shown in embodiments described herein is not only applied to the communication systems shown in
In some embodiments,
S501: A first terminal and a second terminal send registration request information to the AMF network element. Correspondingly, the AMF network element receives the registration request information from the first terminal and the second terminal. The registration request information is used to request to connect the terminal to a core network.
In some embodiments, in response to the terminal accessing the core network, the terminal sends, to the AMF network element, the registration request information that carries identification information of the terminal, where a registration request carries the identification information of the terminal. The identification information of the terminal is an international mobile equipment identity (international mobile equipment identity, IMEI), a subscription permanent identifier (subscription permanent identifier, SUPI), a subscription concealed identifier (subscription concealed identifier, SUCI) of the terminal, or other information that identifies the terminal. This is not specifically limited in embodiments described herein.
In at least one embodiment, the first terminal and the second terminal send the registration request information to the AMF network element means that the second terminal sends the registration request information to the AMF network element after the first terminal sends the registration request information to the AMF network element, means that the first terminal sends the registration request information to the AMF network element after the second terminal sends the registration request information to the AMF network element, or means that the first terminal and the second terminal simultaneously send the registration request information to the AMF network element. This is not specifically limited in embodiments described herein.
S502: The AMF network element determines that the first terminal and the second terminal are in a mutual backup relationship.
In some embodiments, after receiving the registration request information of the first terminal or the second terminal, the AMF network element obtains the identification information of the second terminal or the first terminal from the UDM network element, and determine, based on the identification information of the second terminal or the first terminal, that the first terminal and the second terminal are in the mutual backup relationship.
For example, after receiving the registration request information of the first terminal, the AMF network element sends subscription request information to the UDM network element. The subscription request information is used to request the UDM network element to return identification information of a terminal that is in the mutual backup relationship with the first terminal, and the subscription request information carries the identification information of the first terminal. Correspondingly, after receiving the subscription request information from the AMF network element, the UDM network element determines, based on the identification information of the first terminal, that the terminal that is in the mutual backup relationship with the first terminal is the second terminal, and send subscription information to the AMF network element, where the subscription information carries the identification information of the second terminal. Correspondingly, after receiving the subscription information from the UDM network element, the AMF network element determines, based on the identification information of the second terminal, that the first terminal and the second terminal are in the mutual backup relationship.
In some other embodiments, after receiving the registration request information of the first terminal or the second terminal, the AMF network element obtains the identification information of the second terminal or the first terminal from the registration request information sent by the first terminal or the second terminal, and determine, based on the identification information of the second terminal or the first terminal, that the first terminal and the second terminal are in the mutual backup relationship.
For example, the registration request information of the first terminal carries identification information of a terminal that is in the mutual backup relationship with the first terminal, for example, the identification information of the second terminal. The registration request information of the second terminal carries identification information of a terminal that is in the mutual backup relationship with the second terminal, for example, the identification information of the first terminal. After receiving the registration request information of the first terminal, the AMF network element obtains the identification information of the second terminal from the registration request information sent by the first terminal, and determine, based on the identification information of the second terminal, that the first terminal and the second terminal are in the mutual backup relationship.
In some other embodiments, after receiving the registration request information of the first terminal or the second terminal, the AMF network element obtains, from an AF network element, identification information of terminals in the mutual backup relationship, and determine, based on the identification information of the terminals in the mutual backup relationship, that the first terminal and the second terminal are in the mutual backup relationship.
For example, backup information is preset in the AF network element. The backup information includes the identification information of the terminals in the mutual backup relationship. The identification information of the terminal is an IMEI, an SUPI, or an SUCI of the terminal, or is a generic public subscription identifier (generic public subscription identifier, GPSI), or other information that identifies the terminal. This is not specifically limited in embodiments described herein. The AF network element sends the backup information to the SMF network element. Correspondingly, the SMF network element receives the backup information from the AF network element. In response to In response to the identification information of the terminal being the GPSI, because the GPSI is an external identifier, the AMF network element cannot identify the GPSI, and therefore cannot determine the terminal corresponding to the identification information. In this case, the SMF network element sends the backup information to the UDM network element. Correspondingly, after receiving the backup information from the SMF network element, the UDM network element translates the identification information of the terminal from the GPSI into the IMEI, the SUPI, or the SUCI of the terminal, or the other information that identifies the terminal, and then the UDM network element sends translated backup information to the AMF network element. In response to In response to the identification information of the terminal not being the GPSI, the SMF network element directly sends the backup information to the AMF network element. After receiving the registration request information of the first terminal, the AMF network element determines, based on the backup information from the SMF network element or the UDM network element, that the first terminal and the second terminal are in the mutual backup relationship.
In some other embodiments, after receiving the registration request information of the first terminal or the second terminal, the AMF network element obtains, from the SMF network element, identification information of terminals that are in the mutual backup relationship or support a same service, and determine, based on the identification information of the terminals that are in the mutual backup relationship or support the same service, that the first terminal and the second terminal are in the mutual backup relationship.
For example, backup information or service information is preset in the SMF network element. The backup information carries the identification information of the terminals in the mutual backup relationship, and the service information carries the identification information of the terminals that support the same service. The identification information of the terminal is an IMEI, an SUPI, an SUCI, or a GPSI of the terminal, or other information that identifies the terminal. This is not specifically limited in embodiments described herein. In response to the identification information of the terminal being the GPSI, the SMF network element sends the backup information to the UDM network element. Correspondingly, after receiving the backup information from the SMF network element, the UDM network element translates the identification information of the terminal from the GPSI into the IMEI, the SUPI, or the SUCI of the terminal, or the other information that identifies the terminal, and then the UDM network element sends translated backup information to the AMF network element. In response to the identification information of the terminal not being the GPSI, the SMF network element directly sends the backup information to the AMF network element. After receiving the registration request information of the first terminal, the AMF network element determines, based on the backup information from the SMF network element or the UDM network element, that the first terminal and the second terminal are in the mutual backup relationship.
For example, backup information or service information is preset in the SMF network element. The backup information carries the identification information of the terminals in the mutual backup relationship, and the service information carries the identification information of the terminals that support the same service. The identification information of the terminal is an IMEI, an SUPI, an SUCI, or a GPSI of the terminal, or other information that identifies the terminal. This is not specifically limited in embodiments described herein. In response to the identification information of the terminal being identification information that cannot be identified by the AMF network element or the gNB, for example, the GPSI, the identification information of the terminal is translated or mapped into identification information that is identified by the AMF network element or the gNB, for example, an AMF UE NGAP ID or a RAN UE NGAP ID, and then translated or mapped backup information is sent to the AMF network element. After receiving the registration request information of the first terminal, the AMF network element determines, based on the backup information from the SMF network element, that the first terminal and the second terminal are in the mutual backup relationship.
In at least one embodiment, after receiving the registration request information of the first terminal or the second terminal, the AMF network element determines that the first terminal and the second terminal are in the mutual backup relationship, so that the AMF network element authenticates the backup relationship between the first terminal and the second terminal. Further, the gNB authenticates the backup relationship between the first terminal and the second terminal, so that in response to determining that the first terminal is a primary terminal and the second terminal is a secondary terminal, the gNB sends one copy of downlink data to the first terminal and the second terminal, or send downlink data to the first terminal and send the downlink data to the second terminal in response to the first terminal being faulty. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the gNB, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
S503: The first terminal or the second terminal sends session establishment request information to the AMF network element. Correspondingly, the AMF network element receives the session establishment request information from the first terminal or the second terminal, and sends the session establishment request information to the SMF network element. The session establishment request information is used to request the SMF network element to establish a PDU session shared by the first terminal and the second terminal.
In some embodiments, the AMF network element receives the session establishment request information from the first terminal, and sends the session establishment request information to the SMF network element. The session establishment request information is used to request the SMF network element to establish the PDU session shared by the first terminal and the terminal that is in the mutual backup relationship with the first terminal. Specifically, the session establishment request information carries session establishment indication information, and the session establishment indication information indicates the gNB and the UPF network element to establish the PDU session shared by the first terminal and the terminal that is in the mutual backup relationship with the first terminal. An establishment process is as follows: The SMF network element sends CN Tunnel Info (UPF network element address information) and the session establishment indication information to the AMF network element and the gNB. The gNB sends AN Tunnel Info (gNB address information) to the AMF network element, and the AMF network element forwards the AN Tunnel Info to the SMF network element. Then, the PDU session shared by the first terminal between the gNB and the UPF network element, and the terminal that is in the mutual backup relationship with the first terminal is established.
In some other embodiments, after the AMF network element receives the registration request information of the first terminal, the first terminal sends the session establishment request information to the AMF network element. Correspondingly, the AMF network element receives the session establishment request information from the first terminal, and sends the session establishment request information to the SMF network element. The session establishment request information is used to request the SMF network element to establish a PDU session exclusive to the first terminal. After the AMF network element receives the registration request information of the second terminal, the second terminal sends the session establishment request information to the AMF network element. Correspondingly, the AMF network element receives the session establishment request information from the second terminal, and sends the session establishment request information to the SMF network element. The session establishment request information is used to request the SMF network element to establish a PDU session exclusive to the second terminal. After the SMF network element receives the session establishment request information of the first terminal and the second terminal, in response to the SMF network element or the UPF network element obtaining session-related subscription information according to the method described in step 502, where the session-related subscription information includes the identification information of the terminals in the mutual backup relationship, for example, the identification information of the first terminal and the second terminal, the SMF network element or the UPF network element determines that either of the PDU sessions is selected to send one copy of data to the gNB, for example, the PDU session of the first terminal is selected to send one copy of data to the gNB. In response to the gNB determining that the first terminal and the second terminal are in the mutual backup relationship, the gNB sends one copy of data to either of the first terminal and the second terminal or the first terminal and the second terminal. In response to the gNB determining that the first terminal is faulty, the gNB notifies the core network device to change the PDU session. For example, one copy of data is sent to the gNB by using the PDU session of the second terminal.
In some other embodiments, after the AMF network element receives the registration request information of the first terminal, the first terminal sends the session establishment request information to the AMF network element. Correspondingly, the AMF network element receives the session establishment request information from the first terminal, and sends the session establishment request information to the SMF network element. The session establishment request information is used to request the SMF network element to establish a PDU session exclusive to the first terminal. After the AMF network element receives the registration request information of the second terminal, the second terminal sends the session establishment request information to the AMF network element. Correspondingly, the AMF network element receives the session establishment request information from the second terminal, and sends the session establishment request information to the SMF network element. The session establishment request information is used to request the SMF network element to establish a PDU session exclusive to the second terminal. After the SMF network element receives the session establishment request information of the first terminal and the second terminal, in response to the SMF network element or the UPF network element not obtaining session-related subscription information, where the session-related subscription information includes the identification information of the terminals in the mutual backup relationship, for example, the identification information of the first terminal and the second terminal, the SMF network element or the UPF network element separately sends two copies of data to the gNB by using the PDU sessions of the first terminal and the second terminal. After receiving pairing indication information sent by the AMF network element, the gNB determines that the first terminal and the second terminal are in the mutual backup relationship, so that the gNB sends only one copy of data to the first terminal and the second terminal.
In at least one embodiment, after the first terminal or the second terminal sends the session establishment request information to the AMF network element, the AMF network element sends the session establishment request information to the SMF network element. The AMF network element sends the session establishment request information to the SMF network element before determining that the first terminal and the second terminal are in the mutual backup relationship, or the AMF network element sends the session establishment request information to the SMF network element after determining that the first terminal and the second terminal are in the mutual backup relationship. This is not specifically limited in embodiments described herein.
In at least one embodiment, step 503 is an optional step. The first terminal sends, to the AMF network element, the session establishment request information used to request to establish the PDU session exclusive to the first terminal, and the second terminal sends, to the AMF network element, the session establishment request information used to request to establish the PDU session exclusive to the second terminal. This is not specifically limited in embodiments described herein.
In at least one embodiment, after receiving the registration request information of the first terminal or the second terminal, the AMF network element receives the session establishment request information of the first terminal or the second terminal, and send the session establishment request information to the SMF network element, so that the SMF network element sends, to the gNB, the session establishment indication information indicating the gNB and the UPF network element to establish the PDU session shared by the first terminal and the second terminal. Therefore, in response to any terminal accessing a network, in response to the SMF network element determining that a terminal that is in the mutual backup relationship with the terminal has triggered establishment of a PDU session, a PDU session is not re-established, and a PDU session established by the terminal that is in the mutual backup relationship with the terminal is shared. In this way, in response to the primary terminal being faulty, the secondary terminal directly uses the PDU session shared by the primary terminal and the secondary terminal during data transmission, and a new PDU session is not re-established. This minimizes impact of a fault of the terminal device on service continuity of the terminal device, and improves reliability of the terminal device.
S504: The AMF network element sends the pairing indication information to the gNB. Correspondingly, the gNB receives the pairing indication information from the AMF network element. The pairing indication information indicates that the first terminal and the second terminal are in the mutual backup relationship.
In some embodiments, after determining that the first terminal and the second terminal are in the mutual backup relationship, the AMF network element sends, to the gNB, the pairing indication information indicating that the first terminal and the second terminal are in the mutual backup relationship. The pairing indication information carries the identification information of the first terminal and the second terminal, and the identification information is identification information that is identified by the gNB, for example, an AMF UE NGAP ID or a RAN UE NGAP ID. Signaling for sending the pairing indication information is NG-AP signaling, such as DOWNLINK NAS TRANSPORT, INITIAL CONTEXT SETUP REQUEST, or UE CONTEXT MODIFICATION REQUEST.
In at least one embodiment, after determining that the first terminal and the second terminal are in the mutual backup relationship, the AMF network element sends, to the gNB, the pairing indication information indicating that the first terminal and the second terminal are in the mutual backup relationship, so that the gNB authenticates the backup relationship between the first terminal and the second terminal, and in response to determining that the first terminal is a primary terminal and the second terminal is a secondary terminal, the gNB sends one copy of downlink data to the first terminal and the second terminal, or send downlink data to the first terminal and send the downlink data to the second terminal in response to the first terminal being faulty. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the gNB, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources. In some other embodiments, after the AMF network element determines that the first terminal and the second terminal are in the mutual backup relationship, the AMF network element directly sends association indication information to a peer application layer of the terminal, or sends the association indication information to the peer application layer by using the SMF network element or the UPF network element. This is not specifically limited in embodiments described herein. Correspondingly, the peer application layer receives the association indication information from the AMF network element, the SMF network element, or the UPF network element. The peer application layer of the terminal is an application layer corresponding to a destination internet protocol (internet protocol, IP) address of uplink data sent by the terminal. After the terminal sends the uplink data to the gNB, the gNB needs to send the uplink data to the peer application layer. The association indication information indicates the peer application layer to send downlink data to the first terminal and the second terminal in response to the peer application layer receiving the uplink data sent by the first terminal or the second terminal. The association indication information carries IP addresses of the first terminal and the second terminal or IP addresses of the first terminal and the second terminal and an IP address of the peer application layer.
In at least one embodiment, that the AMF network element sends the association indication information to the peer application layer is that the AMF network element sends the association indication information to the peer application layer before the AMF network element sends the pairing indication information to the gNB, or is that the AMF network element sends the association indication information to the peer application layer after the AMF network element sends the pairing indication information to the gNB. This is not specifically limited in embodiments described herein.
In at least one embodiment, after determining that the first terminal and the second terminal are in the mutual backup relationship, the AMF network element sends, to the peer application layer, the association indication information indicating the peer application layer to send the downlink data to the first terminal and the second terminal in response to the peer application layer receiving the uplink data sent by the first terminal or the second terminal, so that in response to receiving the uplink data sent by any terminal, the peer application layer sends the downlink data to the terminal and the terminal that is in the mutual backup relationship with the terminal. Therefore, in response to the terminal sending the uplink data only after receiving the downlink data or the peer application layer sending the downlink data only after receiving the uplink data, the secondary terminal also normally performs data transmission. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, and improves reliability of the terminal device.
S505: In response to determining, based on the pairing indication information, that the first terminal is a primary terminal and the second terminal is a secondary terminal, the gNB sends first configuration information to the first terminal, and sends a part or all of the first configuration information to the second terminal. Correspondingly, the first terminal receives the first configuration information from the gNB, and the second terminal receives the part or all of the first configuration information from the gNB. The first configuration information carries a group radio network temporary identifier RNTI or a security key shared by the first terminal and the second terminal.
In some embodiments, after receiving, from the AMF network element, the pairing indication information indicating that the first terminal and the second terminal are in the mutual backup relationship, the gNB determines the primary terminal and the secondary terminal in the terminals in the mutual backup relationship. In response to determining that the first terminal is the primary terminal and the second terminal is the secondary terminal, the gNB sends the first configuration information to the first terminal, and send the part or all of the first configuration information to the second terminal. The first configuration information carries a group radio network temporary identifier (radio network temporary identity, RNTI), a security key, a security algorithm, a physical layer configuration, or the like shared by the first terminal and the second terminal. The group RNTI is used to enable the gNB to send one copy of downlink data to the first terminal and the second terminal based on the group RNTI shared by the first terminal and the second terminal. The security key is a key generated by the gNB based on the identifier of the first terminal and the identifier of the second terminal, a key generated by the gNB based on a random number, keys generated by the gNB separately for the first terminal and the second terminal, or a key that is received by the gNB and that is generated by the core network device based on the identifier of the first terminal and the identifier of the second terminal. This is not specifically limited in embodiments described herein. Because the first terminal and the second terminal shares a part of or all configurations, in response to the gNB sending data to the first terminal, the second terminal also receives the data from the gNB. In addition, as the backup terminal, the second terminal does not provide an uplink feedback for the downlink data, and support discontinuous data delivery to an upper layer.
In some other embodiments, after the security keys of the first terminal and the second terminal are activated, the gNB sends the security key of the first terminal to the second terminal by using a radio resource control (radio resource control, RRC) protocol message, so that the second terminal parses, by using the security key of the first terminal, data sent by the gNB to the first terminal. In addition, the gNB sends the identification information of the first terminal, for example, a cell radio network temporary identifier (cell-radio network temporary identifier, C-RNTI), to the second terminal. In this case, the second terminal stores both the C-RNTI of the first terminal and a C-RNTI of the second terminal, so that the second terminal receives, based on the C-RNTI of the first terminal, the data sent by the gNB to the first terminal.
In at least one embodiment, in response to determining that the first terminal is the primary terminal and the second terminal is the secondary terminal, the gNB sends the first configuration information to the first terminal, and send the part or all of the first configuration information to the second terminal, so that the first terminal and the second terminal normally perform data transmission. In addition, the gNB sends one copy of downlink data to the first terminal and the second terminal based on the group RNTI shared by the first terminal and the second terminal. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the gNB. In addition, only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
S506: The gNB sends first state indication information to the second terminal. Correspondingly, the second terminal receives the first state indication information from the gNB. The first state indication information indicates the terminal to enter a non-working state, where the non-working state is a state in which the terminal does not send uplink data but receives downlink data, a state in which the terminal does not perform data transmission, or a state in which the terminal does not perform service data transmission but performs signaling transmission and transmits a media access control control element (medium access control control element, MAC CE).
In some embodiments, after sending the first configuration information to the first terminal and sending the part or all of the first configuration information to the second terminal, the gNB sends, to the second terminal, the first state indication information indicating the terminal to enter the non-working state. The non-working state is a state in which the terminal does not send uplink data but receives downlink data, a state in which the terminal does not perform data transmission, or a state in which the terminal does not perform service data transmission but performs signaling transmission and transmits a MAC CE. For example, in response to the terminal entering the non-working state, the terminal does not receive uplink and downlink service data but receive control information such as uplink and downlink signaling and a MAC CE, or the terminal receives downlink data and provide a feedback, or receives downlink data without providing a feedback. In response to In response to the terminal providing a feedback, the gNB determines, based on feedback information, that a packet data convergence protocol (packet data convergence protocol, PDCP) service data unit (service data unit, SDU) or a complete application layer data packet has been successfully sent to either of the first terminal and the second terminal, and the gNB does not continue to repeatedly send data to ensure that each terminal receives the data. The first state indication information is included in downlink control information (downlink control information, DCI) or a MAC CE, or is included in an RRC message. This is not specifically limited in embodiments described herein.
In at least one embodiment, the gNB sends, to the second terminal, the first state indication information indicating the terminal to enter the non-working state, so that the first terminal normally performs data transmission, and the second terminal does not perform data transmission, or the second terminal does not send uplink data but receives, together with the first terminal, one copy of downlink data sent by the gNB. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the gNB, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
S507: The gNB determines whether the first terminal is faulty. In response to yes, the gNB sends the first state indication information to the first terminal, and sends second state indication information to the second terminal. Correspondingly, the first terminal receives the first state indication information from the gNB, and the second terminal receives the second state indication information from the gNB. The second state indication information indicates the terminal to enter a working state, and the working state is a state in which the terminal sends uplink data and receives downlink data.
In some embodiments, after sending, to the second terminal, the first state indication information indicating the terminal to enter the non-working state, the gNB determines whether the first terminal is faulty. In response to yes, the gNB sends the first state indication information to the first terminal, and sends, to the second terminal, the second state indication information indicating the terminal to enter the working state. The working state is a state in which the terminal sends uplink data and receives downlink data. The second state indication information is sent by using DCI or a MAC CE, or is sent by using an RRC message, for example, an RRC reconfiguration message. This is not specifically limited embodiments described herein.
After sending, to the second terminal, the first state indication information indicating the terminal to enter the non-working state, the gNB also sends the first state indication information to the first terminal in response to determining that a radio link of the first terminal is faulty or that the radio link of the first terminal is poor, and send, to the second terminal, the second state indication information indicating the terminal to enter the working state. This is not specifically limited in embodiments described herein.
For example, the gNB obtains fault detection information of the first terminal. In response to the gNB not obtaining the fault detection information within a preset time period, the gNB determines that the first terminal is faulty or the radio link of the first terminal is faulty and the first terminal is to be taken over by the second terminal. In response to the gNB obtaining the fault detection information within a preset time period, the gNB determines, based on the fault detection information of the first terminal, whether the first terminal is faulty. The fault detection information carries at least one of an uplink reference signal, feedback NACK information (or no received ACK information), uplink data, and fault indication information of the first terminal. The fault indication information indicates whether the first terminal is faulty. Specifically, the second terminal determines, based on a heartbeat packet between the first terminal and the second terminal or feedback NACK information of the gNB, whether the first terminal is faulty, and send the fault indication information to the gNB. This is not specifically limited in embodiments described herein. In response to the fault detection information carrying the uplink reference signal of the first terminal, the gNB performs uplink measurement based on the uplink reference signal of the first terminal. In response to a measurement value being less than a preset threshold for a period of time, the first terminal is faulty or the radio link of the first terminal is faulty. In response to the fault detection information carrying the feedback information of the first terminal, and in response to the base station not receiving, within a preset time period, the feedback information of the first terminal for the downlink data, the first terminal is faulty or that the radio link of the first terminal is faulty. In at least one embodiment, in response to determining that the first terminal is faulty, the gNB sends, to the first terminal, the first state indication information indicating the terminal to enter the non-working state, and sends, to the second terminal, the second state indication information indicating the terminal to enter the working state, so that the second terminal serving as the secondary terminal replaces the first terminal serving as the primary terminal to perform data transmission with the gNB. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, and improves reliability of the terminal device.
In at least one embodiment, after determining that the first terminal and the second terminal are in the mutual backup relationship, the AMF network element sends, to the gNB, the pairing indication information indicating that the first terminal and the second terminal are in the mutual backup relationship, so that in response to determining, based on the pairing indication information, that the first terminal is the primary terminal and the second terminal is the secondary terminal, the gNB sends one copy of downlink data to the first terminal and the second terminal. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the gNB, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
The following describes the embodiments shown in
In some other embodiments, an example in which the wireless communication system shown in
S601: A first terminal and a second terminal send registration request information to an AMF network element. Correspondingly, the AMF network element receives the registration request information from the first terminal and the second terminal. The registration request information is used to request to connect the terminal to a core network.
S602: The AMF network element determines that the first terminal and the second terminal are in a mutual backup relationship.
S603: The first terminal or the second terminal sends session establishment request information to the AMF network element. Correspondingly, the AMF network element receives the session establishment request information from the first terminal or the second terminal, and sends the session establishment request information to an SMF network element. The session establishment request information is used to request the SMF network element to establish a PDU session shared by the first terminal and the second terminal.
S604: The AMF network element sends pairing indication information to a gNB. Correspondingly, the gNB receives the pairing indication information from the AMF network element. The pairing indication information indicates that the first terminal and the second terminal are in the mutual backup relationship.
Steps S601 to S604 are the same as steps S501 to S504 in the embodiment shown in
S605: In response to determining, based on the pairing indication information, that the first terminal is a primary terminal and the second terminal is a secondary terminal, the gNB sends second configuration information to the first terminal, and sends third configuration information to the second terminal. Correspondingly, the first terminal receives the second configuration information from the gNB, and the second terminal receives the third configuration information from the gNB. The second configuration information carries an RNTI, a security key, or a time-frequency resource of the first terminal, and the third configuration information carries an RNTI, a security key, or a time-frequency resource of the second terminal.
In some embodiments, after receiving, from the AMF network element, the pairing indication information indicating that the first terminal and the second terminal are in the mutual backup relationship, the gNB determines the primary terminal and the secondary terminal in the terminals in the mutual backup relationship. In response to determining that the first terminal is the primary terminal and the second terminal is the secondary terminal, the gNB sends the second configuration information to the first terminal, and send the third configuration information to the second terminal. The second configuration information carries the RNTI, the security key, or the time-frequency resource of the first terminal, and the third configuration information carries the RNTI, the security key, or the time-frequency resource of the second terminal. In this way, the first terminal and the second terminal normally perform data transmission, and further, the gNB sends downlink data to the first terminal and send the downlink data to the second terminal in response to the first terminal being faulty, so that the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the gNB, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
S606: The gNB sends first state indication information to the second terminal. Correspondingly, the second terminal receives the first state indication information from the gNB. The first state indication information indicates the terminal to enter a non-working state, and the non-working state is a state in which the terminal does not perform data transmission, or a state in which the terminal does not perform service data transmission but performs signaling transmission and transmits a MAC CE.
In some embodiments, after sending the second configuration information to the first terminal, and sending the third configuration information to the second terminal, the gNB sends, to the second terminal, the first state indication information indicating the terminal to enter the non-working state. The non-working state is a state in which the terminal does not perform data transmission, or a state in which the terminal does not perform service data transmission but performs signaling transmission and transmits a MAC CE. The first state indication information is included in DCI or a MAC CE, or is included in an RRC message. This is not specifically limited in embodiments described herein.
In at least one embodiment, the gNB sends, to the second terminal, the first state indication information indicating the terminal to enter the non-working state, so that the first terminal normally performs data transmission, and the second terminal does not perform data transmission, or the second terminal does not perform service data transmission but performs signaling transmission and transmits a MAC CE. Further, the gNB is enabled to send downlink data to the second terminal in response to the first terminal being faulty. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the gNB, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
S607: The gNB determines whether the first terminal is faulty. In response to yes, the gNB sends the first state indication information to the first terminal, and sends second state indication information to the second terminal. Correspondingly, the first terminal receives the first state indication information from the gNB, and the second terminal receives the second state indication information from the gNB. The second state indication information indicates the terminal to enter a working state, and the working state is a state in which the terminal sends uplink data and receives downlink data.
In some embodiments, after sending, to the second terminal, the first state indication information indicating the terminal to enter the non-working state, the gNB determines whether the first terminal is faulty. In response to yes, the gNB sends the first state indication information to the first terminal, and sends, to the second terminal, the second state indication information indicating the terminal to enter the working state. The working state is a state in which the terminal sends uplink data and receives downlink data. The second state indication information is sent by using DCI or a MAC CE, or is sent by using an RRC message, for example, an RRC reconfiguration message. This is not specifically limited in embodiments described herein.
After sending, to the second terminal, the first state indication information indicating the terminal to enter the non-working state, the gNB also sends the first state indication information to the first terminal in response to determining that a radio link of the first terminal is faulty or that the radio link of the first terminal is poor, and send, to the second terminal, the second state indication information indicating the terminal to enter the working state. This is not specifically limited in embodiments described herein.
For example, the gNB obtains fault detection information of the first terminal. In response to the gNB not obtaining the fault detection information within a preset time period, the gNB determines that the first terminal is faulty or the radio link of the first terminal is faulty and the first terminal is to be taken over by the second terminal. In response to the gNB obtaining the fault detection information within a preset time period, the gNB determines, based on the fault detection information of the first terminal, whether the first terminal is faulty. The fault detection information carries at least one of an uplink reference signal, feedback NACK information (or no received ACK information), uplink data, and fault indication information of the first terminal. The fault indication information indicates whether the first terminal is faulty. Specifically, the second terminal determines, based on a heartbeat packet between the first terminal and the second terminal or feedback NACK information of the gNB, whether the first terminal is faulty, and send the fault indication information to the gNB. This is not specifically limited in embodiments described herein. In response to the fault detection information carrying the uplink reference signal of the first terminal, the gNB performs uplink measurement based on the uplink reference signal of the first terminal. In response to a measurement value being less than a preset threshold for a period of time, is determined that the first terminal is faulty or the radio link of the first terminal is faulty. In response to the fault detection information carrying the feedback information of the first terminal, and in response to a base station not receiving, within a preset time period, the feedback information of the first terminal for the downlink data, the first terminal is faulty or that the radio link of the first terminal is faulty.
In at least one embodiment, in response to determining that the first terminal is faulty, the gNB sends, to the first terminal, the first state indication information indicating the terminal to enter the non-working state, and sends, to the second terminal, the second state indication information indicating the terminal to enter the working state. In other words, the gNB sends downlink data to the second terminal in response to the first terminal being faulty, so that the second terminal serving as the secondary terminal replaces the first terminal serving as the primary terminal to perform data transmission with the gNB, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device is faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
In at least one embodiment, after determining that the first terminal and the second terminal are in the mutual backup relationship, the AMF network element sends, to the gNB, the pairing indication information indicating that the first terminal and the second terminal are in the mutual backup relationship, so that in response to determining, based on the pairing indication information, that the first terminal is the primary terminal and the second terminal is the secondary terminal, the gNB sends downlink data to the first terminal and send the downlink data to the second terminal in response to the first terminal being faulty. Therefore, the first terminal serving as the primary terminal and the second terminal serving as the secondary terminal jointly perform data transmission with the gNB, and only a spectrum resource is occupied or a small quantity of spectrum resources are occupied. This avoids a case in which data transmission cannot be performed in response to the primary terminal device being faulty, minimizes impact of a fault of the terminal device on service continuity of the terminal device, improves reliability of the terminal device, and consumes a small quantity of spectrum resources, to help alleviate a strain on spectrum resources.
In at least one embodiment, each core network device and a base station performs some or all of steps described herein. The steps are only examples. In at least one embodiment, other steps or variations of various steps are further performed. In addition, the steps are performed in a sequence different from a sequence presented in at least one embodiment, and not all the steps are to be performed.
In at least one embodiment, unless otherwise stated or there is a logic conflict, terms and/or descriptions between different embodiments are consistent and is mutually referenced, and technical features in different embodiments is combined based on an internal logical relationship thereof, to form a new embodiment.
The foregoing mainly describes the solutions provided in at least one embodiment from a perspective of interaction between network elements and interaction between each core network device and the base station. To implement the foregoing functions, the first core network device or the base station includes corresponding hardware structures and/or software modules for performing the functions. A person skilled in the art should easily be aware that, in combination with units and algorithm steps of the examples described in embodiments disclosed in this specification, at least one embodiment is implemented by hardware or a combination of hardware and computer software. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraints of the technical solutions. A person skilled in the art is able to use different methods to implement the described functions for each particular embodiment, but the implementation does not go beyond the scope of embodiments described herein.
In at least one embodiment, the first core network device or the base station is divided into functional modules based on the foregoing method examples. For example, each functional module is obtained through division based on each corresponding function, or two or more functions is integrated into one processing module. The integrated module is implemented in a form of hardware, or is implemented in a form of a software functional module. In at least one embodiment, module division is an example, and is merely a logical function division. In actual implementation, another division manner is used.
In response to an integrated unit (module) being used,
The processing unit 701 is configured to control and manage an action of the first core network device 700 and support communication between the first core network device 700 and another network entity. For example, the processing unit 701 is configured to support the first core network device 700 in performing processes S501, S502, and S504 in
Optionally, the first core network device 700 further includes a storage unit 703, configured to store program code and/or data of the first core network device 700. Specifically, reference is made to the following descriptions:
The processing unit 701 is configured to determine that a first terminal and a second terminal are in a mutual backup relationship.
The sending unit 702 is configured to send pairing indication information to the base station, where the pairing indication information indicates that the first terminal and the second terminal are in the mutual backup relationship, so that in response to determining, based on the pairing indication information, that the first terminal is a primary terminal and the second terminal is a secondary terminal, the base station sends one copy of downlink data to the first terminal and the second terminal, or sends downlink data to the first terminal and sends the downlink data to the second terminal in response to the first terminal being faulty.
In at least one embodiment, the processing unit 701 is specifically configured to: receive registration request messages sent by the first terminal and the second terminal, where the registration request messages are used to request to connect the terminal to a core network; and after receiving the registration request information sent by the first terminal or the second terminal, obtain identification information of the second terminal or the first terminal from a second core network device, and determine, based on the identification information of the second terminal or the first terminal, that the first terminal and the second terminal are in the mutual backup relationship; after receiving the registration request information sent by the first terminal or the second terminal, obtain identification information of the second terminal or the first terminal from the registration request information sent by the first terminal or the second terminal, and determine, based on the identification information of the second terminal or the second terminal, that the first terminal and the second terminal are in the mutual backup relationship; or after receiving the registration request information sent by the first terminal or the second terminal, obtain, from an application function AF network element, identification information of terminals in the mutual backup relationship, and determine, based on the identification information of the terminals in the mutual backup relationship, that the first terminal and the second terminal are in the mutual backup relationship.
In at least one embodiment, the processing unit 701 is further configured to receive session establishment request information sent by the first terminal or the second terminal, and send the session establishment request information to a third core network device, where the session establishment request information is used to request the base station to establish, with a fourth core network device, a protocol data unit PDU session shared by the first terminal and the second terminal.
In at least one embodiment, the sending unit 702 is further configured to send association indication information to a peer application layer of the terminal, where the association indication information indicates the peer application layer to send downlink data to the first terminal and the second terminal in response to the peer application layer receiving uplink data sent by the first terminal or the second terminal, and the association indication information carries internet protocol IP addresses of the first terminal and the second terminal or IP addresses of the first terminal and the second terminal and an IP address of the peer application layer.
Operations and/or functions of the modules in the first core network device 700 are separately used to implement corresponding procedures of the methods for performing data transmission by two terminal devices shown in
In response to an integrated unit (module) being used,
Based on a same concept as the foregoing method embodiments, at least one embodiment further provides a first core network device. The first core network device includes a module/unit for performing the method embodiments of the foregoing method for performing data transmission by two terminal devices or any one of the implementations of the method embodiments. These modules/units is implemented by hardware, or is implemented by hardware by executing corresponding software.
In response to an integrated unit (module) being used,
The processing unit 903 is configured to control and manage an action of the base station 900. For example, the processing unit 903 is configured to support the base station 900 in performing the process S507 in
Optionally, the base station 900 further includes a storage unit 904, configured to store program code and/or data of the base station 900. Specifically, reference is made to the following descriptions:
The receiving unit 901 is configured to receive pairing indication information sent by a first core network device, where the pairing indication information indicates that a first terminal and a second terminal are in a mutual backup relationship.
The sending unit 902 is configured to, in response to determining, based on the pairing indication information, that the first terminal is a primary terminal and the second terminal is a secondary terminal, send one copy of downlink data to the first terminal and the second terminal, or send downlink data to the first terminal and send the downlink data to the second terminal in response to the first terminal being faulty.
In at least one embodiment, the receiving unit 901 is further configured to: receive session establishment indication information sent by a third core network device, where the session establishment indication information indicates the base station to establish, with a fourth core network device, a protocol data unit PDU session shared by the first terminal and the second terminal; and establish, with the fourth core network device, based on the session establishment indication information, the PDU session shared by the first terminal and the second terminal.
In at least one embodiment, in response to sending the copy of downlink data to the first terminal and the second terminal, the sending unit 902 is specifically configured to: send the first configuration information to the first terminal, and send a part or all of the first configuration information to the second terminal, where the first configuration information carries a group radio network temporary identifier RNTI or a security key shared by the first terminal and the second terminal.
Specific content of the security key is not limited herein in embodiments described herein. The security key is any one or more of the following: a key generated by the base station based on an identifier of the first terminal and an identifier of the second terminal; a key generated by the base station based on a random number; a key generated by the base station for the first terminal and the second terminal; or a key that is received by the base station and that is generated by the core network device based on an identifier of the first terminal and an identifier of the second terminal.
In at least one embodiment, the sending unit 902 is further configured to send first state indication information to the second terminal, where the first state indication information indicates the terminal to enter a non-working state, and the non-working state is a state in which the terminal does not send uplink data but receives downlink data, a state in which the terminal does not perform data transmission, or a state in which the terminal does not perform service data transmission but performs signaling transmission.
In at least one embodiment, the processing unit 903 is configured to determine whether the first terminal is faulty, and in response to yes, the processing unit 903 sends the first state indication information to the first terminal, and sends second state indication information to the second terminal, where the second state indication information indicates the terminal to enter a working state, and the working state is a state in which the terminal sends uplink data and receives downlink data.
In at least one embodiment, in response to determining whether the first terminal is faulty, the processing unit 903 is specifically configured to: obtain fault detection information of the first terminal, where the fault detection information carries at least one of an uplink reference signal, feedback NACK information, uplink data, and fault indication information of the first terminal, and the fault indication information indicates whether the first terminal is faulty. In response to the fault detection information not being obtained within a preset time period, the processing unit 903 determines that the first terminal is faulty. In response to the fault detection information being obtained within a preset time period, the processing unit 903 determines, based on the fault detection information, whether the first terminal is faulty.
Operations and/or functions of the modules in the base station 900 are separately used to implement corresponding procedures of the methods for performing data transmission by two terminal devices shown in
In response to an integrated unit (module) being used,
Based on a same concept as the foregoing method embodiments, at least one embodiment further provides a base station. The base station includes a module/unit for performing the method embodiments of the foregoing method for performing data transmission by two terminal devices or any one of the implementations of the method embodiments. These modules/units is implemented by hardware, or is implemented by hardware by executing corresponding software.
Based on a same concept as the foregoing method embodiments, at least one embodiment further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. In response to the computer program being run on a computer, the computer is enabled to perform the foregoing method embodiments of the method for performing data transmission by two terminal devices or any one of the implementations of the method embodiments, for example, perform any step of the embodiments of the method for performing data transmission by two terminal devices shown in
Based on a same concept as the foregoing method embodiments, at least one embodiment further provides a program product. In response to the program product being run on a computer, the computer is enabled to perform the foregoing method embodiments of the method for performing data transmission by two terminal devices or any one of the implementations of the method embodiments, for example, perform any step of the embodiments of the method for performing data transmission by two terminal devices shown in
Based on a same concept as the foregoing method embodiments, at least one embodiment further provides a chip. The chip is coupled to a memory in a first core network device or a base station, and is configured to invoke a computer program stored in the memory and perform the foregoing method embodiments of the method for performing data transmission by two terminal devices and any one of the implementations of the method embodiments, for example, perform any step of the embodiments of the method for performing data transmission by two terminal devices shown in
A processor or a processing unit (for example, the processor or the processing unit shown in
A memory or a storage unit in at least one embodiment is a volatile memory or a nonvolatile memory, or includes both a volatile memory and a nonvolatile memory. The nonvolatile memory is a read-only memory (read-only memory, ROM), a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (electrically EPROM, EEPROM), or a flash memory. The volatile memory is a random access memory (random access memory, RAM) that is used as an external cache. Through example but not limitative description, many forms of RAMs is used, for example, a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), a synchronous dynamic random access memory (synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), a synchronous link dynamic random access memory (synchlink DRAM, SLDRAM), and a direct rambus dynamic random access memory (direct rambus RAM, DR RAM). The memory in the system and method described in at least one embodiment is intended to include but is not limited to these memories and any other memories of a proper type.
Various illustrative logic units and circuits described in at least one embodiment implements or operate the described functions by using a general-purpose processor, a digital signal processor, an application-specific integrated circuit (application-specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or another programmable logic apparatus, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof. The general-purpose processor is a microprocessor. Optionally, the general-purpose processor is also any conventional processor, controller, microcontroller, or state machine. The processor is also implemented by a combination of computing apparatuses, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors with a digital signal processor core, or any other similar configuration.
Steps of the methods or algorithms described in embodiments are directly embedded into hardware, a software unit executed by a processor, or a combination thereof. The software unit is stored in a RAM, a flash memory, a ROM, an EPROM, an EEPROM, a register, a hard disk, a removable disk, a CD-ROM, or any other storage medium in the art. For example, the storage medium connects to a processor, so that the processor reads information from the storage medium and write information to the storage medium. Optionally, the storage medium is integrated into a processor. The processor and the storage medium is disposed in an ASIC. The ASIC is disposed in a communication device (such as a first core network device or a base station), for example, is disposed in different components of the communication device.
All or some of the foregoing embodiments is implemented through software, hardware, firmware, or any combination thereof. In response to software being used to implement the embodiments, all or some of the embodiments is implemented in a form of a computer program product. The computer program product includes one or more computer programs and instructions. In response to the computer programs or instructions being loaded and executed on a computer, all or some of the procedures or functions in at least one embodiment are executed. The computer is a general-purpose computer, a dedicated computer, a computer network, or another programmable apparatus. The computer programs or the instructions is stored in a computer-readable storage medium, or is transmitted through the computer-readable storage medium. The computer-readable storage medium is any usable medium accessible by a computer, or a data storage device such as a server integrating one or more usable media. The usable medium is a magnetic medium, for example, a floppy disk, a hard disk drive, or a magnetic tape; or is an optical medium, for example, a DVD; or is a semiconductor medium, for example, a solid-state drive (solid-state drive, SSD).
Embodiments described herein are described with reference to the flowcharts and/or block diagrams of the methods, the apparatuses, and the computer program product according to embodiments. Computer program instructions are used to implement each process and/or each block in the flowcharts and/or the block diagrams and a combination of a process and/or a block in the flowcharts and/or the block diagrams. These computer program instructions are provided for a general-purpose computer, a dedicated computer, an embedded processor, or a processor of another programmable data processing device to generate a machine, so that the instructions executed by a computer or the processor of the another programmable data processing device generate an apparatus for implementing a specific function in one or more procedures in the flowcharts and/or in one or more blocks in the block diagrams.
These computer program instructions are stored in a computer-readable memory that instruct the computer or any other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate an artifact that includes an instruction apparatus. The instruction apparatus implements a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.
The computer program instructions are alternatively loaded onto a computer or another programmable data processing device, so that a series of operations and steps are performed on the computer or the another programmable device, so that computer-implemented processing is generated. Therefore, the instructions executed on the computer or the another programmable device provide steps for implementing a specific function in one or more procedures in the flowcharts and/or in one or more blocks in the block diagrams.
This application is a continuation of International Application No. PCT/CN2020/119569, filed on Sep. 30, 2020, the disclosure of which is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2020/119569 | Sep 2020 | US |
| Child | 18192109 | US |
