Session establishment method and electronic device

Abstract

A session establishment method is disclosed, including: determining, by an electronic device, relay service code (RSC) information; determining, based on the RSC information, parameter information for establishing a relay session. An electronic device and a storage medium are also disclosed.

Description

[0001] This application is a divisional application of Chinese patent application No. 202080100152.2, entitled "A Session Establishment Method, Electronic Device and Storage Medium", which entered the Chinese national phase of PCT international patent application PCT / CN2020 / 106316, filed on July 31, 2020. Technical Field

[0002] This application relates to the field of wireless communication technology, and in particular to a session establishment method, an electronic device, and a storage medium. Background Technology

[0003] In relay communication, in order to address the privacy issues related to service attributes, Relay Service Code (RSC) has been introduced. However, it is not yet clear how remote devices and / or relay devices establish relay sessions based on RSC. Summary of the Invention

[0004] This application provides a session establishment method and an electronic device, which clarifies how the electronic device establishes a relay session based on RSC.

[0005] In a first aspect, embodiments of this application provide a session establishment method, including: electronic device determination code (RSC) information; and determining parameter information for establishing a relay session based on the RSC information.

[0006] Secondly, embodiments of this application provide an electronic device, the electronic terminal device including: a processing unit configured to determine RSC information and, based on the RSC information, determine parameter information for establishing a relay session.

[0007] The session establishment method and electronic device provided in this application include: the electronic device determining RSC information; and determining parameter information for establishing a relay session based on the RSC information. Thus, the implementation process for establishing a relay session after the introduction of RSC is clarified. Attached Figure Description

[0008] Figure 1 This is a schematic diagram of the relay network structure in the embodiments of this application;

[0009] Figure 2 This is a schematic diagram of the network architecture in the LTE system according to an embodiment of this application;

[0010] Figure 3 This is a schematic diagram of a relay from a relay device to a network device in an embodiment of this application;

[0011] Figure 4 This is a schematic diagram of the composition structure of the communication system according to an embodiment of this application;

[0012] Figure 5 A schematic diagram of an optional processing flow for the session establishment method provided in the embodiments of this application;

[0013] Figure 6 This is a schematic diagram of an optional component structure of an electronic device provided in an embodiment of this application;

[0014] Figure 7 This is a schematic diagram of the hardware composition structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0015] In order to gain a more detailed understanding of the features and technical content of the embodiments of this application, the implementation of the embodiments of this application will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for reference and illustration only and are not intended to limit the embodiments of this application.

[0016] Before describing the embodiments of this application, a brief explanation of the relevant content will be provided.

[0017] In Release 13 (Rel-13 ProSe), 3GPP introduced a Layer 3 relay-based UE-to-network relay function. A network architecture diagram for this relay is shown below. Figure 1 As shown, the Remote UE accesses the network through the Relay UE. The Relay UE performs the function of relaying data at the Internet Protocol (IP) layer, transmitting data between the Remote UE and the network. The Remote UE and the Relay UE are connected via a side link. Before performing relay functions, both the Remote UE and the Relay UE need to be authorized. In the Long Term Evolution (LTE) system, the network architecture is as follows: Figure 2 As shown, authorization for remote terminal devices and relay terminal devices is achieved through the PC3 interface via the relay function entity.

[0018] A diagram illustrating a relay from a relay device to a network device, such as... Figure 3As shown, in order to transmit relay data from remote devices, relay devices need to use an appropriate Protocol Data Unit (PDU) session; which PDU session to use for relay data transmission is determined by the relay device. The parameters that a relay device needs to respond to when establishing a relay PDU session are as follows: During the normal session establishment process, the relay device determines the parameters required to establish the PDU session according to the User Equipment Routing Selection Policy (URSP) configured in the network.

[0019] However, to address the privacy concerns related to service attributes, RSCs were introduced, allowing each RSC to represent a service attribute. Remote or relay devices need to be able to obtain session establishment-related parameter information from an RSC.

[0020] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), LTE system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, and Wireless Local Area Network (WLAN). Networks, WLAN, wireless fidelity (WiFi), next-generation communication systems or other communication systems, etc.

[0021] The system architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0022] The network devices involved in the embodiments of this application can be ordinary base stations (such as NodeB, eNB, or gNB), new radio controllers (NR controllers), centralized units, new wireless base stations, remote radio modules, micro base stations, relays, distributed units, transmission reception points (TRPs), transmission points (TPs), or any other devices. The embodiments of this application do not limit the specific technologies or device forms used in the network devices. For ease of description, in all embodiments of this application, the devices that provide wireless communication functions for terminal devices are collectively referred to as network devices.

[0023] In this embodiment, the terminal device can be any terminal, such as a user equipment for machine-type communication. That is, the terminal device can also be referred to as a user equipment (UE), mobile station (MS), mobile terminal, or terminal. The terminal device can communicate with one or more core networks via a radio access network (RAN). For example, the terminal device can be a mobile phone (or "cellular" phone), a computer with a mobile terminal, etc. It can also be a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device that exchanges voice and / or data with the radio access network. No specific limitations are made in this embodiment.

[0024] Optionally, network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on aircraft, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of the network devices and terminal devices.

[0025] Optionally, network devices and terminal devices, as well as terminal devices, can communicate using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication between network devices and terminal devices, as well as between terminal devices, can be conducted using spectrum below 7 gigahertz (GHz), spectrum above 7 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used between network devices and terminal devices.

[0026] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC) communication, and vehicle-to-vehicle (V2V) communication. The embodiments of this application can also be applied to these communication systems.

[0027] For example, the communication system 100 used in the embodiments of this application, such as Figure 4 As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within that coverage area. Optionally, the network device 110 may be a base station (BTS) in a GSM or CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN). Alternatively, the network device may be a mobile switching center, relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, network-side equipment in a 5G network, or network equipment in a future evolved Public Land Mobile Network (PLMN), etc.

[0028] The communication system 100 also includes at least one terminal device 120 located within the coverage area of ​​the network device 110. As used herein, "terminal device" includes, but is not limited to, devices configured to receive / transmit communication signals via wired connections, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM radio transmitters; and / or other terminal devices. Terminal devices configured to communicate via a wireless interface may be referred to as "wireless communication terminal," "wireless terminal," or "mobile terminal." Examples of mobile terminals include, but are not limited to, satellite or cellular phones; personal communications system (PCS) terminals that can combine cellular radiotelephony with data processing, fax, and data communication capabilities; PDAs that may include radiotelephones, pagers, Internet / intranet access, web browsers, notebooks, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or handheld receivers or other electronic devices that include radiotelephone transceivers. Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, terminals, wireless communication equipment, user agents, or user equipment. Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in future PLMNs, etc.

[0029] Optionally, the terminal devices 120 can communicate directly with each other via Device to Device (D2D).

[0030] Alternatively, a 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0031] Figure 4 An exemplary embodiment shows a network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0032] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.

[0033] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Figure 4 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities. This application embodiment does not limit this.

[0034] An optional processing flow of the session establishment method provided in this application embodiment is as follows: Figure 5 As shown, it includes the following steps:

[0035] Step S201: The electronic device determines the RSC information.

[0036] In step S202, the electronic device determines the parameter information used to establish a relay session based on the RSC information.

[0037] In the embodiments of this application, the electronic device can be a relay device or a remote device. Specifically, the electronic device can be a terminal device or a small base station. That is, the electronic device can be a relay terminal device, a remote terminal device, a relay small base station, or a remote small base station.

[0038] When the electronic device is a relay device, the process of determining the RSC information by the electronic device in step S201 can be as follows: during the PC5 connection establishment process, the relay device receives the RSC information sent by the remote device; wherein, the relay device and the remote device can establish a connection through a side link, that is, the relay device and the remote device transmit RSC information through the side link.

[0039] When the electronic device is a relay device or a remote device, the process of determining the parameter information for establishing a relay session based on the RSC information in step S202 is the same. This can be: the electronic device determines the parameter information for establishing a relay session corresponding to the RSC information according to pre-configured rules. The relay session parameters can include at least one or more of the following: Network Slice information, Data Network Name (DNN) information, Session Service Continuity (SSC) information, and PDU session type.

[0040] In some optional implementations, the pre-configured rules include at least one of the following: a first number of bits in the RSC information corresponding to the first network slice information in the parameter information used to establish a relay session; a second number of bits in the RSC information corresponding to the first DNN information in the parameter information used to establish a relay session; a third number of bits in the RSC information corresponding to the first SSC information in the parameter information used to establish a relay session; and a fourth number of bits in the RSC information corresponding to the first PDU session type in the parameter information used to establish a relay session. That is, each part of the bits in the RSC information corresponds to one of the parameter information used to establish a relay session. For example, the format of the RSC information is shown in Table 1 below. If the network slice corresponding to the most significant N bits in the RSC information and the DNN corresponding to the second most significant M bits in the RSC information are pre-configured, then the network slice information and the DNN information can be determined respectively based on the most significant N bits and the second most significant M bits in the RSC information.

[0041] Slice information (Nbit) DNN information (Mbit) Application Information

[0042] Table 1

[0043] The format of the RSC information is determined by the agreement, configured through the contract information, or configured by the Public Land Mobile Network (PLMN).

[0044] In some alternative implementations, the pre-configured rules include: RSC information configured in the service description information field of the URSP rule; and / or, the parameter information configured in the routing description for establishing a trunk session. That is, RSC is configured in the service description information field of the URSP rule; and / or, parameter information for establishing a trunk session is configured in the routing description.

[0045] If RSC information is configured in the URSP service description information field, the URSP rules can be modified as shown in Table 2 below. The bolded parts are the information added based on the existing URSP rules.

[0046]

[0047]

[0048] Table 2

[0049] If the parameter information for establishing a relay session is configured in the route selection description, the route selection description can be modified as shown in Table 3 below. The bolded parts are the information added based on the existing route selection description table.

[0050]

[0051]

[0052] Table 3

[0053] In some alternative implementations, if the electronic device is a remote device, after executing step S202, the electronic device may also execute:

[0054] Step S203: The electronic device sends the parameter information for establishing a relay session to the relay device.

[0055] In some embodiments, after the electronic device sends parameter information for establishing a relay session to the relay device, the relay device establishes a PDU session based on the parameter information for establishing the relay session.

[0056] The session establishment method provided in this application involves a relay device receiving RSC information sent by a remote device and determining parameter information corresponding to the RSC information for establishing a relay session according to pre-configured rules; or, after the remote device determines the parameter information corresponding to the RSC information for establishing a relay session according to pre-configured rules, the remote device sends the parameter information for establishing the relay session to the relay device. In this way, the relay device can establish a relay session based on the parameter information.

[0057] To implement the session establishment method provided in this application embodiment, this application embodiment also provides an electronic device, the composition structure of which is shown in the schematic diagram below. Figure 6 As shown, it includes:

[0058] The processing unit 601 is configured to determine RSC information and, based on the RSC information, determine parameter information for establishing a relay session.

[0059] In an optional embodiment, the processing unit 601 is configured to receive the RSC information sent by a remote device.

[0060] In an optional embodiment, the processing unit 601 is configured to receive the RSC information sent by the remote device during the PC5 connection establishment process.

[0061] In an alternative embodiment, the processing unit 601 establishes a connection with the remote device via a side link.

[0062] In an alternative embodiment, the electronic device 600 further includes:

[0063] The sending unit 602 is configured to send the parameter information used to establish a relay session to the relay device.

[0064] In an optional embodiment, the processing unit 601 is configured to determine parameter information for establishing a relay session corresponding to the RSC information according to pre-configured rules.

[0065] In one alternative implementation, the pre-configured rules include at least one of the following:

[0066] The first number of bits in the RSC information corresponds to the first network slice information in the parameter information used to establish a relay session;

[0067] The second number of bits in the RSC information corresponds to the first DNN information in the parameter information used to establish the relay session;

[0068] The third number of bits in the RSC information corresponds to the first SSC information in the parameter information used to establish a relay session;

[0069] The fourth number of bits in the RSC information corresponds to the first PDU session type in the parameter information used to establish a relay session.

[0070] In one alternative implementation, the format of the RSC information is determined by a protocol, configured through contract information, or configured by a PLMN.

[0071] In one optional implementation, the pre-configured rules include: RSC information configured in the service description information field of the user equipment routing policy rule; and / or, the parameter information configured in the routing description for establishing a relay session.

[0072] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0073] This application also provides an electronic terminal device, including a processor and a memory for storing a computer program that can run on the processor, wherein when the processor runs the computer program, it executes the steps of the session establishment method executed by the above-described electronic device.

[0074] This application also provides a chip, including: a processor, configured to call and run a computer program from a memory, causing a device equipped with the chip to execute the session establishment method executed by the aforementioned electronic device.

[0075] This application also provides a storage medium storing an executable program, which, when executed by a processor, implements the session establishment method executed by the aforementioned electronic device.

[0076] This application also provides a computer program product, including computer program instructions that cause a computer to execute the session establishment method performed by the aforementioned electronic device.

[0077] This application also provides a computer program that enables a computer to execute the session establishment method performed by the aforementioned electronic device.

[0078] Figure 7 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application. The electronic device 700 includes at least one processor 701, a memory 702, and at least one network interface 704. The various components in the electronic device 700 are coupled together through a bus system 705. It is understood that the bus system 705 is used to implement communication between these components. In addition to a data bus, the bus system 705 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 7 The general labeled all buses as Bus System 705.

[0079] It is understood that memory 702 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM). The memory 702 described in this application embodiment is intended to include, but is not limited to, these and any other suitable types of memory.

[0080] The memory 702 in this embodiment is used to store various types of data to support the operation of the electronic device 700. Examples of such data include any computer program for operation on the electronic device 700, such as application program 7022. A program implementing the method of this embodiment may be included in application program 7022.

[0081] The methods disclosed in the embodiments of this application can be applied to processor 701, or implemented by processor 701. Processor 701 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 701 or by instructions in the form of software. The processor 701 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Processor 701 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in memory 702. Processor 701 reads the information in memory 702 and combines its hardware to complete the steps of the aforementioned method.

[0082] In an exemplary embodiment, the electronic device 700 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), FPGAs, general-purpose processors, controllers, MCUs, MPUs, or other electronic components to perform the aforementioned method.

[0083] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0084] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0085] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0086] It should be understood that the terms "system" and "network" are often used interchangeably in this application. The term "and / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Furthermore, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship.

[0087] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A session establishment method, the method comprising: The relay equipment receives the relay service code (RSC) information sent by the remote equipment; Based on the RSC information, parameter information for establishing a relay session is determined. This relay session parameter information includes one or more of the following: network slice information, data network name information, session service continuity information, and protocol data unit session type. The step of determining the parameter information for establishing a relay session based on the RSC information includes: The relay device determines the parameter information for establishing a relay session corresponding to the RSC information according to the pre-configured rules.

2. The method according to claim 1, wherein, The relay device receives the RSC information sent by the remote device, including: During the PC5 connection establishment process, the relay device receives the RSC information sent by the remote device.

3. The method according to claim 1 or 2, wherein, The relay device establishes a connection with the remote device via a side link.

4. The method according to claim 1, wherein, The pre-configured rules include at least one of the following: The first number of bits in the RSC information corresponds to the first network slice information in the parameter information used to establish a relay session; The second number of bits in the RSC information corresponds to the first data network name (DNN) information in the parameter information used to establish a relay session; The third number of bits in the RSC information corresponds to the first session service continuous SSC information in the parameter information used to establish a relay session; The fourth number of bits in the RSC information corresponds to the first Protocol Data Unit (PDU) session type in the parameter information used to establish a relay session.

5. The method according to claim 4, wherein, The format of the RSC information is determined by the agreement, configured through contract information, or configured by the Public Land Mobile Network (PLMN).

6. A relay device, the relay device comprising: The processing unit is configured to receive Relay Service Code (RSC) information sent by a remote device; The processing unit is further configured to determine parameter information for establishing a relay session based on the RSC information. The parameter information of the relay session includes one or more of the following: network slice information, data network name information, session service continuity information, and protocol data unit session type. The processing unit is further configured to determine, according to pre-configured rules, parameter information for establishing a relay session corresponding to the RSC information.

7. The relay device according to claim 6, wherein, The processing unit is configured to receive the RSC information sent by the remote device during the PC5 connection establishment process.

8. The relay device according to claim 6 or 7, wherein, The processing unit establishes a connection with the remote device via a side link.

9. The relay device according to claim 6, wherein, The pre-configured rules include at least one of the following: The first number of bits in the RSC information corresponds to the first network slice information in the parameter information used to establish a relay session; The second number of bits in the RSC information corresponds to the first data network name (DNN) information in the parameter information used to establish a relay session; The third number of bits in the RSC information corresponds to the first Session Continuous Service (SSC) information in the parameter information used to establish a relay session. The fourth number of bits in the RSC information corresponds to the first PDU session type in the parameter information used to establish a relay session.

10. The relay device according to claim 9, wherein, The format of the RSC information is determined by the agreement, configured through contract information, or configured by the Public Land Mobile Network (PLMN).

11. The relay device according to claim 10, wherein, The pre-configured rules include: The RSC information configured in the service description information field of the user equipment routing policy rules; And / or, the parameter information configured in the routing description for establishing a relay session.

Images